XLIFF TC Meeting (Conference Call) | |
Name | XLIFF TC Meeting (Conference Call) |
Time | Tuesday, 06 March 2018, 11:00am to 12:00pm EST
(Tuesday, 06 March 2018, 04:00pm to 05:00pm UTC) |
Description | Call details inside private AI:
https://www.oasis-open.org/apps/org/workgroup/xliff/members/action_item.php?action_item_id=3663 |
Minutes | Attendance: Phil, Bryan, DavidF, Lucía, Yves, Tom Comerford, Steven (6 voters + Steven)
Agenda B: I move to approve Feb 22 meeting minutes P: I second. B: Meeting minutes approved. We can start thinking about an alternative to the web system we use for the meeting. II. Where do we go next? Df: I think it is ok to record the features even if you are not the owners. In practical terms, features without owners do not move forward specially in review phases. But it is ok to add features at this stage even if you do not have an owner. Df: We can add the features that were mentioned in the symposium. The roundtrip validation was one of them. B: yes that it is a good idea to have all the features that were mentioned in the symposiums. I am not prepared to discuss my proposal (adopting LISA standards), I am going to do it next time. Df: you can put the segmentation metadata roundtrip. B: Should I add Steven as owner. Df: we should make a call for an owner. The description could be “Module to specify and keep track of segmentation method changes. Ability to track segmentation methods”. We should also have the “Change Tracking Module” to resolve the issues around the inline element change tracking. [Bryan adds these two features to the wiki]. S: The notes issue is that we need to have top level notes at the XLIFF level that enables links <file>. What we talked in the symposium was adding an extension. Df: We also talked about plurals. S: Another item could be a semantic domain for placeholders. Where the placeholder has an ontology that specifies what the placeholder is. Semantic information about what the placeholder means – beyond human readable. So you can correlate with translation examples. Df: It can be used also for MT. S: sure, that can be used for that as well. Df: another feature can be subsegment matching and reference. Another is rendering requirements (inform XLIFF community how to render XLIFF) Df: we are just defining features at this point, instead of developing them which will be done later. Df: Plural handling should be another feature. S: Specifying plural rules. Df: Likely to address with ITS metadata in source and extraction.
B. TM Profile note Df: are any volunteers to start documenting it? III. Subcommittee and sister TC reports Df: the JLIFF is progressing very well. Df: we are having a SC meeting after this meeting. Df: the sc has started working on the Statement of Use so we will be able to report on this next time. C. ISO Tracker AI: to prepare the ISO submission draft. IV. New business
|
Agenda | I. Approve Feb 22 meeting minutes II. Where do we go next? B. TM Profile note C. ISO approval III. Subcommittee and sister TC reports IV. New business |
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
|