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 6234 - Set or Sequence
Summary: Set or Sequence
Status: CLOSED WORKSFORME
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2008-11-18 15:56 UTC by Sandy Gao
Modified: 2009-04-21 19:21 UTC (History)
1 user (show)

See Also:

Attachments

Description Sandy Gao 2008-11-18 15:56:56 UTC 
There are schema component properties whose values are "a set of ... components". Given that we need to provide SCDs for these components, do we need to replace "set" with "sequence"?

In particular, {identity-constraint definitions} and {substitution group affiliations} on Element Declarations; {attribute uses} on Complex Type Definitions and Attribute Group Definitions; and {facets} on Simple Type Definitions.

I believe this was the reason why we use "sequence" instead of "set" in some other places (e.g. "a sequence of annotations").
Comment 1 David Ezell 2008-11-28 16:37:15 UTC 
SG: I think this isn't really a problem, and propose we propose as WORKSFORME.