Validation Specification

The validation specification defines a standard for the validation of UBL XML instances at three levels:

  • Structure : that the XML instance conforms to the corresponding XSD schema
  • Codes : that the code values used in the XML instance are defined in a relevant code-list, which may be either a core code-list or a context specific code list.
  • Rules : that the XML instance complies with the specific business rules for the implementation context identified by the "ProfileID" element in the XML instance.

The following standards are used there:

Oasis Code List Representation (Genericode) Version 1.0

Context/value association using genericode 1.0

ISO Schematron

The XML instances MUST comply with the UBL 2.1 Specification.

Validation Context

As defined by the UBL Customisation Guide and as implemented by the DBC, UBL allows for the notions of "CustomizationID" and "ProfileID" that are used to define addiotnal restrictions or rules that apply in a specific geographic or industry or porcess context. In general, the "CustomizationID" represents a broad context whilst "ProfileID" reflects further restrictions within that broad context. The Ausdigital.org suite of semantic specifications uses these two identifiers as follows:

  • There is one "CustomizationID" value that indicates the Australian Digitial Business Council restrictions on the global UBL documents. The set of DBC restrictions is evident when comparing the DBC CoreInvoice Schema with the equivalent global UBL 2.1 Invoice Schema.
  • There are a number of "ProfileID" values that represent the rules that apply when the core invoice is used in specific business processes such as RCTI, TaXReceipt, CreditNote, etc. The rules are defined with each semantic specification (eg billing semantics

All validation rules are tagged with the relevant customizationID(s) and profileID(s) that apply. Each instance document also contains both these identifiers. Therefore the validation model is to examine the instance document to determine which validation rules should be applied.