Dear all,
Please find below today's meeting minutes.
Best,
Lucía
-------------
Attendance: Rodolfo, Mathijs, Yoshito, Lucia. We have quorum.
Agenda:
Administration
R: I move to approve September 2, meeting minutes –https://groups.oasis-open.org/discussion/meeting-minutes-25
Y: I second.
R: Meeting minutes approved.
Technical
Promotion activities of the new version.
Webinar. Mihai, all.
L: We have been in contact with OASIS promotion people who helped us with the organisation of and promotion of the webinar. They have set up the webinar and made an announcement on Linkedin. Please share it with your contacts. Next week, they will publish the blog post, please help us to share it as well. Rodolfo, could you take care of including an item in the "announcement" section of the website? I can send a message to the mailing lists (tc and comments)
R: Sure, I will.
L: for the organization of the presentation, there is the presentation that Mihai started using the OASIS template.
M: I have included there my two intro slides.
Y: It would be great if we can have a meeting on the 30.
L: Sure, I can create the meeting and share it with you. You might be get contacted by Jane to try the Zoom platform.
Revisit the test suite topic: https://github.com/oasis-tcs/xliff-xliff-22/tree/master/xliff-21/test-suite . Yoshito.
Y: I created a folder, copied from the previous test suite, I dropped the in and out. I did not add any bad examples.
R: I merged the changes proposed from Yoshito.
Y: While working on it, I noticed an error in one example of the spec. In the example in 4.9.6.2, we have the same id. We need an errata or something to fix it.
R: Good catch about the error. The first thing we need is a ticket to fix it.
Y: Sure, I will do it. The new module. I would like to discuss also the examples, I am not sure if the disp attribute is used correctly. We might need to look into this topic, how the mapping with the variable is being done in those examples.
R: When we will publish the errata, we can also add a note giving more information about how to match variables.
R: Can you create also a ticket on open XLIFF to create the validation of XLIFF 2.2?
Y: Sure.
R: So I can remind myself to update the tool.
Y: There is also an issue with the readme file.
New translation memory standard. https://github.com/oasis-tcs/xliff-xliff-22/tree/master/memory
R: No news on this topic.
Metadata exchange information, all.
L: I am planning to do the metadata analysis on the new version that I mentioned in a previous meeting. I hope to do it before the next official meeting.
M: I would like to share two items with you. The first one, in Blackbird we did a survey on linkedin. https://www.linkedin.com/posts/brunobitter_which-language-technology-staple-is-most-activity-7369315969850089473-CGyp/?utm_source=share&utm_medium=member_desktop&rcm=ACoAAB81RosB9y2IrzTQFlUblxxOsHMb3ks-jQg Interestingly the most voted one is Static style guides (PDF).
The second one. I am working on a project, we are always synchronizing with the TM. We asked ourselves if we wanted to import TMX. And we said no because we did not have enough context. It is very much aligning with what we are planning to do in the TC. In the next meeting I can update you with our work.
L: That would be great. I would add a point in the agenda.
Y: we want the support from big players (adobe, wordpress, etc.).
R: That also depends on clients. If a client says to the company that they should change to XLIFF .2.x they would do it, but they might not hear us. One example, if you send an XLIFF file with matches to Trados, it does not display the matches. So clients must claim a good support of the standards for tools makers to implement it.
R: In any case, the standard is needed.
L: no new business. Meeting adjourned.
------------------------------
Lucía Morado Vázquez
Researcher and lecturer
University of Geneva
------------------------------