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 4839 - Bug in anchor for documentation of hexBinary type
Summary: Bug in anchor for documentation of hexBinary type
Status: RESOLVED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: All All
: P1 minor
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard: cluster: typo+
Keywords: resolved
Depends on:
Blocks: 5465
  Show dependency treegraph
 
Reported: 2007-07-06 20:02 UTC by Paolo Ragone
Modified: 2008-02-08 19:18 UTC (History)
0 users

See Also:


Attachments
wording proposal (96.93 KB, text/html)
2008-02-08 19:12 UTC, C. M. Sperberg-McQueen
Details

Description Paolo Ragone 2007-07-06 20:02:35 UTC
On the xsd, the documentation for the type hexBinary points to:
http://www.w3.org/TR/xmlschema-2/#binary
But on the site, the documentation for this datatype is on:
http://www.w3.org/TR/xmlschema-2/#hexBinary
Comment 1 Dave Peterson 2007-07-24 12:02:24 UTC
The Schema for Datatype Definitions (part of the Schema for Schemas) has, in the <appinfo><documentation> for hexBinary, a link to

   http://www.w3.org/TR/xmlschema-2/#binary

but the intended target is named "hexBinary", so the link in the SfDD is broken.  Probably the easiest fix is the one suggested by Paolo in private communication to the editors, which is to add "hexBinary" as a second target name for the same target.
Comment 2 C. M. Sperberg-McQueen 2008-02-05 03:36:39 UTC
A wording proposal for this issue (among others) was placed on the
server on 4 February 2008 at 
http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.omnibus.200801.html (member-only link).
Comment 3 C. M. Sperberg-McQueen 2008-02-08 19:12:04 UTC
Created attachment 516 [details]
wording proposal

I'm attaching a document showing the specific wording proposal adopted
by the Working  Group today as a resolution of this issue.  It shows
a number of changes to the DTD and schema for schema documents.
Comment 4 C. M. Sperberg-McQueen 2008-02-08 19:15:00 UTC
With the adoption of the wording proposal shown in the attachment,
the WG believes this issue is now resolved for XML Schema 1.1.
I'm going to clone this bug now, in order to allow it to remain open
for XML Schema 1.0 and be closed for 1.1.

Paolo Ragone, as the originator of this issue, you should receive
email notifying you of this change. 

Please let us know if you agree with this resolution of your issue, by adding a comment to the issue record and changing the Status of the issue to Closed. Or, if you do not agree with this resolution, please add a comment explaining why. If you wish to appeal the WG's decision to the Director, then also change the Status of the record to Reopened. If you wish to record your dissent, but do not wish to appeal the decision to the Director, then change the Status of the record to Closed. If we do not hear from you in the next two weeks, we will assume you agree with the WG decision.