XML Schema: Requirements and candidate requirements for version 1.1

Version

Version $Id: reqs.html,v 1.1.2.2 2004/07/15 08:19:23 ht Exp $

This document summarizes the candidate requirements for future versions of XML Schema.

The status of each requirement is recorded in the table. The status may be:

proposed: A new issue (these will typically be unclassified).
todo: An issue that remains to be discussed.
active: The WG is currently discussing the issue. The issue may or may not be classified. See the classification field for further info
roughed: The WG has discussed this and agreed in principle on the technical solution to be used. Draft final wording is to be prepared by the editors.
drafted: The editors have prepared draft final wording for WG approval, but it has not yet been approved.
bounced: The WG has discussed the draft final wording prepared by the editors and has sent it back to the editors for revision.
resolved: The WG has adopted final wording which discharges the issue.
revisit: The WG has discussed this but was unable to reach consensus; we will need to come back to it.
postponed: The WG has discussed this but has set it aside for now. It should come up again, but if it does not, the requirement will not be met in XML Schema 1.1.
overtaken: This item has been overtaken by events and is no longer pertinent. This may be because the requirement refers to or assumes a feature of the spec which has been or will be removed, or because it is subsumed by a more general requirement; in the latter case, there should be a cross reference to that other requirement.
abandoned: The WG has abandoned work on this item; if it is a requirement, it will not be met in version 1.1 of XML Schema; it may be met in other later versions, if any.
ng: This is a non-goal. No further work is expected on it.

The classification of each requirement is recorded in the table. The classification may be:

