XLIFF TC Meeting (Conference Call) | |
Name | XLIFF TC Meeting (Conference Call) |
Time | Tuesday, 15 September 2015, 11:00am to 12:00pm EDT
(Tuesday, 15 September 2015, 03:00pm to 04:00pm UTC) |
Description | Please get the dial in information from our private Action Item here: |
Minutes | Minutes I Administration (0:00 - 0:10) Attendance: Ingo, David F., Uwe, Bryan, Lucia, Felix, Fredrik, Yves, Tom. Regrets: Ryan, Soroush. - Approve meeting minutes, 1 September 2015 B: I move to approve the meeting minutes. I: I second. B: Meeting minutes approved. - Requesting progress of ISO submision of XLIFF 2.0 B: I have not seen any activity since last meeting. dF: I have not heard anything either. II XLIFF 2.1 -. * Question on fragment identifier (Ryan) Y: this one was solved on the mailing list. B: I will remove it from the agenda for next week. -. Typo in example (4.3.1.10 dataRefEnd) (Yves)
-. Question about note references (Ryan) -. Add N Constraint to the core order attribute B: Any progress on this point. dF: I should do it soon. Action item for dF.
-. Template/Model for TBX Mapping with XLIFF v2.0 and Higher Version 1.0 (DavidF)
F: I am still making progress, it will be done soon. [pending AI for Fredrik]
-. ITS storage size restriction F: I am still making progress, it will be done soon. [pending AI for Fredrik] I. Mistakes in the spec (Soroush) J. NVDL for the core is updated (Soroush) K. * NVDL validation for XLIFF 2.0 (Soroush) dF: Felix, do you have an update on Advanced Validation, as you’ve been in touch with Soroush? F: Not really. Souroush has done a good job. B: it is nice that Oxygen has now basic support for XLIFF 2.0, they are looking into the advanced validation artifacts to support advanced constraints and processing requirements.. dF: we should talk to them to see if they could send a comment to the public list, or allow Bryan to post to the working list B: it would be a perfect statement of use for the new version.
L. * Mistake in test suite files (Soroush) dF: Yves, have you looked at it? We had a discussion on this a long time ago, when Jirka still was an OASIS member. If an attribute is on an element from the same vocabulary it is more economical not to declare the namespace and this is also the strategy we use in our XSDs. This is a generic XML validation issue. B: For example: <gls:glossEntry gls:ref="#m1"> dF : yes, this is invalid according to our schema, we only declare namespace module of an attribute if it’s on an element from a different namespace, like fs:fs, it is always on elements from another namespace. Felix, do you have a comment? dF: we should update the examples of the test suite to fix that issue. I can do it, unless Yves wants to do it. Yves: no problem, please do it. Action item for dF: fix the examples of the sample files. F: I agree with dF. B: It’s an issue with our XSDs? dF: it is not an issue, you can do it either way, but once we decided to do it one way [not to state attribute namespace when on it’s own namespace elements] we have to stick to it, because the other way is not equivalent as Jirka explained. I have to check also on the spec if the same example is there.
M. * Ignorables (Ingo) B: do you need more info from us? Ingo: we are happy with the answers, we do not need more info for the moment. Y: is there a latest version of 2.1 somewhere? dF: I have made the latest build on 5th August. Since then I only made one small typo fix, that is not in the build. Tom: ITS XSD is current. I need to confirm extension points in other modules.
dF: The work on the new version of the questionnaire is on. We are having a meeting after this TC meeting. Stefan Gentz raised some interest in XLIFF support on twitter, in an exchange of tweets SDL acknowledged that they’re working on the support of XLIFF 2. It is good news that the community cares about the XLIFF 2 adoption and the reports that we do. Stephan Gentz and @Jeromobot, distinguished Tweeters in the L10n areas were inquiring about the new version of our XLIFF 2 adoption report (SotA). dF: we should also talk about the sister committee (which will be a good home for TMX, as discussed and minuted in August). Anybody interested in the SC meeting should stay on this channel after the TC meeting adjourns. This week TCD will sign OASIS accession, so hopefully there will be good progress on this before next meeting. dF: Next European LocWorld will be in Dublin again, which will be a good location for the next Symposium. It can be a good pre-conference to LocWorld. B: Have you looked at China in LocWord? dF: we have considered an Asian location for the next symposium, I spoke on XLIFF in Shanghai and sounded the ground there, but we should plan it carefully. It might be difficult for members to attend there. IV Current and New Business dF: Phil was interested in the ITS text analytics category in XLIFF, we should put it on the agenda for next meeting. B: Will do, TC meeting adjourned. |
Agenda | I Administration (0:00 - 0:10) B. Approve meeting minutes, 1 September 2015 D. Requesting progress of ISO submision of XLIFF 2.0
II XLIFF 2.1 (0:10 - 0:45) * indicates new topic, not yet discussed A. Discuss whether can be allowed at all extension points (Ryan) F. Add N Constraint to the core order attribute [pending AI for Fredrik] G. Template/Model for TBX Mapping with XLIFF v2.0 and Higher Version 1.0 (DavidF) [pending AI for Fredrik] H. ITS storage size restriction [pending AI for dF] I. Mistakes in the spec (Soroush) J. NVDL for the core is updated (Soroush) K. * NVDL validation for XLIFF 2.0 (Soroush) L. * Mistake in test suite files (Soroush) M. * Ignorables (Ingo)
IV Current and New Business (0:55 - |
Submitter | Bryan Schnabel |
Group | OASIS XML Localisation Interchange File Format (XLIFF) TC |
Access | This event is visible to OASIS XML Localisation Interchange File Format (XLIFF) TC and shared with
|