Recipe #346: Annotating in Multiple Languages about trc

[glenrobson]

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.

[zimeon]

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

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]

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

[stephenwf]

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

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

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

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