Skip to content

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

Closed
wants to merge 14 commits into from

Conversation

saracarl
Copy link

@saracarl saracarl commented Oct 28, 2019

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.

@glenrobson
Copy link
Member

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 :-)).

@glenrobson
Copy link
Member

change minutes to seconds.

Co-Authored-By: cjcolvar <[email protected]>
@azaroth42
Copy link
Member

The annotations should be part of the Canvas, not the Manifest.

@saracarl
Copy link
Author

saracarl commented Nov 7, 2019

Add frontmatter for tags and summary, similar to PR #110 :

tags: [video, presentation, opera]
summary: "Complex nested table of contents for an opera."

Use "annotations" "audio" for our tags.

@saracarl
Copy link
Author

saracarl commented Nov 7, 2019

Replace URLs with magic URLs for IDs.
"{{site.url}}/{{site.basurl}}/{{page.path}}"
requires frontmatter in .json files:

---
layout: null
---

@saracarl
Copy link
Author

saracarl commented Nov 7, 2019

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.

@saracarl
Copy link
Author

saracarl commented Nov 7, 2019

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.
We should just document this as an alternative, but not change our example.

@saracarl
Copy link
Author

saracarl commented Nov 11, 2019

Ok, I believe this is ready for a final review and sponsorship to the TRC.
Changes:

  1. Annotations are part of the canvas, not manifest.
  2. Frontmatter with a summary & tags
  3. Magic URL replacement. This needs another build and check because in order to get them looking right I had to use:
    {{site.url}}{{site.baseurl}}/{{page.path}}
    instead of
    {{site.url}}/{{site.baseurl}}/{{page.path}}
    (note the removal of the / between site.url and site.baseurl)
  4. Implementation notes on arrays for annotation motivation and range selector vs media fragments.

@glenrobson Would you look at #3 above and make sure this gets "processed" appropriately -- organizationally and technically? Thanks!

@azaroth42
Copy link
Member

Is there a reason that the Canvases have URIs that end in canvas/segment? While they are just opaque URIs, it gives the impression that they're parts of canvases, not the whole thing.

I think it would be good to remove all the segment endings from the canvas URIs.

@saracarl
Copy link
Author

I think that is a mistake in my search/replace for the magic URLs. I'll fix it.

Copy link
Member

@glenrobson glenrobson left a 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.

@glenrobson
Copy link
Member

Moving this work to #130 so closing this pull request. Please comment on 130.

@glenrobson glenrobson closed this Dec 3, 2019

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"],`

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants