The open business-document reference.

Reference pages for the documents supply chains actually trade — the despatch advice, the purchase order — written to be the working answer, and licensed so they can stay public.

Why the depth differs by syntax.

This section has a two-depth law, and it is a licensing fact stated as policy, not an editorial accident:

• EDIFACT and EANCOM pages go dictionary-deep. UNECE publishes the UN/EDIFACT directories (UNTDID) openly, and GS1 publishes the EANCOM message documentation freely on gs1.org. The directories this section rules against are vendored whole and sha256-pinned, file by file, in a provenance ledger whose pins change only by journaled human ruling — the same discipline as the conformance pins. Each reference page names the directory release it is written against.
• X12 pages stay original-prose. X12's copyright bars republishing segment and element detail, so no X12 dictionary content appears anywhere on this site — no segment tables, no element lists, no spec text. Structure is explained in our own words, our mapping tables are our own work, and for element-level detail every X12 page deep-links Stedi's X12 reference — live, free, and the best public X12 reference there is. Credit where it is due; copying nowhere.

The pages.

Each page is three things at once: the message anatomy in original prose, a worked wire example we authored (the same fixture lives in the golden corpus, so the page and the test suite cannot drift apart), and the mapping table onto EPCIS 2.0 events — the four spec-sanctioned joins that land document context in core event fields.

Sources.

• UN/EDIFACT directories (UNTDID): published by UNECE at service.unece.org/trade/untdid — the D.96A and D.01B releases are the ones EANCOM 2002 rides on.
• EANCOM message documentation: published by GS1 at gs1.org (the EANCOM 2002 DESADV specification is a freely downloadable PDF).
• CBV 2.0 and EPCIS 2.0: published by GS1 at ref.gs1.org; vendored and pinned on the conformance page.
• X12 element detail: Stedi's X12 reference, credited as the canonical public X12 reference. Linked, never copied.

The door these pages feed is the business-transaction layer: parse the document, validate it, acknowledge it, and land its references on events.