- From: Addison Phillips <notifications@github.com>
- Date: Mon, 15 May 2023 00:33:51 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 15 May 2023 07:33:56 UTC
Privacy and Security https://w3c.github.io/manifest/#priv-sec > As the manifest format is JSON and will commonly be encoded using [[UNICODE](https://w3c.github.io/manifest/#bib-unicode)], the security considerations described in [[JSON](https://w3c.github.io/manifest/#bib-json)] and [[UNICODE-SECURITY](https://w3c.github.io/manifest/#bib-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. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/1089 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/1089@github.com>
Received on Monday, 15 May 2023 07:33:56 UTC