{"action":"created","issue":{"url":"https://api.github.com/repos/KhronosGroup/glTF/issues/1345","repository_url":"https://api.github.com/repos/KhronosGroup/glTF","labels_url":"https://api.github.com/repos/KhronosGroup/glTF/issues/1345/labels{/name}","comments_url":"https://api.github.com/repos/KhronosGroup/glTF/issues/1345/comments","events_url":"https://api.github.com/repos/KhronosGroup/glTF/issues/1345/events","html_url":"https://github.com/KhronosGroup/glTF/issues/1345","id":325480248,"number":1345,"title":"JSON must use UTF-8 encoding without BOM","user":{"login":"bghgary","id":19158740,"avatar_url":"https://avatars2.githubusercontent.com/u/19158740?v=4","gravatar_id":"","url":"https://api.github.com/users/bghgary","html_url":"https://github.com/bghgary","followers_url":"https://api.github.com/users/bghgary/followers","following_url":"https://api.github.com/users/bghgary/following{/other_user}","gists_url":"https://api.github.com/users/bghgary/gists{/gist_id}","starred_url":"https://api.github.com/users/bghgary/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bghgary/subscriptions","organizations_url":"https://api.github.com/users/bghgary/orgs","repos_url":"https://api.github.com/users/bghgary/repos","events_url":"https://api.github.com/users/bghgary/events{/privacy}","received_events_url":"https://api.github.com/users/bghgary/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-22T22:05:24Z","updated_at":"2018-05-22T22:18:07Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"@lexaknyazev \r\n\r\nhttps://github.com/KhronosGroup/glTF/tree/master/specification/2.0#json-encoding\r\n\r\n> 1. JSON must use UTF-8 encoding without BOM.\r\n\r\nIs there a specific reason why we restrict it to \"without BOM\"? Can we add some validation to the validator?\r\n\r\nhttps://github.com/KhronosGroup/glTF/issues/831 seems to talk about this, but I see no discussion on BOM."},"comment":{"url":"https://api.github.com/repos/KhronosGroup/glTF/issues/comments/391158711","html_url":"https://github.com/KhronosGroup/glTF/issues/1345#issuecomment-391158711","issue_url":"https://api.github.com/repos/KhronosGroup/glTF/issues/1345","id":391158711,"user":{"login":"lexaknyazev","id":3479527,"avatar_url":"https://avatars2.githubusercontent.com/u/3479527?v=4","gravatar_id":"","url":"https://api.github.com/users/lexaknyazev","html_url":"https://github.com/lexaknyazev","followers_url":"https://api.github.com/users/lexaknyazev/followers","following_url":"https://api.github.com/users/lexaknyazev/following{/other_user}","gists_url":"https://api.github.com/users/lexaknyazev/gists{/gist_id}","starred_url":"https://api.github.com/users/lexaknyazev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lexaknyazev/subscriptions","organizations_url":"https://api.github.com/users/lexaknyazev/orgs","repos_url":"https://api.github.com/users/lexaknyazev/repos","events_url":"https://api.github.com/users/lexaknyazev/events{/privacy}","received_events_url":"https://api.github.com/users/lexaknyazev/received_events","type":"User","site_admin":false},"created_at":"2018-05-22T22:18:07Z","updated_at":"2018-05-22T22:18:07Z","author_association":"MEMBER","body":"From [RFC-7159 (JSON), section 8.1](https://tools.ietf.org/html/rfc7159#section-8.1)\r\n> Implementations MUST NOT add a byte order mark to the beginning of a JSON text.  In the interests of interoperability, implementations that parse JSON texts MAY ignore the presence of a byte order mark rather than treating it as an error.\r\n\r\nAlso it allows loaders to not support full UTF-8 charset because all glTF-defined strings are ASCII-representable.\r\n\r\nThe validator will refuse to load an asset starting with BOM in some cases, I'll investigate to make that consistent across all builds/inputs."}}
{"actor":{"display_login":"lexaknyazev"}}