Re: i18n review request for the Presentation API

On 2015-08-24 10:24, Matitiahu Allouche wrote:
> I don't see many i18n implications in this API, since i18n will apply to the content which is sent from controllers to presentation displays (and is not governed by this API), while the API addresses the means of managing  connections between controllers and presentations.

That matches my evaluation of the spec, thanks for the confirmation!


>
> One possible item of interest i18n-wise is that presentation session identifiers are limited to alphanumeric ASCII characters (section 6.1). These identifiers are likely to be externalized to human users to allow creation of new sessions or operations on existing sessions. Limiting them to ASCII would not be friendly for many users.

The intent is rather for these session identifiers to remain "internal" identifiers that an application may save from one session to the other using some local storage (IndexedDB, WebStorage, cookie, etc.) to resume a session e.g. when the user navigates from one page to the other in the controlling browser context. Presentation session identifiers are not meant to be presented to users in particular. Now, the spec could benefit from a note to clarify that point, since it is true that they could be presented to users in practice.

I note that the definition and usage of presentation session identifiers may still change in the spec depending on the result of on-going discussions (not related to i18n) within the Second Screen group.

Francois.



>
> --
> Shalom (Regards),  Mati
>
> -----Original Message-----
> From: Francois Daoust [mailto:fd@w3.org]
> Sent: Wednesday, August 19, 2015 6:44 PM
> To: public-i18n-core@w3.org
> Cc: Kostiainen, Anssi
> Subject: i18n review request for the Presentation API
>
> Hello i18n group,
>
> The Second Screen WG has been working on the Presentation API over the last year or so. The Presentation API defines an API to enable web content to access external presentation-type displays and use them for presenting web content.
>
> While not entirely stable yet, the specification already addresses most of the features that the group would like to cover. Now seems like a good time to evaluate the spec from an i18n perspective, so we would like to request review of the spec by the i18n WG.
>
> The latest editor's draft is at:
>
>     http://w3c.github.io/presentation-api/
>
>     (Note the Second Screen WG uses a semi-automated process to push the spec to /TR space on a regular basis)
>
> Logistic-wise, the Second Screen WG uses GitHub issues extensively and would welcome issues flagged with an "i18n" label. We should be able to setup automatic redirections to the www-international@w3.org mailing-list for these issues if needed:
>
>     http://github.com/w3c/presentation-api/issues
>
> We do not have an explicit deadline in mind for the review, but would rather learn about potential new issues before our F2F meeting at TPAC, end of October.
>
> I (or someone else in the group) would be happy to present the ins and outs of the specification in an i18n group call if you think that could be useful. I do not have a clear view of the possible i18n issues such an API may trigger. Of possible interest, the specification deals with a controlling browsing context and a presenting browsing context, which may run on two different devices that do not share the same locales.
>
> Thanks,
> Francois, staff contact, Second Screen WG.
>
>

Received on Monday, 24 August 2015 13:57:11 UTC