< draft-ucarion-jddf-04.txt   draft-ucarion-jddf-05.txt >
Independent Submission U. Carion Independent Submission U. Carion
Internet-Draft Segment Internet-Draft Segment
Intended status: Experimental November 18, 2019 Intended status: Experimental January 23, 2020
Expires: May 21, 2020 Expires: July 26, 2020
JSON Data Definition Format (JDDF) JSON Data Definition Format (JDDF)
draft-ucarion-jddf-04 draft-ucarion-jddf-05
Abstract Abstract
This document proposes a format, called JSON Data Definition Format This document proposes a format, called JSON Data Definition Format
(JDDF), for describing the shape of JavaScript Object Notation (JSON) (JDDF), for describing the shape of JavaScript Object Notation (JSON)
messages. Its main goals are to enable code generation from schemas messages. Its main goals are to enable code generation from schemas
as well as portable validation with standardized error indicators. as well as portable validation with standardized error indicators.
To this end, JDDF is strategically limited to be no more expressive To this end, JDDF is strategically limited to be no more expressive
than the type systems of mainstream programming languages. This than the type systems of mainstream programming languages. This
strategic limitation, as well as the decision to make JDDF schemas be strategic limitation, as well as the decision to make JDDF schemas be
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 21, 2020. This Internet-Draft will expire on July 26, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 6, line 7 skipping to change at page 6, line 7
successfully use JDDF to facilitate information interchange within successfully use JDDF to facilitate information interchange within
their internal systems or between systems operated by independent their internal systems or between systems operated by independent
parties. parties.
If this experiment is deemed successful, and JDDF is determined to be If this experiment is deemed successful, and JDDF is determined to be
a valuable and popular approach, it may be taken to the IETF for a valuable and popular approach, it may be taken to the IETF for
further discussion and revision. One possible outcome of this further discussion and revision. One possible outcome of this
discussion and revision could be that a working group produces a discussion and revision could be that a working group produces a
Standards Track specification of JDDF. Standards Track specification of JDDF.
Some implementations of JDDF, as well as code generators and other
tooling related to JDDF, are available at <https://github.com/jddf>.
2. Syntax 2. Syntax
This section describes when a JSON document is a correct JDDF schema. This section describes when a JSON document is a correct JDDF schema.
Because CDDL is well-suited to the task of defining complex JSON Because CDDL is well-suited to the task of defining complex JSON
formats, such as JDDF schemas, this section uses CDDL to describe the formats, such as JDDF schemas, this section uses CDDL to describe the
format of JDDF schemas. format of JDDF schemas.
JDDF schemas may recursively contain other schemas. In this JDDF schemas may recursively contain other schemas. In this
document, a "root schema" is one which is not contained within document, a "root schema" is one which is not contained within
another schema, i.e. it is "top level". another schema, i.e. it is "top level".
skipping to change at page 37, line 25 skipping to change at page 37, line 25
6.2. Informative References 6.2. Informative References
[I-D.handrews-json-schema] [I-D.handrews-json-schema]
Wright, A., Andrews, H., Hutton, B., and G. Dennis, "JSON Wright, A., Andrews, H., Hutton, B., and G. Dennis, "JSON
Schema: A Media Type for Describing JSON Documents", Schema: A Media Type for Describing JSON Documents",
draft-handrews-json-schema-02 (work in progress), draft-handrews-json-schema-02 (work in progress),
September 2019. September 2019.
[OPENAPI] OpenAPI Initiative, "OpenAPI Specification", October 2019, [OPENAPI] OpenAPI Initiative, "OpenAPI Specification", October 2019,
<http://spec.openapis.org/oas/v3.0.2>. <https://spec.openapis.org/oas/v3.0.2>.
[RFC7071] Borenstein, N. and M. Kucherawy, "A Media Type for [RFC7071] Borenstein, N. and M. Kucherawy, "A Media Type for
Reputation Interchange", RFC 7071, DOI 10.17487/RFC7071, Reputation Interchange", RFC 7071, DOI 10.17487/RFC7071,
November 2013, <https://www.rfc-editor.org/info/rfc7071>. November 2013, <https://www.rfc-editor.org/info/rfc7071>.
[RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493, [RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493,
DOI 10.17487/RFC7493, March 2015, DOI 10.17487/RFC7493, March 2015,
<https://www.rfc-editor.org/info/rfc7493>. <https://www.rfc-editor.org/info/rfc7493>.
Appendix A. Other Considerations Appendix A. Other Considerations
 End of changes. 6 change blocks. 
6 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/