# XML-Edifact

## Research Papers

- release Notes
- RDF and XML-Edifact namespaces
- Note to the W3C

## XML-Edifact - Document Type Definition

- edifact03.dtd

## Example Files

The first 3 messages are from the book publishing order chain. EDItUER are old orders designed by the Library in Frankfurt, Springer provided an invoice. And TeleOrdering as one of the major Value Added Network in this bussiness send me a rather large message also about ORDERs but using less code list extensions than the academic EDItUER example. All of those messages will fail with a validating parser, because of "unknown:code".

- [ EDI ] [ XML ] EDItEUR
- [ EDI ] [ XML ] Springer Verlag
- [ EDI ] [ XML ] TeleOrdering

The next two messages came from ETIS, and even if they dont look so - they are normal phon bills.

- [ EDI ] [ XML ] ELFE
- [ EDI ] [ XML ] EVA

The last messages are experiments. XML::Edifact is able to translate any well formed UN/EDIFACT into XML. Those messages here are just message fragments.

- [ EDI ] [ XML ] Linux
- [ EDI ] [ XML ] Buyer
- [ EDI ] [ XML ] ISBN