{"action":"opened","issue":{"url":"https://api.github.com/repos/json-ld/json-ld.org/issues/540","repository_url":"https://api.github.com/repos/json-ld/json-ld.org","labels_url":"https://api.github.com/repos/json-ld/json-ld.org/issues/540/labels{/name}","comments_url":"https://api.github.com/repos/json-ld/json-ld.org/issues/540/comments","events_url":"https://api.github.com/repos/json-ld/json-ld.org/issues/540/events","html_url":"https://github.com/json-ld/json-ld.org/issues/540","id":264109161,"number":540,"title":"embedded @context triple lost in toRDF processing","user":{"login":"christopher-johnson","id":5990301,"avatar_url":"https://avatars1.githubusercontent.com/u/5990301?v=4","gravatar_id":"","url":"https://api.github.com/users/christopher-johnson","html_url":"https://github.com/christopher-johnson","followers_url":"https://api.github.com/users/christopher-johnson/followers","following_url":"https://api.github.com/users/christopher-johnson/following{/other_user}","gists_url":"https://api.github.com/users/christopher-johnson/gists{/gist_id}","starred_url":"https://api.github.com/users/christopher-johnson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/christopher-johnson/subscriptions","organizations_url":"https://api.github.com/users/christopher-johnson/orgs","repos_url":"https://api.github.com/users/christopher-johnson/repos","events_url":"https://api.github.com/users/christopher-johnson/events{/privacy}","received_events_url":"https://api.github.com/users/christopher-johnson/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-10-10T06:08:42Z","updated_at":"2017-10-10T06:08:42Z","closed_at":null,"author_association":"NONE","body":"As shown in [this gist](https://json-ld.org/playground/#/gist/88790348d13006f3cffa48a3841b011b), embedded `@context` triples are lost when processing from JSON-LD to RDF. \r\n\r\nIs this expected or rather a consequence of the special characteristics of the `@context` keyword for from JSON-LD processors? \r\n\r\nOne solution would be to map _only_ the embedded  `@context`(s) to a property IRI that would be recognizable for fromRDF processors to deserialize, similar to `@type` and rdf:type, or alias a different keyword for this embedded `@context` functionality that would have a corresponding property IRI.\r\n\r\nPossibly relates to #521"}}
{"actor":{"display_login":"christopher-johnson"}}