Skip to content
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

Open
glenrobson opened this issue Jun 12, 2024 · 9 comments
Open

Recipe #346: Annotating in Multiple Languages #126

glenrobson opened this issue Jun 12, 2024 · 9 comments
Assignees
Labels

Comments

@glenrobson
Copy link
Member

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.

@stephenwf
Copy link

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/)

@triplingual
Copy link

@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?

@zimeon
Copy link
Member

zimeon commented Jun 13, 2024

+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:

You would like to make [a] text annotations in multiple language[s] translations on an image. Because the annotations are semantically equivalent, the expectation is that the user or client would choose which translation[language] to display for the annotation.

@stephenwf
Copy link

@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.

@triplingual
Copy link

@stephenwf I see where you are coming from now. Thank you for writing the crux of the next recipe. 😉
But seriously, I think it would benefit client/viewer devs to spell out in a new recipe the ways this is different so they can think in a sophisticated way about how to code for the ways. Remains to decide then, whether the recipe in this TRC issue should get text carving out a tag from the pattern. I'll leave that up to the community, as it's an easyish textual addition, possibly in Restrictions. I will be unable to make the TRC call on the 19th and Glen will present in my stead.

@triplingual
Copy link

@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.

@glenrobson
Copy link
Member Author

glenrobson commented Jun 19, 2024

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.

@glenrobson
Copy link
Member Author

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]
0: 0 []
-1: 0 []
Not TRC: 0 []
Ineligible: 1 [mixterj]

Result: 15 / 15 = 1.00

Super majority is in favor, issue is approved

@triplingual
Copy link

Cx/changes to make

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

No branches or pull requests

4 participants