- From: Ivan Herman <ivan@w3.org>
- Date: Thu, 8 Sep 2011 09:41:37 +0200
- To: Thomas Steiner <tomac@google.com>
- Cc: Niklas Lindström <lindstream@gmail.com>, public-linked-json@w3.org
On Sep 8, 2011, at 09:22 , Thomas Steiner wrote:
> Niklas, all,
>
> I think this is a very reasonable suggestion. Being able to declare
> the default language can be very valuable. I believe we should go with
> the simplest solution, which is your solution 1.
+1. That approach is pretty much known by most of the people, no need for extra mental cycles to understand it...
Ivan
> We could align
> ourselves with the way you declare languages in (X)HTML [1], where you
> can declare the language on the top level of the document (<html
> lang="en">). Personally I'm also a big friend of HTTP headers
> (remember the @context discussion?) to keep the actual payload clean,
> so I could also imagine an HTTP header like "Content-Language: en".
> The overall opinion with @context was that HTTP headers are not
> considered the most suitable solution for a number of reasons. Long
> story short, your solution 1 ({…, "@language": "en",…}) works perfect
> for the needs I see.
>
> Best,
> Tom
>
> [1] http://www.w3.org/International/tutorials/language-decl/
>
> --
> Thomas Steiner, Research Scientist, Google Inc.
> http://blog.tomayac.com, http://twitter.com/tomayac
>
----
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 Thursday, 8 September 2011 07:41:46 UTC