Closed pchampin closed 4 years ago
As a consequence, the corresponding text in API 8.6 Data Round Tripping is states:
The canonical lexical form of a JSON literal value is non-normative,
and still uses SHOULD. I guess we should update it as well?
Yes. But I would simplify the whole portion of the text related to the JSON literal: let us not repeat the canonicalization algorithm (although we do not use the term 'canonicalization' in the new version of the syntax:-), but just refer to the value space of the JSON Literal, as defined in the syntax document. The value space being valid JSON, that should be somehow enough for the round tripping: a value in the value space is also a valid lexical form for the JSON part.
(Yes, this means that there is no roundripping for JSON literals in the sense of keeping the original key order, spaces, indentation, etc. Let it be...)
(I wonder why github replicated my comment three times...)
@iherman
I believe that the lexical-to-value mapping section must be changed as well.
It was changed... and it does reference the constraints described in the definition of the value space.
(I wonder why github replicated my comment three times...)
It didn't, at least from where I stand.
This issue was discussed in a meeting.
RESOLVED: Update api document to be in line with syntax for json datatype, test descriptions, and “canonicalization” algorithm (modulo key ordering)
addressing #323
Note that the description of the canonical form, which used to be non-normative (and using SHOULD) is now normative and uses MUST. It seemed inappropriate to define the value space non-normatively... :-/
As a consequence, the corresponding text in API 8.6 Data Round Tripping is states:
and still uses SHOULD. I guess we should update it as well?
Preview | Diff