draft-bormann-cbor-04 adds text about handling maps with multiple identical
keys., but it is contradictory. Section 3.4. "Specifying Keys for Maps" says:
A CBOR-based protocol should make an intentional decision about what
to do when a receiving application sees multiple identical keys in a
draft-bormann-cbor-04 adds text about handling maps with multiple identical
keys., but it is contradictory. Section 3.4. "Specifying Keys for Maps" says:
A CBOR-based protocol should make an intentional decision about what
to do when a receiving application sees multiple identical keys in a
If we were starting from scratch and defining JSON Pointer again I would argue
for distinguishing array indices and object names in the syntax. For instance,
prefix an object name with "/" and an array index with ":".
json-pointer = *segment
segment = "/" name / ":" index
name = *( un
> On Wed, 24 Oct 2012, Manger, James H wrote:
> >
> > Currently, I don't think url.spec.whatwg.org distinguishes between
> > strings that are valid URLs and strings that can be interpreted as
> > URLs by applying its standardised error handling. Consequently, err
> From: Ian Hickson [mailto:i...@hixie.ch]
> I think we can agree that the error handling should be, at the option
> of the software developer, either to handle the input as defined by the
> spec's algorithms, or to abort and not handle the input at all.
Currently, I don't think url.spec.whatwg.or
