{"action":"created","issue":{"url":"https://api.github.com/repos/inspire-eu-validation/ats-metadata/issues/10","labels_url":"https://api.github.com/repos/inspire-eu-validation/ats-metadata/issues/10/labels{/name}","comments_url":"https://api.github.com/repos/inspire-eu-validation/ats-metadata/issues/10/comments","events_url":"https://api.github.com/repos/inspire-eu-validation/ats-metadata/issues/10/events","html_url":"https://github.com/inspire-eu-validation/ats-metadata/issues/10","id":56843389,"number":10,"title":"A.01.validate.md","user":{"login":"aquaglia","id":550442,"avatar_url":"https://avatars.githubusercontent.com/u/550442?v=3","gravatar_id":"","url":"https://api.github.com/users/aquaglia","html_url":"https://github.com/aquaglia","followers_url":"https://api.github.com/users/aquaglia/followers","following_url":"https://api.github.com/users/aquaglia/following{/other_user}","gists_url":"https://api.github.com/users/aquaglia/gists{/gist_id}","starred_url":"https://api.github.com/users/aquaglia/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aquaglia/subscriptions","organizations_url":"https://api.github.com/users/aquaglia/orgs","repos_url":"https://api.github.com/users/aquaglia/repos","events_url":"https://api.github.com/users/aquaglia/events{/privacy}","received_events_url":"https://api.github.com/users/aquaglia/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/inspire-eu-validation/ats-metadata/labels/help%20wanted","name":"help wanted","color":"159818"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-02-06T17:42:33Z","updated_at":"2015-02-09T10:56:36Z","closed_at":null,"body":"The description of the ATC says:\r\n> Document shall pass schema validation without errors, using one of the following XML schema definitions:\r\n* schemaLocation A\r\n* schemaLocation B\r\n* schemaLocation C\r\n\r\nWe need to specify the criteria to determine which schemaLocation to use.\r\nOtherwise a validator, in order to claim compliance, would have to try A and if it fails B and if it fails C.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/inspire-eu-validation/ats-metadata/issues/comments/73490394","html_url":"https://github.com/inspire-eu-validation/ats-metadata/issues/10#issuecomment-73490394","issue_url":"https://api.github.com/repos/inspire-eu-validation/ats-metadata/issues/10","id":73490394,"user":{"login":"pvgenuchten","id":299829,"avatar_url":"https://avatars.githubusercontent.com/u/299829?v=3","gravatar_id":"","url":"https://api.github.com/users/pvgenuchten","html_url":"https://github.com/pvgenuchten","followers_url":"https://api.github.com/users/pvgenuchten/followers","following_url":"https://api.github.com/users/pvgenuchten/following{/other_user}","gists_url":"https://api.github.com/users/pvgenuchten/gists{/gist_id}","starred_url":"https://api.github.com/users/pvgenuchten/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pvgenuchten/subscriptions","organizations_url":"https://api.github.com/users/pvgenuchten/orgs","repos_url":"https://api.github.com/users/pvgenuchten/repos","events_url":"https://api.github.com/users/pvgenuchten/events{/privacy}","received_events_url":"https://api.github.com/users/pvgenuchten/received_events","type":"User","site_admin":false},"created_at":"2015-02-09T10:56:36Z","updated_at":"2015-02-09T10:56:36Z","body":"@ilkkarinne, it might be the case that in general a namespace is enough to identify a schema, this is not the case in iso-metadata. We have quite some examples of namespace-naming being kept equal, while the underlying schema changed.\r\n\r\nI think at this point we can choose some approaches:\r\n- Develop an algorythm as @aquaglia suggests that will grab the xsd and check if it's similar as the appropriate schema\r\n- Assume some of the other tests in this suite will likely fail if the appropriate schema is not provided, so just check if the document validates against the schema it's advertising to validate against and continue with the other tests\r\n- As approach 2, but additionally, replace the customised schema locations by the appropriate schema locations and validate the document again.\r\n\r\n@ilkkarinne your comment 'makes them completely different from the validator's perspective' suggests that the validator should not validate a metadata document that is based on an extended schema. "}}