 XLIFF TC Call (Conference Call) |
|
| Name | XLIFF TC Call (Conference Call) |
| Time | Tuesday, 03 May 2016, 11:00am to 12:00pm EDT
(Tuesday, 03 May 2016, 03:00pm to 04:00pm UTC) |
| Description | Please get the dial in information from our private Action Item here: |
| Minutes |
I Administration (0:00 - 0:10) Attendance: Bryan, David F., Yves, Fredrik, Phil, Lucia, Soroush, Tom Comerford Bryan: I move to approve meeting minutes, 19 April 2016 DavidF: I second. C. Revise scheduled for XLIFF 2.1 - Bryan will provide this NLT second meeting in May
D. ISO submission of XLIFF 2.0 Liaison report to ISO TC 37 (Peter) E. XLIFF 2.0 Support - Survey (Lucía) (moved to the P&L subcommittee) F. Action Item progress (as tracked in kavi AI tracker) Some of the AI have been closed, thank you Yves and David for the good work on the closed AI ones. Fredrik: Unfortunately I do not have progress on my AI. B: I do not have progress to report on mine. Phil: No progress on mine either. DavidF: Felix has been organising the work on the ITS categories. There is work going on. I propose an AI on the MT confidence data category for me.
G. Check prefix registration. B: I have not registered my prefix, I think nobody has done it yet. We have not received any information on this. Df: I think it is good to have the routine to check for the registration. F: It is used to register prefix that I used or fragment identifiers? Df: It is related, because it is recommend to have them related. F: I can see a near future where people can have customised values for some attributes like matches. Df: I think that case specifically would be very valuable to have it published. F: Exactly. We can also allow for an URL where they can actually have all the information in their own systems. Y: When you register a prefix we can also have the URL that points to the definition. Df: this could be also good for the owners, so they can maintain themselves in their own systems. Yves: I can take AI to update the information on the wiki on that topic. F: It sounds great. B: It is a step on the good direction. Df: I would like people that own prefixes to test how it works.
H. Ann: XLIFF 2.1 - ITS support (Yves) Y: I sent the information and I would like people to test it if they can. There is still work to do, but I am working on it. Df: Thank you Yves.
K. * 5.9.8.1 annotatorsRef (Yves) Y: I think we addressed in some of our discussions with Soroush, David and Felix. Information was added to the draft. This item can be considered as closed. B: perfect, I will remove it from the agenda for next meeting.
L. * ITS in XLIFF 2.1 edits, feedback welcome (Felix) B: Felix made two proposals to move on this topic. I ask you to please have a look on them, and we will discuss on the next May meeting. Y: We need to organise ourselves as Felix pointed out. We can get lost when defining things in the spec. The sooner we do that, the better. B: Ok, we can discuss it today. (Bryan reads Felix message) F: I agree with Felix. The problem with modules and having crossrefences is that we can get lost easily on the spec, that is a problem. Df: that is an issue with docbook. Y: A different aspect that can be simplified. I think that we should have in the same module all the data categories definitions. Having all the information there can help to make it more understandable. Df: I can remove the appendix and move everything into the module. I can do that. But I would not want to break the module structure. Attributes and elements should be placed as in other modules. Y: The annotation can also be done by category. So all the information is grouped in the same section. Df: this will be different from the rest of the spec. Y: this module is different from the rest. Df: If you do not define all the data categories, then you need to create another module. Y: not necessarily, you can just update the module. Df: we discussed this before, and we thought about not updating but to create new ones. F: then it sounds like we fail on this, if we cannot update them. Y: Yes. F: As far as I see it, we should be able to update modules, instead of adding new ones. As long as we release an update, with the information on the additions, I do not see a problem. Df: we need to know how to specify that information. F: I do not see the big problem. Df: one thing is the version of the module and the version of the namespace. B: We should continue with this discussion after this meeting.
III Sub Committee Report (0:45 - 0:55) Df: There will be a meeting. I was in the JIAMCATT in Geneva last week, there seems to be a strong interest in the new version. Some work will be done in their own interoperability group. The speakers for the new symposium were announced today. Do register for the next symposium and come to Dublin. Y: OMOS tc report: there was a short attendance. Lucian took an AI to work on the diagrams and we are waiting for Df to start working on the specification.
B: Meeting adjourned |
| Agenda | I Administration (0:00 - 0:10) B. Approve meeting minutes, 19 April 2016 D. ISO submission of XLIFF 2.0 Liaison report to ISO TC 37 (Peter) E. XLIFF 2.0 Support - Survey (Lucía) F. Action Item progress (as tracked in kavi AI tracker) G. Check prefix registration. H. Ann: XLIFF 2.1 - ITS support (Yves) II XLIFF 2.1 (0:10 - 0:45) * indicates new topic, not yet discussed A. Inline attributes and canCopy (Ryan) B. * CanReorder Validation error (Ryan) C. * ITS text analytics (David) D. Internationalization and beyond related metadata for JSON - XLIFF perspective? (Felix) E. * Question on namespace re-writing and ITS text analysis (Felix)
G. * XLIFF and ITS mapping-ID value (Soroush) I. * XLIFF 2.1 - ITS support; editing calls (Felix) J. * itsm namespace in extension registration (Yves) K. * 5.9.8.1 annotatorsRef (Yves) L. * ITS in XLIFF 2.1 edits, feedback welcome (Felix) III Sub Committee Report (0:45 - 0:55) 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
|