CA Technologies

erik.wilde@dret.net http://dret.net/netdret/

Structured Syntax Suffixes for media types allow other media types to build on them and make it explicit that they are built on an existing media type as their foundation. This specification defines and registers "json-seq" as a structured syntax suffix for JSON Text Sequences. This draft should be discussed on the art mailing list. Online access to all versions and files is available on github.

Media Type Structured Syntax Suffixes were introduced as a way of how a media type can signal that it is based on another media type as its foundation. Some structured syntax suffixes were registered initially , including "+json" for the widely popular JSON Format format. JSON Text Sequences is a new specification in the JSON space that defines how a sequence of multiple JSON texts can be represented in one representation. Since this specification can be used as the foundation for other formats, this specification defines and registers the "+json-seq" structured syntax suffix.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 .

The use case for the "+json-seq" structured syntax suffix is the same as for "+json": It SHOULD be used by media types when parsing the JSON Text Sequence of a media type leads to a meaningful result, by simply using the generic JSON Text Sequence processing. Applications encountering such a media type then can either simply use generic processing if all they need is a generic view of the JSON Text Sequence, or they can use generic JSON Text Sequence tools for initial parsing, and then can implement their own specific processing on top of that generic parsing tool.

IANA has added the following "+json-seq" structured syntax suffix to its registry of structured syntax suffixes established by : Name: JSON Text Sequence +suffix: +json-seq References: Encoding considerations: See Fragment identifier considerations: The syntax and semantics of fragment identifiers specified for +json-seq SHOULD be as specified for "application/json-seq". (At publication of this document, there is no fragment identification syntax defined for "application/json-seq".) The syntax and semantics for fragment identifiers for a specific "xxx/yyy+json-seq" SHOULD be processed as follows: For cases defined in +json-seq, where the fragment identifier resolves per the +json-seq rules, then process as specified in +json-seq. For cases defined in +json-seq, where the fragment identifier does not resolve per the +json-seq rules, then process as specified in "xxx/yyy+json-seq". For cases not defined in +json-seq, then process as specified in "xxx/yyy+json-seq". Interoperability considerations: n/a Security considerations: See Contact: Applications and Real-Time Area Working Group (art@ietf.org) Author/Change controller: The Applications and Real-Time Area Working Group. IESG has change control over this registration.

Harvard University

1350 Mass. Ave. Cambridge MA 02138 - +1 617 495 3864

This document defines procedures for the specification and registration of media types for use in HTTP, MIME, and other Internet protocols. This memo documents an Internet Best Current Practice. This document describes the JavaScript Object Notation (JSON) text sequence format and associated media type "application/json-seq". A JSON text sequence consists of any number of JSON texts, all encoded in UTF-8, each prefixed by an ASCII Record Separator (0x1E), and each ending with an ASCII Line Feed character (0x0A). This memo describes use cases, requirements, and protocol extensions for using the Session Description Protocol (SDP) offer/answer model for establishing audio and video media streams over circuit-switched bearers in the Public Switched Telephone Network (PSTN). A content media type name sometimes includes partitioned meta- information distinguished by a structured syntax to permit noting an attribute of the media as a suffix to the name. This document defines several structured syntax suffixes for use with media type registrations. In particular, it defines and registers the "+json", "+ber", "+der", "+fastinfoset", "+wbxml" and "+zip" structured syntax suffixes, and provides a media type structured syntax suffix registration form for the "+xml" structured syntax suffix. This document is not an Internet Standards Track specification; it is published for informational purposes.