Thank you, again, Paul, for this feedback.

At 2021-12-14 17:42 -0500, Paul Knight wrote:

If some changes for the CN01 documents can be accommodated (I seem to remember there might be some obstacle� with� part of this, due to the DocBook dependency - ?), I hope you can make these changes (in each document set):

Thankfully, there are no dependencies on the DocBook stylesheets. The templates are boilerplate that initiate a document and are not "live" links that are automatically updated. So I'm making changes to the initial templates for a couple of these.

• In "Notices", set the latest copyright year to 2021.

Not a problem ... I was missing an entity reference.

• In Section 1.3 References (present in all three Notes) - the link for [ISO 21778 - ECMA JSON] gets redirected to https://www.ecma-international.org/publications-and-standards/standards/ecma-404/. This link should be used in future publications if possible. (instead of current http://www.ecma-international.org/publications/standards/Ecma-404.htm).

Easy change. Gosh, but having a standard numbered "404" feels like it is just destined to be problematic!

(Maybe part of this one is tied up in the current DocBook template?) If possible, please change "version" to "stage" in four places:

• in "Related work" for [BDNDR] - Latest version --> Latest stage
• in the first paragraph of "Status" - Latest version --> Latest stage
• in "Citation format"�  - Latest version --> Latest stage
• in Section� 1.3 References -�  for [BDNDR] - Latest version --> Latest stage

https://issues.oasis-open.org/browse/DSSD-15

One last minor item - due to the redesign of the OASIS website, most links to items there (www.oasis-open.org) now have a terminating slash. This occurs only once in the Notes - in the "Notices" section, there is a hyperlink under "Policy" which should be "https://www.oasis-open.org/policies-guidelines/ipr/". [This last item comes more into play for standards-track documents, where there are five or six similar changes... hope this can be incorporated into the DocBook templates with their next revision.]

https://issues.oasis-open.org/browse/DSSD-14

Thanks and best regards,

Thank you, as always!

Here are the documents that (I hope!) address all of your comments:

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

Getting started on this.

Downloaded https://www.oasis-open.org/committees/document.php?document_id=69437

• UBL-2.2-JSON-v1.0-cn01-20211215-215510z.zip
• No issues noted in first review.

Prepared and installed files for staging review:

• prepared files with timestamps, ZIP, and manifest in personal directory
• UBL staging directory in place already
• created stage directory [typically ".../ztest/TCName/WorkProductAbbreviation/VersionNumber/Stage"]
• copied files into stage directory
• updated existing symlinks
• installed README warning file
• set timestamps for directory and symlinks, also for version directory.
• checked installation

Will request internal OASIS staff staging review along with other two UBL JSON CN01 publications.

[skipped staging review]

Promoted to docs.oasis-open.org

• Synced files from /ztest to canonical directory (/htdocs)
• Synced to OASIS Library (docs.oasis-open.org)
• checked links, etc.
• requested sanity check:

Please review the OASIS Library installation of these THREE UBL-JSON committee Notes.

Since there are minimal changes from the recent CND02 publications, I've skipped the staging review - so this is the final review before release. I did not find any issues with the documents.

The files are:

UBL 2.1 JSON Alternative Representation Version 2.0
Committee Note 01
01 December 2021

https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/UBL-2.1-JSON-v2.0-cn01.html
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/UBL-2.1-JSON-v2.0-cn01.pdf
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/UBL-2.1-JSON-v2.0-cn01.xml
JSON legacy examples: https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/json-legacy/
JSON model examples: https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/json-model/
JSON legacy schemas: https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/json-schema-legacy/
JSON model schemas: https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/json-schema-model/
Validation test environment: https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/val/

Please add comments to https://issues.oasis-open.org/browse/TCADMIN-4128.
****************************

UBL 2.2 JSON Alternative Representation Version 1.0
Committee Note 01
01 December 2021

https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/UBL-2.2-JSON-v1.0-cn01.html
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/UBL-2.2-JSON-v1.0-cn01.pdf
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/UBL-2.2-JSON-v1.0-cn01.xml
JSON legacy examples: https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-legacy/
JSON model examples: https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-model/
JSON legacy schemas: https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-schema-legacy/
JSON model schemas: https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-schema-model/
Validation test environment: https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/val/

Please add comments to https://issues.oasis-open.org/browse/TCADMIN-4126.
****************************

UBL 2.3 JSON Alternative Representation Version 1.0
Committee Note 01
01 December 2021

https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/UBL-2.3-JSON-v1.0-cn01.html
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/UBL-2.3-JSON-v1.0-cn01.pdf
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/UBL-2.3-JSON-v1.0-cn01.xml
JSON legacy examples: https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/json-legacy/
JSON model examples: https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/json-model/
JSON legacy schemas: https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/json-schema-legacy/
JSON model schemas: https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/json-schema-model/
Validation test environment: https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/val/

Please add comments to https://issues.oasis-open.org/browse/TCADMIN-4127.

All good. I approve to release.

Prepared files for announcements

• Removed README warning file and reset directory timestamp in canonical directory on staging server.
• synced to OASIS Library (docs.oasis-open.org)
• Installed link document in TC's Kavi repository, in "Approved Work Products":

**********
Document Name: UBL 2.2 JSON Representation v1.0 CN01
Description
This document is a link to https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/UBL-2.2-JSON-v1.0-cn01.html
CN01:

UBL 2.2 JSON Alternative Representation Version 1.0
Committee Note 01
01 December 2021

https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/UBL-2.2-JSON-v1.0-cn01.html
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/UBL-2.2-JSON-v1.0-cn01.pdf
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/UBL-2.2-JSON-v1.0-cn01.xml
JSON legacy examples:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-legacy/
JSON model examples:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-model/
JSON legacy schemas:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-schema-legacy/
JSON model schemas:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-schema-model/
Validation test environment:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/val/

Submitter: Paul Knight
Technical Contact: Mr. Kenneth Bengtsson
Group: OASIS Universal Business Language (UBL) TC
Folder: Approved Work Products
Date submitted: 2021-12-01 13:05:26
*********

• Ready for announcements.

Sent out announcement message to:

• project-announce@lists.oasis-open.org, members@lists.oasis-open.org, ubl@lists.oasis-open.org, ubl-comment@lists.oasis-open.org
• email: https://lists.oasis-open.org/archives/members/202112/msg00006.html

Installed announcement in OASIS website; submitted for Chet's review.

Assigning to Chet to review and publish website article.

the website announcement has been published. I will go ahead and close this ticket.