Dear all,
Please find below yesterday's meeting minutes.
Best,
Lucía
**************
Attendance: Rodolfo, Mathijs, Mihai, Lucía, Yoshito.
Administration
R: I move to approve November 4, meeting minutes – https://groups.oasis-open.org/discussion/meeting-minutes-28
L: I second.
R: Meeting minutes approved.
Technical
Errata status. Rodolfo.
R: Mihai updated and I created the branch to publish the errata. (Rodolfo shows the github and explains where the branch with the errata is located). The its namespace is fixed, and the examples from Mihai were fixed as well. We would need to add "errata" included in the document, and the urls might need to be changed. We need to contact Kelly for assistance on this.
L: Thank you both. Do we have a place where these changes are documented?
R: we will also have to modify the Appendix F (Revision History). If you agree with the changes. It is not difficult but it is time consuming. All we need to do is to review and say we are happy with the changes.
L: How do we communicate that we have done the review?
R: you can send a message to the official list.
Y: you can also reply to the issues, add a comment there.
Mathijs: I have found a possible issue in example 4.6.9, no id in the ph element.
M: yes, it is an issue.
R: you can add an issue.
M: I always appreciate when I see examples of code, so it is great if no issues are present.
Revisit the test suite topic: https://github.com/oasis-tcs/xliff-xliff-22/tree/master/xliff-21/test-suite . Yoshito.
R: I ran all the validator against all the files in the folders. There are invalid files in the valid folder (more than one) (Rodolfo shows the results on his screen), for example, there is a duplicate id in notes. We had several of these.
Y: Can you create an issue and paste this list of errors? I will fix it.
R: sure.
Y: I will fix it later this week.
New translation memory standard. https://github.com/oasis-tcs/xliff-xliff-22/tree/master/memory
R: I had to finish the library for typescript. It is freely available now. https://github.com/rmraya/TypesXML
L: That is really good news.
Provenance metadata discussion. https://groups.oasis-open.org/discussion/metadata-discussion, work on progress on the note draft to describe how to include provenance metadata in XLIFF 2.2, Lucía.
L: I have already prepared a draft I will try to share it with you by the end of the week or early next week.
Updates from Mathijs.
Mahtijs: Blackbird is not a tms, we are an orchestrator, you connect all different applications and you can create a workflow. (Mathijs is sharing his screen and doing a demo). You workflow gets more elaborated and you are more in control. The moment we go from monolingual to multilingual, we use XLIFF. Black Lake is the new storage system that we are releasing.
M: Can you have a list of languages?
MA: sure, I am showing just one language for the demo, but we can have other languages.
MA: There is extra data that we can apply (for example, what system did it). We can also make changes, and the metadata about those changes are kept in the metadata.
Ma: Let me show you the xliff, we are using ITS module. (shows example of metadata that are being used and who provenance metadata is being kept)
R: That is great, that what XLIFF can do and that TMX cannot.
Ma: we use XLIFF 2.2, of course.
M: We also use XLIFF for TM.
R: We have tms coming from different sources, we want to have inside a list of files.
Ma: do we need that?
R: just for easier transfer, we are still dealing with XLIFF.
Ma: for me it will be interesting to know if we have two files that have the same content to know which was modified more recently.
L: How do you include the information about the date?
MA: the system does, it is not kept in XLIFF.
M: for information like history, can be included in a history event, and then you can attach them.
R: We used to have the change tracking module, but it was demoted.
M: The whole OKAPI system works in a similar way.
Y: This a good example of use of XLIFF.
L: that is what we need, examples from real cases where metadata is used in XLIFF. It can be used as a base to improve the metadata module or any other mechanism to store metadata information that we might have in XLIFF.
R: This is great, we should provide a guideline, for example, if you are going to store a date how to do this.
M: I am brainstorming now, but I think we would need to some kind of manifestor description to say what the tool supports.
R: Yes, I had examples when they did not support matches.
M: Same here, we had several experiences.
L: We do not have more time today, thank you for all the work that you have done and the fruitful discussion, see you in two weeks.
------------------------------
Lucía Morado Vázquez
Researcher and lecturer
University of Geneva
------------------------------