XML to CSV Conversion Is a Flattening Problem (And It Is Harder Than It Looks)

XML is hierarchical. CSV is flat. Converting between them requires making decisions about how to collapse a tree structure into rows and columns. These decisions are not obvious, and different tools make different choices, which is why the "same" conversion can produce wildly different CSV outputs. The simple case <users> <user> <name> Alice </name> <email> alice@example.com </email> <age> 30 </age> </user> <user> <name> Bob </name> <email> bob@example.com </email> <age> 25 </age> </user> </users> This maps cleanly to CSV: name,email,age Alice,alice@example.com,30 Bob,bob@example.com,25 Each <user> element becomes a row. Each child element becomes a column. Simple. But real-world XML is rarely this clean. Nested elements <user> <name> Alice </name> <address> <street> 123 Main St </street> <city> Springfield </city> <state> IL </state> </address> </user> How do you flatten the nested <address> ? Options: Dot notation columns: address.street , address.city , address.state . This preserve