[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (XLIFF-6) ITSM id values scope
David Filip created XLIFF-6: ------------------------------- Summary: ITSM id values scope Key: XLIFF-6 URL: https://issues.oasis-open.org/browse/XLIFF-6 Project: OASIS XML Localisation Interchange File Format (XLIFF) TC Issue Type: Improvement Components: ITS Module Affects Versions: 2.1_csprd01 Environment: https://lists.oasis-open.org/archives/xliff-comment/201610/msg00017.html Reporter: David Filip Assignee: David Filip Fix For: 2.1_csprd02 Currently the spec says: [[ Any value of this id attribute MUST be unique either among all <locQualityIssues> and <provenanceRecords> elements within the given enclosing <unit> element if the ITS Module elements, on which the attributes are set are children of a <unit> element, within the enclosing <group> element, in case of <provenanceRecords> elements that are children of a <group> element, or within the enclosing <file> element, in case of <provenanceRecords> elements that are children of a <file> element. ]] But the value probably need to be unique at the document level to match the ITS semantics. A pure ITS processor would not be able to make the distinction of scope done by XLIFF. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]