Dear all,
Please find yesterday's meeting minutes.
Best,
Lucía
----------
Attendance: Rodolfo, Mihai, Yoshito, Mathijs, Lucia. We have quorum.
Administration
R: I move to approve August 5, meeting minutes – https://groups.oasis-open.org/discussion/meeting-minutes-23
M : I second.
R : Meeting minutes approved.
Charter clarification approved. Special Majority Vote to approve a clarified charter for OASIS XLIFF TC. https://groups.oasis-open.org/higherlogic/ws/groups/3d0f1f56-8477-4b53-9b14-018dc7d3eecf/ballots/ballot?id=3891
L : The updated charter is now available on the OASIS website: https://groups.oasis-open.org/higherlogic/ws/public/document?document_id=72908&wg_id=3d0f1f56-8477-4b53-9b14-018dc7d3eecf
R: The content is not longer in HTML, is in a PDF.
L: Yes, that PDF document includes the table including the changes and the explanations. We can close this topic.
R: About the renewal of the co-chairs.
L: We had a roll call on this topic, but if you think that we should inform our OASIS administrator, we will do it. And I am not really attached to this position, so if anybody at some point wants to take it, I will happily step over.
R: We actually did that when you were on maternity leave and Yoshito took the co-chair role. I think we are all happy on how things are running.
Technical
Promotion activities of the new version. Webinar. Mihai, all.
L: We have received an answer from OASIS explaining the support that they can offer us, we need to prepare now all the materials.
R: I think we have already stablished the distribution of tasks.
L: yes, you, Mihai and Yoshito will work on the presentation and I will prepare a draft of all the promotional materials they need, I will send it to you for approval. In terms of deadlines, they told us that the promotion could start after US labour day, we are meeting ourselves a day after, so we can discuss the last details on that meeting.
L: Mathijs, If you have any advice on this or if you want to be involved, let us know.
M: It would be great to have the implementers. Let me think about it, I will ask around.
Revisit the test suite topic: https://github.com/oasis-tcs/xliff-xliff-22/tree/master/xliff-21/test-suite . Yoshito.
Y: I have not had the time to work on it but hopefully I will do before the next meeting.
New translation memory standard. https://github.com/oasis-tcs/xliff-xliff-22/tree/master/memory and Metadata exchange information, Mathijs, all.
R: I got an email from Lucia with metadata with suggestions. Thank you. I have been doing a lot of research on this. I do not see a lot of people including information on state. We are not suggesting metadata at unit level, and that would be very important for TM. I think is something we should write about it, an implementation note. It might be good to store the information in the segment, so we have the metadata there that can be retrieved later in the future. We do not have that right now and we are not telling people how to do it.
M: I wonder if vendors have an interest in that. The point is, for example, I do not want my client to have the name of my translators.
R: But it can very useful internally and for other purposes, for example, I provide translation memory servers, sometimes I need to move data from one server to another.
M: Another thing is that people might be storing that information but we are not receiving it.
R: That is something different. I am suggesting that we tell people how to store it, but them it is up to them if they use it and they could always use a filter to delete it if they want to pass it over.
M: It is quiet common in 1.2, It is shared.
R: I am suggesting using the same mechanism as in 1.2 but in 2.2.
Y: We can use the metadata module, but there are not standarised attributes for that
L: I am actually working on an analysis of the current attributes in the spec that allow us to include metadata about the localisation process. I did that analysis for my PhD research with version 1.2 (Lucia shares her screen where she shows a table where all localization metadata related attributes are organized), I started doing the same thing for 2.2 but the task was harder than I anticipated as much of the information is not there or is scattered in different modules. If you think that this is helpful I will try to work on it and send my results to the main mailing list.
M: yes, that information could be useful.
R: I agree.
R: We cannot force implementers to do something, but we can recommend them how to do things.
Y: we can extend the metadata module.
R: That can be a way that.
Y: The metadata module as it is now is quite free.
M: I am checking it now, in the sample code, we have an example with phase.
R: I have been working with metadata in my products, I realized that there is no standarised way for phase, as you mentioned.
M: there is not standarised way of calling phase.
R: That is why I am suggesting we do something about that.
New business
M: When I search for XLIFF specs, all the links are broken. It is difficult to find the official specs. Even in Wikipedia, we cannot find the new version.
R: the new OASIS page has broken many things, not only XLIFF-related content. I can try to update Wikipedia as this might alleviate somehow the problem.
M: only partially, we can change Wikipedia, be we cannot change the OASIS page. Can we fix this?
R: only the OASIS administrators can make those changes.
L: I think we need to address this issue, thank you Mihai for raising it, if we ourselves are having an issue finding the specs, imagine the rest of the audience. Mihai, could you prepare a short message explaining the issue? We will forward it to the OASIS admins so they are aware of the problem and hopefully fix it.
M: I can do it.
L: That would be great, thank you.
M: Another topic, in the message format group, there is a couple of members that come from the javascript world, there are missing a standarised mechanism to store the translatable content. There is interesting to develop a standard for that. Do you think that OASIS could be a good solution for them?
R: they have an internationaltion module .
M: Yes, but there is not a standarised way for indicating which elements should be translated. Message format is just for messages. I think OASIS could be a good home for them.
Y: Most of javascript currently uses json to store resources.
M: but there is no standard way.
R: I used json to translate javascript. We can be a good home for them because we can publish localisation notes. We can provide a format for storing that information.
M: I do not think it would belong to XLIFF, but maybe another group.
Y: There was another group that is already closed in OASIS that tried to define JLIFF.
R: Your idea suggesting OASIS is good, we could collaborate with converting that standard in XLIFF. They might be interested in participating.
M: The other reason is because I think in OASIS they understand how localisation work.
R: Suggesting OASIS is a good idea.
Y: I am just wondering if it is too late, because people are doing their own thing.
R: It has to be compatible with the internationalization module.
L: Yes, OASIS could be a good place for them. However, just let them know that participation requires a membership, and that this can sometimes be a barrier for some individuals or companies (as it is not inexpensive)
No new business, meeting adjourned.
-------------------------------------------