Description: Standing monthly XLIFF TC Teleconference.
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 (030543)
b. Asked to speak your name followed by the # key
==========
Agenda: Agenda:
1/roll call (Welcome TC New Members: Steve Harris of Idiom, and Joachim Schurig of Lionbridge)
2/Previous meeting minutes (http://lists.oasis-open.org/archives/xliff/200605/msg00062.html) Amend, Approve, Reject as official record:
3/ Work in Progress:
A. XLIFF 1.2 Specification
Committee Draft Process:
We have now successfully completed the work for XLIFF 1.2 Committee Draft. The inventory of approved documents is as follows:
Approved work as part of the Monday, 22 May 2006 @ 15:00 ET Ballot (http://www.oasis-open.org/apps/org/workgroup/xliff/ballot.php?id=1017)
XLIFF 1.2 Committee Draft Specification:
(http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/18200/draft-xliff-core-1.2-20060516.zip)
Supporting normative content:
- the XLIFF 1.2 Strict XSD (Committee Draft)
(http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/18196/xliff-core-1.2-strict-20060512.xsd)
- the XLIFF 1.2 Transitional XSD
(http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/18197/xliff-core-1.2-transitional-20060512.xsd)
Supporting non-normative content:
- the XLIFF HTML Representation Guide Draft
(http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/18201/xliff_profile_html_1.2_committee_draft_20060516.zip)
- the XLIFF Java Resource Bundles Representation Guide Draft
(http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/18202/xliff-profile-java-draft-20060516.zip)
Approve work as part of the Tuesday, 20 June 2006 @ 11:00 ET closing ballot: (http://www.oasis-open.org/apps/org/workgroup/xliff/ballot.php?id=1048)
Supporting non-normative content:
- the XLIFF Gettext PO Representation Guide Draft
(http://lists.oasis-open.org/archives/xliff/200605/msg00061.html)
*NOTE: there was one vote against approval - we will discuss if there is any need to reopen the issue.
Next step is to formally submit the entire package to OASIS to start a public review. All work has been approved as committee draft so no further ballots are required - unless any new issues arise in the TC Teleconference we will submit the work for formal OASIS committee spec process at the close of the teleconference. The full OASIS policy is outlined here: http://www.oasis-open.org/committees/process.php#3.1 . The public review will run for 60 days. If no issues arise we can vote to approve the work as a Committee Spec. Any revisions will require additional 15 day public review periods until no further open issues remain.
Regarding affidavits:
The OASIS TC process requires that we submit 3 affidavits from Organisational members (ie., not individual or associate members) in order to submit the spec to OASIS standard process. The following is an acceptable template for such affidavits:
"I certify that is successfully using the XLIFF 1.2 specification, as approved for submission to the OASIS membership, consistent with the requirements of the OASIS Technical Committee Process."
B. Open issues:
a. Translation of Voice XML Issues
UPDATE (5 Mar 2006) from Mat: http://lists.oasis-open.org/archives/xliff/200603/msg00003.html
Archived Historical detail:
~ Open until resolution of namespace issue.
- Action Item: Mat will submit a proposal on how to handle Voice XML issues.
Initial: http://lists.oasis-open.org/archives/xliff/200403/msg00016.html
Update: http://www.oasis-open.org/archives/xliff/200403/msg00017.html
b. Extending XLIFF with separate namespaces.
Some thought has been put into this issue but not yet even in draft form.
ACTION ITEM: Mat & Andzrej will work offline to advance this work.
c. (Closed) Best practice: should extraction process create target elements?
Topic proposed by Doug. Discussed in mailing list:
Initial Proposal (Doug): http://lists.oasis-open.org/archives/xliff/200603/msg00023.html
Comment (Bryan): http://lists.oasis-open.org/archives/xliff/200603/msg00025.html
Comment (Tony): http://lists.oasis-open.org/archives/xliff/200603/msg00035.html
Comment (Rodolfo): http://lists.oasis-open.org/archives/xliff/200603/msg00032.html
The optional meeting took place Thursday 1 June. The meeting notes are detailed here: http://lists.oasis-open.org/archives/xliff/200606/msg00006.html
As a very brief summary, it was agreed that any XLIFF compliant tool should be capable of dealing with empty target elements, since it valid XLIFF. We did not feel it necessary to make any changes to the spec, but felt that an entry in the FAQ and/or whitepaper covering the topic would be helpful. We'll keep this item as a working agenda item until it's time to revise the FAQ / Whitepaper with this information.
d. (OPEN) XLIFF - DITA Best Practices:
Purpose of this discussion is to brainstorm what the TC can and should do to provide guidance to those who want to localise / translate DITA content, with potential recommended best practice centered around XLIFF as intermediate container.
Meeting was held on Thursday, 15 June -> http://lists.oasis-open.org/archives/xliff/200606/msg00014.html
RECOMMENDATION TO XLIFF TC:
The best practice of interchanging data between DITA and XLIFF is the same issue as how to interchange data XML and XLIFF in general... e.g., how to use XLIFF with ITS, XML:tm, etc. We suggest that the TC author profile documents similar to the other profiles we've developed, ie, HTML profile... in them we recommend which elements to use or avoid, skeleton file approach, transformation approach, other common problems and recommended solutions. Should address XLIFF ITS, XLIFF XML:TM, XLIFF DITA, maybe XLIFF Docbook.
4/XLIFF 1.2 Certification activities:
Ignite had their 2nd meeting last week - feedback and report from Reinhard if he is in attendance.
Report for the next meeting.
5/XLIFF Face to Face in November?
There's an OASIS Open Standards Day happening in Germany where I think a number of XLIFF TC members may already be planning to attend. We haven't had a TC F2F in years, and I think it would be good timing to schedule a TC Face to Face to brainstorm what our next objectives and steps should be as a TC.
Date: 8-9 November 2006
Location: Wiesbaden, Germany
Venue: Rhein-Main-Hallen
Hosted by: Gesellschaft für technische Kommunikation e.V. - tekom
6/ Reports from liaisons involved with other standards groups:
A. W3C i18n
B. Oscar
C. Trans-WS
D. LRC
E: OASIS DITA Translation Subcommittee
7/Any Other Business
==========
Minutes: 1/roll call There were 9 members present as recorded in Kavi.
Tony welcomed two new TC Members: Steve Harris of Idiom, and Joachim
Schurig of Lionbridge
Steve and Joachim introduced themselves. Steve works with the import/ export functionality on idiom WorldServer. Joachim is the architect for Logoport, Lionbridge’s TM technology.
2/Previous meeting minutes
(http://lists.oasis-open.org/archives/xliff/200605/msg00062.html)
There minutes were agreed as a correct record. Proposed by Bryan and seconded by Rodolfo.
3/ Work in Progress:
A. XLIFF 1.2 Specification
Committee Draft Process:
We have now successfully completed the work for XLIFF 1.2 Committee
Draft. The inventory of approved documents is as follows:
Approved work as part of the Monday, 22 May 2006 @ 15:00 ET Ballot
(http://www.oasis-open.org/apps/org/workgroup/xliff/ballot.php?id=1017)
XLIFF 1.2 Committee Draft Specification:
(http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/18200/d
raft-xliff-core-1.2-20060516.zip)
Supporting normative content:
- the XLIFF 1.2 Strict XSD (Committee Draft)
(http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/18196/x
liff-core-1.2-strict-20060512.xsd)
- the XLIFF 1.2 Transitional XSD
(http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/18197/x
liff-core-1.2-transitional-20060512.xsd)
Supporting non-normative content:
- the XLIFF HTML Representation Guide Draft
(http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/18201/x
liff_profile_html_1.2_committee_draft_20060516.zip)
- the XLIFF Java Resource Bundles Representation Guide Draft
(http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/18202/x
liff-profile-java-draft-20060516.zip)
Approve work as part of the Tuesday, 20 June 2006 @ 11:00 ET closing
ballot:
(http://www.oasis-open.org/apps/org/workgroup/xliff/ballot.php?id=1048)
Supporting non-normative content:
- the XLIFF Gettext PO Representation Guide Draft
(http://lists.oasis-open.org/archives/xliff/200605/msg00061.html)
Tony pointed out that Christian had voted against. He made the following comment with his vote, ‘I don't think that meta data like that from a PO header should be put into a trans-unit (that's what is mentioned as one possibilitiy in the document).’
Rodolfo agreed with Christian. He said that we have not got anything within XLIFF which will deal with the header data in the PO file and we are using the trans-unit as a kludge. This is something which we will look at in future versions.
Next step is to formally submit the entire package to OASIS to start a
public review. All work has been approved as committee draft so no
further ballots are required - unless any new issues arise in the TC
Teleconference we will submit the work for formal OASIS committee spec
process at the close of the teleconference. The full OASIS policy is
outlined here: http://www.oasis-open.org/committees/process.php#3.1 .
The public review will run for 60 days. If no issues arise we can vote
to approve the work as a Committee Spec. Any revisions will require
additional 15 day public review periods until no further open issues
remain.
Regarding affidavits:
The OASIS TC process requires that we submit 3 affidavits from
Organisational members (ie., not individual or associate members) in
order to submit the spec to OASIS standard process. The following is an
acceptable template for such affidavits:
"I certify that is successfully using the XLIFF 1.2 specification, as
approved for submission to the OASIS membership, consistent with the
requirements of the OASIS Technical Committee Process."
Mat mentioned that Oracle would like to provide an affidavit. They intend using XLIFF 1.2 with WorldServer 8.0. Tony pointed out that it was not needed to have something which was on actual commercial work but that this was very positive.
B. Open issues:
a. Translation of Voice XML Issues
UPDATE (5 Mar 2006) from Mat:
http://lists.oasis-open.org/archives/xliff/200603/msg00003.html
Archived Historical detail:
~ Open until resolution of namespace issue.
- Action Item: Mat will submit a proposal on how to handle Voice XML
issues.
Initial: http://lists.oasis-open.org/archives/xliff/200403/msg00016.html
Mat confirmed that this issue is currently on hold. He will raise again when it becomes an issue in the future.
Update: http://www.oasis-open.org/archives/xliff/200403/msg00017.html
b. Extending XLIFF with separate namespaces.
Some thought has been put into this issue but not yet even in draft
form.
ACTION ITEM: Mat & Andzrej will work offline to advance this work.
c. (Closed) Best practice: should extraction process create target
elements?
Topic proposed by Doug. Discussed in mailing list:
Initial Proposal (Doug):
http://lists.oasis-open.org/archives/xliff/200603/msg00023.html
Comment (Bryan):
http://lists.oasis-open.org/archives/xliff/200603/msg00025.html
Comment (Tony):
http://lists.oasis-open.org/archives/xliff/200603/msg00035.html
Comment (Rodolfo):
http://lists.oasis-open.org/archives/xliff/200603/msg00032.html
The optional meeting took place Thursday 1 June. The meeting notes are
detailed here:
http://lists.oasis-open.org/archives/xliff/200606/msg00006.html
As a very brief summary, it was agreed that any XLIFF compliant tool
should be capable of dealing with empty target elements, since it valid
XLIFF. We did not feel it necessary to make any changes to the spec,
but felt that an entry in the FAQ and/or whitepaper covering the topic
would be helpful. We'll keep this item as a working agenda item until
it's time to revise the FAQ / Whitepaper with this information.
d. (OPEN) XLIFF - DITA Best Practices:
Purpose of this discussion is to brainstorm what the TC can and should
do to provide guidance to those who want to localise / translate DITA
content, with potential recommended best practice centered around XLIFF
as intermediate container.
Meeting was held on Thursday, 15 June ->
http://lists.oasis-open.org/archives/xliff/200606/msg00014.html
RECOMMENDATION TO XLIFF TC:
The best practice of interchanging data between DITA and XLIFF is the
same issue as how to interchange data XML and XLIFF in general... e.g.,
how to use XLIFF with ITS, XML:tm, etc. We suggest that the TC author
profile documents similar to the other profiles we've developed, ie,
HTML profile... in them we recommend which elements to use or avoid,
skeleton file approach, transformation approach, other common problems
and recommended solutions. Should address XLIFF ITS, XLIFF XML:TM,
XLIFF DITA, maybe XLIFF Docbook.
4/XLIFF 1.2 Certification activities:
Ignite had their 2nd meeting last week - feedback and report from
Reinhard was not present so will report for the next meeting.
5/XLIFF Face to Face in November?
There's an OASIS Open Standards Day happening in Germany where I think a
number of XLIFF TC members may already be planning to attend. We haven't
had a TC F2F in years, and I think it would be good timing to schedule a
TC Face to Face to brainstorm what our next objectives and steps should
be as a TC.
Date: 8-9 November 2006
Location: Wiesbaden, Germany
Venue: Rhein-Main-Hallen
Hosted by: Gesellschaft fr technische Kommunikation e.V. - tekom
It was agreed that this was a good idea and we will try and organize this. Mat suggested that it would be good if there was other factors which would be taken into account with this conference. Several people mentioned that tekom was Europe’s major technology conference.
6/ Reports from liaisons involved with other standards groups:
A. W3C i18n
B. Oscar – Nothing new to report
C. Trans-WS – Nothing new to report
D. LRC
E: OASIS DITA Translation Subcommittee
7/Any Other Business
==========
Attendance:
| Meeting Statistics |
| Quorum rule |
51% of voting members |
| Achieved quorum |
true |
| Counts toward voter eligibility |
true |
| Individual Attendance |
Members: 9 of 38 (23%)
Voting Members: 8 of 11 (72%) (used for quorum calculation)
|
| Company Attendance |
Companies: 9 of 24 (37%)
Voting Companies: 8 of 10 (80%)
|