{"action":"opened","issue":{"url":"https://api.github.com/repos/w3c/vc-data-model/issues/194","repository_url":"https://api.github.com/repos/w3c/vc-data-model","labels_url":"https://api.github.com/repos/w3c/vc-data-model/issues/194/labels{/name}","comments_url":"https://api.github.com/repos/w3c/vc-data-model/issues/194/comments","events_url":"https://api.github.com/repos/w3c/vc-data-model/issues/194/events","html_url":"https://github.com/w3c/vc-data-model/issues/194","id":339244724,"node_id":"MDU6SXNzdWUzMzkyNDQ3MjQ=","number":194,"title":"Use schema.org as the base schema?","user":{"login":"msporny","id":108611,"node_id":"MDQ6VXNlcjEwODYxMQ==","avatar_url":"https://avatars3.githubusercontent.com/u/108611?v=4","gravatar_id":"","url":"https://api.github.com/users/msporny","html_url":"https://github.com/msporny","followers_url":"https://api.github.com/users/msporny/followers","following_url":"https://api.github.com/users/msporny/following{/other_user}","gists_url":"https://api.github.com/users/msporny/gists{/gist_id}","starred_url":"https://api.github.com/users/msporny/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/msporny/subscriptions","organizations_url":"https://api.github.com/users/msporny/orgs","repos_url":"https://api.github.com/users/msporny/repos","events_url":"https://api.github.com/users/msporny/events{/privacy}","received_events_url":"https://api.github.com/users/msporny/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-08T17:59:36Z","updated_at":"2018-07-08T17:59:36Z","closed_at":null,"author_association":"MEMBER","body":"We could use: `https://w3id.org/credentials/v1` as the base schema, or we could use `https://schema.org/` as the base schema.\r\n\r\nDoing the former enables us to strictly control the base vocabulary. \r\n\r\nDoing the latter enables people to express just about everything in schema.org AND digitally sign it (which could turn into a pretty big use case). The downside of the latter approach means that things might be introduced to schema.org that stomp on our vocabulary.\r\n\r\nThere is a hybrid approach where we still do `https://w3id.org/credentials/v1` and put those terms into schema.org in due course. The problem there being that pure JSON implementations might have to check for both `https://w3id.org/credentials/v1` and `https://schema.org/` and wouldn't be able to reference a static version of schema.org. Another issue may be the overhead when processing the thousands of terms in the schema.org context.\r\n\r\nThoughts?"}}
{"actor":{"display_login":"msporny"}}