Unclassified version: WG needs to classify.
Req version: A requirement for that version.
Desideratum version: A desideratum for that version. I.e. we wish to achieve the goal described and will expend time and effort to do so, but we will drop the requirement if it proves too difficult or conflicts with other requirements including our schedule.
Opp Des version: An opportunistic desideratum for that version. We will achieve it if doing so proves easy and straightforward (i.e. if it's low-hanging fruit); we do not expect to expend significant resources to do so.
Non-goal version: A non-goal for that version. This does not necessarily mean that it is a non-goal for future versions.

Num	Cl	Cluster	Status	Originator	Description
RQ-1	Req	Num	resolved	Henry Zongaro	Specify canonical representation of float and double
RQ-2	Req	D/T	roughed	Mark Davis	Specify canonical representation of duration
RQ-3	Req	D/T	postponed	I18n WG	Address localization issues with date and time types
RQ-4	Req	Dat	postponed	I18n WG	Address localization issues with datatypes
RQ-6	Req	D/T	resolved	Kohsuke Kawaguchi	Specify unit of length for all primitive types
RQ-7	Req	Str	roughed	Matthew Fuchs	Improve interaction between wildcards and substitution groups
RQ-9	Req	Str	postponed	James Clark	Expand wildcard namespace constraints
RQ-10	Req	Str	abandoned	Matthew Fuchs	Improve interaction between exclusions and disallowed substitutions
RQ-11	Req	Restr	overtaken	Yan Leshinsky	Address problems with pointless occurrences rule
RQ-12	Req	Restr	overtaken	Achille Fokoue	Resolve choice:choice derivation issues
RQ-13	Req	D/T	roughed	Kohsuke Kawaguchi	Time zone normalization crosses date line
RQ-14	Req	SCD	roughed	Mary Holstege	Provide schema component for selector/field annotations
RQ-15	Req	Restr	roughed	Khaled Noaman/Henry S. Thompson	Correct restriction of identity constraints
RQ-16	Req	SCD	overtaken		Include the identity constraints in the schema component
RQ-17	Req	Restr	roughed	Matthew Fuchs	Redo restriction rules
RQ-19	Req	SCD	roughed	XML Schema WG	Correctly handle annotations in the PSVI
RQ-20	Desideratum	D/T	resolved		Provide ordered duration types
RQ-21	Desideratum	Dat	roughed		Provide regex or BNF for all primitive types
RQ-22	Desideratum	PSVI	roughed		Add normalized default value for attributes
RQ-23	Desideratum	SCD	overtaken	Dan Connolly	First class objects
RQ-24	Desideratum	Dat	drafted	Dave Peterson	Systematic treatment of fundamental facets
RQ-25	Non-goal	ID	ng		Interactions with legacy types
RQ-26	Desideratum	Str	abandoned	XML Schema WG	Simplify final and block
RQ-28	Opp.Des.	Num	roughed	Mike Cowlishaw	Allow scientific notation for decimals
RQ-29	Opp.Des.	Str	postponed	I18N WG	Address localization issues in Structures
RQ-30	Opp.Des.	Num	roughed	Mike Cowlishaw	Allow negative fractionDigits
RQ-31	Desideratum	Num	roughed	Mike Cowlishaw	Provide decimal type that retains trailing zeroes
RQ-32	Opp.Des.	Dat	abandoned	Bob Schloss, Mike McCaleb	Allow abstract simple types
RQ-33	Opp.Des.	ID	todo	Jane Hunter (MPEG-7)	Add key constraints based on element types
RQ-34	Opp.Des.	XSD	resolved		Add inline schemas
RQ-35	Opp.Des.	Str	abandoned		Improve named model group syntax
RQ-36	Opp.Des.	Str	revisit		Allow local references
RQ-37	Opp.Des.	PSVI	postponed		Provide normalized value for complex/mixed elements
RQ-38	Desideratum	Str	revisit		Add co-constraints
RQ-39	Non-goal	D/T	ng	Michael Anderson	Restricting duration
RQ-40	Non-goal	D/T	ng	David RR Webber	support non-Gregorian dates
RQ-41	Non-goal	D/T	ng	Ninggang Chen	duration is incomplete
RQ-42	Non-goal	Str	ng	I18n WG	pattern on mixed content
RQ-43	Non-goal	D/T	ng	I18n WG	Locale-dependent datatype support
RQ-44	Non-goal	MiPa	ng	Martin Roberts	Allow other list delimiters
RQ-45	Non-goal	D/T	ng	Robert Miller	Support for Arrays
RQ-46	Non-goal	D/T	ng		Multiple order relationships
RQ-47	Non-goal	D/T	ng	I18n WG	Single lexical representation
RQ-48	Non-goal	D/T	ng	Philipp Niederau	Hierarchy Facet
RQ-49	Non-goal	Str	ng	Curt Arnold	Schema component binding to the namespace without a name
RQ-50	Non-goal	Dat	ng	Uwe Zeise	Run-time parameterization of types
RQ-51	Non-goal	XSD	ng	Patrick Sheppard	Dynamic facets
RQ-52	Non-goal	XSD	ng		Support multiple inheritance
RQ-53	Non-goal	sfs	ng	Martin Duerst	Order of declarations
RQ-54	Non-goal	Str	ng	Martin Duerst	maxOccurs and all group
RQ-55	Non-goal	MiPa	ng	Anders W. Tell	Microparsing
RQ-56	Non-goal	Str	ng		Drop nested element declarations
RQ-57	Non-goal	Str	ng		Global Attributes
RQ-58	Non-goal	MiPa	ng		Association of repeated child elements with lists
RQ-59	Non-goal	D/T	ng		Array type refs
RQ-60	Non-goal	XSD	ng		multiple schema languages
RQ-61	Non-goal	PSVI	ng		PSVI as schema input
RQ-62	Non-goal	D/T	ng		Mapping between enumerations
RQ-63	Non-goal	D/T	ng		Restricting unions and lists
RQ-64	Non-goal	D/T	ng		Derivation of Simple Types
RQ-65	Non-goal	XML	ng		Drop notations
RQ-66	Non-goal	ID	ng		Multi-part keys
RQ-67	Non-goal	ID	ng		Multi-doc keys
RQ-68	Non-goal	ID	ng	CMSMCQ	Reify symbol spaces
RQ-69	Non-goal	ID	ng		ID constraints and chameleon include
RQ-70	Non-goal	XSD	ng	Paul Grosso	Locating Schemas by Public Identifiers
RQ-71	Non-goal	XSD	ng	Curt Arnold	Schema locations declared before use
RQ-72	Non-goal	Str	ng		Allow block, default on element refs
RQ-73	Non-goal	Str	ng		Allow derivation of named groups
RQ-74	Non-goal	Restr	ng		Redefine restrictions
RQ-75	Non-goal	Str	ng	I18n WG	Merge mixed with string
RQ-76	Non-goal	Str	ng	XML Query WG	New method of defining repetition
RQ-77	Non-goal	Str	ng	I18n WG	Character Repertoire Restrictions
RQ-78	Non-goal	Str	ng		Element defaults
RQ-79	Non-goal	XSD	ng	XForms WG	XForms requirements
RQ-80	Non-goal	XSD	ng	MSM	The grammar needs a start symbol.
RQ-81	Non-goal	XML	ng	HTML WG, Jeffrey Yasskin	General entities
RQ-82	Non-goal	XSD	ng		Conformance profiles
RQ-83	Non-goal	Lang	ng	Kohsuke Kawaguchi	language datatype case sensitivity
RQ-84	Non-goal	lib	ng	I18N WG	Type Library for I18N related datatypes
RQ-85	Non-goal	XSD	ng		Canonical form for schema documents
RQ-86	Non-goal	D/T	ng	I18n WG	Control characters and localization
RQ-87	Non-goal	lib	ng	Martin Bryan	Type Library for Measurements
RQ-88	Non-goal	patt	ng		Named patterns
RQ-89	Non-goal	Restr	ng	Curt Arnold	Revise restriction rules
RQ-90	Non-goal	QT	ng	XML Query WG	Untyped type
RQ-91	Non-goal	ID	ng	Eric van der Vlist	Validating XPointer IDREFS
RQ-92	Non-goal	ID	ng	Mike McCaleb	Allow key/keyRef mechanism to augment IDREFs
RQ-93	Non-goal	Str	ng		Forbid numeric exponents on groups
RQ-94	Non-goal	Str	ng		Forbid numeric exponents on named model groups
RQ-95	Non-goal	XSD	ng		Eliminate elements with simple types
RQ-96	Non-goal	XSD	ng		Streaming Processors
RQ-97	Opp.Des.	Str	postponed	Xan Gregg	Allow typed wildcards
RQ-98	Non-goal	XSD	ng	Jonathan Robie	Deprecate unused language features
RQ-99	Desideratum	Str	todo	Paul. V. Biron	Allow an element to be in more than one substitution group
RQ-100	Opp.Des.	Lang	resolved	Ashok Malhotra	Canonical form for language
RQ-101	Non-goal	PSVI	ng	Philip Wadler	PSVI Representation of Untyped Character Data
RQ-102	Non-goal	PSVI	ng	Henry Thompson	PSVI access to e.g. [validation attempted] and [validity]
RQ-103	Non-goal	QT	ng	Noah Mendelsohn	Typing of nodes not governed by a schema
RQ-104	Non-goal	MiPa	ng	xiaotaow@cs.columbia.edu	User-defined delimiters for lists
RQ-105	Opp.Des.	ID	abandoned	Stefan.Wachter@gmx.de	Allow complex types more than one ID attribute
RQ-106	Non-goal	QN	ng	Dan Connolly	A QName can have multiple values if bound to more than one URI
RQ-107	Non-goal	ver	ng	dtchang@us.ibm.com	Define use of xsi:schemaVersion
RQ-108	Non-goal	Dat	ng	Mark Baker	Add URI datatype
RQ-109	Non-goal	XSD	ng	Francois SORIN	Allow multiple target namespaces in a Schema
RQ-110	Non-goal	ID	ng	David Parker-Bastable	Allow uniqueness based on a function of the value
RQ-111	Non-goal	Str	ng	Robert Brotherus	Default element on a choice group
RQ-112	Opp.Des.	Dat	abandoned	ben@jetpen.com	Support extensible enumerations
RQ-113	Non-goal	Dat	ng	Paul V. Biron	Equivalence comparisons on anyURI
RQ-114	Non-goal	D/T	ng	Rick Jellife	Add a anyString datatype as parent of string
RQ-115	Non-goal	XSD	ng	Michael Russ <mruss@edvision.com>	Indicate element cannot be root
RQ-116	Non-goal	D/T	ng	Mark Preston <mark@magpiesnest.co.uk>	Permit derivation of new atomic types as combination of existing types
RQ-117	Non-goal	ID	ng	Rick Taylor, Michael Gruebsch	Allow keys on complex and simple types
RQ-118	Non-goal	XSD	ng	Mark Seaborne, Michael Gruebsch	Provide choice groups for attributes
RQ-119	Non-goal	XSD	ng	Douglas and Elena Husemann (husemann@cox-internet.com)	Allow vendors to extend XML Schema
RQ-120	Desideratum	XSD	revisit	Berthold Daum	Make consistent use of the term "derived"
RQ-121	Req	Str	roughed	Stanley Guan, Ashok Malhotra	Clarify behavior for attributes that are both fixed and prohibited
RQ-122	Req	D/T	active	Dave Peterson	Define value space for dateTime more precisely
RQ-123	Req	D/T	roughed	Dave Peterson	Allow year 0000 in date-related types
RQ-125	Req	Str	roughed	Michael Sperberg-McQueen	Clarify identity of anonymous types
RQ-126	Req	Dat	roughed	Dave Peterson	Restricting away canonical forms
RQ-128	Opp.Des.	Dat	abandoned	Francois Yergeau	Allow an additional value for the whitespace facet called, perhaps, I18N-collapse
RQ-129	Desideratum	Dat	roughed	Xan Gregg	Remove dependency on canonical lexical representations
RQ-130	Req	SCD	roughed	Asir Vedamuthu, Mary Holstege	Lost annotations
RQ-131	Req	SCD	roughed	Asir Vedamuthu, Mary Holstege	Ordering for {annotations} property
RQ-132	Non-goal	SCD	ng	Asir Vedamuthu, Mary Holstege	Origin of attribute/model group components
RQ-133	Req	SCD	overtaken	Asir Vedamuthu, Mary Holstege	Identity constraints accessibility in component graph
RQ-134	Req	SCD	roughed	Asir Vedamuthu, Mary Holstege	Origin of inherited portions of content model
RQ-135	Opp.Des.	XSD	todo	Matthew Fuchs	Consistency and validity for a set of schema components
RQ-137	Req	XSD	roughed	Sandy Gao	Provide error codes for all violations
RQ-138	Non-goal	Str	ng	Sandy Gao, Asir Vedamuthu	Nillable and Fixed are allowed together
RQ-139	Non-goal	D/T	ng	Jim Melton	Make anyURI a subtype of string
RQ-140	Req	Num	drafted	XML Schema WG	Distinguish negative from positive zero.
RQ-141	Req	Dat	roughed	XML Schema WG	Add the abstract datatype anyAtomicType
RQ-142	Req	PSVI	roughed	Lisa Martin	Are non-required PSVI properties forbidden?
RQ-143	Req	Str	todo	Richard Tobin	Question about assessment outcome for attributes
RQ-144	Req	Str	active	Noah Mendelsohn	Which PSVI properties must processors report?
RQ-145	Non-goal	Str	ng	Noah Mendelsohn	Add a "value" property for attributes and elements with simple content.
RQ-146	Req	Str	active	David Bau	needs clarification re. wildcards
RQ-147	nongoal	Str	ng	Noah Mendelsohn	Allow "length" after "min/maxLength", but not the other way around.
RQ-147b	Desideratum	Str	todo	Noah Mendelsohn	Make "length" specifications set "min/maxLength" facets, not a separate facet.
RQ-148	Req	Dat	roughed	Steven Taschuk	Clarify the use of the word "truncation" in lexical forms.
RQ-149	Non-goal	Str	abandoned	Xan Gregg	Deprecate use of numeric exponents on model groups
RQ-150	Req	Dat	roughed	John Tebbutt, Ashok Malhotra	Problems with minimum number of digits for decimal
RQ-151	Req	XSD	active	Xan Gregg	Define schema composition
RQ-152	Unclassified	unassigned	proposed	Henry Thompson, Noah Mendelsohn	Should XML Schema be aligned with XML 1.1?
RQ-153	Unclassified	unassigned	proposed	David Ezell	Schema 1.1 Namespace

RQ-1 canonical-float: Specify canonical representation of float and double

Locus: datatypes Cluster: Num

Class: Req Status: resolved
Assigned to:
Originator: Henry Zongaro

Description

The canonical representation of float and double must be refined because it currently maps several lexical representations into a single legal value. Specifically, the description of the canonical representation must address (1) signed exponents, and (2) trailing zeroes in the mantissa.

See (member-only link) http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Mar/0184.html.

Interactions and Input

Input from Straw Poll O-4.

This item was discussed in the meeting of 2004-01-22

This item was discussed in the Cannes face to face meeting of 2004-03-02. Phase 2 wording was amended and approved.

Proposed Resolution

Mail from Ashok Malhotra and subsequent thread (member-only links)

RQ-2 canonical-duration: Specify canonical representation of duration

Locus: datatypes Cluster: D/T

Class: Req Status: roughed
Assigned to:
Originator: Mark Davis

Description

There must be a canonical representation of duration, and a process for calculating the canonical representation from any other lexical representation. Currently, a period of one day and a period of 24 hours are considered two different values in the value space. They should be considered two different lexical representations of the same value.

See (member-only link) http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Jan/0215.html. See also http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JulSep/0102.html : R-170.

Interactions and Input

Input from Straw Poll O-5.

Microsoft proposals, item 1.1 (member-only link)

Michael Kay (member-only link)

This item was mentioned in the meeting of 2003-09-18

This item was discussed in the meeting of 2003-10-03

This item was discussed in the meeting of 2004-01-09

This item was discussed in the meeting of 2004-06-11.

RQ-3 datetime-localization: Address localization issues with date and time types

Locus: datatypes Cluster: D/T

Class: Req Status: postponed
Assigned to:
Originator: I18n WG

Description

Address localization concerns regarding the date and time types.

See (member-only link) http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#i18n-datetime : LC-221.

Interactions and Input

Input from Straw Poll O-5.

NOTE 2002-08-02: this needs to be analysed into its constituent items, and each item acted on individually.

RQ-4 localization: Address localization issues with datatypes

Locus: datatypes Cluster: Dat

Class: Req Status: postponed
Assigned to:
Originator: I18n WG

Description

Address localization concerns regarding Part 2: Datatypes.

See (member-only link) http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#i18n-dt-misdirected : LC-207.

Interactions and Input

Input from Straw Poll O-6

NOTE 2002-08-02: this needs to be analysed into its constituent items, and each item acted on individually.

This item was postponed in the meeting of 2004-04-22.

RQ-6 unit-of-length: Specify unit of length for all primitive types

Locus: datatypes Cluster: D/T

Class: Req Status: resolved
Assigned to:
Originator: Kohsuke Kawaguchi

Description

Unit of length must be defined for the all primitive types, including anyURI, QName, and NOTATION.

See http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0391.html.

Interactions and Input

Input from Straw Poll O-7

This item was mentioned in the meeting of 2003-09-18

Actual Resolution

Discussion on the June 19, 2003, telcon established that in the 2e draft, all simple types to which the length facet applies have lengths defined.

RQ-7 wildcards: Improve interaction between wildcards and substitution groups

Locus: structures Cluster: Str

Class: Req Status: roughed
Assigned to:
Originator: Matthew Fuchs

Description

Address problems with the interaction between wildcards and substitution groups. Specifically, resolve the bug where if complex type A has a wildcard, and B restricts A, then it can restrict the wildcard to a set of elements that match the wildcard. Not all elements in the substitution groups of those elements necessarily match the wildcard - so B is not a subset of A.

See (member-only link) http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Apr/0047.html.

Interactions and Input

Input from Straw Poll O-12

Cf. RQ-135.

This item was discussed, and phase-1 agreement was reached, in the meeting of 2004-03-18. All we need to say to discharge this requirement is that restriction is transitive. The types derived by multiple restriction steps should also obey the wildcard. There was some doubt over whether the constructive rules of XML Schema 1.0 achieve this, but the definition of restriction in section 2 seems to entail it.

Actual Resolution

RESOLVED: our phase 1 agreement on RQ-007 is that it appears to be taken care of by the existing constructive rules. Phase 2 approval will be established by our accepting a proof that this is so.

In leaving the topic, MSM remarked that if we discharge requirement RQ-017 correctly, RQ-007 should follow automatically.

RQ-9 wildcard-ns-sets: Expand wildcard namespace constraints

Locus: structures Cluster: Str

Class: Req Status: postponed
Assigned to:
Originator: James Clark

Description

The namespace constraints on wildcards must be more expressive in order to be able to express the union or intersection of any two wildcards. Specifically, it must be possible to express "any namespace except those in the following list."

See http://www.w3.org/2000/12/xmlschema-crcomments.html#wildcard-minus : CR-20.

Interactions and Input

Input from:

James Clark: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0216

Judith A. Slein: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0050

Matthew Fuchs: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0052

Judith A. Slein: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0053

Matthew Fuchs: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0054

Judith A. Slein: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0057

Straw Poll O-12

This item was discussed in the meeting of 2003-11-04

This item was postponed in the meeting of 2004-05-13. It may be taken up again in the context of the discussion of how best to support versioning.

Proposed Resolution

Microsoft proposals, item 1.3 (member-only link)

Asir Vedamuthu(member-only link)

RQ-10 substitution-groups: Improve interaction between exclusions and disallowed substitutions

Locus: structures Cluster: Str

Class: Req Status: abandoned
Assigned to:
Originator: Matthew Fuchs

Description

Improve interaction between substitution group exclusions and disallowed substitutions in the element component.

See (member-only link) http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Apr/0049.html.

Interactions and Input

Input from Straw Poll O-12

This item was abandoned in the meeting of 2004-05-13.

RQ-11 pointless-occs: Address problems with pointless occurrences rule

Locus: structures Cluster: Restr

Class: Req Status: overtaken
Assigned to:
Originator: Yan Leshinsky

Description

Revise the derivation of complex-type restriction so as to eliminate the problems with pointless occurrences. Currently, it eliminates some derivations that should otherwise be valid.

See http://www.w3.org/2001/05/xmlschema-rec-comments#pfipointless : R-24.

Interactions and Input

Input from Straw Poll O-14

This item was discussed in the meeting of 2004-04-09.

This item was closed in the meeting of 2004-05-13. It has been overtaken by events: if RQ-17 succeeds, this has no referent in the spec.

Proposed Resolution

Microsoft proposals, item 1.2 (member-only link)

RQ-12 choice-vs-choice: Resolve choice:choice derivation issues

Locus: structures Cluster: Restr

Class: Req Status: overtaken
Assigned to:
Originator: Achille Fokoue

Description

Revise the particle derivation rules so as to eliminate the problems with choice/choice rules.

See http://www.w3.org/2001/05/xmlschema-rec-comments#pfichoicechoice : R-42.

Interactions and Input

Input from Straw Poll O-14

This item was closed in the meeting of 2004-05-13. It has been overtaken by events: if RQ-17 succeeds, this has no referent in the spec.

RQ-13 time: Time zone normalization crosses date line

Locus: datatypes Cluster: D/T

Class: Req Status: roughed
Assigned to:
Originator: Kohsuke Kawaguchi

Description

Resolve the issue that relates to timezone normalization resulting in a time crossing over the date line.

See http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0366.html.

Interactions and Input

Input from :

Straw Poll O-5

This item was discussed in the meeting of 2003-09-05

This item was discussed in the meeting of 2003-09-11

This item was discussed in the meeting of 2003-09-17

This item was discussed in the meeting of 2003-09-26

This item was discussed in the meeting of 2003-10-02

This item was discussed in the meeting of 2003-11-03

RQ-14 id-inconsistency: Provide schema component for selector/field annotations

Locus: structures Cluster: SCD

Class: Req Status: roughed
Assigned to:
Originator: Mary Holstege

Description

The XML representation for field and selector allows an annotation, but there is no schema component to which this annotation can adhere. This inconsistency must be resolved.

See http://www.w3.org/2001/05/xmlschema-rec-comments#pfiIdConstrAnnot : R-46.

Interactions and Input

Input from Straw Poll O-10

Proposed Resolution

Henry Thompson, proposing a resolution for RQ-14, RQ-19, RQ-130 and RQ-131.

RQ-15 id-restriction: Correct restriction of identity constraints

Locus: structures Cluster: Restr

Class: Req Status: roughed
Assigned to:
Originator: Khaled Noaman/Henry S. Thompson

Description

Resolve the issues associated with restricting types whose elements include identity constraints. Specifically, (1) the rule must changed to state that the restricted type must have a superset rather than a subset of identity constraints, (2) the term superset must be clearly defined, and (3) there must be a way to redefine identity constraints in the restricted type without causing duplicate name problems.

See http://www.w3.org/2001/05/xmlschema-rec-comments#pfiIdConsRestrict : R-94.

Interactions and Input

Input from Straw Poll O-10

Interacts with RQ-17.

This item was discussed in the meeting of 2004-04-09. We agreed that we would like to see the proposal written down. The minutes say “The description in the minutes may suffice as written proposal; if not, HT will write it up. Others to say if the minutes are insufficient.”

Further action is needed.

This item was discussed, and phase-1 agreement was reached, in the meeting of 2004-05-13.

RQ-16 id-components: Include the identity constraints in the schema component

Locus: structures Cluster: SCD

Class: Req Status: overtaken
Assigned to:
Originator:

Description

Add an [identity constraints] property of the schema component, which contains all the identity constraint components, just as the [type definitions] property contains all the type definition components.

Interactions and Input

Input from Straw Poll O-10

NOTE 2002-08-02: this item is unclear to the members of the WG present at the August 2002 face to face meeting; a clearer statement of the intended requirement is needed.

Clarified by Henry.

This item was mentioned in the meeting of 2003-09-18

This item was closed in the meeting of 2003-11-04. The issue has been classified as an erratum (R-105) and does not need to be taken care of as part of 1.1. Cf. also RQ-133.

RQ-17 restrictn-rules: Redo restriction rules

Locus: structures Cluster: Restr

Class: Req Status: roughed
Assigned to:
Originator: Matthew Fuchs

Description

Remove the current rules on derivation by restriction; define legal restrictions in terms of their effect on the language, not in terms of a structural relationship between the base type and the derived type.

See (member-only link) http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2001May/0018.html.

Interactions and Input

Input from Straw Poll O-14

Interacts with several other requirements; proposals for this requirement also cover or affect RQ-11, RQ-12, RQ-15, RQ-146.

Confirmed as Requirement at 2002-08-02 F2F. We discussed reclassifying it and decided not to.

This item was discussed in the meeting of 2003-11-04

This item was discussed in the meeting of 2004-04-09.

This item was discussed in the meeting of 2004-04-15.

This item was discussed in the meeting of 2004-05-06.

This item was discussed in the meeting of 2004-05-07.

This item was discussed in the meeting of 2004-05-12.

This item was discussed in the meeting of 2004-05-20.

This item was discussed in the meeting of 2004-06-04.

RQ-19 annotation-psvi: Correctly handle annotations in the PSVI

Locus: structures Cluster: SCD

Class: Req Status: roughed
Assigned to:
Originator: XML Schema WG

Description

Systematise and correct the handling of annotations and out-of-bound attributes in the PSVI.

Interactions and Input

Input from Straw Poll O-15

This item was discussed in the meeting of 2003-11-04

This item was discussed in the meeting of 2003-11-21; Noah Mendelsohn to draft a phase-1 proposal (making sure that foreign-namespace attributes are not lost).

This item was discussed, and phase-1 agreement was reached, in the meeting of 2004-03-18.

Proposed Resolution

Henry Thompson, proposing a resolution for RQ-14, RQ-19, RQ-130 and RQ-131.

RQ-20 ordered-duration: Provide ordered duration types

Locus: datatypes Cluster: D/T

Class: Desideratum Status: resolved
Assigned to:
Originator:

Description

Provide totally ordered duration types, specifically one that is expressed only in years and months, and one that is expressed only in days, hours, minutes, and seconds (ignoring leap seconds.) Possibly define other totally ordered duration types such as day/hour/minute and hour/minute/second duration.

Interactions and Input

Input from Straw Poll O-5

This item was discussed in the meeting of 2003-09-17

This item was mentioned in the meeting of 2003-09-18

This item was discussed in the meeting of 2003-10-03

This item was discussed (and phase-1 agreement reached) in the meeting of 2003-10-09

This item was discussed in the meeting of 2003-10-10. The draft wording was returned to the editors for revision.

This item was discussed in the meeting of 2003-11-03

This item was discussed in the meeting of 2003-12-04; the editors submitted revised text that day.

This item was discussed and phase 2 wording was considered, amended, and approved in the meeting of 2003-12-18.

This item was discussed in the meeting of 2004-01-09.

This item was discussed in the meeting of 2004-06-11.

Proposed Resolution

yearMonthDuration and dayTimeDuration as defined in XQuery and XPath Function and Operators

RQ-21 bnf: Provide regex or BNF for all primitive types

Locus: datatypes Cluster: Dat

Class: Desideratum Status: roughed
Assigned to:
Originator:

Description

Provide regular expressions or BNF productions to express (1) the valid lexical representations and (2) the canonical lexical representation of each primitive built-in type.

Interactions and Input

Input from Straw Poll O-7

This item was mentioned in the meeting of 2003-09-18

This item was discussed in the meeting of 2003-10-10

This item was discussed in the meeting of 2003-10-16

This item was discussed in the meeting of 2003-11-04. We agreed that yes, we will have BNF and/or regular expressions and that this constitutes agreement for phase 1. Details of the BNF and regexes are to be considered in phase 2.

This item was discussed in the meeting of 2004-01-09

This item was discussed in the meeting of 2004-04-29. The WG noted that we were (already) done with phase 1 agreement.

Proposed Resolution

Alexander Falk (member-only link)

RQ-22 norm-default: Add normalized default value for attributes

Locus: structures Cluster: PSVI

Class: Desideratum Status: roughed
Assigned to:
Originator:

Description

Add a [normalized value] property to the constructed attribute infoitem which arises when a default value is applied.

Interactions and Input

Input from Straw Poll O-15

This item was discussed, and phase-1 agreement was reached, in the meeting of 2004-04-22.

RQ-23 first-class-obj: First class objects

Locus: structures Cluster: SCD

Class: Desideratum Status: overtaken
Assigned to:
Originator: Dan Connolly

Description

Define an algorithm for generating a URI for any construct in a schema (or, possibly, in a schema document), thus making schema constructs first-class objects in the Web. Minimally the algorithm should cover element( type)s, attributes, simple types, complex types, and notations. Optionally it may also cover other constructs such as named groups and items in enumerations of legal values.

* URIs for terms: motivation [was Requirement Document] Dan Connolly (Fri, Feb 08 2002) http://lists.w3.org/Archives/Public/www-webont-wg/2002Feb/0028.html

See http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002AprJun/0025.html.

Interactions and Input

Input from Straw Poll O-16

This item was closed (because overtaken by events) in the meeting of 2004-04-23. It remains a requirement for the work of the Working Group, but it will be met by the Schema Component Designators draft, not by XML Schema 1.1. So it does not need to be tracked in this requirements list.

RQ-24 fundamentals: Systematic treatment of fundamental facets

Locus: datatypes Cluster: Dat

Class: Desideratum Status: drafted
Assigned to:
Originator: Dave Peterson

Description

Make the treatment of fundamental facets more systematic. Define canonical forms for all types, and specify the rules for generating the canonical form, given a value. Clarify the status of anySimpleType and define its value space (if any). Clarify the assignment of types to nodes in the absence of relevant schema components. Distinguish our identity relation from the mathematical relation of quantitative equality.

Interactions and Input

Input from Straw Poll O-7

Retained as desideratum 2 August 2002; this is important.

This item was discussed in the meeting of 2003-08-29

This item was discussed in the meeting of 2003-10-23

This item was discussed in the meeting of 2003-10-30

This item was discussed in the meeting of 2003-10-31

This item was discussed in the meeting of 2003-11-04

This item was discussed in the meeting of 2004-05-12.

This item was discussed in the meeting of 2004-05-27.

This item was discussed in the meeting of 2004-06-03.

This item was discussed in the meeting of 2004-06-11. (N.B. the available draft covers part but not all of the substance of our phase-1 agreement.)

Proposed Resolution

Dave Peterson (member-only link)

RQ-25 legacies: Interactions with legacy types

Locus: datatypes Cluster: ID

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

Interaction between uniqueness and referential integrity constraints on legacy types and union types.

See http://www.w3.org/2000/12/xmlschema-crcomments.html#idrefinunion : CR-50 (broken link).

Example, <simpleType name="referenceType"> <union memberTypes="IDREF uriReference mpeg7:xPathType"/> </simpleType> WG did not consider this issue. Also, "requiring enforcement of the uniqueness constraint would involve arbitrary lookahead before allowing a processor to know what type a value has"

Interactions and Input

Input from Straw Poll O-10

NOTE 2002-08-02: the meaning of this item is unclear to the members of the WG present at the August 2002 face to face; it needs to be clarified and either retained or dropped.

This item was reclassified as a non-goal in the meeting of 2004-03-18.

RQ-26 final-and-block: Simplify final and block

Locus: structures Cluster: Str

Class: Desideratum Status: abandoned
Assigned to:
Originator: XML Schema WG

Description

Eliminate or simplify the interactions between final and block.

Interactions and Input

Input from Straw Poll O-12

This item was abandoned in the meeting of 2004-05-13.

RQ-28 scientific-notn: Allow scientific notation for decimals

Locus: datatypes Cluster: Num

Class: Opp.Des. Status: roughed
Assigned to:
Originator: Mike Cowlishaw

Description

Allow scientific notation for decimals.

See http://www.w3.org/2000/12/xmlschema-crcomments.html#scientific-decimals : CR-23.

Interactions and Input

Our comment of http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0298 : March 2001: "There is sentiment in the WG towards allowing some form of exponential notation for decimals in future, but it would be explicit in instances (e.g. value="3E-10"), not implicit in type definitions."

Input from Straw Poll O-4

This item was discussed in the meeting of 2004-04-01. Phase 1 discussion was closed, because this item will succeed or fail with RQ-031.

RQ-29 localization2: Address localization issues in Structures

Locus: structures Cluster: Str

Class: Opp.Des. Status: postponed
Assigned to:
Originator: I18N WG

Description

Address localization concerns regarding Part 1: Structures.

NOTE: This needs to be analysed into its constituent items, and each item acted on individually.

See (member-only link) http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#i18n-str-misdirected : LC-206.

Interactions and Input

Input from Straw Poll O-16

This item was postponed in the meeting of 2004-04-30.

RQ-30 negative-scale: Allow negative fractionDigits

Locus: datatypes Cluster: Num

Class: Opp.Des. Status: roughed
Assigned to:
Originator: Mike Cowlishaw

Description

Allow negative values for the fractionDigits facet.

See http://www.w3.org/2000/12/xmlschema-crcomments.html#negative-scale : CR-22.

Interactions and Input

Input from Straw Poll O-4

This item was discussed in the meeting of 2004-04-01. Phase 1 discussion was closed, because this item will succeed or fail with RQ-031.

RQ-31 trailing-zeroes: Provide decimal type that retains trailing zeroes

Locus: datatypes Cluster: Num

Class: Desideratum Status: roughed
Assigned to:
Originator: Mike Cowlishaw

Description

Provide a datatype which retains trailing zeroes in the lexical representation of decimal numbers. More generally, provide a precision decimal type, in which each value is associated not only with a magnitude but also with a precision.

See http://www.w3.org/2000/12/xmlschema-crcomments.html#canonical-decimals : CR-42.

Interactions and Input

Input from Straw Poll O-4

Interacts with RQ-28, RQ-30 (the same proposal discharges all).

Changed to desideratum on telcon 2002-11-21. The rationale was that we already have a well developed proposal for this.

This item was discussed in the meeting of 2004-03-02

This item was discussed in the meeting of 2004-04-01. We reached phase-1 agreement on canonical forms and keeping a single NaN.

This item was discussed in the meeting of 2004-05-12. A proposal to reclassify it as a non-goal was discussed briefly, and postponed until late June.

Proposed Resolution

Dave Peterson and Mike Cowlishaw (member-only link)

Latest from Dave Peterson (member-only link)

RQ-32 abstract-simples: Allow abstract simple types

Locus: datatypes Cluster: Dat

Class: Opp.Des. Status: abandoned
Assigned to:
Originator: Bob Schloss, Mike McCaleb

Description

Allow abstract simple types.

See http://www.w3.org/2000/12/xmlschema-crcomments.html#abstract-simples : CR-47.

One way to resolve it would be to return to the system of abstract simple types we had in a working draft, and to resolve the issues we encountered with it. These include:

getting both abstract and concrete simple types into the type hierarchy
possibly rewording rules on restriction to make it produce the expected results with a hierarchy of both abstract and concrete types
making more explicit the role of the mapping from lexical form to value in the constitution of a simple type
providing hooks to allow explicit definition of the mapping from lexical space to value space

Interactions and Input

Input from Straw Poll O-7

NOTE 2002-08-02: there was some support for demoting this to a non-goal, on the grounds that it was too hard to get right for 1.1 and it would be better to wait and do it right in 2.0. The idea did not achieve consensus; some members of the WG believed they could define an abstract simple type mechanism which would achieve consensus in the WG.

This item was abandoned in the meeting of 2004-04-22. Three kinds of abstract simple types had been discussed: (a) an abstract numeric type from which the other numerics could be derived, (b) our old (pre-1.0) design for a complete hierarchy of abstract simple types, and (c) user ability to specify abstract = "true" for simple types, as can be done for complex types. It was clear in this meeting that there was no proposal on the table that commanded anything like consensus in the Working Group.

Proposed Resolution

Dave Peterson (member-only link)

Microsoft proposals, item 2.2 (member-only link)

RQ-33 keys-constraints: Add key constraints based on element types

Locus: structures Cluster: ID

Class: Opp.Des. Status: todo
Assigned to:
Originator: Jane Hunter (MPEG-7)

Description

Key constraints to restrict which element types can be pointed to: Allow a schema author use key constaints to specify that a value (which otherwise behaves like an SGML or XML ID) is restricted to pointing at one (or more) particular element type(s)?

See (member-only link) http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#typed-refs : LC-151.

Interactions and Input

Input from Straw Poll O-10

Discussion at http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Nov/0127.html

http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Nov/0129.html

http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Nov/0131.html

RQ-34 inline-schema: Add inline schemas

Locus: structures Cluster: XSD

Class: Opp.Des. Status: resolved
Assigned to:
Originator:

Description

Specify a manner in which schema documents can be included in-line in instances.

See (member-only link) http://www.w3.org/XML/Group/xmlschema-current/issues.html#inlineSchemaInfo : Issue 42.

Interactions and Input

Input from Straw Poll O-11

NOTE 2002-08-02: there was some support at our face to face meeting for promoting this to desideratum, and some for removing it, and some for handling it as a clarification with erratum for XML Schema 1.0 Second Edition; there was most support for leaving it as an opportunistic desideratum. In the absence of consensus to move it, we left it alone. There was speculation that if we get good text for this, the WG might be willing to put it into 2E anyway.

This item was resolved in the meeting of 2004-03-18, with the observation that it is already possible to use inline schemas and that a task force is working on the area.

RQ-35 named-groups: Improve named model group syntax

Locus: structures Cluster: Str

Class: Opp.Des. Status: abandoned
Assigned to:
Originator:

Description

Clean up named model group syntax and component.

See http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0339.html.

Interactions and Input

Input from Straw Poll O-11

NOTE 2002-08-02: there was some sentiment at our face to face meeting for demoting this to a non-goal, but there was not consensus.

This item was abandoned in the meeting of 2004-03-25. The consensus of the WG was that we should make no change here; some attribute this view to compatibility reasons, others to other reasons. The current status quo does in any case match what several commentators said was an acceptable fallback when the issue was discussed in 2000.

RQ-36 local-references: Allow local references

Locus: structures Cluster: Str

Class: Opp.Des. Status: revisit
Assigned to:
Originator:

Description

Change the XML representation (and possibly the component structure) of local element declarations to at least allow, if not require, all particles to be references, with scope, i.e. put the local declarations directly under <complexType>

(Cf. no-nesting).

Interactions and Input

This is subsumed proposals to deal with R-17.

Input from Straw Poll O-15

This item was postponed in the meeting of 2004-04-30. It will stand or fall with the ‘landscape’ proposal for RQ-017 and friends. If that proposal succeeds, this requirement will be discharged; if not, we are unlikely to do this on its own.

This item was discussed in the meeting of 2004-05-20.

Proposed Resolution

Asir Vedamuthu (member-only link)

RQ-37 norm-value: Provide normalized value for complex/mixed elements

Locus: structures Cluster: PSVI

Class: Opp.Des. Status: postponed
Assigned to:
Originator:

Description

Provide a [schema normalized value] for all valid element infoitems, not just those of simple type, and address the question of typing the characters in mixed content.

Interactions and Input

Input from Straw Poll O-15

This item was postponed in the meeting of 2004-03-25.

This item was taken up again and discussed in the face to face meeting of 2004-05-13 but there was no consensus on the proposal. The item was again postponed.

RQ-38 coconstraints: Add co-constraints

Locus: structures Cluster: Str

Class: Desideratum Status: revisit
Assigned to:
Originator:

Description

Add the ability to define and enforce co-constraints on attribute values, or on attribute values and sub-elements. For example, if attribute a has value foo, the attribute b must have one of the values fuzz, duz, or buzz; but if attribute a has value bar, the attribute b must have one of the values car, far, or tar. Or: if attribute href occurs, the element must be empty; if it does not occur, then it must have type phrase-level-content.

See http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0040.html : LC-193 Response.

See http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001AprJun/0175.html : R-7 in Errata List.

Interactions and Input

This issue was also formerly known as co-occurrence (RQ-27; removed)

Input from Straw Poll O-13

Opportunistic desideratum for 1.1: At our meeting in August 2002, some members of the WG felt that co-constraints needed to be a requirement for 1.1, others that the feature is too complex to design in the time available and with the compatibility constraints agreed for 1.1. Some WG members thought an 80/20 solution would be easy to specify, and undertook to demonstrate this by doing so.

This item was abandoned in the meeting of 2004-03-25.

A request to reopen it was was received on 25 May from Fabio Vitali (member-only link).

RQ-39 patterned-durati: Restricting duration

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator: Michael Anderson

Description

Can a schema author constrain values of the time-duration type to be measured only or at most in days?

See http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#duration-restricting : LC-103.

Interactions and Input

Input from Straw Poll O-5

RQ-40 non-gregorian: support non-Gregorian dates

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator: David RR Webber

Description

support non-Gregorian dates

See http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#non-gregorian-dates : LC-21.

Interactions and Input

Input from Straw Poll O-5

RQ-41 timeduration: duration is incomplete

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator: Ninggang Chen

Description

duration is incomplete per ISO 8601, because it provides no way to identify start or end point of the duration.

See http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#pt2-durations : LC-120.

Interactions and Input

Input from Straw Poll O-5

RQ-42 mixed-patterns: pattern on mixed content

Locus: structures Cluster: Str

Class: Non-goal Status: ng
Assigned to:
Originator: I18n WG

Description

Allow a pattern facet on complex types with content='mixed', so as to allow control over the character repertoire allowed in the character content of elements witha particular complex type?

See http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#complexpattern : LC-217.

Interactions and Input

Input from Straw Poll O-6

RQ-43 loc-independence: Locale-dependent datatype support

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator: I18n WG

Description

Take steps to support the definition of locale-dependent datatypes (i.e., datatypes with locale-specific lexical spaces)?

See http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#mlr : LC-219.

Interactions and Input

Input from Straw Poll O-6

RQ-44 list-delimiters: Allow other list delimiters

Locus: datatypes Cluster: MiPa

Class: Non-goal Status: ng
Assigned to:
Originator: Martin Roberts

Description

Allow schema authors to provide list delimiters other than white space?

See http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0261 : List types.

Interactions and Input

Input from Straw Poll O-8

RQ-45 arrays: Support for Arrays

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator: Robert Miller

Description

Should XML Schema be modified to provide support for arrays?

See http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#arrays : LC-84.

Interactions and Input

Input from Straw Poll O-8

RQ-46 multiple-orders: Multiple order relationships

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

Should it be possible for ordered datatypes to have multiple (user-defined?) order relations?

See http://www.w3.org/XML/Group/xmlschema-current/issues.html#multipleOrders : Issue 108.

Interactions and Input

Input from Straw Poll O-8

RQ-47 single-lex: Single lexical representation

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator: I18n WG

Description

Single lexical representation for each built-in type: Modify XML Schema so that each built-in type has only a single legal lexical representation for each value in its value space?

See http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#SLR : LC-220.

Interactions and Input

Input from Straw Poll O-9

RQ-48 hierarchy: Hierarchy Facet

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator: Philipp Niederau

Description

Add a new hierarchy facet to simplify definitions which would otherwise require complex regular expressions or verbose enumerations?

See http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0338 : Hierarchy constraining facets)

and http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0372 : Meaning of block="substitution"?

Interactions and Input

Input from Straw Poll O-9

RQ-49 unqualified-bits: Schema component binding to the namespace without a name

Locus: structures Cluster: Str

Class: Non-goal Status: ng
Assigned to:
Originator: Curt Arnold

Description

Change the method of binding schema components to the namespace without a name and using them to validate unqualified elements in a document.

See http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#undeclared-ns : LC-89

Interactions and Input

Input from Straw Poll O-11

RQ-50 run-time-parm: Run-time parameterization of types

Locus: structures Cluster: Dat

Class: Non-goal Status: ng
Assigned to:
Originator: Uwe Zeise

Description

Allow the run-time parameterization of types.

See http://www.w3.org/2001/05/xmlschema-rec-comments#pfiRuntimeTypes : R-7

Interactions and Input

Input from :

Straw Poll O-13

RQ-51 dynamic-facets: Dynamic facets

Locus: datatypes Cluster: XSD

Class: Non-goal Status: ng
Assigned to:
Originator: Patrick Sheppard

Description

Dynamic specification of maxOccurs: Allow maxOccurs and other schema information to be specified dynamically in the document instance?

See http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0310

Interactions and Input

Input from Straw Poll O-13

RQ-52 multiple-inher: Support multiple inheritance

Locus: structures Cluster: XSD

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

Support multiple inheritance.

Interactions and Input

Input from Straw Poll O-14

RQ-53 attdecl-order: Order of declarations

Locus: structures Cluster: sfs

Class: Non-goal Status: ng
Assigned to:
Originator: Martin Duerst

Description

Should XML Schema drop the current requirement that in the declaration of a complex type, the attribute declarations should follow the content-model declaration (if any)?

See http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#attribute-ghetto : LC-190

and http://www.w3.org/2000/12/xmlschema-crcomments.html#pfiOrderCMAtt : CR-4

Also, mail from James Clark.

Interactions and Input

Input from Straw Poll O-15

RQ-54 maxOccurs-all: maxOccurs and all group

Locus: structures Cluster: Str

Class: Non-goal Status: ng
Assigned to:
Originator: Martin Duerst

Description

Relationship of all and maxOccurs: Should the all group allow occurrence indicators with maxOccurs > 1?

See http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#all-with-n-gt-1 : LC-16

and http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#all-grp : LC-132

Interactions and Input

Input from Straw Poll O-15

RQ-55 abstract-models: Microparsing

Locus: datatypes Cluster: MiPa

Class: Non-goal Status: ng
Assigned to:
Originator: Anders W. Tell

Description

Should XML Schema be modified to allow the definition of abstract information models together with rules for encoding the information either as elements or strings (for use as attribute values)?

See http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#microparsing : LC-102

Interactions and Input

Input from Straw Poll O-15

RQ-56 no-nesting: Drop nested element declarations

Locus: structures Cluster: Str

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

Remove support for nested element declarations.

See http://www.w3.org/XML/Group/xmlschema-current/issues.html#dropNestedElementTypeDecl : Issue 29

Interactions and Input

Input from Straw Poll O-15

RQ-57 global-atts: Global Attributes

Locus: structures Cluster: Str

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

The namespace REC effectively creates a category of global attributes. We can't at the moment define such things, and their use in an instance would ipso facto render it schema-invalid.

See http://www.w3.org/XML/Group/xmlschema-current/issues.html#globalAttrs : Issue 26

Interactions and Input

Input from Straw Poll O-15

RQ-58 lists-children: Association of repeated child elements with lists

Locus: structures Cluster: MiPa

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

Allow the association of repeated child elements in a content model with lists (and possibly ordered sets).

See http://www.w3.org/XML/Group/xmlschema-current/issues.html#collections : Issue 108

Interactions and Input

Input from Straw Poll O-16

RQ-59 arrays-type-refs: Array type refs

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

Allow arrays of the type and references to type once a type is defined. [?]

See http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2001May/0039.html : [Martin Gudgin]

Interactions and Input

