-
Notifications
You must be signed in to change notification settings - Fork 1
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 #346: Annotating in Multiple Languages #126
Comments
Would this be the same if you wanted a label with multiple languages on a tag? (https://preview.iiif.io/cookbook/0346-multilingual-annotation-body/recipe/0258-tagging-external-resource/) |
@stephenwf That's a good question, and a possibility for a recipe on its own. I also think the W3C model's guidance is substantially the same, as from the model's standpoint a tag is just a particular kind of annotation. There's often something I'm overlooking, though, so say more? |
+1 overall but I would be inclined to have the intro just talk about things in different languages rather than about translations (implying a process that likely doesn't apply at least one version). Perhaps:
|
@triplingual A tag is a combination of a link and a textual body - so a viewer might miss that the link and the Choice body (from this recipe) make a single tag. {
"type": "SpecificResource",
"source": "http://www.wikidata.org/entity/Q18624915"
},
{
"type": "TextualBody",
"value": "Gänseliesel-Brunnen",
"format": "text/plain",
"language": "de"
} Which could be: {
"type": "SpecificResource",
"source": "http://www.wikidata.org/entity/Q18624915"
},
{
"type": "Choice",
"items": [
{
"type": "TextualBody",
"value": "Gänseliesel-Brunnen",
"language": "de",
"format": "text/plain"
},
{
"type": "TextualBody",
"value": "Gänseliesel fountain",
"language": "en",
"format": "text/plain"
}
]
} With the addition of this new recipe. |
@stephenwf I see where you are coming from now. Thank you for writing the crux of the next recipe. 😉 |
@zimeon Good point about noting that in the use case exemplified in the recipe there is a reference language, necessarily not a translation. It also makes the use case slightly more generalizable because it then covers a situation where there are multiple reference languages. |
TRC Group support a seperate recipe for multilingual labels with tagging. Would be useful to update: https://preview.iiif.io/cookbook/0346-multilingual-annotation-body/recipe/0118-multivalue/ to mention this new recipe. |
Issue 126 (Recipe #346: Annotating in Multiple Languages)+1: 15 [akrishnan15 cubap danieltbrennan glenrobson irv julsraemy kirschbombe ksclarke mikeapp nfreire regisrob robcast tpendragon tristanr-cogapp zimeon] Result: 15 / 15 = 1.00Super majority is in favor, issue is approved |
Cx/changes to make
|
Links
Background and Summary
This recipe looks at how to annotate an image with a body with two languages. IIIF uses the Web Annotation Data Model for annotations so the way of denoting langauge is different to the typcial language map used with IIIF properties.
Voting and changes
We welcome comments on the recipe and as well as voting +1, confused face or -1 feel free to add comments to this issue. If this issue is approved then the author will take account of the comments before we merge the branch in to the master cookbook branch.
If the recipe is rejected by the TRC then we will make the changes requested and resubmit it to a future TRC meeting. If you feel that your comments are substantial enough that the recipe should be looked at again by the TRC after the changes have been made please vote -1 (thumbs down). A confused face is treated as abstaining.
Changes to the recipe will only be made after the TRC voting process has concluded.
The text was updated successfully, but these errors were encountered: