OASIS XML Localisation Interchange File Format (XLIFF) TC

  • 1.  type for ref of match and glossEntry and #212

    Posted 03-16-2014 20:36
    Hi all, The comment 212 stated that ctr:revisions@ref was NMTOKEN in the space and xs:anyUri in the schema. https://lists.oasis-open.org/archives/xliff-comment/201402/msg00012.html That has been corrected: they are both NMTOKEN now. However, the following text was added in the issue tracker: [same issue applies also to gls:glossEntry@ref, gls:translation@ref, and mtc:match@ref] So Tom changed the type for those two refs as well. But they were (and still are) IRI in the specification. Personally I think having NMTOKEN for match@ref would OK. But for glossEntry@ref, gls:translation@ref it would mean we can't point to content in the target. In any case: we have a discrepancy now. I think glossEntry@ref, gls:translation@ref and match@ref need to be set back to xs:anyUri in the schemas. -yves


  • 2.  RE: [xliff] type for ref of match and glossEntry and #212

    Posted 03-17-2014 01:50
    Yves, thanks for catching and correcting this. My notes don't shed much light on why I changed all of the attributes in the first place. This is also one of the few kinds of errors that the QC scripts can't (yet) catch.
    Original Message


  • 3.  RE: [xliff] type for ref of match and glossEntry and #212

    Posted 03-17-2014 02:17
    It got caught thanks to the few hundreds of unit tests the toolkit has. I think you were just following the text that was added in the issue tracker. I should have noticed and double check the extra references to the matchea and glossary modules when we went through the list. -ys
    Original Message


Related Content