BDNDR 1.1CSD02, 1.2, or 2.0?

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

Fellow UBL NDRSC members,

January 11, 2017 is when we published the latest BDNDR:

http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/csprd01/Business-Document-NDR-v1.1-csprd01.html

We never finalized 1.1 as it was the first BDNDR with JSON and we 
never finalized our JSON format. So we still do not have a Committee 
Specification, let alone an OASIS Standard.

Based on our latest NDR call, we are going ahead with a change in the 
JSON format that is not backward compatible with CSPRD01.

Personally, I have no problems making the change in 1.1 CSD02WD01 
since 1.1 was never an OASIS Standard. We abandon the CS01 track and 
start a CS02 track.

Does anyone on the subcommittee think this is inappropriate? If so, 
should this be a 1.2 or a 2.0 instead?

Please speak up promptly, as I'm working on the documentation 
already. It isn't a big change, but it will take time to undo the few 
things I have to do to set up a CS02 track.

BTW, there are only four open NDR items in JIRA. Does anyone see 
anything that is missing?

All:
https://issues.oasis-open.org/browse/UBL-273?filter=13472

Open and applied:
https://issues.oasis-open.org/browse/UBL-273?filter=13472&jql=project%20%3D%20UBL%20AND%20status%20in%20(Open%2C%20Applied)%20AND%20resolution%20in%20(Unresolved%2C%20Fixed%2C%20%22Won%27t%20Fix%22%2C%20Duplicate%2C%20Incomplete%2C%20%22Cannot%20Reproduce%22%2C%20Applied%2C%20%22No%20Action%22%2C%20Invalid%2C%20Later)%20AND%20component%20%3D%20%22Naming%20and%20Design%20Rules%20(NDR)%22%20ORDER%20BY%20status%20ASC%2C%20resolution%20DESC%2C%20key%20DESC

Thanks!

. . . . . . 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$45 (5 hours free) |
Essays (UBL, XML, etc.) http://www.linkedin.com/today/author/gkholman |