{"action":"opened","issue":{"url":"https://api.github.com/repos/adlnet/xAPI-Spec/issues/736","labels_url":"https://api.github.com/repos/adlnet/xAPI-Spec/issues/736/labels{/name}","comments_url":"https://api.github.com/repos/adlnet/xAPI-Spec/issues/736/comments","events_url":"https://api.github.com/repos/adlnet/xAPI-Spec/issues/736/events","html_url":"https://github.com/adlnet/xAPI-Spec/issues/736","id":99282899,"number":736,"title":"Use one type of JWS Serialization. ","user":{"login":"nashyura","id":3335473,"avatar_url":"https://avatars.githubusercontent.com/u/3335473?v=3","gravatar_id":"","url":"https://api.github.com/users/nashyura","html_url":"https://github.com/nashyura","followers_url":"https://api.github.com/users/nashyura/followers","following_url":"https://api.github.com/users/nashyura/following{/other_user}","gists_url":"https://api.github.com/users/nashyura/gists{/gist_id}","starred_url":"https://api.github.com/users/nashyura/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nashyura/subscriptions","organizations_url":"https://api.github.com/users/nashyura/orgs","repos_url":"https://api.github.com/users/nashyura/repos","events_url":"https://api.github.com/users/nashyura/events{/privacy}","received_events_url":"https://api.github.com/users/nashyura/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-08-05T19:41:14Z","updated_at":"2015-08-05T19:41:14Z","closed_at":null,"body":"There are two types of Serialization defined in the JWS spec: [Compact and JSON](https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-41#section-3.1)\r\n\r\nI have only seen the compact serialization implemented in libraries I've used.  If nobody currently uses the JSON serialization, and there is no need for it in the xAPI spec, it makes sense to explicitly limit the xAPI spec to use the Compact Serialization.\r\n\r\nWe can modify 1.x to say that signatures SHOULD be serialized using the compact serialization format, and in 2.x we could change that to a MUST.\r\n\r\nOf course, this suggestion is not useful if anybody that is adopting the spec uses JSON serialization."}}