W3C home > Mailing lists > Public > public-i18n-its-ig@w3.org > July 2011

RE: ITS Teleconference - Jul-26-2011 - Summary

From: Yves Savourel <ysavourel@translate.com>
Date: Tue, 26 Jul 2011 17:39:37 +0200
To: <public-i18n-its-ig@w3.org>
Message-ID: <assp.0188569441.assp.018897bb0f.007e01cc4baa$3b083960$b118ac20$@com>
ITS IG Teleconference on Tuesday Jul-26-2011 - Summary

The session was exceptionally held at 4pm CEST for practical reasons.
Jirka was present at the 5pm normal call.
(his report on the HTML5 bug are included below).

Presents at 4pm: Ingo, Yves, Christian
Present at 5pm: Jirka, Yves
Regrets: Felix, John Gregory

Last meeting minutes:
(June meeting skipped)

=== ITS-oriented reviews of XML specifications

--- MIME type:
Still waiting for an answer.
Nothing news on this.
Still nothing new.

Need to escalate this topic. Yves to talk to Felix about the next step could be.

--- HTML5
Jirka has logged an issue with HTML5 for the lack of translatability flag:
See thread here: http://www.w3.org/Bugs/Public/show_bug.cgi?id=12417

Jirka reported the proposal refused.

Jirka has re-opened the bug:
See Richard's new comment on the differences in how "dont-translate" feature is supported by Google and Microsoft as example:

Yves: The HTML5 answer is really flawed.
Encourage people to read the thread and participate to it.

--- XLIFF 2.0
Possible discussion on usage of ITS in XLIFF 2.0 for example for translate, simpleNote, term, etc.
(when is it appropriate, when is it possible, how to integrate it, etc.) See some of the discussion here:
http://lists.oasis-open.org/archives/xliff/201107/msg00014.html (and thread)

Summary: in XLIFF 2.0 discussion was a proposal to use a simple note.
Christian proposed to use ITS to do this. (its:locNote).
Yves noted that this may not work too well because of XPath.
Felix then précised Christian's input: The idea is to implement the same semantic, using an XLIFF-specific implementation.
Christian may make a proposal to the XLIFF TC following this line of thought.

Yves: What about other features?
Christian: Same idea, trying to implement the data category, no necessarily the default ITS implementation.
Trying to always use the best practices may be able to take advantage of ITS-based libraries.

=== ITS Rules repository

No new rules added.

Yves: We may want to add XLIFF 2.0 rule file there at some point.

=== ITS General issues

--- Context data category
Should go there:
ACTION ITEM: Felix to talk to RDFa WG about "context data category" mechanism
-> pending.

Christian summarized the proposal
Idea is to use well-defined things like namespace-based values or MIME-type-like mechanism for the values
Allowing extensibility and standardization.

New ACTION ITEM: Christian to continue working on this data-category.
Ingo to look at it as well.

--- Idea for a "localeSpecificContent" data category.
ACTION ITEM: Christian to update the "locale specific content" text so that it reflects the difference to xml:lang
-> Done.

Christian summarized the proposal.
Idea is to annotated content meant for a given locale.

New ACTION ITEM: Christian to include the notes from Felix feedback.

--- Permission for inline codes
ACTION ITEM: Yves to draft an extension for setting permission (clone/delete/etc.) in ITS inline codes.
--> In progress.
See categories here: http://wiki.oasis-open.org/xliff/OneContentModel/Draft
No notation proposal yet.

--- Transliteration
Shaun McCance inquired about how to provide information for text to only transliterate See http://lists.w3.org/Archives/Public/public-i18n-its-ig/2011May/0001.html
ACTION ITEM: Christian to turn the discussion surrounding the "transliteration / NLP content" into a proposal.
-> Done.
Note: possible notation for transliteration http://tools.ietf.org/html/draft-davis-t-langtag-ext-03 (updated link)
Side topic: possible concerns about the language tag becoming overly complex and covering different domain.

Christian summarized the proposal.
Idea is to provide a way to identify the type of process to be done/allowed on a content.
Concepts not all clear yet.

Yves: No clear how the t extension of UTS35 would help as this is one source to many targets case.

=== Any Other Business?

--- ITS-based filters used to convert data to Moses Inline Text format for MT processing.
ACTION ITEM: Yves to write blurb about it and send it to Richard.
--> Not done yet.

--- Presentation on ITS work for Multilingual Web event at Limerick was accepted.
Christian to provide a draft.

=== Next teleconference is Aug-23

Received on Tuesday, 26 July 2011 15:40:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:11:28 UTC