XSD
OASIS · 2.1
UBL 2.1 Application Response
A generic UBL response to another document: received, accepted, rejected, with reasons.
About
Peppol uses the Application Response document for its Invoice Response, Catalogue Response and Message Level Response transactions.
Good to know
- This entry checks the schema only; for the Peppol rules, choose the matching Peppol response.
- OASIS ships no Application Response sample for UBL 2.1; the example is the Peppol Invoice Response one.
Files
14 files · 2.7 MB-
maindoc/UBL-ApplicationResponse-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
InvoiceResponse_Example.xml · 2.5 KB · valid against this schema
In CI and from code
The same schema by its name, ubl-2.1-application-response, through the API.
npx @xmlvalid/cli validate "**/*.xml" --schema ubl-2.1-application-response
- uses: xmlvalid/validate-action@v1
with:
files: "**/*.xml"
schema: ubl-2.1-application-response
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-application-response
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