- From: Hugo Manguinhas via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Feb 2016 14:33:05 +0000
- To: public-annotation@w3.org
hugomanguinhas has just created a new issue for
https://github.com/w3c/web-annotation:
== Language Literals not supported within the Body ==
At the moment, the only way to express the language of the text used
as body of the annotation, is to create a Textual Body with a
dc:language property referring to the language. There is also no way
to add a language to a String Body (see 3.2.2.3).
A proposal would be to define oa:bodyText and oa:text as Language
Literals according to the RDF spec, allowing for the Literal to be
explicitly annotated with the language.
Pros:
- In line with the common practice for RDF.
- allow for text in multiple languages.
- the language becomes explicit and not implicit in the model.
Cons:
- an indirection (in JSON-LD) is needed for the text value and
language.
Example 1: a case with a String Body tagged with language "en":
```jsonld
{
"motivation": "commenting",
"bodyText": { "@value": "my useful comment", "@language": "en" },
"target": "http://..."
}
```
Example 2: A Textual Body with a text written in English. In this
situation, there was no need to create the Textual Body, only if for
example a role was needed.
```jsonld
{
"motivation": "commenting",
"body": {
"text": { "@value": "my useful comment", "@language": "en" }
},
"target": "http://..."
}
```
Please view or discuss this issue at
https://github.com/w3c/web-annotation/issues/149 using your GitHub
account
Received on Monday, 8 February 2016 14:33:06 UTC