[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xdi] Fwd: [Json] Small ABNF change to do some semantic separation
The original message in this thread criticizes ABNF in a proposed standard using JSON, not a standard for JSON itself:REPUTE Working Group N. Borenstein
Internet-Draft Mimecast
Intended status: Standards Track M. Kucherawy
Expires: March 19, 2014 September 15, 2013
A Media Type for Reputation Interchange
draft-ietf-repute-media-type-13
Abstract
This document defines the format of reputation response data
("reputons"), the media-type for packaging it, and definition of a
registry for the names of reputation applications and response sets. Of course you may find this proposed standard to be of separate interest! As it turns out, 4627bis itself says: This revision does not change any of the rules of the specification; all texts which were legal JSON remain so, and none which were not JSON become JSON. The revision's goal is to fix the errata and highlight practices which can lead to interoperability problems. The following Changes list is mostly errata, attributions, and clarifications, which however so far do not seem to have changed any of the ABNF. One other thing to note is that 4627 defines both JSON text and JSON value, in that order. We use value, not text. A JSON text is a serialized object or array. JSON-text = object / array A JSON value MUST be an object, array, number, or string, or one of the following three literal names: false null true The literal names MUST be lowercase. No other literal names are allowed. value = false / null / true / object / array / number / string On Sep 22, 2013, at 3:31 PM, Drummond Reed <drummond.reed@xdi.org> wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]