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 4674 - add definition of a dangling reference
Summary: add definition of a dangling reference
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal
Target Milestone: FPWD
Assignee: Kumar Pandit
QA Contact: SML Working Group discussion list
URL: http://www.w3.org/2005/06/tracker/sml...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-20 16:41 UTC by John Arwe
Modified: 2007-07-26 06:55 UTC (History)
0 users

See Also:


Attachments

Description John Arwe 2007-06-20 16:41:10 UTC
SML mentions dangling references in several places but does not define them.  I believe a dangling reference is an SML reference, for which at least one scheme is specified, but which is not retrievable using the retrieval mechanism defined by any scheme the implementation supports.

Need to cover several cases:
- SML reference (defined elsewhere) with no child content
- ...with child content containing no sml schemes
- ...                          ... no sml schemes supported by the impl
- ...                          ... at least one scheme supported by the impl
Nb: if SML changes to support schemes via attributes on the sml:ref=true element, more cases become relevant.
Comment 1 Kumar Pandit 2007-07-26 06:55:22 UTC
The following cases identified by John should be covered under the definition of a null reference. 
- with child content containing no sml schemes
- no sml schemes supported by the impl

I have opened the following bug for this.

4884 update the definition of a null reference to include the unimplemented-schemes case