-
Notifications
You must be signed in to change notification settings - Fork 32
Recipe #103 -- Annotating a Poetry Reading #107
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
Conversation
Manifest validates OK with new 3.0 validator: https://iiif.io/api/presentation/validator/service/validate?url=https://raw.githubusercontent.com/IIIF/cookbook-recipes/1ab053f8abb678488b86b9b1ecf98681f35b58c4/recipe/0103-poetry-reading-annotations/manifest1.json&version=3.0 (Probably more of a test for my validator code :-)). |
change minutes to seconds. Co-Authored-By: cjcolvar <[email protected]>
The annotations should be part of the Canvas, not the Manifest. |
Add frontmatter for tags and summary, similar to PR #110 :
Use "annotations" "audio" for our tags. |
Replace URLs with magic URLs for IDs.
|
annotation motivation should be an array. -- actually, the W3C annotation spec doesn't enforce this, so arguably it could be an array or not an array. |
Where we use "RangeSelector" for the annotation target, we could instead use Media Fragments "#t=1.23,2.23" appended to the canvas URL. Instead of "source" you'd condense it into the "target" field. |
Ok, I believe this is ready for a final review and sponsorship to the TRC.
@glenrobson Would you look at #3 above and make sure this gets "processed" appropriately -- organizationally and technically? Thanks! |
Is there a reason that the Canvases have URIs that end in I think it would be good to remove all the |
I think that is a mistake in my search/replace for the magic URLs. I'll fix it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should merge this one: #130 which contains the latest jekyll variables.
Adding comment to ensure this isn't merged by mistake.
Moving this work to #130 so closing this pull request. Please comment on 130. |
|
||
is correct, but unusual for a IIIF resource. It could also be expressed (and must be if there is more than one motivation) as follows: | ||
|
||
`"motivation": ["commenting"],` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the IIIF spec requires arrays for motivations, should we remove this implementation note altogether?
An initial attempt at a IIIF v3 manifest with annotations on an audio file.
This needs to be updated with github pages references instead of raw github references to our repo, but I think that's a chicken & egg problem that will be fixed after merging (by whom?)
Discussion here or in the IIIF AV Slack channel.