This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
from "...variety of schemes, and SML does not mandate ..." to "...variety of schemes; SML does not mandate ..." from: A reference scheme normally uses, but is not required to use, child elements, attributes or both to capture the information necessary to identify a resource. to: A reference scheme MAY use child elements, attributes, both, or neither to capture the information necessary to identify the reference target. from: "...reference MUST be represented using the URI scheme and ..." to: "...reference MUST be represented when using SML-defined reference schemes." (second change makes the text age better as it gets updated)
Section now reads: An SML reference MAY be represented by using a variety of schemes; SML does not mandate the use of any specific schemes. A reference scheme MAY use child elements, attributes, both, or neither to capture the information necessary to identify the reference target. Although SML does not require the use of any specific scheme, it does specify how a reference MUST be represented when using SML-defined reference schemes. The 4.2.1 URI Scheme and 4.2.2 EPR Scheme are two schemes defined by SML for identifying reference targets.