{"action":"created","issue":{"url":"https://api.github.com/repos/IIIF/iiif.io/issues/620","labels_url":"https://api.github.com/repos/IIIF/iiif.io/issues/620/labels{/name}","comments_url":"https://api.github.com/repos/IIIF/iiif.io/issues/620/comments","events_url":"https://api.github.com/repos/IIIF/iiif.io/issues/620/events","html_url":"https://github.com/IIIF/iiif.io/issues/620","id":120183978,"number":620,"title":"Limiting max height and width that can be requested","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},"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":11,"created_at":"2015-12-03T14:32:18Z","updated_at":"2015-12-09T05:20:41Z","closed_at":null,"body":"See the [thread started by Glen yesterday](https://groups.google.com/forum/#!topic/iiif-discuss/j-tg5F7J6VM). We've heard it before, and I was about to add my own slightly different use case, but @tomcrane has already done so. I'm perfectly happy to give you `full` of anything, but from a practical, systems perspective, I can't do it because the full image is just too large (i.e. scrolls, and some other huge prints we have) and the server will time out.\r\n\r\nYes, practically speaking, if you can get the tiles you can recreate the whole image. However, we've heard enough times now that it would make people comfortable and further adoption if we could find a solution.\r\n\r\nThe cheap solution would be to add a predicate like `fullAvailable: true|false`, and force clients to work with `sizes` to determine what they can get. The better solution, in my opinion, is something like the discussion around #277."},"comment":{"url":"https://api.github.com/repos/IIIF/iiif.io/issues/comments/163112191","html_url":"https://github.com/IIIF/iiif.io/issues/620#issuecomment-163112191","issue_url":"https://api.github.com/repos/IIIF/iiif.io/issues/620","id":163112191,"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},"created_at":"2015-12-09T05:20:41Z","updated_at":"2015-12-09T05:20:41Z","body":"I understand the rationale behind `largestAreaSupported` but I don't think that any use cases support it? The server should provide as much access as possible, and no one has said that they want to restrict access by total pixel count, rather than edge length.\r\n\r\nAnd (at 5:30 this morning :S) I had the realization that what we're talking about I think should be a property of the profile, not of the image.  The /image/ doesn't have a max height and width, the service that provides access to the image has those restrictions in the same way that it can deliver a set of formats, qualities and so forth.\r\n\r\nSo my proposal:\r\n  * Add `maxHeight` and `maxWidth` as OPTIONAL properties in Section 5.3.\r\n  * Maybe add `maxArea` as OPTIONAL in Section 5.3, if there are systems willing to implement\r\n\r\n```\r\n{\r\n  \"profile\" : [\r\n    \"http://iiif.io/api/image/2/level2.json\",\r\n    {\r\n      \"formats\" : [ \"gif\", \"pdf\" ],\r\n      \"qualities\" : [ \"color\", \"gray\" ],\r\n      \"maxHeight\": 2048,\r\n      \"maxWidth\": 2048\r\n    }\r\n  ]\r\n}\r\n```\r\n\r\n\r\n"}}