Original author: jasn...@gmail.com (April 05, 2012 21:04:34)
SPECIFICATION BUGS ONLY - Description=====================================
RFC 4647 defines a standard format for language tags and ranges for matching. These are pretty straightforward to use. We should be using those instead of separate language and country codes...
e.g. instead of <Locale language="en" country="US" /> it would be something like <Locale for="en-US-*" /> ... much more concise...
Likewise, when using proxied content, the spec currently says that the container can put country and lang attributes as querystrings in the request... why? Why not use Accept-Language instead?
That way we don't have to muck around with the querystring for these items.
Document affected:==================1.) Please attach a patch for the document if appropriate.2.) Post a thread athttp://groups.google.com/group/opensocial-and-gadgets-spec/topicslinking to this issue report.3.) Post a comment on this issue, linking back to the thread.
Original author: jasn...@gmail.com (April 05, 2012 21:04:34)
SPECIFICATION BUGS ONLY - Description ===================================== RFC 4647 defines a standard format for language tags and ranges for matching. These are pretty straightforward to use. We should be using those instead of separate language and country codes...
e.g. instead of <Locale language="en" country="US" /> it would be something like <Locale for="en-US-*" /> ... much more concise...
Likewise, when using proxied content, the spec currently says that the container can put country and lang attributes as querystrings in the request... why? Why not use Accept-Language instead?
e.g. instead of sending http://example.org/foo?lang=en&country=US ... why not send
GET /foo HTTP/1.1 Accept-Language: en-US
That way we don't have to muck around with the querystring for these items.
Document affected: ================== 1.) Please attach a patch for the document if appropriate. 2.) Post a thread at http://groups.google.com/group/opensocial-and-gadgets-spec/topics linking to this issue report. 3.) Post a comment on this issue, linking back to the thread.
Original issue: http://code.google.com/p/opensocial-resources/issues/detail?id=1290