Subject: [Cbor] Fwd: Invitation to comment on Specification for JSON Abstract Data Notation v1.0 - ends January 27th

From: Carsten Bormann <[email-masked]>
Date: Tue, 29 Dec 2020 01:02:34 +0100

This is an interesting piece of work, somewhat related to both CDDL and SDF, and (contrary to its JSON-centric name) with a CBOR-related generic data model and CBOR serialization rules.  
I don’t have an immediate opinion how this might become useful for IETF work, but it certainly exhibits an elaborate set of design choices worth pondering.

Grüße, Carsten

> Begin forwarded message:
> 
> From: Paul Knight <[email-masked]>
> Subject: Invitation to comment on Specification for JSON Abstract Data Notation v1.0 - ends January 27th
> Date: 2020-12-28 at 23:38:26 CET
> To: [email-masked], [email-masked], OASIS TAB <[email-masked]>, [email-masked], [email-masked]
> Message-Id: <CADgeAH8ZHQaFPKd5N8Rfk=2xORZHHFDw=[email-masked]>
> 
> OASIS members and other interested parties,
> 
> OASIS and the OASIS Open Command and Control (OpenC2) TC are pleased to announce that Specification for JSON Abstract Data Notation Version 1.0 is now available for public review and comment. This is the first public review for this specification.
> 
> JSON Abstract Data Notation (JADN) is an information modeling language. It has several purposes including defining data structures, validating data instances, informing user interfaces working with structured data, and facilitating protocol internationalization. JADN specifications consist of two parts: abstract type definitions that are independent of data format, and serialization rules that define how to represent type instances using specific data formats. A JADN schema is itself a structured information object that can be serialized and transferred between applications, documented in multiple formats such as text-based interface definition languages, property tables or diagrams, and translated into concrete schemas used to validate specific data formats.
> 
> The documents and related files are available here:
> 
> Specification for JSON Abstract Data Notation Version 1.0
> Committee Specification Draft 01
> 21 October 2020
> 
> Editable source:
> https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.md <https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.md>
> 
> HTML:
> https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.html <https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.html>
> 
> PDF (Authoritative):
> https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.pdf <https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.pdf>
> 
> For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:
> https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.zip <https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01.zip>
> 
> How to Provide Feedback
> 
> OASIS and the OpenC2 TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of our technical work.
> 
> The public review starts 29 December 2020 at 00:00 UTC and ends 27 January 2021 23:59 UTC.
> 
> 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=openc2 <https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=openc2>).
> 
> Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
> https://lists.oasis-open.org/archives/openc2-comment/ <https://lists.oasis-open.org/archives/openc2-comment/>
> 
> 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, we call your attention to the OASIS IPR Policy [1] applicable especially [2] 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 the specification and the OpenC2 TC can be found at the TC's public home page:
> https://www.oasis-open.org/committees/openc2/ <https://www.oasis-open.org/committees/openc2/>
> 
> Additional information related to this public review can be found in the public review metadata document [3].
> 
> ========== Additional references:
> 
> [1] https://www.oasis-open.org/policies-guidelines/ipr <https://www.oasis-open.org/policies-guidelines/ipr>
> 
> [2] https://www.oasis-open.org/committees/openc2/ipr.php <https://www.oasis-open.org/committees/openc2/ipr.php>
> https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode <https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode>
> Non-Assertion Mode
> 
> [3] Public review metadata document:
> - https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01-public-review-metadata.html <https://docs.oasis-open.org/openc2/jadn/v1.0/csd01/jadn-v1.0-csd01-public-review-metadata.html>
> -- 
> 
> Paul Knight
> Document Process
> OASIS Open
> 
> 
> +1 781-883-1783 <tel:+1+781-883-1783>
> 	[email-masked] <mailto:[email-masked]>
> 	www.oasis-open.org <https://www.oasis-open.org/>