New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fragment selectors or fragment-URI shortcuts when annotating images onto canvas? #1338
Comments
Impacts #1332 as the fragment selector would be more compatible with the proposed AudioTrackSelector as well as the regular SvgSelector. |
Consensus on AV call of 2018-02-06, and Editors on 2018-02-07 was that the selector model should be recommended but not required, and the fragment URI pattern documented as also possible. |
I think this needs further discussion in light of #1386 |
IIIF AV Meeting: Use the full form in examples, and explain that the hash-fragment URI form MAY be used. |
In 5.5 Annotations? |
Given that we're only talking about Canvas annotations, and we have #1386, I think they it can go into Canvas. See the (currently not written, but a bright place holder) block in: |
Closed by #1500 |
In Web Annotation, fragment selectors are the RECOMMENDED way to reference a fragment. Should this be the IIIF RECOMMENDED way to paint onto a portion of the canvas (and use fragments in annotations in other places)? If so then I'd assume a direct URI-with-fragment-ed would also be allowed (per Web Annnotation) OR Is this all too long winded, we we instead profile Web Annotation to say that the short URI-with-fragment-ed form SHOULD or MUST be used?
Taking a short version of the second example from http://iiif.io/api/presentation/2.1/#segments:
we would in Presentation 3 have the following if we follow the RECOMMENDED fragment selector form:
The text was updated successfully, but these errors were encountered: