 XLIFF TC Meeting (Conference Call) |
|
| Name | XLIFF TC Meeting (Conference Call) |
| Time | Tuesday, 02 February 2016, 11:00am to 12:00pm EST
(Tuesday, 02 February 2016, 04:00pm to 05:00pm UTC) |
| Description | Please get the dial in information from our private Action Item here:
|
| Minutes | Attendance: Bryan, Fredrik, Patrik Mazanek, Yves, Felix, Lucia, Phil, Soroush, David F, Felix.
I Administration (0:00 - 0:10) B. Approve meeting minutes, 19 January 2016 B: I move to approve. David F.: I second. B: minutes approved.
D. Requesting progress of ISO submision of XLIFF 2.0 Df: I have not heard from Peter or Jamie, but Felix put me into contact with another ISO member who might help us to move this forward. I will try to join the Irish delegation. If this delegation proposes this item, it might be on time for the Copenhagen meeting.
E. * XLIFF 2.0 Support - Survey (Lucía)
L: we had Bryan’s entry. This will be discussed in the subcommittee today. Phil: we still have to do it. Fredrik: we also have to do it. Davidf: we will try to ping people from Microsoft too.
F. * Action Item progress (as tracked in kavi AI tracker) B: we will agree to move the remaining AI to the kavi tracker too weeks ago. From my side, I still have not found the time to make the changes to the test suite. Df: I have made some svn in my new machine and I will make some progress in the few next weeks. F: I am moving forward with the editing of the docbook, and I found time to work on it. What takes more time is all the crosslinking and docbook technical issues. I am using an XML editor. B: that’s great, thank you. Davidf will continue to work on his, and I will continue to work on mine.
G. XLIFF 2.0 beta for Studio 2015 available - (Patrik) https://lists.oasis-open.org/archives/xliff/201601/msg00015.html Thank you to Patrik and SDL, they have made the announcement and they have asked everybody to test it. On behalf of the TC, we will be happy to provide you feedback. P: If you need temporary licenses to try it, I can provide you. Btw, the beta filter will be added to the list of filters already present. P: People are asking if we are having support for CD data inside source and target. Df: for enterprise solutions, will it work? P: they can still test it locally with Studio. We have some detailed documentation that I can share it with you. Df: if the beta goes well, how long would it take to have in stable versions? P: I cannot speak for them on that. B: Thank you very much, Patrik, for this good news.
II XLIFF 2.1 (0:10 - 0:45) B: there have not been any new issues on the mailing list since last meeting. N. * Inline IDs in / in mtc and ctr modules (Yves) Y: everybody agreed on this point, I think we can close it. B: If we can capture that language would be step 1, and to assign AI to the owners would be step 2. Df: Isnt it Phil Df: we can say that the TC only talks on core’s uniqueness. Y: Another way to record it properly is to have an example that helps people to understand. I can take an AI to do the examples. Df: we should have a warning saying that uniqueness is only for core (DavidF’s AI). We should also have the module’s owner to define the uniqueness in their specific cases (AIs). We should also solve this issue for the advanced validation (AI). Y: can we have another AI for Ryan for their tools? Df: Maybe Patrik can check that too? P: We are using some of the content from the public Microsoft libraries. F: Another Ai, would be to allow inline elements in change tracking. That relates to point K ( K. * Inline codes in Change Tracking (Yves) https://lists.oasis-open.org/archives/xliff/201512/msg00010.html). Y: that’s true. P: I can take a look at that and see if we need some work on the schema and the duplicate ids.
B: Any other agenda items that we should discuss today?
III Sub Committee Report (0:45 - 0:55) Y: Omos XLIFF, we met last week. Df: we discussed the Json representation and we agreed to move ahead. The wiki is also set now. It was a good discussion. I am participating in the augmented reality committee, we can add a liaison as well, it is a new exiting field, and we should be able to see how to represent in XLIFF. They are also interested in multilinguism. Do you agree to add this TC to the Tc0s liaison? I can call for a call for dissent next time. B: Sounds good. F: I would like to know what they make them special for content to have a liaison with us. Df: they are having connections with CMS. The modality has different models. Our interests is that they are aware of our existence, and that they are aware of the possibilities that XLIFF can provide them B: A same procedure happened with DITA, which they become aware of the advantages of XLIFF and they embraced. Df: Felix, do you think that we should outreach HTML5 group or any other W3C group? Felix: Most of the work now is doing through working groups. I can contact them to get some traction. Df: so you suggest to create new liaisons, instead F: I would sit down and see how they are addressing. Felix: I think that there were some efforts to have Aria and HTML together. I think the more concrete actions, the more traction you would get. Df: the reference guides. We might uncover some needs from other modules and put them into reference guides. Getting w3c input for the requirements, even if the reference guides will be eventually done by the TC.
Df: We still have not enough proposals for the symposium. We will discuss it further in the subcommittee. Df: Souroush is giving a seminar on XLIFF and ITS. |
| Agenda | I Administration (0:00 - 0:10) B. Approve meeting minutes, 19 January 2016 D. Requesting progress of ISO submision of XLIFF 2.0 E. * XLIFF 2.0 Support - Survey (Lucía) F. * Action Item progress (as tracked in kavi AI tracker) G. XLIFF 2.0 beta for Studio 2015 available - (Patrik) https://lists.oasis-open.org/archives/xliff/201601/msg00015.html
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) / in mtc and ctr modules (Yves)
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
|