On 22/11/2013 09:44, Thomas Beale wrote: > > Something IMPORTANT I have said before, and completely forgot due to > other distractions:
'should' have said before! > > There is a proposal (it's on the SPECPR issue tracker somewhere) to > add a property to the LOCATABLE class called (say) sibling_id: INTEGER > > which would have the effect of unambiguously numbering sibings under a > container attribute in the data. In XML data I would expect to make > this an attribute, so the effect on paths would be be able to say > > cluster[at0009]/items[at0008, 2] > > as ADL short hand for > > cluster[@archetype_node_id='at0009']/items[@archetype_node_id='at0008', > @sibling_id='2'] > > > This is for next-gen openEHR obviously, so doesn't help Bert/Leo right > now. > > anyone have thoughts on that? Note that the position() predicate > should still work, which means it can't be in its short form as [...., > 2], or else the sibling_id needs a different short syntax. > > Other note: sibling_id order will be the same regardless of > re-ordering whereas the value of position() is whatever the physical > position is. > > - thomas
