Fwd: WG Review: Javascript Object Notation Update (jsonbis)

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Open this post in threaded view
Report Content as Inappropriate

Fwd: WG Review: Javascript Object Notation Update (jsonbis)

Mark Nottingham-2

> Begin forwarded message:
> From: The IESG <[hidden email]>
> Subject: WG Review: Javascript Object Notation Update (jsonbis)
> Date: 13 June 2015 1:42:15 am AEST
> To: "IETF-Announce" <[hidden email]>
> Cc: jsonbis WG <[hidden email]>
> Reply-To: [hidden email]
> Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/wY0_xzsjWFckBLVSFX-LmFirjGo>
> A new IETF working group has been proposed in the Applications and
> Real-Time Area. The IESG has not made any determination yet. The
> following draft charter was submitted, and is provided for informational
> purposes only. Please send your comments to the IESG mailing list (iesg
> at ietf.org) by 2015-06-22.
> Javascript Object Notation Update (jsonbis)
> ------------------------------------------------
> Current Status: Proposed WG
> Chairs:
>  Matthew Miller <[hidden email]>
> Assigned Area Director:
>  Barry Leiba <[hidden email]>
> Mailing list
>  Address: [hidden email]
>  To Subscribe: https://www.ietf.org/mailman/listinfo/json
>  Archive: https://www.ietf.org/mail-archive/web/json/
> Charter:
> Javascript Object Notation (JSON) is a lightweight, text-based,
> language-independent data interchange format. It was derived from the
> ECMAScript Programming Language Standard, and is published in both
> ECMA-404 and RFC 7159. First published over 10 years ago, JSON has come
> into nearly ubiquitous use, often the first choice for data interchange
> over other forms -- especially for applications that work over the World
> Wide Web.  Given this ubiquity it makes sense to move JSON to Internet
> Standard.
> JSON is defined in two separate documents from two different bodies.
> ECMA-404, published by Ecma International, focuses on the abstract
> syntax.
> RFC 7159, published by the IETF, focuses on the interoperability concerns
> when exchanging JSON over a network. The two documents agree on the
> structure of what JSON is.
> The JSON working group will have as its only task the minor
> revision of RFC 7159 to bring it to Internet Standard, and fully
> acknowledge the syntax definition in ECMA-404. The work is essentially
> a reclassification in place, with absolute minimal changes, though those
> changes will require publication of a new RFC.  The working group will
> review errata and update the document as needed to incorporate those.
> The resulting RFC will be aligned with a corresponding publication by
> The Working Group will work with the liaison managers to coordinate with
> Ecma International TC39 on the editing of both documents. The responsible
> AD will work with the liaison managers to coordinate the approval process
> with Ecma International so that the versions of the document that are
> approved by each body are properly aligned with regard to syntax and
> shared semantics.
> Milestones:
>  Oct 2015 - Request publication of JSON standard

Mark Nottingham   https://www.mnot.net/