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 4993 - Remove the concept of "empty" and "dangling" references
Summary: Remove the concept of "empty" and "dangling" references
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P1 normal
Target Milestone: Second draft
Assignee: Valentina Popescu
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords: editorial
Depends on: 4780
Blocks:
  Show dependency tree / graph
 
Reported: 2007-08-29 19:35 UTC by Sandy Gao
Modified: 2007-09-05 16:18 UTC (History)
0 users

See Also:

Attachments

Description Sandy Gao 2007-08-29 19:35:05 UTC 
Discussed these concepts at 2007-08-23 telecon and t 2007-08-29 F2F. The WG decided

1. The concept "empty reference" does not carry any significant meaning, and is no different from any other non-null references. So we should remove the definition of "empty reference" (if any) and any references to it.

2. SML and SML-IF specs mentions "dangling references" and "unresolved references". They seem to be for the same concept. Some WG members feel that "dangling" implies a meaning that's not always true. WG decided to remove and replace "dangling" references with "unresolved" references.
Comment 1 Valentina Popescu 2007-09-05 16:18:39 UTC 
I have removed 'Empty Reference' concept and replaced 'Dangling' with 'Unresolved'

The changes have been applied to the sml-source.xml ( no occurrences of empty or dangling references outside of the SML spec )