New rules for JSON syntax - review ends October 22nd
We are pleased to announce that Business Document Naming and Design Rules (BDNDR) Version 1.1 from the UBL TC  is now available for public review and comment. This is the third public review for BDNDR v1.1.
An important and powerful method to design interoperable business documents is to construct logical semantic models using concepts described in the UN/CEFACT Core Components Technical Specification (CCTS) Version 2.01. From these semantic models one can create physical syntax models with which to express the content constraints of actual business documents to be interchanged.
The OASIS Business Document Naming and Design Rules (BDNDR) Version 1.1 Draft Specification prescribes a set of naming and design rules used to create complete CCTS models of interoperable business documents. It also includes the rules needed to create validation artefacts corresponding to them. For XML syntax, the rules govern creating W3C Schema (XSD) and OASIS Context/value Association (CVA) validation artefacts. For JSON syntax, the rules govern creating JSON Schema validation artefacts.
BDNDR Version 1.1 changes no rules for XML syntax from BDNDR Version 1.0 and only adds the new rules prescribed for JSON syntax.
The specification documents and related files are available here:
Business Document Naming and Design Rules (BDNDR) Version 1.1
Committee Specification Draft 04
08 September 2021
Editable source (Authoritative):
For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file at:
How to Provide Feedback
OASIS and the UBL TC value your feedback. We solicit feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.
This public review starts 08 October 2021 at 00:00 UTC and ends 22 October 2021 at 11:59 UTC.
This specification was previously submitted for public review . This 15-day review may be limited in scope to changes made from the previous review. Changes are described in the previous comment resolution log  and highlighted in a red-lined file included in the package .
Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ubl).
Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:
All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with the public review of this work, we call your attention to the OASIS IPR Policy  applicable especially  to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.
OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.
Additional information about this specification and the UBL TC may be found on the TC’s public home page .
 OASIS Universal Business Language (UBL) TC
 ÂPrevious public reviews and comment resolution logs:
– Please see the “Timeline Summary” in the public review metadata document at: