Groups - XLIFF Teleconference added

[bryan.s.schnabel@tektronix.com]

XLIFF Teleconference has been added by Bryan Schnabel*

Date:  Tuesday, 16 February 2010
Time:  11:00am - 12:00pm ET

Event Description:
To access the meeting go to:
https://www1.gotomeeting.com/join/277182288

- You can use your microphone and speakers (VoIP)
- Or, call in using your telephone:
Dial: 1-630-869-1010
Access Code: 277-182-288
Meeting ID: 277-182-288
(thanks to Yves for providing this)

#####################
# Note, I included the old dial in as *plan B*
#
#1/ Call one of the FreeConferenceCall phone numbers:
#
#US: (712) 432-1600
#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
vSpain: 902 886025
#Switzerland: 0848 560 179
#UK: 0844 581 9102
#
#2/ Enter the Participant Access Code: 737043#
#####################

Agenda:
1/ Roll call
 
2/ Approve Tuesday, 19 January 2010 meeting minutes:
   Accept, reject, or amend.
       http://lists.oasis-open.org/archives/xliff/201002/msg00002.html

3/ Announcements
  1. Lucia and Dimitra announce the first XLIFF International Symposium
     TC to determine what we can do to help:
     http://lists.oasis-open.org/archives/xliff/201002/msg00004.html
  2. Dimitra released XLIFF questionnaire results
     http://lists.oasis-open.org/archives/xliff/201002/msg00001.html

4/ LISA/OSCAR proposal to re-establish a partnership in developing common text markup 
   is accepted by the XLIFF TC. Discuss next steps. 
  
5/ XLIFF 1.2 Errata Status Update
  1. Rodolfo's report
  2. Steps are listed in wiki (http://wiki.oasis-open.org/xliff/)

6/ XLIFF 2.0
 1. Finish our work regarding text elements in XLIFF 2.0 
  (http://wiki.oasis-open.org/xliff/OneContentModel/Requirements?action=show&redirect=Requirements). 
   1.1 Scope section:
    1.1.1 Finish items (3.1.2, 3.1.5, 3.1.6)
    1.1.2 Bryan will assign action based on each documented resolution
   (for example: 3.1.3, (1) Rodolfo adds a note to section 2.5 explaining that extension points are intended 
   for providing support for internal tool processing, not for solving XLIFF deficiencies.)
   1.2 Requirements section:
    1.2.1 Validate that each of these are requirements
    1.2.2 Identify any missing requirements
    1.2.3 Create code examples to show resolution for each requirement
    1.2.4 Turn the examples into words for the specification
    1.2.5 Turn the examples into code for the schemas
  (now for our "where do we go from here moment")
  2. Decide how to go forward with remaining (non-text) parts of XLIFF 2.0 
    2.1 Revisit Feature Tracking (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking)
    2.2 Revisit XLIFF 2.0 Dashboard (http://wiki.oasis-open.org/xliff/XLIFF2.0)
  3. Write a new Conformance Clause
  4. Update the charter


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)

    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)
 
9/ New Business


Minutes:


View event details:
http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=26695

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:20100215T000000Z
DTSTART:20100216T160000Z
DTEND:20100216T170000Z
SEQUENCE:0
SUMMARY:XLIFF Teleconference
DESCRIPTION:To access the meeting go
  to:\nhttps://www1.gotomeeting.com/join/277182288\n\n- You can use your
  microphone and speakers (VoIP)\n- Or\, call in using your
  telephone:\nDial: 1-630-869-1010\nAccess Code: 277-182-288\nMeeting
  ID: 277-182-288\n(thanks to Yves for providing
  this)\n\n#####################\n# Note\, I included the old dial in as
  *plan B*\n#\n#1/ Call one of the FreeConferenceCall phone
  numbers:\n#\n#US: (712) 432-1600\n#Austria: 0820 4000 1552\n#Belgium:
  070 35 9974\n#France: 0826 100 256\n#Germany: 01805 00 76 09
  \n#Ireland: 0818 270 021\n#Italy: 848 390 156\n#Netherlands: 0870 001
  920\nvSpain: 902 886025\n#Switzerland: 0848 560 179\n#UK: 0844 581
  9102\n#\n#2/ Enter the Participant Access Code:
  737043#\n#####################\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=26695
UID:http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=26695
END:VEVENT
END:VCALENDAR