Groups - XLIFF TC Telelconference added

Hello,

Please note the new agenda item about my proposed methodology for taking
XLIFF 2.0 forward (7/2.). I think it will take about 30 minutes for me to
present this. I will send the proposal ahead of time, and update this
agenda to point to the correct URL. I can send the proposal in Open Office
(my preferred format), or PowerPoint, or PDF. I suppose PDF is the safest.
Please let me know if you'd prefer me to send you one of the other
formats).

- Bryan


 -- Bryan Schnabel*


XLIFF TC Telelconference has been added by Bryan Schnabel*

Date:  Tuesday, 04 May 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)

Agenda:
1/ Roll call
 
2/ Approve Tuesday, 6 April 2010 meeting minutes:
   Accept, reject, or amend.
http://lists.oasis-open.org/archives/xliff/201004/msg00001.html
 (and clarified by David and Mary)
http://lists.oasis-open.org/archives/xliff/201004/msg00004.html

3/ Current XLIFF business
 1. Updates on the 1st International XLIFF Symposium
 2. Dealing with spam on the XLIFF user list

4/ XLIFF Inline text SC report (LISA/OSCAR proposal to re-establish a partnership 
   in developing common text markup)
  1. Bryan and Yves requested OASIS Administrator, Mary to set up the SC
  2. Yves' SC report (this is a placeholder for the regular report to the TC)
  
5/ XLIFF 1.2 Errata Status Update
  1. Rodolfo's report
  2. Steps are listed in wiki (http://wiki.oasis-open.org/xliff/)
  3. OASIS provided an SVN repository

6/ Rodolfo raises questions regarding 
  1. "Translatable stuff in XLIFF 1.2"(http://lists.oasis-open.org/archives/xliff/201002/msg00012.html)
  2. segmentation  (http://lists.oasis-open.org/archives/xliff/201002/msg00029.html)
      (note: this thread had many facets. The url above is the latest entry, 
       and also contains references to all the other email)
  3. problems with seg-source (http://lists.oasis-open.org/archives/xliff/201002/msg00028.html)

7/ XLIFF 2.0
(note: item 1. is a placeholder for now; to be taken over by inline SC)
 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
(note: Bryan has a presentation on a proposed methodology to be submitted via the XLIFF list)
  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


(note: if proposed way forward (7/2.) is accepted, this item goes away)
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=27016

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.