XSD
OASIS · 2.1
UBL 2.1 Order
A purchase order in UBL 2.1, the syntax of Peppol ordering and many e-procurement platforms.
About
The Order document lists what a buyer wants to buy, from whom, at what price and where it should be delivered.
Good to know
- This entry checks the schema only. To check a Peppol order against its business rules as well, choose Peppol Order.
- The example is the order sample from the OASIS UBL 2.1 distribution.
Files
14 files · 2.7 MB-
maindoc/UBL-Order-2.1.xsd main
-
common/UBL-CommonAggregateComponents-2.1.xsd
-
common/UBL-CommonBasicComponents-2.1.xsd
-
common/UBL-CommonExtensionComponents-2.1.xsd
-
common/UBL-QualifiedDataTypes-2.1.xsd
-
common/UBL-UnqualifiedDataTypes-2.1.xsd
-
common/UBL-ExtensionContentDataType-2.1.xsd
-
common/CCTS_CCT_SchemaModule-2.1.xsd
-
common/UBL-CommonSignatureComponents-2.1.xsd
-
common/UBL-SignatureAggregateComponents-2.1.xsd
-
common/UBL-SignatureBasicComponents-2.1.xsd
-
common/UBL-xmldsig-core-schema-2.1.xsd
-
common/UBL-XAdESv132-2.1.xsd
-
common/UBL-XAdESv141-2.1.xsd
The validator loads all of these with their folder structure, so includes and imports resolve as published.
Example document
UBL-Order-2.1-Example.xml · 13.6 KB · valid against this schema
In CI and from code
The same schema by its name, ubl-2.1-order, through the API.
npx @xmlvalid/cli validate "**/*.xml" --schema ubl-2.1-order
- uses: xmlvalid/validate-action@v1
with:
files: "**/*.xml"
schema: ubl-2.1-order
api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
-H "Authorization: Bearer $XMLVALID_API_KEY" \
-F document={{ $schema->example ?? 'document.xml' }} -F schema=ubl-2.1-order
Free accounts get 100 API validations a month. On Pro, a URL monitor can check a published document against this schema every hour and email you when it breaks. More CI setups