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 modified

Added meeting minutes.

 -- Rodolfo Raya

XLIFF TC Meeting has been modified by Rodolfo Raya

Date:  Tuesday, 16 June 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.


3/ Announcements

 A. Rodolfo released XLIFF Checker tool

 B. Bryan released xliffRoundTrip Tool v.0.7.03

 C. New resolution tracker added to wiki

4/ Review Requirements for inline elements [define, understand, the vote - being mindful of Tony's suggestion of limiting the length of discussion]
(come to consensus on the requirements, then assign owners to propose wording for the spec)    

5/ If something is valid XML and not disallowed explicitly by the specification, it means it is allowed?(http://lists.oasis-open.org/archives/xliff/200906/msg00008.html) (Question captured from Yves' comment on Rodolfo's XLIFF Checker Tool)

6/  "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)
7/ XLIFF 2.0 

Present: Magnus Martikainen, Bryan Schnabel, Rodolfo Raya, Yves Savourel, Lucia Morado Vazquez, Doug Domeny, Christian Lieske.

Regrets: Asgeir, Dimitra

Yves moved to approve previous minutes, Rodolfo seconded and none objected.

Lucia commented that her name is not properly spelled. KAVI doesnt support accented characters yet. Bryan indicated that OASIS officers should be notified of this problem and a fix requested.

Announcements: Rodolfo released XLIFFChecker, a tool for validating XLIFF files. Bryan released a new version of XLIFF RoundTrip Tool.

Bryan commented that it would be important to allow XML markup in , as Christian requested. Rodolfo mentioned that the  element should also allow storing glossaries in XML format. 

Magnus announced that SDL has released SDL Trados Studio 2009, which is based on XLIFF 1.2.

Bryan updated the wiki page and added placeholders for tracking issue resolution. The wiki discussion now contains comments from the minutes indicating TC decisions.

Yves updated the wiki regarding question 3 in section 3.1.1, indicating that The model should describe how sub-flow are handled, including the relation between its extracted representation and its original location. It seems that the TC agrees on this statement. 
Discussion on actual implementation will happen at a later stage.

The meaning and need for a canonical representation of inline markup was discussed (wiki section 3.1.2).  Christian proposed to move discussion to an email thread. 

Magnus reminded that XML 1.0 doesnt allow control characters and XLIFF 2.0 should provide a way to represent them.

Christian will modify item 3.1.3 and separate extensibility from annotations. Action item: Christian to extend the text to clarify the scope and meaning of the request.

Yves indicated that an attribute from a foreign namespace can be used in the  element for basic extensibility in  or .

A vote on item 3.1.4 was conducted. It was agreed that the specification should define how the inline-content (and block level) model can be manipulated.

Rodolfo asked if it is OK to have XLIFF files that do not have target language. Magnus explained that it is OK when the file has only source text, which can be used for pre-processing before handing the file out for translation, but agreed that an XLIFF file that contains translated target elements should indicate the target language.

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
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]