In general, for a given selector, which selects the first/last position inside a subtree, there exists a referentially equivalent and the XPath components of this referentially equivalent selector selects a subtree outside of the substree selected by the given selector! Exceptions are the first and last position in a document.
Example:
<r>Sol<t1>ar</t1><t2>pan</t2>el!</r>
Should the two selectors /r[1]/t1[1]; char=2 and /r[1]/t2[1]; char=0
be treated as referentially equivalent and be normalized to the same selector?
Both select the position between Solar and panel!
If referential equivalence is transitive, we must conclude, that the selectors are equivalent:
/r[1]; char=5 = /r[1]/t1[1]; char=2 and
/r[1]; char=5 = /r[1]/t2[1]; char=0
ergo: /r[1]/t1[1]; char=2 = /r[1]/t2[1]; char=0.
Cf. Wiki!
Assignees: @memowe, @inormann, @lueck
Migrated from GitLab: https://zivgitlab.uni-muenster.de/SCDH/selectors/selection-engine/-/issues/12
In general, for a given selector, which selects the first/last position inside a subtree, there exists a referentially equivalent and the XPath components of this referentially equivalent selector selects a subtree outside of the substree selected by the given selector! Exceptions are the first and last position in a document.
Example:
Should the two selectors
/r[1]/t1[1]; char=2and/r[1]/t2[1]; char=0be treated as referentially equivalent and be normalized to the same selector?
Both select the position between
Solarandpanel!If referential equivalence is transitive, we must conclude, that the selectors are equivalent:
/r[1]; char=5=/r[1]/t1[1]; char=2and/r[1]; char=5=/r[1]/t2[1]; char=0ergo:
/r[1]/t1[1]; char=2=/r[1]/t2[1]; char=0.Cf. Wiki!
Assignees: @memowe, @inormann, @lueck
Migrated from GitLab: https://zivgitlab.uni-muenster.de/SCDH/selectors/selection-engine/-/issues/12