-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON-to-RON encoding #28
Comments
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I know, JSON is here just for an illustration, but this is inconsistent.
There are 2 JSON example in the Spec.
Example 1.
Problems
The Spec says header is mandatory.
If these are raw ops, then semicolons must present.
If reduced, then a header must present.
From example 2 one may conclude that you must create and empty dictionary
before filling its fields. There is no empty object op here.
Example 2.
Problem
How can a reader know this object is a dictionary (JSON object)?
Just because the fields are filled with values? What about an empty dictionary?
Does its encoding differ from
null
?Just question: what is the purpose of the header? Declaration of the object?
Must it be the root op?
The text was updated successfully, but these errors were encountered: