RE: Exclusivity and atomicity of local and global ITS

Hi Nathan,

 

I think the scenario of your question 1 cannot exist.

You cannot have both a local reference to a stand-off annotation and a local LQI info. (or a global info with a global stand-off
annotation)

As for a stand-off annotation and a rule: if the stand-off annotation is from a local rrference it wins over the global rule.

 

For #2 I think the rule applies, but the processor generates (possibly) some type of error if it tries to access the pointed
information.

 

Just my 2 cents

-yves

 

From: Nathan Glenn [mailto:garfieldnate@gmail.com] 
Sent: Wednesday, October 9, 2013 7:55 PM
To: public-i18n-its-ig@w3.org
Subject: Exclusivity and atomicity of local and global ITS

 

Hello all,

I am wondering about of couple of possible situations in an ITS-decorated document that require information about the
exclusivity/atomicity of global and local markup:

 

1) If a rule of the same general category as existing local markup happens to match an element, but the rule and the local markup
give values for different exact categories, do they both apply? This question is only relevant for provenance and locQualityIssue.
For example, let's say there's a provRule that matches element X, and references a provenanceRecords element that contains person
and org information, and local markup on X specifies tool. Does the element then have ITS information on person, org and tool, or
does the local specification of tool erase any provRule matches? For locQualityIssue, a similar question would arise when a global
rule specified locQualityIssueType and the local markup specified a locQualityIssueComment. This one is specified with "in parallel
to local inline markup", so I'm guessing that both would apply.

 

2) If a rule has a pointer attribute that doesn't match, does the rule still match? Is it supposed to depend on what parts of the
rule are required attributes? For example say that the selector for this rule: <its:termRule selector="//term" term="yes"

  termInfoPointer="../def"/> matched a <term> element, but its termInfoPointer did not match anything. Does the rule still match?

 

Nathan