{"action":"created","issue":{"url":"https://api.github.com/repos/uber-hypermedia/specification/issues/31","labels_url":"https://api.github.com/repos/uber-hypermedia/specification/issues/31/labels{/name}","comments_url":"https://api.github.com/repos/uber-hypermedia/specification/issues/31/comments","events_url":"https://api.github.com/repos/uber-hypermedia/specification/issues/31/events","html_url":"https://github.com/uber-hypermedia/specification/issues/31","id":82332092,"number":31,"title":"\"document\" vs. \"message\"","user":{"login":"dret","id":1848612,"avatar_url":"https://avatars.githubusercontent.com/u/1848612?v=3","gravatar_id":"","url":"https://api.github.com/users/dret","html_url":"https://github.com/dret","followers_url":"https://api.github.com/users/dret/followers","following_url":"https://api.github.com/users/dret/following{/other_user}","gists_url":"https://api.github.com/users/dret/gists{/gist_id}","starred_url":"https://api.github.com/users/dret/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dret/subscriptions","organizations_url":"https://api.github.com/users/dret/orgs","repos_url":"https://api.github.com/users/dret/repos","events_url":"https://api.github.com/users/dret/events{/privacy}","received_events_url":"https://api.github.com/users/dret/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-05-29T08:33:15Z","updated_at":"2015-05-29T14:57:57Z","closed_at":null,"body":"\"Throughout this specification, we refer to UBER *documents*, but occasionally we \r\nmay say: \"UBER message\", which refers to an UBER document that is being transmitted \r\nover a wire protocol. Due to the strongly message-oriented nature of the UBER model, the \r\ndistinction is typically minor.\"\r\n\r\nwhat *is* the distinction, then? and in which way is it non-minor in non-typical cases?"},"comment":{"url":"https://api.github.com/repos/uber-hypermedia/specification/issues/comments/106839034","html_url":"https://github.com/uber-hypermedia/specification/issues/31#issuecomment-106839034","issue_url":"https://api.github.com/repos/uber-hypermedia/specification/issues/31","id":106839034,"user":{"login":"inadarei","id":30158,"avatar_url":"https://avatars.githubusercontent.com/u/30158?v=3","gravatar_id":"","url":"https://api.github.com/users/inadarei","html_url":"https://github.com/inadarei","followers_url":"https://api.github.com/users/inadarei/followers","following_url":"https://api.github.com/users/inadarei/following{/other_user}","gists_url":"https://api.github.com/users/inadarei/gists{/gist_id}","starred_url":"https://api.github.com/users/inadarei/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/inadarei/subscriptions","organizations_url":"https://api.github.com/users/inadarei/orgs","repos_url":"https://api.github.com/users/inadarei/repos","events_url":"https://api.github.com/users/inadarei/events{/privacy}","received_events_url":"https://api.github.com/users/inadarei/received_events","type":"User","site_admin":false},"created_at":"2015-05-29T14:57:57Z","updated_at":"2015-05-29T14:57:57Z","body":"Thank you, @dret and @mamund.\r\n\r\nLet me clarify what I meant and we can modify wording if it is ambiguous or unclear.  \r\n\r\nUBER is a document format. The document itself can be written on paper, saved as file, published in a blog post, pasted in a Slack or Hipchat chat, or used as a response from an API. \r\n\r\nIn all these cases we use UBER to format documents. However, in the specific case when we are transmitting that document over a wire, it may make more sense to say \"message\", because transmission assumes sending messages. That said the contents of that message is still the same UBER document that we could have written on the paper, saved as file... you get the point.\r\n\r\nMakes sense?"}}