Another note on this idea, not all XML files are tabular, so an XML file may not contain a clearly defined set of rows/columns.

You can think of this as a visual way of building up the equivalent XSL translation used to convert from one schema to the Visokio XML data schema.

We would like to submit IATA industry standard schema file for use in testing

I would like to ask if there is any prospect of an XML import wizard?

The difficulty is XML is a very flexible and hierarchical format, and one document's solution might not work for another's.

If you're still talking about the invoice XML above, for example, this is highly hierarchical. In this case what node in the XML would constitute a record in the output? How would attributes and body text of child nodes be handled?

We're considering a solution which can be entirely automatic without configuration, where each terminating XML node (a node without children) results in a single record, and all attributes of all parent nodes are repeated for every record.

In this case that wouldn't work very well, since InvoiceIDVATRegistrationNumber and InvoiceIDName1 would result in separate records.

You could then configure what node level constituted a record, e.g. Invoice. But this would then need to deal with flattening multiple children (InvoiceHeader, InvoiceIDDetails) into a single record cell for each invoice field.

But the principle of our current planned automatic solution is to convert the data into tabular form in a consistently reproducible way; you could then use other operations to restructure the data appropriately.

Currently you have to write an XSL transformation file, which is the most flexible way of dealing with an arbitrary schema.

Thanks for explaining this.

It would still be exceptionally helpful if an XML wizard were available to assist in defining the record start/end nodes and other hierarchy nodes. In effect to build an XSL file with the assistance of a wizard. I have no idea whether this might be possible since I am not really familiar with the complexities of XML schema.