This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4825 - How should deref() handle reference elements with multiple child elements.
Summary: How should deref() handle reference elements with multiple child elements.
Status: RESOLVED DUPLICATE of bug 4658
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P1 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-28 00:00 UTC by Bassam Tabbara
Modified: 2007-07-18 23:36 UTC (History)
0 users

See Also:

Attachments

Description Bassam Tabbara 2007-06-28 00:00:33 UTC 
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>
Comment 1 Virginia Smith 2007-07-18 23:36:53 UTC 

*** This bug has been marked as a duplicate of bug 4658 ***