RE: [xliff] Groups - XLIFF TC Teleconference added

["Doug Domeny" <ddomeny@ektron.com>]

Tuesday the 20th is fine with me.

-----Original Message-----
From: bryan.s.schnabel@tektronix.com
[mailto:bryan.s.schnabel@tektronix.com] 
Sent: Thursday, November 15, 2007 5:06 PM
To: xliff@lists.oasis-open.org
Subject: [xliff] Groups - XLIFF TC Teleconference added

Thursday and Friday are holidays in the United States.  But we would
like
to hold this meeting if possible, because the next meeting date,
December 4
brings us close to some deadlines for getting our OASIS ballot going in
January.  
Please let me know if you're unable to attend, and if moving this
meeting
out a week (November 27) works better for you.

Thanks,

Bryan


 -- Bryan Schnabel*


XLIFF TC Teleconference has been added by Bryan Schnabel*

Date:  Tuesday, 20 November 2007
Time:  11:00am - 12:00pm ET

Event Description:
1/ Call one of the MeetingPlace phone numbers: 
From the AMER region dial: * 1-888-967-2253 * +1-650-607-2253 
From the APAC region dial: * +61 2 8817 6100 
From the EMEA region dial: * +44 118 924 9000 

2/ Enter the Meeting ID (805534) followed by the # key 

3/ If the organizer has not started the meeting you will be: 
A. Asked to speak your name followed by the # key 
B. Placed in the waiting room on music hold until the organizer starts
the meeting. 

If the organizer has started the meeting you will be: 
A. Asked to enter the Meeting Password (805534) 
B. Asked to speak your name followed by the # key

Agenda:
+++++++++++++++++++++++
1/ Roll call 

2/ Approve previous meeting minutes: 
Accept, reject, or amend.
(http://www.oasis-open.org/archives/xliff/200711/msg00005.html)

3/ XLIFF 2.0 Goals (http://wiki.oasis-open.org/xliff/XLIFF2.0Goals)
 A. Continue to classify remaining Potential Goals (Must Have, Should
Have, Nice to Have)
 B. Reports from Requirements owners on status of requirement 
 C. XLIFF 2.0 Requirements Document draft
 D. When does it become time to begin to write the actual "XLIFF Version
2.0 Working Draft"?

4/ Review Doug's proposed solution to Asgeir Frimannsson's Errata
suggestions
(http://www.oasis-open.org/archives/xliff/200711/msg00006.html)

Asgeir's suggestions are collected here:
(http://wiki.oasis-open.org/xliff/XLIFF2.0Goals) "Issues collected from
xliff-comment list"
 A. Small inconsistency between the schema and specification with
regards to count-type attribute values
(http://lists.oasis-open.org/archives/xliff-comment/200710/msg00000.html
)
 B. The 'datatype' attribute is specified with a default value of 'Empty
string'. This should be 'undefined'
(http://lists.oasis-open.org/archives/xliff-comment/200710/msg00001.html
)
 C. Schema glitch in  element definition
(http://lists.oasis-open.org/archives/xliff-comment/200711/msg00000.html
)
 D. Tool element inconsistency between spec and schema (schema allows
text)
(http://lists.oasis-open.org/archives/xliff-comment/200711/msg00001.html
)
 E. Content Model for  element enforces order
(http://lists.oasis-open.org/archives/xliff-comment/200711/msg00003.html
)
 F. Suggestion for schema cleanup towards 2.0
(http://lists.oasis-open.org/archives/xliff-comment/200711/msg00004.html
)
 G. Implementer FAQ Entry / Suggestion
(http://lists.oasis-open.org/archives/xliff-comment/200711/msg00005.html
)

5/ Approval of XLIFF 1.2 as an OASIS Specification: Remaining Steps
(http://wiki.oasis-open.org/xliff/RemainingApprovalSteps) 
 A. New feedback from Mary makes it worthwhile to quickly revisit this
topic

6/ XLIFF Webinar? (http://www.oasis-open.org/events/webinars/) 

7/ Rodolfo suggests the TC charter may need a review and update

8/ Reports from liaisons involved with other standards groups: 
 A. W3C i18n 
 B. Oscar 
 C. Trans-WS 
 D. LRC 
 E: OASIS DITA Translation Subcommittee 

9/ Any Other Business
+++++++++++++++++++++++

Minutes:


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

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.