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 3044 - RQ-133 Identity constraints accessibility in component graph (scd-accessible-constraints)
Summary: RQ-133 Identity constraints accessibility in component graph (scd-accessible-...
Status: RESOLVED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: Other All
: P2 normal
Target Milestone: ---
Assignee: Henry S. Thompson
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2006-03-25 17:44 UTC by C. M. Sperberg-McQueen
Modified: 2006-03-25 17:48 UTC (History)
0 users

See Also:


Attachments

Description C. M. Sperberg-McQueen 2006-03-25 17:44:15 UTC
This issue was originally reported by Asir Vedamuthu and Mary Holstege.

While identity constraints are available through the element to which
they are bound, as named members in their own symbol space, it would
be beneficial to have them directly available at the top level, i.e.
from a property on the schema-as-a-whole schema component.

add a property to schema-as-a-whole component; text analogous to those
for complex type definitions, in section 2 (symbol spaces),
schema-as-a-whole component description, and in QName resolution.

Decided on June 26th to call it erratum and we're waiting for text.

See RQ-16 (#id-components). These two issues are related (if not
identical).

See
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0222.html

This item was mentioned in the meeting of 2003-09-18
(http://www.w3.org/XML/Group/2003/09/xml-schema-ftf-minutes.html)

This item was closed in the meeting of 2004-04-02
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Apr/0041.html). It
does not need to be done for 1.1, because it should be taken care of
as an erratum to XML Schema 1.0 (see R-105
(http://www.w3.org/2001/05/xmlschema-rec-comments.html#pfiSchemaComponent)).
Comment 1 C. M. Sperberg-McQueen 2006-03-25 17:48:45 UTC
This issue has been resolved in the working drafts of
XML Schema 1.1.