Canonical URIs

[jpstroop]

It should be possible for a client to request an image and avoid any potential redirects. Furthermore, level 0 implementations may only have one URI that 'works'.

• Should we recommend adding rel=canonical to the Link header? And if so, to what?
• Need a recommendation on float v int for rotation
• What about the #level0 case (all static images)
• Canonical URI should prefer pixels over pct, due to:
  • The pct:50 problem with odd pixel dimensions as a justification
  • And floating point percents being inaccurate

Region canonical = ‘full’ if the whole thing else pixels, and never pct
Size canonical = full if the native size else w,h
Rotation canonical = 0 (as integer if possible, trim trailing zeros if decimal)
Quality = native if native is what you requested, else lower format is required

Add link header with rel="canonical"

[jpstroop]

See

https://github.com/IIIF/specifications/blob/master/image_api/image_api_1.2.md#47-canonical-uri-syntax

We made a decent pass at this in CPH, so promoting to ready for review.

[zimeon]

c.f. issue #5 discussion: should we remove "(those conforming to level 0 only)" so as not to mention the levels?

suggest expanding "a 404" to "an HTTP 404 Not Found response"

otherwise +1

[azaroth42]

+1 to both suggestions

On Tue, Mar 4, 2014 at 12:45 PM, Simeon Warner notifications@github.comwrote:

c.f. issue #5 https://github.com/IIIF/specifications/issues/5discussion: should we remove "(those conforming to level 0 only)" so as not
to mention the levels?

suggest expanding "a 404" to "an HTTP 404 Not Found response"

otherwise +1

Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-36665476
.

[jpstroop]

Yup. Consistency++
Sorry I haven't been online much! Planning on giving some time to IIIF
on Thursday.