This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
What should be the semantics of the smlfn:deref() function if a reference element has multiple child elements that represent the reference using the same scheme? E.g., <EnrolledCourse xmlns="http://www.university.example.org/ns" sml:ref="true"> <sml:uri>SomeValidUri</sml:uri> <sml:uri>AnotherValidUri</sml:uri> </EnrolledCourse>
*** Bug 4825 has been marked as a duplicate of this bug. ***
A simple solution is to say that a reference scheme can be used at most once in a reference element, so this example will result in error EnrolledCourse xmlns="http://www.university.example.org/ns" sml:ref="true"> <sml:uri>SomeValidUri</sml:uri> <sml:uri>AnotherValidUri</sml:uri> </EnrolledCourse>
adding 'SML references' whiteboard to group all related defects
I like the solution in section 3 "How are schemes defined?" from the Reference proposal. How is a scheme recognized. That is, there is a set of rules that, when satisfied, identify elements with sml:ref="true" as instances of this scheme. (e.g. for the "uri/iri" scheme, the rule can include: there is one and only one sub-element named <sml:uri>, whose value is xs:anyURI.) That is, either a reference element is an instance of (or an example of, or uses) a scheme, or it is not. How many instances of a reference scheme does an SML reference R use/include is an ill-formed question.
Resolution is to fix as per Sandy's sml reference proposal.