Soroush, does that sound right?
Felix, did you commit to SVN?
Felix, please say this also on the issue 45, since the change from IDREF to URI is due to this issue
Cheers and thanks
dF
Dr. David Filip
===========
OASIS XLIFF OMOS TC Chair
OASIS XLIFF TC Secretary, Editor, Liaison Officer
Spokes Research Fellow
ADAPT Centre
KDEG, Trinity College Dublin
Mobile: +420-777-218-122
On Tue, Apr 4, 2017 at 1:13 PM, Felix Sasaki <> wrote:
Hi David, Soroush, all,
I validated the complex example in the latest draft and got an error reported by its.sch . I adapted the its.sch as highlighted below.
<sch:pattern>
<sch:rule context="xlf:mrk[@its:locQualityIssuesRef] | xlf:sm[@its:locQualityIssuesRef]">
<sch:report test="@its:locQualityIssueSeverity or @its:locQualityIssueProfileRef or @its:locQualityIssueEnabled">
If the 'its:locQualityIssuesRef' attribute is declared, the following attributes are not allowd: its:locQualityIssueSeverity, its:locQualityIssueProfileRef, and its:locQualityIssueEnabled".
</sch:report>
<sch:assert test="count(ancestor::xlf:unit//its:locQualityIssues[@xml:id=substring-after(current()/@its:locQualityIssuesRef , '#its=')])=1">
The value of the locQualityIssuesRef attribute must be relative URI (starting with "#its="), and the value after "#its=" must be one of the id attributes declared on a <locQualityIssues> elements within the same 'unit'.
</sch:assert>
</sch:rule>
</sch:pattern>
Cheers,
Felix