Latest working drafts of proposed NDR documents

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

Fellow UBL TC members,

Many weeks ago we decided that a single JSON serialization was 
insufficient and that there should be three distinct JSON 
serialization options for UBL users.

Two of those three require JSON schemas for those who choose to 
validate their JSON instances.

(Finally!) I have updated the Business Document Naming and Design 
Rules (BDNDR) standard to incorporate descriptions of the three and 
rules for the generation of the two types of schema. I have also 
created the three pairs of schemas, themselves, in revisions to the 
committee notes.

I think the following working draft documents are ready to be made 
into committee drafts, but I need help reviewing them because I've 
been staring at these too long. The three notes are practically 
identical, but I had to make distinctions for the versions. The 
standard has the new text and the new changes to the rules to 
accommodate synthesizing the two kinds of schemas.

BD-NDR 1.1
https://www.oasis-open.org/committees/document.php?document_id=68916

UBL 2.1 JSON 2.0
https://www.oasis-open.org/committees/document.php?document_id=68917

UBL 2.2 JSON 1.0
https://www.oasis-open.org/committees/document.php?document_id=68918

UBL 2.3 JSON 1.0
https://www.oasis-open.org/committees/document.php?document_id=68919

If these working drafts are acceptable, then I will create committee 
drafts for us to vote on.

BTW, the UBL production incorporates the latest code and so follows 
the new rules when generating artefacts.

Thank you for any time you can find to review what I've prepared 
here. I apologize for how long it has taken to get to this point.

. . . . . . . . Ken


--
Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/o/ |
Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training class @US$125 (5 hours free) |
Essays (UBL, XML, etc.) http://www.linkedin.com/today/author/gkholman |