-
-
Notifications
You must be signed in to change notification settings - Fork 309
Investigate EXI for JSON compatability #13
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
Comments
Update news: a new Editor's Draft of the EXI4JSON document is now available at Comments about this document are welcome on the [email protected] mailing list Announcement by Daniel Peintner: https://lists.w3.org/Archives/Public/public-exi/2016Aug/0004.html All, EXI4JSON allows one to convert JSON documents in an efficient representation by means of EXI. Lossless round-trip conversion back to the original JSON structures is supported too. For people that would like to experiment there are already some implementations available in Java [2, 3], JavaScript [4] and C [5]. -- Daniel [1a] https://www.w3.org/TR/2016/WD-exi-for-json-20160823/ |
Nice! This is still a very theoretical idea, but thanks for the notice @brutzman |
Weird shower thought: There's only one thing (afaict) that prevents you from building an ABNF out of a JSON Schema, and that is the fact that properties may appear in any order. If we could figure out a way to enforce a property order, then we could generate an ABNF, and/or a more efficient EXI representation. |
EXI for JSON https://www.w3.org/TR/exi-for-json/ is a method of compressing JSON into a compact binary form, using the algorithm defined by EXI (originally defined for XML).
For draft-5, we need not add define any specific compatibility features, but do consider the ways it might be used.
The text was updated successfully, but these errors were encountered: