Re: lang tags on literals

The problem is that this requirement (even if it is a SHOULD) would create problems on the JSON-LD representation, which does not let you use a simple syntax for the language (as turtle does). Ie,

"body" : "simple textual body"

would become

"body" : {
	"text" : "simple textual body",
	"@language" : "en"

which is quite convoluted. And I am not sure how I would explain to a JSON-LD user why adding that "@language" term if "dc:language" is also used.


> On 14 Sep 2015, at 10:20 , Vladimir Alexiev <> wrote:
> and
> don't avail themselves of the opportunity to use lang tags on the text
> literal, and instead use dc:language.
> Using dc:language is a good practice, especially for resources that are not
> a simple text string.
> But I think that for strings, the language should be repeated as a lang tag
> for consistency & completeness.
> (This approach is adopted by Getty LOD, e.g. see
> So for I
> propose:
> - after the phrase "additional properties such as dc:format and dc:language
> should be given if known"
> - add this sentence: "If the language is known, it should also be provided
> as a language tag on the string literal"
> - and add lang tag in the example:
>   rdf:value "content"@en ;
> For, I would
> allow it to be used with a lang tag,
> which will extend this economical representation also for this case, but I
> don't feel strongly about it.
> Cheers!

Ivan Herman, W3C
Digital Publishing Lead
mobile: +31-641044153

Received on Monday, 14 September 2015 09:00:00 UTC