This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In section 4.2.4, the 2nd sentence applies to the definition of reference schemes and, as such, does not belong in this section which is about elements being targets multiple references. Proposal: 1. Remove 2nd sentence in section 4.2.4 Multiple References - "These reference elements may use different schemes and/or be expressed in different ways" 2. Add sentence to section 4.2.3 similar to the removed sentence to indicate that a target may be reached by 2 different instantiations of the same reference scheme e.g., 2 different xpath expressions may identify the same element.
It seems to me that 4.2.3 is referring to the case where a reference element has two different schemes or possibly two different instances of the same scheme to refer to the same element. 4.2.4 is talking about two different references, i.e. two different elements, possibly unrelated, which happen to refer to the same target element.
[1] +1 for bullet #1 in the original proposal. [2] The definition in 4.2.3 seems to be complete. No need to add the removed sentence (or a sentence like it) to 4.2.3.
Resolution: fix per proposal amended by comment #2. However, editor to review spec and make sure that the proposal item #2 statement is expressed somewhere in the spec and if not add this as a non-normative statement.
Removed second sentence in 4.2.4 and added similar sentence in SML Refernce Scheme definition (2.2).
4.2.4 Multiple References from: An element in a document MAY be targeted by multiple SML reference. to: An element in a document MAY be targeted by multiple SML references.
The text at one point was "An element in a document MAY be targeted by multiple SML reference elements." I'm not sure if the removal of the word "elements" was intentional, but it was, obviously this needs to be changed as in comment #5.
+1 for the changes (as ammended by comment# 5)
The change from "SML reference element" to "SML reference" was intentional. This change was made throughout the spec as part of bug #5388.