[Cbor] EDN - carriage returns

[Joe Hildebrand <[e-mail]>]

The grammar in -11 says:

    unescaped       = %x0A ; new line
                    / %x0D ; carriage return -- ignored on input

I agree that "\r" should be ignored in input.  I hope that Mac-style "\r"-only line terminators are not in enough use to matter anymore.  Could we please add some normative text that describes this behavior and the trade-offs?

For example, after "The following additional items should help in the interpretation:"

- Unescaped uses of CARRIAGE RETURN (U+000D, also often seen as "\r" in many programming languages) that exist in the input should be ignored as if they were not in the input wherever they appear.  This is most important when they are found in tstr or bstr contexts (see the "unescaped" ABNF rule).  On some operating systems, a carriage return is always paired with a LINE FEED (U+000A, also often seen as "\n" in many programming languages), but in other operating systems, they are not used.  The intent behind this approach is to ensure that input generated on either of these kinds of operating systems will generate the same CBOR bytes.  Operating systems that use only LINE FEED are no longer relevant and the files they produce are out of scope for this document.

— 
Joe Hildebrand