Input from Straw Poll O-16

RQ-60 multiple-langs: multiple schema languages

Locus: structures Cluster: XSD

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

Allow support for multiple schema languages. Allow more than one schema language; design a framework to allow them to fit together.

See http://www.w3.org/XML/Group/xmlschema-current/issues.html#multSchemaLangs : Issue 41

Interactions and Input

Input from Straw Poll O-16

RQ-61 psvi-input: PSVI as schema input

Locus: structures Cluster: PSVI

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

What happens if the input to the schema processor is a PSVI?

See http://www.w3.org/2000/12/xmlschema-crcomments.html#x3 : CR-59

Interactions and Input

Input from Straw Poll O-16

RQ-62 enumeration-maps: Mapping between enumerations

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

Mapping between enumeration, Lexical labels for dataypes. Offline list of enumerations.

See http://www.w3.org/XML/Group/xmlschema-current/issues.html#enumerationMapping : Issue 111

and http://www.w3.org/XML/Group/xmlschema-current/issues.html#labelEnum : Issue 200

Interactions and Input

Input from Straw Poll O-8

RQ-63 restrict-unions: Restricting unions and lists

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

Allow restrictions of unions and lists in obvious ways, e.g. by restricting the itemType or by subsetting memberTypes (with or without further restriction of the member types)

Interactions and Input

Input from Straw Poll O-8

RQ-64 simple-deriv: Derivation of Simple Types

Locus: datatypes Cluster: D/T

Class: Non-goal Status: ng
Assigned to:
Originator:

Description

We would like better mechanisms for deriving simple types. For some months we worked with abstract types that allowed derivation of value spaces which could then be linked with lexical spaces but were unable to make this work. While revising the date/time types Mark Davis wanted to derive date from dateTime by restricting its lexical space by a pattern. This is difficult but important.