ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

Legal

Disclaimer

ediverse.io is an independent documentation platform. This page formalises the copyright policy, editorial neutrality, source citation rules, and the takedown procedure.

Independent editorial status

ediverse.io is edited by an independent editorial collective. The site is neither sponsored, mandated, nor operated by any normative body. The trademarks mentioned — EDIFACT, UN/CEFACT, ANSI ASC X12, cXML, Ariba, SAP, OCI, OpenPEPPOL, OASIS, UBL, UNECE — belong to their respective holders. Their citation falls under fair-use rights for documentary and educational purposes.

No contractual relationship exists between ediverse.io and those bodies. Use of the marks is limited to identifying the subject discussed and implies no approval, agreement, certification, or endorsement on the part of their holders.

Vendor neutrality

Vendor, platform, and tooling comparisons published on ediverse follow strict neutrality. No ranking is conditioned by financial consideration. Affiliate links, where they exist, are clearly disclosed on the page concerned. The editorial team reserves the right to decline any sponsored-placement proposal.

Editorial coverage on ediverse respects the legal nature of every source. Three regimes coexist:

  • Open specifications (UN/EDIFACT directories, OASIS UBL, OpenPEPPOL BIS, IETF RFCs): reproduced in full or in summary, with attribution, under the original licence of the source. UNECE directories are public; IETF RFCs are governed by BCP 78.
  • Restricted public specifications (ANSI ASC X12 public index, SAP OCI reference PDFs): only the information made public by the publisher is cited. The detail of X12 Implementation Guides (TR3), accessible only by subscription, is never republished.
  • Paid proprietary specifications (ISO 9735, derived ISO norms): coverage is limited to the conceptual level. Formal definitions, normative tables, and annexes are not reproduced. Published examples are original didactic illustrations written by the editorial team.

The editorial content native to ediverse — explanations, diagrams, original didactic examples — is published under an open licence permitting reuse with attribution. The applicable licence is specified page by page when it differs from the site default.

Source policy

Every technical fact cited on ediverse is tied to a primary source archived in the site repository (content/_sources/). Sources fall into the following groups:

  • UN/EDIFACT directories from UNECE (versions D.96A, D.01B, D.16B, D.21B, D.24B);
  • cXML 1.2 DTDs published by Ariba / SAP Business Network;
  • X12 public index published on x12.org;
  • SAP Open Catalog Interface reference documents (OCI 4 and OCI 5);
  • OASIS UBL 2.1 and OpenPEPPOL BIS Billing 3.0 profiles;
  • IETF RFCs AS1 (RFC 3335), AS2 (RFC 4130), OFTP2 (RFC 5024).

When a source is updated by its publisher, ediverse updates the corresponding page within a reasonable timeframe. The last-updated date is shown in the footer of each article.

Limitation of liability

The information published on ediverse is provided for informational purposes. Despite the care taken in verification and sourcing, readers remain responsible for validating any information against their own operational use. Real EDI implementations depend on contractual parameters (industry subset, trading partner, directory version) that no generalist documentation can cover exhaustively. No warranty of accuracy, completeness, or fitness for a particular purpose is given.

The interactive tools published on ediverse (validators, parsers) run in the reader's browser. They are provided as-is and do not replace a syntactic or semantic audit performed as part of a production integration.

Takedown procedure

Any rights holder considering that an ediverse page infringes their intellectual property rights may submit a motivated request to contact@ediverse.io. The request must identify the content concerned (URL), specify the nature of the right invoked (copyright, trademark, trade secret), and provide the identity of the requester.

The editorial team commits to examining any good-faith request within a useful timeframe, to removing the disputed content as a precautionary measure when the request is manifestly grounded, and to publishing a transparency note recording the removal without disclosing the requester's identity absent consent.

Contact

For any question relating to this page: contact@ediverse.io. Other contact channels are described on the Contribute page.