Comment

Comment by GeneThomas

- The flexibility in name is to support the plethora of programming languages.

- Commas are for readability as per English.

- Three digits are recommended for the encoder.

- Textual data is decoded into binary information in software so setting expectations, e.g. supporting ∞, facilitates interoperability by reducing impedance mismatches.

- If the implementation uses ɪᴇᴇᴇ doubles the rounding shall be as expected.

- Unicode surrogates are disallowed.

- We are following the Base64 standard exactly.

- It is essential for data to be structured as a graph, it simply occurs. Serialization on most data formats has the required support for graphs awkwardly layered on top of the encoding.

- The C# implementation defines the data model; essentially objects, array and scalars with multiple parents for nodes. The Formats section is to, as stated, facilitate interoperability.

- Limiting whitespace to spaces and tabs does speed processing. The ᴜᴛꜰ-8 bytes can be left in the input buffer rather than copied. All significant bytes are ᴀꜱᴄɪɪ.

- There are no unmatched angle brackets (that was a typo).

- I know the reasoning behind XML.

parent GeneThomas 2 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton