OASIS XML Localisation Interchange File Format (XLIFF) TC

XLIFF Teleconference has been modified by Bryan Schnabel* Date: Tuesday, 21 June 2011 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
(meeting setup Courtesy of Yves) Agenda: 1/ Roll call

2/ Approve Tuesday, 17 May 2011 meeting minutes:
Accept, reject, or amend.
( http://lists.oasis-open.org/archives/xliff/201106/msg00007.html )

3/ Sub Committee Reports
- Inline text (Yves)

4/ XLIFF 2.0 ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking )
1. XLIFF 2.0 Core (note: per our decision that we will
define feature, and then vote if they
are core or module, I've moved all feature
into the modules category for now, except
segmentation which we identified as core -
though I need to locate the vote to
confirm this)
a. Segmentation - Yves, et al.
begin: ( http://lists.oasis-open.org/archives/xliff/201104/msg00005.html )
most recent ( http://lists.oasis-open.org/archives/xliff/201104/msg00034.html )
b. Philosophy of core vs. modules - David W.
( http://lists.oasis-open.org/archives/xliff/201104/msg00020.html )
and
( http://lists.oasis-open.org/archives/xliff/201105/msg00024.html )

2. XLIFF 2.0 Modules
a. Rodolfo's latest schema with examples and two optional modules
( http://lists.oasis-open.org/archives/xliff/201105/msg00023.html )
b. Compliance - Rodolfo, Yves
( http://lists.oasis-open.org/archives/xliff/201104/msg00031.html )
- note, shall we table compliance until we begin Conformance criteria discussion?
c. Crossover aligned segments - Yves
( http://lists.oasis-open.org/archives/xliff/201105/msg00038.html )
d. Feedback from OpenTM2 XLIFF interoperability enhancements (Andrew Pimlott)
( http://lists.oasis-open.org/archives/xliff-comment/201105/msg00000.html )

3. XLIFF 2.0 Attributes - Rodolfo
( http://lists.oasis-open.org/archives/xliff/201104/msg00056.html )
- note, do we want attributes to be discussed at this level?
or should they be discussed under 1. and 2. ?
a. Translation status values for 2.0 - Yves
( http://lists.oasis-open.org/archives/xliff/201104/msg00058.html )

4. Conformance criteria

5. Review items approved in section 1 ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking )
(we now have 4 approved new features and 16 proposed features to be evaluated)

5/ Charter Draft (David F.)
( http://lists.oasis-open.org/archives/xliff/201106/msg00003.html )

6/ Current XLIFF business
1. Alternate meeting focussed on Current Business?
2. XLIFF and other standards: activity/impact
a. LISA/OSCAR status
b. Helena's announcement about Unicode Localization Interoperability Technical Committee
( http://www.unicode.org/uli/ )
- - Note, Call for Participation: Unicode Localization Interoperability Kick-off
( http://lists.oasis-open.org/archives/xliff/201105/msg00062.html )
c. LocWorld Panel debrief (David/Helena)
d. ETSI membership (Peter/Arle)
e. XLIFF and TM, Glossary, Segmentation Rules (Christian)
( http://lists.oasis-open.org/archives/xliff/201105/msg00043.html )
- - Need a full discussion on this topic (Peter)
( http://lists.oasis-open.org/archives/xliff/201105/msg00047.html )
f. ISO/OASIS XLIFF - XLIFF as an ISO standard (Peter)
( http://lists.oasis-open.org/archives/xliff/201010/msg00004.html )
- - Note 1, Liaison report for TC 37 (Peter)
( http://lists.oasis-open.org/archives/xliff/201105/msg00049.html )
g. Schedule conversation (with TAUS, to discuss ideas around
XLIFF promotion and evolution) (Bryan)
( http://lists.oasis-open.org/archives/xliff/201105/msg00031.html )
3. 2nd Annual XLIFF Symposium in Poland progress (Peter)
4. XLIFF Symposium 1 Debrief: "Voice of our customer" (Christian)
- Christian is in contact with Multilingual and has written to Robin Cover
5. Gathering common extension points from
existing XLIFF Tools as a guide for 2.0 features (Bryan, Thomas)
( http://lists.oasis-open.org/archives/xliff/201101/msg00007.html )
- Lucia has taken over Micah's matrix
- David F is investigating funding for XLIFF tools page
6. XLIFF Spec in XLIFF (Lucia)
7. International Cloud Symposium: The intersection of policies,
standards and best practices for robust trusted public
sector cloud deployments.
( http://lists.oasis-open.org/archives/xliff/201105/msg00029.html )
a. The Symposium will be held October 10-13 in Slough, United Kingdom (near London).
b. OASIS encourages us to conduct a F2F

8. Using remaining Multilingual Web Events (e.g. in Limerick) as an opportunity to talk about the current state and the possible future of XLIFF (Christian)
7/ New Business Minutes: View event details: http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=30734 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:20110621T000000Z
DTSTART:20110621T150000Z
DTEND:20110621T160000Z
SEQUENCE:2
SUMMARY:XLIFF Teleconference
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
(meeting setup Courtesy of Yves)

Group: OASIS XML
Localisation Interchange File Format (XLIFF) TC
Creator: Bryan
Schnabel*
URL: http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=30734
UID: http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=30734
END:VEVENT
END:VCALENDAR

XLIFF Teleconference - Summary Date: Tuesday, 21 June 2011 === Agenda: 1/ Roll call Presents: Yves, Bryan, Rodolfo, Tom, Christian, Helena, David-F, Arle (later), Andrew (later) Regrets: Arle (but joined later), Lucìa, Peter === 2/ Approve Tuesday, 17 May 2011 meeting minutes: Accept, reject, or amend. ( http://lists.oasis-open.org/archives/xliff/201106/msg00007.html ) Bryan moves to accept the minutes. David-F: small amendment: ETSI is allowing only FRAND IP mode. Rodolfo second with this amendment. No objections. === 3/ Sub Committee Reports Inline text (Yves) Yves was away. See notes from Arle: http://lists.oasis-open.org/archives/xliff-inline/201106/msg00003.html Yves to gather list of elements for Rodolfo's schema. 4/ XLIFF 2.0 ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking ) Rodolfo has maintain an experimental schema. Question of core vs. modules Maybe need to touch on the mechanism we're using to track the work. === 4.1. XLIFF 2.0 Core --- a. Segmentation - Yves, et al. begin: ( http://lists.oasis-open.org/archives/xliff/201104/msg00005.html ) most recent ( http://lists.oasis-open.org/archives/xliff/201104/msg00034.html ) --- b. Philosophy of core vs. modules - David W. ( http://lists.oasis-open.org/archives/xliff/201104/msg00020.html ) and ( http://lists.oasis-open.org/archives/xliff/201105/msg00024.html ) === 4.2. XLIFF 2.0 Modules --- a. Rodolfo's latest schema with examples and two optional modules ( http://lists.oasis-open.org/archives/xliff/201105/msg00023.html ) --- b. Compliance - Rodolfo, Yves ( http://lists.oasis-open.org/archives/xliff/201104/msg00031.html ) - note, shall we table compliance until we begin Conformance criteria discussion? --- c. Crossover aligned segments - Yves ( http://lists.oasis-open.org/archives/xliff/201105/msg00038.html ) Discussion about the cross-over segments. Current attribute should be ok. Yves to try implementation Discussion about "ignorable" May take a lot of space to mark them up. May be able to use reference to skeleton May be able to point to a place where repeated span of data can be pointed to. Skeleton type depends on type of original file (e.g. HTML vs some binary file can't be handled the same way). Same of trans-unit (repetitions) entries that are repeated But translation may be different. DITA has conref: maybe we could used something like that for ignorable. And possibly for source text too. Even further: re-use of "topic" We have not started to discuss the skeleton, topic worth to discuss at some point. New topic: repeatable / referenceable Rodolfo: will try to come up with schema change to explore this. Let's make sure we have those on record ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking ) Rodolfo: should we use David's work plan vs wiki? Bryan: not sure both are mutually exclusive Wiki to start documentation Think we could start a draft specification It could help us to keep track where we are and our focus Wiki for tracking feature Rodolfo: should I start docbook draft? David-F: currently the draft working charter has no plan yet Could reference the wiki tracking page Timeline/priority would go to charter Access to the docbook source on version control? Rodolfo: yes, SVN server Bryan: need ground rules about making sure people working on the file don't break it. Open-source and commercial tools available to edit docbook. === 6/ Current XLIFF business --- 6.1. Alternate meeting focused on Current Business? May need another regular call for current business. For example new meeting once a month on the 4th Tuesday of the month, Or after the SC meeting on the second Tuesday of the month Rodolfo: or maybe 90mn vs 60mn? Issue for Bryan Helena: frankly some of those topics are not interesting. Maybe some of those discussion could be off-line and on a ad-hoc basis. Bryan: to summarize: current business may be bloated and we could trim it so we don't need extra meeting. Probably a temporary situation David-F: having separate meeting would allow people not interested to not attend. Transparency is important. Helena: some of those discussions may need to be done not at the schedule time of the planned meeting. Rodolfo: same for me, prefer the tech stuff. Helena: those topics should not drive away the focus we need to have. Bryan: alas some of those topics need discussions. Prefer the tech stuff too. Could make those current-business meeting not mandatory Helena: if not mandatory and no voting decision are taken there then it's ok. Arle: stating time limit could be a way to enforce a better disposal of the issues. Will continue the current-business discussion on email. === 7/ New Business None -end-