[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Groups - XLIFF TC Meeting (XLIFF 2.0 focus) added
Bryan: unfortunately, I have a conflict today with the XLIFF TC meeting. Please accept my apologies as I cannot attend. Regards, Tony -----Original Message----- From: email@example.com [mailto:firstname.lastname@example.org] Sent: 01 December 2008 04:38 To: email@example.com Subject: [xliff] Groups - XLIFF TC Meeting (XLIFF 2.0 focus) added This will be an XLIFF 2.0 meeting. -- Bryan Schnabel* XLIFF TC Meeting (XLIFF 2.0 focus) has been added by Bryan Schnabel* Date: Tuesday, 02 December 2008 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: +++++++++++++++++++++++ ** Category 1 Issues: General, not tied to 1.2.1 or 2.0 ** 1/ Roll call 2/ Approve previous meeting minutes: Accept, reject, or amend. ( http://www.oasis-open.org/apps/org/workgroup/xliff/email/archives/200811/msg 00005.html) 3/ TC charter may need a review and update (http://www.oasis-open.org/committees/xliff/charter.php) A. Mary outlined the criteria for updating the charter: http://lists.oasis-open.org/archives/xliff/200806/msg00004.html B. Tony to draft charter update for first December meeting. 4/ Promoting XLIFF (Peter, David F.) A. Peter to write up proposal on how to promote XLIFF among content handlers to export/import XLIFF. B. Rodolfo to invite Translations.com to join the XLIFF TC. He will contact Mary McRae and ask her to invite the company C. Bryan making inroads with XML Editor Tool companies (recommending that their product include a function called *export to XLIFF/import XLIFF* as an out-of-the-box feature for all of their out-of-the-box DTDs and schemas (like Docbook, XHTML, DITA, etc.)) This will be a huge competitive advantage to the first company to do this. 5/ Preparing for a vote on Eric's representation guide (ICU Resource Bundle) (http://source.icu-project.org/repos/icu/icuhtml/trunk/design/locale/xliff-p rofile-icuresourcebundle-1.2.htm) A. Rodolfo to test XLIFF code samples B. Rodolfo and Eric to adapt the guide to the current templates (For XLIFF 2.0 themed meetings, jump to Category 3) ** Category 2 Issues: XLIFF 1.2.1 (quick Turn) ** Note - All issues should be identified, and ready to be put into the 1.2.1 Spec and Schema. It would be useful now to verify or identify action items to make it so. (report from Rodolfo and Doug), Doug has given Rodolfo the updated schema for XLIFF 1.2.1 6/ XLIFF 1.2.1 Issues are tracked on the WIKI (http://wiki.oasis-open.org/xliff/XLIFF1.2/Errata) (Errata page begun by Asgeir) A. Link updated XLIFF 1.2.1 schemas to this page, and perhaps TC page i The items to be changed in the new specifications will be discussed in the wiki first. All changes to the wiki should indicate the name of the comment author. B. Start an XLIFF 1.2.1 Committee Specification and link it to this page i Start a draft specification document for 1.2.1 and the corresponding schemas. ii Rodolfo will create the initial draft, based in current XLIFF 1.2 specification, and iii Doug will edit and update the schemas to reflect the new changes iv Doug and Rodolfo will be listed as editors in the new specification document. C. Proposal to add scope (criteria and due dates) to this page i 1st CS of 1.2.1; ii Public review during December, iii Ready to go standard vote by March. 7/ Semantics on Attributes on Structural Elements (Christian) (http://lists.oasis-open.org/archives/xliff/200808/msg00006.html) 8/ Doug proposed discussing the issues raised by Stefan Uhrig (http://lists.oasis-open.org/archives/xliff-comment/200808/msg00001.html) Note: Resolved, Stefan's comments are essentially addressed by 1.2.1. (just want to get formal agreement that it can be taken off the agenda) A. Section 2.5.2 B. Section 2.5.1 C. Section 3.2.1 D. Section 3.2.2 E. schema is too lax in Stefan's opinion ** Category 3 issues: XLIFF 2.0 ** 9/ Make XLIFF 2.0 modular. That way tools could certify to support XLIFF modules (like Full XLIFF Trans-unit support) A. Christian and Magnus to create proposal on modular subsets and report back on progress by end-of-year. 10/ Asgeirs tracking details page (http://lists.oasis-open.org/archives/xliff/200804/msg00001.html), (http://wiki.oasis-open.org/xliff/XLIFF2.0/Ideas) will serve as documentation for each of the items being tracked on the goals page (http://wiki.oasis-open.org/xliff/XLIFF2.0Goals). Note: Asgeir's ideas for 2.0. Ideas and suggested recommendations are still open. We need to categorize the new ideas. 11/ Topics for XLIFF 2.0 (Rodolfo) (http://lists.oasis-open.org/archives/xliff/200807/msg00003.html) 12/ XLIFF 2.0 proposal: Allow [note] to reference [mrk] (Magnus, Bryan, Doug) (http://lists.oasis-open.org/archives/xliff/200808/msg00004.html) Note: Magnus stated this item has been moved to the wiki. [ Magnus, I could not find it in the wiki -Doug ] 13/ XLIFF 2.0 Goals (http://wiki.oasis-open.org/xliff/XLIFF2.0Goals) A. Reports from Requirements owners on status of requirement B. Continue to classify remaining Potential Goals (Must Have, Should Have, Nice to Have) C. XLIFF 2.0 Requirements Document draft D. Begin to write the actual "XLIFF Version 2.0 Working Draft" (covered under item 13/ ) ** Non categorized ** 14/ Reports from liaisons involved with other standards groups: A. W3C i18n B. Oscar C. LRC D. OASIS DITA Translation Subcommittee E. OAXAL 15/ New Business +++++++++++++++++++++++ Minutes: View event details: http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=20407 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.