Skip to content
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

Should the spec define what JSON spec we adhere to? #23

Open
Zegnat opened this Issue Mar 4, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@Zegnat
Copy link
Member

commented Mar 4, 2018

The parsing specification builds an dictionary object in JSON syntax, but it never defines how to handle encodings etc.

There are several JSON standards out there, some better defined than others. It might be worth pinning microformats to one of them so parsers outputting JSON will all be compatible with the same consumers. To this end it might be good to specify RFC 7493 as our flavour of JSON, as it is “designed to maximize interoperability”.

For some of the history behind the several JSON standards, I refer to this piece by Tim Bray and the links therein. He too writes:

[…] I ac­tu­al­ly don’t rec­om­mend 8259, I rec­om­mend I-JSON, RFC 7493, which de­scribes ex­act­ly the same syn­tax as all the oth­er specs (by ref­er­enc­ing 7159), but ex­plic­it­ly rules out some legal-but-dumbass things you could do that might break your pro­to­col, […]

@Zegnat Zegnat changed the title Should the spec define what JSON it expects? Should the spec define what JSON spec we adhere to? Mar 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.