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 5069 - Use of "reference" for reference elements vs. schemes
Summary: Use of "reference" for reference elements vs. schemes
Status: RESOLVED WONTFIX
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Virginia Smith
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-24 19:38 UTC by Kirk Wilson
Modified: 2008-06-05 18:58 UTC (History)
0 users

See Also:


Attachments

Description Kirk Wilson 2007-09-24 19:38:16 UTC
What does the world "resolve" properly apply to--a scheme or a reference?  The current text uses "resolve" with respect to both concepts, which causes the notion of resolution to float between two levels.  This could cause confusion on the part of a reader who is quite so attuned to the nuance of context as the spec authors.  I would suggest that reference element should *refer* while schemes should *point*.  Reference elements are *dereferenced* by deref(); whereas schemes are not explicitly an argument to deref()--I believe.
Comment 1 Pratul Dublish 2007-10-25 18:53:50 UTC
Editors should submit a proposal for this to the WG for review
Comment 2 Virginia Smith 2007-11-02 00:55:34 UTC
The editors feel that the specification has evolved such that it is clear how SML references and schemes are resolved. In addition, 'resolved' is a well-known term and should be able to be applied to both references and schemes. The editors propose that this bug be marked as DONT FIX. This can be reconsidered if we receive feedback on this after LC.
Comment 3 Pratul Dublish 2007-11-12 04:18:28 UTC
The editors' proposal looks good - recommend resolving this bug as FIXED