OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ubl-comment] Invitation to comment on Universal Business Language v2.3 from the UBL TC - ends September 2nd

There are still problems with the examples.  Two of them will not load with schema validation.


1) UBL-GoodsCertificate-2.3-Example.xml


lineNumber: 299; columnNumber: 29; cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2":AcceptanceIndicator}'. One of '{"urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2":Description, "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2":Note, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":ValidityPeriod, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":IssuerParty}' is expected.


2) UBL-GoodsItemPassport-2.3-ExampleIssued.xml


lineNumber: 6; columnNumber: 18; cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2":StatusCode}'. One of '{"urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2":IssueTime, "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2":Note, "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2":VersionID, "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2":ExportReasonCode, "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2":ExportReason, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":ValidityPeriod, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":IssuerParty, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":HolderParty}' is expected.


The final problem, and much the most serious, is with PriorInformationNotice.  I think I raised this before, but I think it is worth revisiting.


 In all other root documents, the ID field is mandatory.  Here it is optional.  Without an ID you can not create a DocumentReference, and thus ApplicationResponse, DocumentStatus and DocumentStatusRequest are all useless.

I realise that this is an old (pre-2.30) document, but at least can we have a note somewhere that says that this field should be present even if formally it is not required.  I only noticed this because the I have a base class for all my UBL objects, and this is passed into the constructor for DocumentReference objects - I then strip the fields in this base class from each object and include them by inheritance.  So the two examples pass schema validation, but my code will not load them as the base class has them as required.


At the very least there needs to be a note in the documentation saying that if you do not provide an ID then DocumentReferences, ApplicationResponses, DocumentStatuses and DocumentStatusRequests will not be able to be generated and so an ID should be provided.  I could make ID optional in my base class, and simply not generate a DocumentReference if no ID is present, and use the schema to ensure that ID is present where needed, but its absence renders the object so useless I am minded to leave it as it (i.e. mandatory) and to reject any incoming object which leaves it out.




On Wednesday, 19 August 2020 03:54:46 BST Paul Knight wrote:


OASIS Members and other interested parties,


We are pleased to announce that Universal Business Language Version 2.3 from the UBL TC [1] is now available for public review and comment. This is the third public review for Universal Business Language v2.3.


UBL is the leading interchange format for business documents. It is designed to operate within a standard business framework such as ISO/IEC 15000 (ebXML) to provide a complete, standards-based infrastructure that can extend the benefits of existing EDI systems to businesses of all sizes. The European Commission has declared UBL officially eligible for referencing in tenders from public administrations, and in 2015 UBL was approved as ISO/IEC 19845:2015.


Specifically, UBL provides:

 - A suite of structured business objects and their associated semantics expressed as reusable data components and common business documents.

 - A library of schemas for reusable data components such as Address, Item, and Payment, the common data elements of everyday business documents.

 - A set of schemas for common business documents such as Order, Despatch Advice, and Invoice that are constructed from the UBL library components and can be used in generic procurement and transportation contexts.


UBL v2.3 is a minor revision to v2.2 that preserves backwards compatibility with previous v2.# versions. It adds five new document types, bringing the total number of UBL business documents to 86.


The specification documents and related files are available here:


Universal Business Language Version 2.3

 Committee Specification Draft 03

 29 July 2020


Editable source (Authoritative):














Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:










Paul Knight....Document Process Analyst

OASIS - Advancing open standards for the information society


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]