{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/csvw/issues/615","labels_url":"https://api.github.com/repos/w3c/csvw/issues/615/labels{/name}","comments_url":"https://api.github.com/repos/w3c/csvw/issues/615/comments","events_url":"https://api.github.com/repos/w3c/csvw/issues/615/events","html_url":"https://github.com/w3c/csvw/issues/615","id":88061823,"number":615,"title":"Include @context in JSON output?","user":{"login":"gkellogg","id":46296,"avatar_url":"https://avatars.githubusercontent.com/u/46296?v=3","gravatar_id":"","url":"https://api.github.com/users/gkellogg","html_url":"https://github.com/gkellogg","followers_url":"https://api.github.com/users/gkellogg/followers","following_url":"https://api.github.com/users/gkellogg/following{/other_user}","gists_url":"https://api.github.com/users/gkellogg/gists{/gist_id}","starred_url":"https://api.github.com/users/gkellogg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gkellogg/subscriptions","organizations_url":"https://api.github.com/users/gkellogg/orgs","repos_url":"https://api.github.com/users/gkellogg/repos","events_url":"https://api.github.com/users/gkellogg/events{/privacy}","received_events_url":"https://api.github.com/users/gkellogg/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/w3c/csvw/labels/CSV%20to%20JSON%20mapping","name":"CSV to JSON mapping","color":"84b6eb"},{"url":"https://api.github.com/repos/w3c/csvw/labels/Requires%20telcon%20discussion/decision","name":"Requires telcon discussion/decision","color":"e11d21"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-06-13T20:35:29Z","updated_at":"2015-06-17T15:30:46Z","closed_at":null,"body":"Bringing it up now, as it will likely come up in comments later.\r\n\r\nOur JSON output is not intended to be strict-JSON-LD, and doesn't have the semantic integrity of the RDF output, however, it does have the form of JSON-LD, and so people may expect that it can be used that way. Without including `@context`, the results may not satisfy exceptions. Simply including the following boilerplate would allow the results to work as JSON-LD:\r\n\r\n```\r\n{\r\n  \"@context\": \"http://www.w3.org/ns/csvw\",\r\n  ...\r\n}\r\n```\r\n\r\nWe should consider adding that as part of the standard output. This would allow JSON-LD algorithms to be used on it natively and would satisfy objections that the result _looks_ like JSON-LD, but isn't actually valid JSON-LD.\r\n\r\nThe addition of the `@context` entry wouldn't otherwise affect the use of the results as JSON."},"comment":{"url":"https://api.github.com/repos/w3c/csvw/issues/comments/112847720","html_url":"https://github.com/w3c/csvw/issues/615#issuecomment-112847720","issue_url":"https://api.github.com/repos/w3c/csvw/issues/615","id":112847720,"user":{"login":"JeniT","id":395050,"avatar_url":"https://avatars.githubusercontent.com/u/395050?v=3","gravatar_id":"","url":"https://api.github.com/users/JeniT","html_url":"https://github.com/JeniT","followers_url":"https://api.github.com/users/JeniT/followers","following_url":"https://api.github.com/users/JeniT/following{/other_user}","gists_url":"https://api.github.com/users/JeniT/gists{/gist_id}","starred_url":"https://api.github.com/users/JeniT/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JeniT/subscriptions","organizations_url":"https://api.github.com/users/JeniT/orgs","repos_url":"https://api.github.com/users/JeniT/repos","events_url":"https://api.github.com/users/JeniT/events{/privacy}","received_events_url":"https://api.github.com/users/JeniT/received_events","type":"User","site_admin":false},"created_at":"2015-06-17T15:30:46Z","updated_at":"2015-06-17T15:30:46Z","body":"@gkellogg I view the use of `@id` and `@type` within the JSON output as adopting a useful convention rather than creating a new one, not as a mechanism for ensuring the JSON output is full JSON-LD. Users who are interested in getting RDF out of the CSV will surely transform to RDF rather than through the JSON output: the resulting mapping is a hell of a lot richer, particularly around datatyping.\r\n\r\nSo -1 from me on adding a `@context`."}}