Jon Stroop
Jon Stroop
Based on the Slack convo, what about: > If the appropriate JSON-LD Content-Type header, including a profile parameter, cannot be supplied, then the Content-Type value SHOULD ...
I was not on the discovery call this week, so may have the full picture. > Also, the information really /should/ be at the HTTP transport layer, rather than in...
Editors proposed close. Covered by Change discovery and HTTP.
@IIIF/editors continue to defer pending use cases. Will write to IIIF Discuss later today.
:+1: maybe there will be a lull in spec work (hah!) after prezi and image 2.1, and search and auth 1.0.
Use case here: https://github.com/IIIF/api/issues/1777#issuecomment-462977980 > Finally, a text version should be provided for screen readers so that all users are aware of the content and purpose of the image.
Some text that is more descriptive than `label` seems like it could go with a logo, or **any other** image or a/v content for that matter
Isn't part of the level 0 use case that, from a client perspective, one should be able to construct an image request without examining the `info.json`? If so, then `jpg`...
I could see a higher-level document (not really a spec; maybe recipe?) regarding IIIF and analytics best-practices? (Eds. discussed on 15 Apr. 2019)