OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only
  • 1.  Meeting minutes

    Posted 58 minutes ago

    Hello all,

    You can find below this week's meeting minutes.

    Best,

    Lucía

    -----------------

    Attendance: Mihai, Rodolfo, Yoshito, Lucia, Mathijs. We have quorum.

    Administration

    R: I move to approve November 18, meeting minutes – https://groups.oasis-open.org/discussion/meeting-minutes-29

    Ma: I second.

    R: Meeting minutes approved.

    Technical

    Errata status. Rodolfo.

    L: I have found an issue with the URL location of the schemas https://github.com/oasis-tcs/xliff-xliff-22/issues/50

    R: I will look into it.  The location of the schemas were changed by the OASIS administrator.

    R: I have also found another issue, (number 49), the its schema declares the xliff namespace but it does not really need it.

    L: We do not need it because ITS does not really exist on its own.

    R: What do the others think?

    Y: If we do not use it, we can drop it.

    R: the reference is to a specific xliff version, so if we update xliff, this will have to be changed.

    Roll call: Do you all agree to remove the xliff namespace from the its module schema?

    Yes: Rodolfo, Yoshito, Mathijs, Lucia, Mihai.

    The roll call passes.

    R: I will make the change for the errata.

    Y: we have the same issue in itsm.xsd.

    R: I will analyse this case and if you think we can remove the itsm schema. This might be more than an errata, I think.

    Y: It sounds like we need to investigate the history of this.

    R: the only thing itsm seems to do is to contribute with the attributes domains and lang. I do not think it is safe to remove this.

    M: we have a mix of versions in many cases. I looked in the folder xliff 2.2, and we have inconsistent version. In change tracking we have several issues.

    L: But change tracking is not a 2.2 module, it was demoted.

    M: (shares his screen and shows the problem with the versions in the namespaces).

    L: In the XML Schema Tree, it specifies the two schemas.

    R: I personally do not use that module, I do not think it is a good idea to remove it, we just need to update the xliff version. Let me think about this. Can you add a ticket for this?

    Y: we can amend the existing one.

    R: I think we need to stop talking about an errata and start talking about a new version if we decide to make those changes.

    Y: If I understand it correctly, a schema change should not be done in the errata. But dropping the namespace does not seem to be a change.

    R: but the itsm is pointing to the old version and it needs to be updated.  That is a major thing.

    Y: I do not understand how its is pointing to xliff namespace.

    R: itsm is importing core and it is adding attributes, but I don't understand why is importing xliff.

    Y: We need some investigation on this matter. This is homework.

    Revisit the test suite topic: https://github.com/oasis-tcs/xliff-xliff-22/tree/master/xliff-21/test-suite . Yoshito.

    Y: Thank you Rodolfo for finding the issues. I will do my part this month.

    New translation memory standard. https://github.com/oasis-tcs/xliff-xliff-22/tree/master/memory

    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. https://groups.oasis-open.org/discussion/first-draft-guidance-on-provenance-metadata-in-xliff

    L: I have shared the very first draft of the document, thank you Mihai for your feedback.

    M: the document looks good, I have made some comments to improve some aspects.

    L: thank you for your comments, very helpful.

    R: I think the table was a good idea.

    L: I found it confusing as it was standalone, but I can put it there as a summary.

    R: Yes, that can be a good idea.

    L: I had this fundamental question about the prefixes in the modules. I need to review this aspect in the document.

    Ma: the treatment of inline tags for using xliff as a tm.

    R: when we were discussing, Yoshito suggested dropping the definitions.

    Y: It is more like the implementation.

    Ma: there are different ways that you can deal with this.

    L: We do not have more time today, but I will add this issue to the next agenda so we can discuss it properly.

    Indexing issues, Mihai

    You can remove this from the agenda, the issues seem to have been solved



    ------------------------------
    Lucía Morado Vázquez
    Researcher and lecturer
    University of Geneva
    ------------------------------