[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] type for ref of match and glossEntry and #212
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----- From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Yves Savourel Sent: Sunday, March 16, 2014 04:36 PM To: xliff@lists.oasis-open.org Subject: [xliff] type for ref of match and glossEntry and #212 Importance: High 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 --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]