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

JSON "commonly" encoded in Unicode #1089

Closed
aphillips opened this issue May 15, 2023 · 2 comments · Fixed by #1100
Closed

JSON "commonly" encoded in Unicode #1089

aphillips opened this issue May 15, 2023 · 2 comments · Fixed by #1100
Assignees
Labels
Editorial clarification i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@aphillips
Copy link

Privacy and Security
https://w3c.github.io/manifest/#priv-sec

As the manifest format is JSON and will commonly be encoded using [UNICODE], the security considerations described in [JSON] and [UNICODE-SECURITY] apply.

Actually, JSON documents are always encoded in UTF-8 on the wire (they may be decoded into UTF-16 or some other Unicode encoding in memory) and are processed in terms of Unicode, so the word "commonly" should be removed. Note that the references to Unicode and UTS39 should probably use SpecRef.

@christianliebel
Copy link
Member

Note that the references to Unicode and UTS39 should probably use SpecRef.

@aphillips Could you explain this a bit more? To me the references look like they are SpecRefs.

@aphillips
Copy link
Author

@christianliebel My bad. I didn't realize that UNICODE-SECURITY is a specref defined alias of UTR36.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Editorial clarification i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants