OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Groups - XLIFF TC Meeting (XLIFF 2.0 focus) modified

Added meeting minutes.

 -- Rodolfo Raya

XLIFF TC Meeting (XLIFF 2.0 focus) has been modified by Rodolfo Raya

Date:  Tuesday, 03 March 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#

1/ Roll call
2/ Approve previous meeting minutes:
Accept, reject, or amend. (http://lists.oasis-open.org/archives/xliff/200902/msg00003.html)

3/ Announcements
 A. Welcome back to the TC Yves!
4/ TC charter update
 A. Mary outlined the criteria for updating the charter: 
 B. Tony will draft a charter update.

5/ Readiness for a vote on XLIFF 1.2.1 as a committee draft 
  - warm thanks to Rodolfo for this great work!
  - Conformance section requirement (http://lists.oasis-open.org/archives/xliff/200903/msg00000.html)
  - Approve Eric's representation guide (ICU Resource Bundle)

6/ Promoting XLIFF (Peter, David F.)

7/ Unifying XLIFF inline element(s) with TMX's new proposal for inline element(s)

8/  "XLIFF 2.0 will be complete when _______" 
  There are two camps for filling in the blank
  1. 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 - 
2. 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)

9/ Turning schemas over to Asgeir to begin XLIFF 2.0

10/ Asgeirs tracking details page, 
    will serve as documentation for each of the items being     tracked on the goals page.
Note: kept the 1.x numbering to match the wiki

  1.1. Change Tracking / Version Control
  1.2. Document-centric Localisation
  1.3. Native support for ITS
  1.4. Enhanced Commenting Support
  1.5. Permission Control and Validation
  1.6. XLIFF as a Project Model
  1.7. Resource Inheritance
  1.8. Improved Whitespace Handling

  ***Need to add these topics to Asgeir's page, from 
      Must Haves:
  1.9 - Enable internal-file to contain XML Markup, not CDATA [Christian]   

   * Bryan mocked up samples of how this could be done   

  1.10 - Create a bare-bones XLIFF core, then provide extension modules that support additional features. 

  [Magnus, Christian]
   * "Simplify, Extend and Clarify" - V2.0
   * (Core XLIFF functionality would be in primary XLIFF namespace; would be very simple to implement.) 
     (Extensions would provide support for more complicated features like, Segmentation, Pre-Translation, 

     Generic Inline Markup, etc.) 
     Magnus said that he will try and get back to this and add more information. 
   * Official XLIFF guide for subsetting the XLIFF XSD   

   * Named Types for XLIFF XSD (http://www.oasis-open.org/archives/xliff/200709/msg00007.html) 
Note: Bryan merged this item as a sub here - might need to make it its own item
   * 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.

      Should Haves:
  1.11 - Submitting to ISO once XLIFF becomes an OASIS standard [Tony]
  1.12 - Additional Representation Guides (DITA,.NET / Win32, Docbook)
   * Proposed ICU Reference Guide 


tm [Eric] 
  1.13 - Subsetting / restricting XSD as proposed by Christian - V2.0 Should have but could be Must have. 

We will wait until Christian discusses with TC
  1.14 - Version control Metadata - need to track revision information - V2.0
  1.15 - Include xml:tm in the non-normative section (http://www.lisa.org/standards/xmltm/) 
  1.16 - Ability to store Multilingual Content. - 
          (will be promoted to Must or Should if a champion is assigned) 
          We had a brief discussion on this and various questions were raised about how this would work. 
          Bryan mentioned that his company achieve this through using the file element and having the 
          same id and source for corresponding trans units. 
          It was agreed that we would find the owner for this and they should champion it. 
          Until then we will keep it on the requirements doc.
  1.17 - Adapt inline element to match the markup of the new convention in TMX
   * need to have one tag for content though
   * and one for localization metadata
   * need to associate more information than we do today 
     (i.e., need extensibility point)  

13/ Reports from liaisons involved with other standards groups:
 A. W3C i18n
 B. Oscar
 D. OASIS DITA Translation Subcommittee
14/ New Business

Present: Doug Domeny, Yves Savourel, Bryan Schnabel, Rodolfo Raya, David Filip, Tony Jewtushenko, Asgeir Frimannsson, Christian Lieske and Magnus Martikainen.

Bryan welcomed Yves Sovourel back to the XLIFF TC.

Asgeir moved to approve previous minutes, Yves seconded and there were no objections.

Rodolfo uploaded a zip file to Kavi with the draft for XLIFF 1.2.1.

Asgeir reorganized the wiki for XLIFF 2.0, improving it considerably.

Christian asked about the need to add a Conformance section to XLIFF 1.2.1 and Rodolfo explained that the TC has to define the conformance requirements to put in the specifications. Requirements could be the same for XLIFF 1.2.1 and 2.0.

Tony will try to update the charter for next meeting. Charter update is not an obstacle for working on XLIFF 1.2.1 and 2.0. 

Potential content for the new conformance was discussed and multiple options were considered. Conformance for 1.2.1 should be as basic as possible, leaving detailed conformance for the 2.0 specs. Discussion will continue by email.

Call dismissed.

View event details:

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

PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
X-WR-CALNAME:My Calendar
SUMMARY:XLIFF TC Meeting (XLIFF 2.0 focus)
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*

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]