RE: i18n review request for the Presentation API

Hello François,

Thank your for the note. I have added your document to our Review Radar [1] and opened a Tracker product that we'll use to collect issues on our side. Issues will be forwarded to your group by creating github issues using the 'i18n' label, as you suggest. If you could please set it up so that these forward to www-international@w3.org, I'd appreciate it.

I'll let you know if additional introduction would be helpful.

Regards (for I18N),

Addison

Addison Phillips
Principal SDE, I18N Architect (Amazon)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.



[1] https://www.w3.org/International/wiki/Review_radar#Current_Reviews


> -----Original Message-----
> From: Francois Daoust [mailto:fd@w3.org]
> Sent: Wednesday, August 19, 2015 8:44 AM
> 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 Wednesday, 19 August 2015 16:47:38 UTC