{"action":"created","issue":{"url":"https://api.github.com/repos/thebuzzmedia/universal-binary-json/issues/60","labels_url":"https://api.github.com/repos/thebuzzmedia/universal-binary-json/issues/60/labels{/name}","comments_url":"https://api.github.com/repos/thebuzzmedia/universal-binary-json/issues/60/comments","events_url":"https://api.github.com/repos/thebuzzmedia/universal-binary-json/issues/60/events","html_url":"https://github.com/thebuzzmedia/universal-binary-json/issues/60","id":51493736,"number":60,"title":"DISCUSSION - Reconciling optimized headers, flexible STC, n-dimensional arrays and schemas","user":{"login":"thebuzzmedia","id":533480,"avatar_url":"https://avatars.githubusercontent.com/u/533480?v=3","gravatar_id":"","url":"https://api.github.com/users/thebuzzmedia","html_url":"https://github.com/thebuzzmedia","followers_url":"https://api.github.com/users/thebuzzmedia/followers","following_url":"https://api.github.com/users/thebuzzmedia/following{/other_user}","gists_url":"https://api.github.com/users/thebuzzmedia/gists{/gist_id}","starred_url":"https://api.github.com/users/thebuzzmedia/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thebuzzmedia/subscriptions","organizations_url":"https://api.github.com/users/thebuzzmedia/orgs","repos_url":"https://api.github.com/users/thebuzzmedia/repos","events_url":"https://api.github.com/users/thebuzzmedia/events{/privacy}","received_events_url":"https://api.github.com/users/thebuzzmedia/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/thebuzzmedia/universal-binary-json/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":15,"created_at":"2014-12-09T22:51:48Z","updated_at":"2015-03-01T16:50:31Z","closed_at":null,"body":"This needs to be a bigger discussion, so filing here for thoughts...\r\n\r\n## Big ideas in-flight...\r\n1. #48 - Allow STC headers to repeating inside a container to more closely match JSON container design.\r\n2. #51 - Redefine container headers to have a single, consistent and concise format (#<TYPE><SIZE>)\r\n3. #43 [detail in comment](https://github.com/thebuzzmedia/universal-binary-json/issues/43#issuecomment-48524976) - Proposal to allow pre-defining of container 'structure' upfront - potentially massive space savings in highly optimized cases (currently a case UBJSON is not great at)\r\n4. #50 Alex's `TypeSpec` proposal; basically schemas. I think somewhat ties into the conversation around Point 3 above - basically allowing you to upfront define 'structure' of a container completely upfront - then the entire payload is just hard data.\r\n\r\n## My question\r\nWe are getting close to finalizing Point 1 above and allowing the headers (#51) to repeat during a container... that is great, but it doesn't address the potentially HUGE space savings discussed in Points 3 and 4 above and I wanted to make sure we weren't moving forward with a change that was either pointless (to be undone later) or conflicting with potentially addressing 3 and 4 later.\r\n\r\nThis issue is a forum for us to discuss where all these concerns are heading towards."},"comment":{"url":"https://api.github.com/repos/thebuzzmedia/universal-binary-json/issues/comments/76610880","html_url":"https://github.com/thebuzzmedia/universal-binary-json/issues/60#issuecomment-76610880","issue_url":"https://api.github.com/repos/thebuzzmedia/universal-binary-json/issues/60","id":76610880,"user":{"login":"Steve132","id":877616,"avatar_url":"https://avatars.githubusercontent.com/u/877616?v=3","gravatar_id":"","url":"https://api.github.com/users/Steve132","html_url":"https://github.com/Steve132","followers_url":"https://api.github.com/users/Steve132/followers","following_url":"https://api.github.com/users/Steve132/following{/other_user}","gists_url":"https://api.github.com/users/Steve132/gists{/gist_id}","starred_url":"https://api.github.com/users/Steve132/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Steve132/subscriptions","organizations_url":"https://api.github.com/users/Steve132/orgs","repos_url":"https://api.github.com/users/Steve132/repos","events_url":"https://api.github.com/users/Steve132/events{/privacy}","received_events_url":"https://api.github.com/users/Steve132/received_events","type":"User","site_admin":false},"created_at":"2015-03-01T16:50:31Z","updated_at":"2015-03-01T16:50:31Z","body":"Obviously there is a relation to JSON in that it is inspired by json.  You are right that it's in the name.  \r\n\r\nMy point that I was trying to make is that even if JSON had never been invented then the format which we call UBJSON would still *independently* be incredibly useful and valuable as what it is: which is a serialization format.   THAT is why I disagree that characterizing it as 'either a binary json 1-1 or a binary transfer coding for json documents' is accurate.  You might use it for those things but that's not what it *is*.  It's a way to serialize data."}}