[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Groups - XLIFF TC Meeting modified
Much gratitude to Yves for taking minutes, and thanks to David for recommending a modification. -- Bryan Schnabel* XLIFF TC Meeting has been modified by Bryan Schnabel* Date: Tuesday, 05 May 2009 Time: 11:00am - 12:00pm ET Event Description: 1/ Call one of the FreeConferenceCall phone numbers: US: (712) 432-1600 US: (605) 772-3100 Austria: 0820 4000 1552 Belgium: 070 35 9974 France: 0826 100 256 Germany: 01805 00 76 09 Ireland: 0818 270 021 Italy: 848 390 156 Netherlands: 0870 001 920 Spain: 902 886025 Switzerland: 0848 560 179 UK: 0870 35 204 74 2/ Enter the Participant Access Code: 737043# Agenda: Agenda: 1/ Roll call 2/ Approve previous meeting minutes: Accept, reject, or amend. http://lists.oasis-open.org/archives/xliff/200904/msg00023.html 3/ Review Common Requirements for elements between TMX and XLIFF (come to consensus on the requirements, then assign owners to propose wording for the spec) (http://wiki.oasis-open.org/xliff/OneContentModel/Requirements?action=show&redirect=Requirements) A. Report on the TMX meeting attended by XLIFF TC invitees B. Christians proposal for next steps (http://lists.oasis-open.org/archives/xliff/200904/msg00017.html) C. Adding an adjacent item not included in the list on the wiki page: issues around SUB (http://lists.oasis-open.org/archives/xliff/200904/msg00005.html) D. Asgeirs thoughts on XLIFF 2.0 in 3D (Testing the friendship between XLIFF and TMX) (http://lists.oasis-open.org/archives/xliff/200904/msg00016.html) 4/ "XLIFF 2.0 will be complete when _______" There are two camps for filling in the blank A. Set a calendar goal. All items that are complete and approved by the TC make it into XLIFF 2.0 - All others need to wait for the "next train," i.e., XLIFF 2.X or XLIFF 3. Special care needs to be taken to define doneness and ensure no dependency issues between items. And "XLIFF 2.0 is complete on set date of *Month/Day/Year*" - or - B. Define a finite set of XLIFF 2.0 items. Set a cutoff date for adding items. The list of accepted items becomes our requirements document. And "XLIFF 2.0 is complete when items 1 through X are finished" (some in this camp see our current set of goals, as is, as that finite list) i. Yves commented that XLIFF is not a software. And we should be careful with releasing versions that do not have some specific features we know will ultimately end up there. (http://lists.oasis-open.org/archives/xliff/200904/msg00018.html) 5/ XLIFF 2.0 (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking) Minutes: 1) --- Roll call: Yves, Bryan, David, Asgeir, Magnus, Christian, +Lucia. 2) --- Asgeir move to accept minute, Yves second. No objections. http://lists.oasis-open.org/archives/xliff/200904/msg00023.html 3) --- Review Common Requirements for elements between TMX and XLIFF Come to consensus on the requirements, then assign owners to propose wording for the spec http://wiki.oasis-open.org/xliff/OneContentModel/Requirements?action=show&redirect=Requirements A. Report on the TMX meeting attended by XLIFF TC invitees B. Christians proposal for next steps (http://lists.oasis-open.org/archives/xliff/200904/msg00017.html) C. Adding an adjacent item not included in the list on the wiki page: issues around SUB (http://lists.oasis-open.org/archives/xliff/200904/msg00005.html) D. Asgeir's thoughts on XLIFF 2.0 in 3D (Testing the friendship between XLIFF and TMX) (http://lists.oasis-open.org/archives/xliff/200904/msg00016.html) Christian: Need to have time and space to proceed, or we are losing momentum and opportunities. Need for timelines. Bryan: Also for work in general (XLIFF 2.0)? Christian: Personal opinion: just the inline markup. Email is just examples. Main point is we need timelines. Bryan: Group good at generating ideas, but less good at finalizing things. So I'm for it. Yves: +1. Christian: anyone thing it would be counter-productive? None voiced. Are current steps ok, or too generic? Christian: Yes, high-level milestones would be fine. Bryan: Feel like we are on step-2 already. So maybe need to have a deadline for that step and a milestone for step-3. Second week of June for end of Step-2. Yves, Asgeir: sounds good. Christian: sounds fine. Step-3 starting first week of July. David: need scope defined (3.2) first. Or we won't know if requirements cover the scope. Bryan: right. David: 3.2 may need to be more developed. At what level is the scope? Group? Or source/target? Bryan: inline affect XLIFF above source/target? David: Until next meeting for scope (questions). Bryan: Conclusion of next meeting for closing step-1. David: For example, all to answer questions listed in scope by next meeting. Bryan: Wiki as the "source of truth" for our work. Email thread for discussion, wiki for the conclusion. Is that ok with everyone? Yves: yes. Asgeir: yes, I can also enter data to the wiki if some prefer. Asgeir: email for the discussion, then we state the agreed upon conclusion in the wiki. We can use link to the emails. David: yes. But make sure not all the burden to maintain the wiki falls on Asgeir's shoulder. Asgeir: yes, for people comfortable with it, and cautious about not overriding other's work. It's a balance to find. Bryan: make sure also to set comments when committing the changes. David: Maybe to restrict what changes can be done between the meetings. For example for now, work only on the scope (add answers). Asgeir: yes, bullet points for answer, and associated name. If people more comfortable with email use email. David: important to use email for notifying new info is being set. Christian: are we discussing general discussion mechanism here? (not just inline content). Asgeir: yes, a way to collaborate in general. Here applied to the inline content, but we can use this later for the other XLIFF 2.0 parts. Bryan: yes. Important to define the scope for example: is text just what in inside source/target or within group? Summary from Bryan: - define methodology for working on inline content, and may be useable for other parts of 2.0 - "scope" is the target for next meeting. - people can edit wiki, email as well. Usually: use email for discussion and wiki for conclusion. - adding sub-bullets (possible answers) to scope (including pros and cons and name of the proponent) AND adding requirements is allowed between this and next meeting. 4) --- Method to define when XLIFF 2.0 is done. Tabled for later as Rodolfo is not there. 5) --- XLIFF 2.0 requirements Not in this meeting. Bryan: no new business. Lucia: we can become voting member at the end of second meeting. Next meeting is third Tuesday of May. Meeting adjourned. View event details: http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=24180 PLEASE NOTE: If the above link does not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.
BEGIN:VCALENDAR METHOD:PUBLISH VERSION:2.0 PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN X-WR-CALNAME:My Calendar BEGIN:VEVENT CATEGORIES:MEETING STATUS:TENTATIVE DTSTAMP:20090506T000000Z DTSTART:20090505T150000Z DTEND:20090505T160000Z SEQUENCE:2 SUMMARY:XLIFF TC Meeting DESCRIPTION:1/ Call one of the FreeConferenceCall phone numbers:\nUS: (712) 432-1600\nUS: (605) 772-3100\nAustria: 0820 4000 1552\nBelgium: 070 35 9974\nFrance: 0826 100 256\nGermany: 01805 00 76 09 \nIreland: 0818 270 021\nItaly: 848 390 156\nNetherlands: 0870 001 920\nSpain: 902 886025\nSwitzerland: 0848 560 179\nUK: 0870 35 204 74\n \n2/ Enter the Participant Access Code: 737043#\n\nGroup: OASIS XML Localisation Interchange File Format (XLIFF) TC\nCreator: Bryan Schnabel* URL:http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=24180 UID:http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=24180 END:VEVENT END:VCALENDAR