{"action":"opened","issue":{"url":"https://api.github.com/repos/OSLC/oslc-client/issues/21","repository_url":"https://api.github.com/repos/OSLC/oslc-client","labels_url":"https://api.github.com/repos/OSLC/oslc-client/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/OSLC/oslc-client/issues/21/comments","events_url":"https://api.github.com/repos/OSLC/oslc-client/issues/21/events","html_url":"https://github.com/OSLC/oslc-client/issues/21","id":359137408,"node_id":"MDU6SXNzdWUzNTkxMzc0MDg=","number":21,"title":"OSLCResource might be the result of a query","user":{"login":"jamsden","id":1114794,"node_id":"MDQ6VXNlcjExMTQ3OTQ=","avatar_url":"https://avatars2.githubusercontent.com/u/1114794?v=4","gravatar_id":"","url":"https://api.github.com/users/jamsden","html_url":"https://github.com/jamsden","followers_url":"https://api.github.com/users/jamsden/followers","following_url":"https://api.github.com/users/jamsden/following{/other_user}","gists_url":"https://api.github.com/users/jamsden/gists{/gist_id}","starred_url":"https://api.github.com/users/jamsden/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jamsden/subscriptions","organizations_url":"https://api.github.com/users/jamsden/orgs","repos_url":"https://api.github.com/users/jamsden/repos","events_url":"https://api.github.com/users/jamsden/events{/privacy}","received_events_url":"https://api.github.com/users/jamsden/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-09-11T17:04:00Z","updated_at":"2018-09-11T17:04:00Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"So it could contain more than one member, or be a graph that contains more than one RDF subject. So a server.read() might not actually return an OSLC Resource. How should this be handled?\r\n\r\nOSLC 3.0 does introduce LDPCs as potential resources. OSLC Query Capability can return many resources if there's an oslc.select clause. These are not \"OSLC\" resources in that that are defined in an OSLC domain specification and are expected to have an identifier, title, description, etc. as defined by OSLC Core. \r\n\r\nFor now, this implementation assumes that OSLCResource is a resource defined by an OSLC domain vocabulary. a server.read operation on one of these resources would only return one."}}
{"actor":{"display_login":"jamsden"}}