xml2edi(1)
NAME
xml2edi - translate XML messages back to UN/EDIFACT
SYNOPSIS
xml2edi [-i] [-x extension] filename.xml > filename.edi
DESCRIPTION
xml2edi is able to translate those XML messages to XML,
which conforms to the semantic translation of UN/EDIFACT
to XML. This semantic translation is currently
static-coded. And no external entities are used. Version
0.5 will provide more freedom in XML to UN/EDIFACT trans
lation by using RDF for semantic mapping.
- -i When reading UN/EDIFACT on a screen, I prefer a new
- line as an advice segment seperator. Some UN/EDIFACT parsers may not like this, so it's optional.
- -x The 0.34 version provided an initial way to use names
- pace migration for code list extensions. This way is
still crude and not XML/RDF. For patching an exten
sion SDBM into edi2xml, use the -x switch without the
trailing .dir/.pag. - filename.xml
- XML files have to contain documents of namespace:mes
sage type, where namespace is either the default edi
fact or matched by the extension SDBM. Future versions
from 0.7x up will focus on orders, invoices and so on.
Current translation is flat and ignores the TRED/EDMD documents.
BUGS
Most bugs might better be called not yet implemented, e.g.
missing external RDF files, as can be seen in the Roadmap
section of the README file, but the existing code has cer
tainly many others. Drop me a note, if you find some mis
behavior.
I call XML::Edifact an aproach towards XML/EDI as a proto
type in Perl. Nothing is carved in stone, but should be
seen as painted on wood with the coal from fire, intended
to be thrown into the fire to provide fuel for the
release. So drop me a note, if you think something should
be changed.
SEE ALSO
XML::Edifact XML::Parser.
For further study, browse at http://www.unece.org/trade/, http://www.unece.org/trade/untdid/download/d99a.zip, http://www.w3.org/TR/REC-xml, http://www.xmledi.org/ and http://www.xml-edifact.org/.
AUTHOR
- Kraehe@Copyleft.de - Michael Koehne - MK25-RIPE