mlw-lt-track-ISSUE-45 (its-api-for-html5): Do we need an ITS API for HTML5?

mlw-lt-track-ISSUE-45 (its-api-for-html5): Do we need an ITS API for HTML5?

http://www.w3.org/International/multilingualweb/lt/track/issues/45

Raised by: Felix Sasaki
On product: 

We had discussed this before, and I assume that most of the people would say: no. ITS processing is done outside of the browser, or very different things happen to the same data category (e.g. "translate": do MT, do pseudo translate, transform to XLIFF; ...) so why having an API for HTML5?

One answer might be: making it easier to create applications in the browser based on ITS. For these, having just one method that takes an element / attribute node as an input and gives back ITS information would be helpful.

Also I would like to create some working group consensus on this before or meeting with the HTML working group in Lyon.

Received on Tuesday, 21 August 2012 14:39:52 UTC