C
Casper B
If I have 3-4 specific ASCII/non-XML vendor-specific data-sheets,
forming tables of simple types (int, float, string) with space as
delimiter. The data is simple (from a grammar point of view) yet not as
simple as a 2D-array/recordset. Example:
1234567894 00000100 50 10400
01330002 003 0000213337 10400
01330025 002 0000066887 10400
01330027 000 0000033841 10400
01330029 001 0000061182 10400
01330030 004 0000047411 10400
9999999998 0001165422- 10400
1234567894 00000100 50 10400
01330003 001 0000033671- 10400
01330004 001 0000116653- 10400
....looped data!
Normally I would parse this and do transformation using a
Compiler-Compiler. This is however, a very static approach (new format
would require recompilation etc) and certainly not suited for database
integration.
Can I somehow use XML or any features hereof (DTD, Xpath...) to
parse/validate vendor-specific ASCII/non-XML data-sheets and transform
this into a standard XML format.
The goal is of course, to be able to receive vendor-data in a new
propriatary ASCII format and still be able to read the data provided an
associated grammar has been created for this new format. Unfortunately I
have no way of requireing the vendor to provide/follow a schema/XML
format.
Thanks in advance for any feedback!
Casper Bang
forming tables of simple types (int, float, string) with space as
delimiter. The data is simple (from a grammar point of view) yet not as
simple as a 2D-array/recordset. Example:
1234567894 00000100 50 10400
01330002 003 0000213337 10400
01330025 002 0000066887 10400
01330027 000 0000033841 10400
01330029 001 0000061182 10400
01330030 004 0000047411 10400
9999999998 0001165422- 10400
1234567894 00000100 50 10400
01330003 001 0000033671- 10400
01330004 001 0000116653- 10400
....looped data!
Normally I would parse this and do transformation using a
Compiler-Compiler. This is however, a very static approach (new format
would require recompilation etc) and certainly not suited for database
integration.
Can I somehow use XML or any features hereof (DTD, Xpath...) to
parse/validate vendor-specific ASCII/non-XML data-sheets and transform
this into a standard XML format.
The goal is of course, to be able to receive vendor-data in a new
propriatary ASCII format and still be able to read the data provided an
associated grammar has been created for this new format. Unfortunately I
have no way of requireing the vendor to provide/follow a schema/XML
format.
Thanks in advance for any feedback!
Casper Bang