- From: Ben <ben@thatmustbe.me>
- Date: Thu, 22 Oct 2015 10:13:45 -0400
- To: Sandro Hawke <sandro@w3.org>
- Cc: Social Web Working Group <public-socialweb@w3.org>
The most pertinent piece is the Language section.
Based on that I would say that the <property>Map, etc is the wrong way to go.
There is actually nothing that says about giving multiple languages at
the same time to any piece of data, just that you label and can
request certain languages.
for example something like this..
{
...
"@lang": "en",
displayName: {
"@lang": "jp",
"text": "nihongo de posuto"
}
"content": "I made the title in japanese!"
....
}
It would also effect the API in that there should be an option to
submit a preference of language,
though there really is no requirement to actually respond in the
preferred language.
On Thu, Oct 22, 2015 at 8:50 AM, Sandro Hawke <sandro@w3.org> wrote:
> There's finally a first draft of W3C expertise on how to design technologies
> which are suitably international
>
> http://www.w3.org/International/techniques/developing-specs-dynamic
>
> It would be splendid for someone to go through this thinking of AS2.
>
> -- Sandro
>
Received on Thursday, 22 October 2015 14:14:14 UTC