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: UBL 2.1 JSON Alternate Representation v1.0 and Business Document Naming and Design Rules v1.1 start public review - ends April 1st

OASIS members and other interested parties, 

The OASIS Universal Business Language TC [1] members have recently approved two Committee Drafts and submitted them for 60 day public review:

Business Document Naming and Design Rules Version 1.1
Committee Specification Draft 01 / Public Review Draft 01
11 January 2017


UBL 2.1 JSON Alternative Representation Version 1.0
Committee Note Draft 01 / Public Review Draft 01
11 January 2017


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.

JSON is the _javascript_ Object Notation described by ISO/IEC 21778 Information technology — The JSON data interchange format, initially published at https://www.ecma-international.org/publications/standards/Ecma-404.htm as ECMA 404 The JSON data interchange format.  JSON Schema is the vocabulary described at http://json-schema.org for annotating and validating JSON documents.

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 UBL 2.1 JSON Alternative Representation Version 1.0 Draft Note engages the JSON rules from BDNDR and publishes the CCTS models of UBL 2.1 as json-schema.org validation artefacts.  Also included in the package is a transliteration into JSON syntax of each of the UBL 2.1 sample XML instances, all of which validate with the provided JSON schemas.

These two work products are being published simultaneously for reviewers to work with a complete implementation of the proposed new rules for JSON serialization of CCTS document models.  The OASIS UBL TC welcomes formal feedback of this new approach to working with JSON syntax.  Please use the https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ubl
comment list to do so.

Public Review Period:

The public review starts 01 February 2017 at 00:00 UTC and ends 01 April 2017 at 23:59 UTC. 

This is an open invitation to comment. OASIS solicits 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.


The prose specification document and related files are available here:

- Business Document Naming and Design Rules Version 1.1

Editable source (Authoritative): 



- UBL 2.1 JSON Alternative Representation Version 1.0

Editable source (Authoritative): 



ZIP distribution file (complete):

For your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:

- Business Document Naming and Design Rules Version 1.1:

- UBL 2.1 JSON Alternative Representation Version 1.0: 

Additional information about the specification and the UBL can be found at the TC's public home page:


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, or directly at:


Comments submitted by TC non-members for this work and for other work of this TC are 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 this public review of "Business Document Naming and Design Rules Version 1.1" and "UBL 2.1 JSON Alternative Representation Version 1.0", we call your attention to the OASIS IPR Policy [2] applicable especially [3] 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 references:

[1] OASIS Universal Business Language TC

[2] http://www.oasis-open.org/who/intellectualproperty.php

[3] http://www.oasis-open.org/committees/ubl/ipr.php
RF on Limited Terms Mode


Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

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