A Media Type Structured Syntax Suffix for JSON Text Sequences
RFC 8091

Document Type RFC - Informational (February 2017; No errata)
Was draft-wilde-json-seq-suffix (individual in art area)
Last updated 2017-02-16
Replaces draft-json-seq-suffix
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd Brian Raymor
Shepherd write-up Show (last changed 2016-12-11)
IESG IESG state RFC 8091 (Informational)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to "Brian Raymor" <brian.raymor@microsoft.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                          E. Wilde
Request for Comments: 8091                               CA Technologies
Category: Informational                                    February 2017
ISSN: 2070-1721

     A Media Type Structured Syntax Suffix for JSON Text Sequences

Abstract

   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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8091.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Wilde                         Informational                     [Page 1]
RFC 8091      JSON Text Sequences Structured Syntax Suffix February 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  The "+json-seq" Structured Syntax Suffix  . . . . . . . . . .   2
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Media type structured syntax suffixes [RFC6838] were introduced as a
   way for a media type to signal that it is based on another media type
   as its foundation.  Some structured syntax suffixes were registered
   initially [RFC6839], including "+json", for the widely popular JSON
   format [RFC7159].

   JSON text sequences [RFC7464] is a recent specification in the JSON
   space that defines how a sequence of multiple JSON texts can be
   represented in one representation.  This document defines and
   registers the "+json-seq" structured syntax suffix in the "Structured
   Syntax Suffix Registry".

2.  Terminology

   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 [RFC2119].

3.  The "+json-seq" Structured Syntax Suffix

   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 can then 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 implement their own specific processing on
   top of that generic parsing tool.

Wilde                         Informational                     [Page 2]
RFC 8091      JSON Text Sequences Structured Syntax Suffix February 2017
Show full document text