Hi there,
I see only some of my LC comments have been addressed in -08; please
have another look at those I list below.
Hi there,
below are my editorial comments:
Abstract
JavaScript Object Notation (JSON) is a lightweight, text-based,
language-independent data interchange format. It was derived from
the ECMAScript Programming Language Standard. JSON defines a small
set of formatting rules for the portable representation of structured
data.
This document makes no changes to the definition of JSON; it repairs
specification errors and offers experience-based interoperability
guidance.
I believe historical considerations do not belong into the abstract (but
into the Introduction)
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 10, 2014.
Are we sure that we do not need the "pre-5378 escape clause" here?
(Section 4 of <http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf>)
The grammatical rules in this document are to be interpreted as
described in [RFC5234].
Maybe note which productions are imported as well (HEXDIG and DIGIT it
seems).
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.
s/fix errata/apply errata/ ?
Insignificant whitespace is allowed before or after any of the six
structural characters.
ws = *(
%x20 / ; Space
%x09 / ; Horizontal tab
%x0A / ; Line feed or New line
%x0D ) ; Carriage return
We *could* use SP, HTAB, LF, and CR here.
JSON text SHALL be encoded in Unicode...
That's a bit misleading. How do I "encode in Unicode"? I think what it
tries to say is that one of the Unicode-compatible character encoding
schemes needs to be used.
An implementation may set limits on the size of texts that it
accepts. An implementation may set limits on the maximum depth of
nesting. An implementation may set limits on the range and precision
of numbers. An implementation may set limits on the length and
character contents of strings.
Maybe this should be a bullet list?
10. Generators
A JSON generator produces JSON text. The resulting text MUST
strictly conform to the JSON grammar.
"strictly"?
o Changed Working Group attribution to JSON Working Group.
...this is a change that will not be visible in the RFC.
Best regards, Julian