{"action":"created","issue":{"url":"https://api.github.com/repos/gbv/daiaspec/issues/13","labels_url":"https://api.github.com/repos/gbv/daiaspec/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/gbv/daiaspec/issues/13/comments","events_url":"https://api.github.com/repos/gbv/daiaspec/issues/13/events","html_url":"https://github.com/gbv/daiaspec/issues/13","id":64751706,"number":13,"title":"Require query-URI == document-URI","user":{"login":"lahmann","id":7081217,"avatar_url":"https://avatars.githubusercontent.com/u/7081217?v=3","gravatar_id":"","url":"https://api.github.com/users/lahmann","html_url":"https://github.com/lahmann","followers_url":"https://api.github.com/users/lahmann/followers","following_url":"https://api.github.com/users/lahmann/following{/other_user}","gists_url":"https://api.github.com/users/lahmann/gists{/gist_id}","starred_url":"https://api.github.com/users/lahmann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lahmann/subscriptions","organizations_url":"https://api.github.com/users/lahmann/orgs","repos_url":"https://api.github.com/users/lahmann/repos","events_url":"https://api.github.com/users/lahmann/events{/privacy}","received_events_url":"https://api.github.com/users/lahmann/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-03-27T12:16:18Z","updated_at":"2015-04-02T12:28:25Z","closed_at":null,"body":"During the implementation of a VuFind DAIA driver (see https://github.com/vufind-org/vufind/pull/327) capable of querying multiple IDs (as specified in http://gbv.github.io/daiaspec/daia.html#query-api) separated by \"|\" we came upon the issue that the current DAIA specification is not strict on the relationship between the queried URI and the URI(s) in the response document as some implementations of DAIA services provide a URI for the document-id that differs from the queried URI.\r\n\r\nThis makes it impossible to identify the documents in the response with the queried IDs. It also implies that any response from a DAIA service contains the availability information for the queried URI even though the response contains a document that does not show any relationship to the queried URI (apart from being the server's response to that queried URI). This disqualifies the DAIA response as an information base for placing holdings etc..\r\n\r\nTherefore it is suggested to require that the document id corresponds with the queried URI, identifying the document-element as being the document with the availability information for that specific URI."},"comment":{"url":"https://api.github.com/repos/gbv/daiaspec/issues/comments/88883142","html_url":"https://github.com/gbv/daiaspec/issues/13#issuecomment-88883142","issue_url":"https://api.github.com/repos/gbv/daiaspec/issues/13","id":88883142,"user":{"login":"dmj","id":58969,"avatar_url":"https://avatars.githubusercontent.com/u/58969?v=3","gravatar_id":"","url":"https://api.github.com/users/dmj","html_url":"https://github.com/dmj","followers_url":"https://api.github.com/users/dmj/followers","following_url":"https://api.github.com/users/dmj/following{/other_user}","gists_url":"https://api.github.com/users/dmj/gists{/gist_id}","starred_url":"https://api.github.com/users/dmj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dmj/subscriptions","organizations_url":"https://api.github.com/users/dmj/orgs","repos_url":"https://api.github.com/users/dmj/repos","events_url":"https://api.github.com/users/dmj/events{/privacy}","received_events_url":"https://api.github.com/users/dmj/received_events","type":"User","site_admin":false},"created_at":"2015-04-02T12:28:25Z","updated_at":"2015-04-02T12:28:25Z","body":"Re the core of this issue: \"we came upon the issue that the current DAIA specification is not strict on the relationship between the queried URI and the URI(s) in the response document as some implementations of DAIA services provide a URI for the document-id that differs from the queried URI.\"\r\n\r\nI don't see why this is a problem that must be solved on the specification level. Did you ask the provider(s) of the mentioned services why they return different document-ids than requested?"}}