{"action":"created","issue":{"url":"https://api.github.com/repos/IIIF/iiif.io/issues/621","labels_url":"https://api.github.com/repos/IIIF/iiif.io/issues/621/labels{/name}","comments_url":"https://api.github.com/repos/IIIF/iiif.io/issues/621/comments","events_url":"https://api.github.com/repos/IIIF/iiif.io/issues/621/events","html_url":"https://github.com/IIIF/iiif.io/issues/621","id":120247745,"number":621,"title":"Cannot generate valid info.json if full/full is not supported","user":{"login":"azaroth42","id":871868,"avatar_url":"https://avatars.githubusercontent.com/u/871868?v=3","gravatar_id":"","url":"https://api.github.com/users/azaroth42","html_url":"https://github.com/azaroth42","followers_url":"https://api.github.com/users/azaroth42/followers","following_url":"https://api.github.com/users/azaroth42/following{/other_user}","gists_url":"https://api.github.com/users/azaroth42/gists{/gist_id}","starred_url":"https://api.github.com/users/azaroth42/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/azaroth42/subscriptions","organizations_url":"https://api.github.com/users/azaroth42/orgs","repos_url":"https://api.github.com/users/azaroth42/repos","events_url":"https://api.github.com/users/azaroth42/events{/privacy}","received_events_url":"https://api.github.com/users/azaroth42/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/IIIF/iiif.io/labels/image","name":"image","color":"207de5"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-12-03T19:18:55Z","updated_at":"2015-12-03T21:45:36Z","closed_at":null,"body":"__Issue:__\r\nAs per #620, some images cannot be delivered at full/full for policy and/or technical reasons.  The lowest level of requirements for compliance with the Image API (level 0) requires support for full size and full region.  The first profile in the info.json profile list MUST be a compliance URI. Thus the images where full/full cannot be delivered cannot be described using info.json\r\n\r\n__Proposal:__\r\nThe minimal fix to this (IMO) bug is to introduce a null compliance URI (level null? level -1? level custom?) that has no requirements at all. Then the actual capabilities for the image would need to be described in a separate profile object.\r\n"},"comment":{"url":"https://api.github.com/repos/IIIF/iiif.io/issues/comments/161794046","html_url":"https://github.com/IIIF/iiif.io/issues/621#issuecomment-161794046","issue_url":"https://api.github.com/repos/IIIF/iiif.io/issues/621","id":161794046,"user":{"login":"jpstroop","id":999701,"avatar_url":"https://avatars.githubusercontent.com/u/999701?v=3","gravatar_id":"","url":"https://api.github.com/users/jpstroop","html_url":"https://github.com/jpstroop","followers_url":"https://api.github.com/users/jpstroop/followers","following_url":"https://api.github.com/users/jpstroop/following{/other_user}","gists_url":"https://api.github.com/users/jpstroop/gists{/gist_id}","starred_url":"https://api.github.com/users/jpstroop/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jpstroop/subscriptions","organizations_url":"https://api.github.com/users/jpstroop/orgs","repos_url":"https://api.github.com/users/jpstroop/repos","events_url":"https://api.github.com/users/jpstroop/events{/privacy}","received_events_url":"https://api.github.com/users/jpstroop/received_events","type":"User","site_admin":false},"created_at":"2015-12-03T21:45:36Z","updated_at":"2015-12-03T21:45:36Z","body":"Having to declare level null (or whatever) and then enumerate every feature the server supports (in the case of Loris that's _every_ feature), and having to do it only when images are, at least in my use case, above a certain size threshold, seems very heavy-handed."}}