Permit DFDL Editor to automatically create field names based on a sample file - eg CSV #EMEA #uki

We're talking Build time, within the IIB Toolkit's DFDL Editor.

At the moment, when one starts to build a new Message Model (schema) for CSV data, the wizard lets one define the EndOfRecord character(s) and the number of fields, as well as whether the first record/row is a Header or not. It then creates a schema in which it assigns the *NAMES* of the elements as fieldnnnn (field1, field2 ... field10, field11... field100, field101 ... etc).

This is all very well and works. But the names fieldnnnn are not very friendly. It means that when using the Mapping node, it is difficult and cumbersome to work out which elements one should be mapping to/from. This is particularly the case for customers with very wide CSV files (by which I mean 100 columns or more).

In nearly all cases that I have come across, these customers' CSV files *DO* use record/row 1 as a Header, and in that Header are the names of all the fields/columns. So the customer has quite reasonably asked "if these field names already exist in an example CSV file, can the DFDL editor analyse that example CSV file and create nicer field names ?".

So, technically, the requirement is for the DFDL editor to be able to analyse an example data file at Buildtime, and to extract data from that example data file when creating the schema. In this particular case, I want the DFDL editor to extract the column/field names from the first row/record of a CSV file, and then make a stab at creating element names based thereon.