Re: [media-types] Review requested for draft-bormann-cbor-04

[Tony Hansen <[e-mail]>]

On 7/15/2013 11:20 AM, John R Levine wrote:
> draft-bormann-cbor-04 describes a new binary structured data format
> called Concise Binary Object Representation (CBOR), and proposes a
> media type for it.  The media type info in the draft is:

An open question in draft-bormann-cbor-04 is:

>    TBD: Maybe add application/mmmmm+cbor for specific protocols?

I think CBOR is worthy of defining a structured syntax suffix. Here is a
candidate addition.

    Tony Hansen

7.4. The +cbor Structured Syntax Suffix Registration

   Name:  Concise Binary Object Representation (CBOR)

   +suffix:  +cbor

   References:  [RFC-THIS-SPEC]

   Encoding considerations: CBOR is a binary format.

   Fragment identifier considerations:
      The syntax and semantics of fragment identifiers specified for
      +cbor SHOULD be as specified for "application/cbor".  (At
      publication of this document, there is no fragment identification
      syntax defined for "application/cbor".)

      The syntax and semantics for fragment identifiers for a specific
      "xxx/yyy+cbor" SHOULD be processed as follows:

      For cases defined in +cbor, where the fragment identifier resolves
      per the +cbor rules, then process as specified in +cbor.

      For cases defined in +cbor, where the fragment identifier does
      not resolve per the +cbor rules, then process as specified in
      "xxx/yyy+cbor".

      For cases not defined in +cbor, then process as specified in
      "xxx/yyy+cbor".

   Interoperability considerations:  n/a

   Security considerations:  See [RFC-THIS-SPEC]

   Contact:  Apps Area Working Group ([e-mail])

   Author/Change controller:
      The Apps Area Working Group.  IESG has change control over this
      registration.