-
Notifications
You must be signed in to change notification settings - Fork 32
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
Recipe #103 -- Annotating a Poetry Reading #130
base: master
Are you sure you want to change the base?
Conversation
change minutes to seconds. Co-Authored-By: cjcolvar <[email protected]>
(Automated comment): Branch aviliable for testing at https://preview.iiif.io/cookbook/0103-poetry |
Actually recipe available at: https://preview.iiif.io/cookbook/0103-poetry/recipe/0103-poetry-reading-annotations/ |
Comments on the text:
Comments on the examples:
|
Thanks for your comments Rob. Regarding:
We did discuss this but haven't heard from Harvard if they are happy for us to take a copy of the content so haven't done so. It would be interesting to raise in the TRC what peoples thoughts are on this but is it better to have examples with external content soon or examples with hosted content which may take longer to arrange? For info there was a similar discussion with the Newspapers and thankfully Europeana were OK for us to copy the images but we only copied the first two images and left the last two as remote. |
{ | ||
"id":"{{ id.path }}/canvas/annotation1", | ||
"type":"Annotation", | ||
"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.
Oh this is a difficult one... Is noting a breath taken a comment or a transcription?
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.
but should be an array of values.
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.
Comment. Pretty sure our academic partner calls this "paratext", which I wouldn't call transcription.
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.
Sorry I'm wrong here it should be a string not an array...
{ | ||
"id":"{{ id.path }}/canvas/segment1/annotation/4", | ||
"type":"Annotation", | ||
"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.
Per Rob's comment "Is "her kind" a transcription of the spoken content? If so then it should be motivation supplementing, not commenting. See: https://iiif.io/api/presentation/3.0/#35-values"
Listening to the recording it is a transcription so this should be:
"motivation":["supplementing"]
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'll change this to an array so it matches the IIIF spec rather than the w3c annotation spec.
Commenting is the correct motivation, as below.
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.
Sorry I'm wrong here it should be a string...
{ | ||
"id":"{{ id.path }}/canvas/1/annotation/1", | ||
"type":"Annotation", | ||
"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.
Should this be supplementing as above?
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.
but needs to be an array
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.
Sorry I'm wrong here it should be a string...
{ | ||
"id":"{{ id.path }}/canvas/1/annotation/2", | ||
"type":"Annotation", | ||
"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.
Per Rob's comment "Is "her kind" a transcription of the spoken content? If so then it should be motivation supplementing, not commenting. See: https://iiif.io/api/presentation/3.0/#35-values"
Listening to the recording it is a transcription so this should be:
"motivation":["supplementing"]
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're going to change "her kind" into "repetition of 'her kind'" -- it's meant as commentary on the structure of the poem, rather than a direct transcription. That will clarify 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.
Sorry I'm wrong here it should be a string...
```json | ||
``` | ||
|
||
<a name="annotations"></a>Annotation examples, both a point annotation (at a particular time) and a range annotation (covering a time range). We use the "supplementing" motivation because these annotations are derived from the audio file on the canvas and the "commenting" motivation because the annotations are a comment about the canvas. Annotations must have "supplementing" as a motivation for any annotations derived from the items on the canvas. |
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.
Related to the other changes but Rob's comments:
"The text and example do not line up -- The text says the final example has both supplementing and commenting, whereas it only has commenting. As below, I think it should be only supplementing."
…into 0103-poetry
I'm trying to figure out whether the motivations in this example should be The IIIF spec says,
A scholar who notes when a performer draws a breath or emphasizes a phrase is not really transcribing the poem--especially if the remaining text of the poem is not also represented in the associated annotations--so we're not required to use The spec also gives some hints when it suggests behavior for presenting annotations with a
When presenting these annotations, we hope to see them alongside the media. However, they should not replace the media or be presented over the media: if, for example, these annotations were applied to a video recording of the performance instead of a pure audio recording, we would not want these annotations presented as captions. They function as footnotes to the performance--intended to be linked to particular sections of the media--but don't replace it. Clearly we should not use |
As they're not intended to be transcription, then they're not supplementing. That said, I think the example is a poor one for a recipe due to this confusion. If the authors are confused, then people reading the recipe will be even more confused. |
We'll remove the paragraph about |
Note the build is breaking as it expects the motivation to be a string... so I will need to fix that. |
Changes from the TRC:
Should we break this into 2 recipes; this one would only demonstrate scholarly commentary on audio files; another one would show how annotations can be internal to a manifest OR linked to an external annotation file? |
Changes from today's cookbook meeting:
|
Tasks:
|
Merging Sara's remote copy to the IIIF repo so that it can be built automatically. Original pull request with comments is #107. Original description from Sara: