Order in JSON response "MUST"

[Christian Müller <christian@flownative.com>]

Hi all,

I am new here and currently working on a OData implementation and reading the spec a lot.

I stumbled upon the following sentence in:

http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata02/os/odata-json-format-v4.0-errata02-os-complete.html#_Toc403940642

"The odata.count name/value pair represents the number of entities in the collection. If present, it MUST come before the value name/value pair."

I am very irritated by the "MUST come before the value name/value pair". IMHO that violates the JSON spec and should be removed.

To cite JSON spec: "An object is an unordered set of name/value pairs". And many implementations treat it like that, which means the order

is not guaranteed if you use JSON tools of your language. The only way to make sure this piece of the OData spec is respected

would be using raw string operations. So I propose to remove all notions of order of keys in the JSON format spec.

Best,

Christian