Hi all,
Please find below today's meeting minutes.
Best,
Lucía
----------------
Attendance: Mihai, Mathijs, Rodolfo, Yoshito, Lucía. We have quorum
Administration
R: I move to approve September 16, meeting minutes –https://groups.oasis-open.org/discussion/meeting-minutes-26
Mi: I second.
R: Meeting minutes approved.
Technical
Promotion activities of the new version. Feedback on webinar.
L: It went really well. Thank you for your efforts. I had some private requests for the recordings before the OASIS blog post. I have reposted the blog post of OASIS. I am planning to do another post explaining where all the 2.2 related resources are. I was wondering if we should have an official channel in Linkedin of the TC, instead of publishing from our personal pages. I know that OASIS has it, but we may have ours to have our announcements there.
R: we can contact OASIS.
L: Sure, I will contact them and see what would be the best communication strategy. If you have any other ideas about promotion please let us know
Ma: I have talked to several people in the last days.
Y: do you know if OKAPI is supporting 2.2?
M: I do not really know.
Y: I think if would be great if important libraries support it.
-Indexing issues, Wikipedia. Mihai .
R: I edited Wikipedia, so it has the updated information.
L: Mihai, It would be great if you could prepare an email that we can forward to OASIS explaining the indexing issues.
Revisit the test suite topic: https://github.com/oasis-tcs/xliff-xliff-22/tree/master/xliff-21/test-suite . Yoshito.
Y: I am not active in this one.
R: I've checked the files and that are still issues. For example, valid files that have a ph issue, or the opposite. I abandoned the project. I do not know if you want me to collect them. While doing that, I found an error in the spec that came from 2.1. The namespace of ITS was not correct. There is not https in the spec. I added a couple of issues in github.
L: they look like editorial issues to me, we could create an errata for this.
R: We need to initiate the process of publishing an errata.
R: Yes, they are easy to fix.
Y: I am just worried about this one (45) I think it is important that we do it as soon as possible to have the examples fixed in the new module. https://github.com/oasis-tcs/xliff-xliff-22/issues
L: Lets do a roll call. Do you agree to initiate the process of publishing an errata to fix issues 43, 44 and 45 (described at https://github.com/oasis-tcs/xliff-xliff-22/issues)?
Yes: Mihai, Rodolfo, Mathijs, Lucía, Rodolfo.
L: thank you, Rodolfo and I will check the OASIS protocol and initiate the process.
New translation memory standard. https://github.com/oasis-tcs/xliff-xliff-22/tree/master/memory
R: I do not have any updates on this topic. We need to find users that tell us what they want.
Metadata exchange information.
L: I will do my best to do the analysis of the spec and send it to you before the next meeting.
L: No new business, meeting adjourned.
------------------------------
Lucía Morado Vázquez
Researcher and lecturer
University of Geneva
------------------------------