W3C home > Mailing lists > Public > public-linked-json@w3.org > September 2011

Re: Compact forms of language literals

From: Gregg Kellogg <gregg@kellogg-assoc.com>
Date: Mon, 12 Sep 2011 11:21:40 -0400
To: Ivan Herman <ivan@w3.org>
CC: Markus Lanthaler <markus.lanthaler@gmx.net>, "public-linked-json@w3.org" <public-linked-json@w3.org>
Message-ID: <9529E703-7401-4581-88AA-376621616E75@kellogg-assoc.com>
+1, I had mistakenly read the example as putting it @context, this is where it should go,

Also, as with other stuff in @context, it applies through all sub-nodes, unless overridden by another definition. (@language = null might clear a setting.

Gregg Kellogg

Sent from my iPad

On Sep 12, 2011, at 1:11 AM, "Ivan Herman" <ivan@w3.org> wrote:

> 
> On Sep 11, 2011, at 23:27 , Markus Lanthaler wrote:
> 
>>> 1. Add JSON-LD support for declaring a document-wide language
>>> directive (within the context or at the top level, i.e. where
>>> "@context" and the optional "@base" appear). This is for scenarios
>>> where there is one dominant language for a given resource.
>>> 
>>> This would enable us to use @language like this:
>>> 
>>> {
>>>   "@context": ...,
>>>   "@language": "en",
>>>   "@subject": "http://example.org/",
>>>   "title": "The Example"
>>> }
>> 
>> +1 but perhaps we should move @language into the context description. The
>> "meaning" of the document is described in the context so I think that's the
>> place to be for the @language tag as well.
> 
> I would also feel it more natural if this was part of the @context. It would also make it clear/clean that children of a node would inherit the language setting, just like any other contextual settings.
> 
> Ivan
> 
> 
>> 
>> 
>> 
>> --
>> Markus Lanthaler
>> @markuslanthaler
>> 
>> 
>> 
>> 
> 
> 
> ----
> Ivan Herman, W3C Semantic Web Activity Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> PGP Key: http://www.ivan-herman.net/pgpkey.html
> FOAF: http://www.ivan-herman.net/foaf.rdf
> 
> 
> 
> 
> 
> 
Received on Monday, 12 September 2011 15:21:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:32 UTC