Subject: XLIFF TC Call - Apr-3-2012 - Summary
XLIFF TC Call - April 3rd 2012 - Summary === 1/ Roll call Present: Lucia, Rodolfo, Shirley, Tom, Victor, Arle, Asanka, Bryan, DavidW, Fredrik, Helena, Ingo, Joachim, Klemens, Steven, Jung, DavidF, Christian. Regrets: Paul === 2/ Approve Tuesday, 20 March 2012 meeting minutes: http://lists.oasis-open.org/archives/xliff/201203/msg00076.html Bryan moves to approve the minutes Arle, Rodolfo second No objections. === 3/ XLIFF 2.0 (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking) Reference implementation: Rodolfo: want to pass ownership to someone else Yves: could take it DavidF: could split reference implementation and validation tool Bryan: Yves to get R30 and Rodolfo get new feature for a validation tool Christian: would need explanation of validation tool would do. Rodolfo: same as XLIFF-Checker. Christian: we may need more in term of definition (i.e. what is checked) Also what goes into schema vs tool-only Fredrik: also maybe to supply two files and validate the modifications Rodolfo, DavidF: +1 DavidF: Propose to have a formal ballot Bryan: This is different than what we did in the past. Rodolfo: sure, I will add the item in the wiki DavidF: proposed this because R30 was approved already Bryan: fine, we just need to make sure the item is clear Christian: I would also like to see a definition of "Reference Implementation" Rodolfo: yes, will add a proposed feature in the wiki. ACTIOn ITEM: Yves to take ownership of R30 (done by Rodolfo, thanks) --- 1. Features proposed and seconded between meetings via mailing list, and features mentioned c. String length constraint (should be added to wiki) http://lists.oasis-open.org/archives/xliff/201202/msg00059.html Fredrik: we need an attribute (or more) for this. Rodolfo: just characters should be fine. Fredrik: we do use plugins to test other units DavidF: this is example of a basic functionality with extended facility needed too. Propose that Fredrik define the feature in the wiki Fredrik: advance support could be supported with extensibility. But what should we have for the basic feature? Just chars? Bryan: 1.2 tend to try to provide too much, in general the smaller the picklist the better Rodolfo: yes, just char should be enough for the basic feature. DavidF: what about bytes Rodolfo, Arle: Unicode chars better Joachim: fullwidth vs normal may be different? Fredrik, Rodolfo: too much maybe. Helena: you are mixing processing and display Fredrik: for length check it may be important Helena: is it for display or for process/buffer? Steven: Simplest is to count Unicode chars (so max length for the process) Helena: what the char is (zero-width, etc.) is for the tool to decide Arle: MLW-LT is also looking at this. Interoperability would be nice. Joachim: just Unicode char count would be the easiest. Rendering length would need more (font, etc.) Fredrik: just counting code-point may not be useful Rodolfo: let's describe the feature in the wiki Arle: two use cases: UI and DB (rendering and buffer/process) Fredrik: buffer length also need encoding info Helena: trying to understand the user scenario Could use average size by char in most cases Knowing length by code point gives a starting point Joachim: agree we won't have a full solution for all cases Fredrik: not sure if I like the proposed feature That feature is in 1.2 and is used, but it's not in 2.0 It needs to be resolved in 2.0 Could drop it too Joachim: but production would need it. Bryan: a proposed feature in the wiki could be a good starting point Just need to see what use cases are possible and which one we want 2.0 to support Use of wiki: Bryan: will try to create a video to explain how to use the wiki d. Attributes for translation candidates http://lists.oasis-open.org/archives/xliff/201202/msg00082.html Helena: Yves, I want to follow up on the "translation candidate attribute" thread off line. Will do by email. --- 3. XLIFF 2.0 Technical issues (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#TechnicalIssuesforXLIFF2.0) a. Source read-only or not? (http://lists.oasis-open.org/archives/xliff/201204/msg00004.html) Rodolfo: seems source does not need to be read-only Bryan: some aspects may need discussion in Inline Markup SC. === 4/ Sub Committee Reports --- 1. Inline text (Yves) No meeting. Not much to report on. Will have a face-to-face meeting in Dublin on June-14/15 --- 2. XLIFF Promotion and Liaison SC Charter (David) No SC meeting today. XLIFF symposium for 15-17 Oct as pre-event of LocWorld Federated event with LocWorld, MLW-LT and ULI Call for volunteers for the review committee (to review proposal) a. David formally proposes to create a formal liaison with MultilingualWeb-LT and nominate Arle Lommel to serve as the first XLIFF TC liaison on MultilingualWeb-LT (http://lists.oasis-open.org/archives/xliff/201203/msg00091.html On Mar-29 I move to have that vote. Joachim seconded today. Christian: proposal is to liaise with W3C WG or the MLW-LT project? DavidF: the W3C WG Christian: would imagine the W3C has rules for these liaisons DavidF: W3C is clear for this. The WG has dependency to XLIFF in charter Liaison from XLIFF TC -> WG is decided by TC. Bryan: responsibility of Arle/davidF to make sure the liaison follows rules b. XLIFF support in CAT tools Survey (http://lists.oasis-open.org/archives/xliff/201204/msg00001.html) Lucia started the new questionnaire We have already some answers completed Should get info from most no-show of previous round Arle: anyone interested in LOD or MLW-LT workshop (second week of June in Dublin) should contact Arle. === 5/ Current XLIFF business Note: moved XLIFF, TM, Glossary, Segmentation and Using other standards off current business agenda (assume they are covered on wiki proposed featutres and inline text SC). If my assumption is incorrect - please let me know. --- 1. Normalized the state values in wiki http://lists.oasis-open.org/archives/xliff/201203/msg00045.html Bryan: make sure to look at wiki for the changes. Should help to get final approval later on. --- 3. Proposed OASIS XLIFF TC liaison with MultilingualWeb-LT (David) http://lists.oasis-open.org/archives/xliff/201203/msg00066.html This one is done. === 6/ New Business None.