XML Schema: Comments on Recommendation

Version $Id: xmlschema-rec-comments.html,v 1.38 2005/09/08 18:50:03 cmsmcq Exp $

Note, 8 September 2005:

This document was closed in May of 2004 and is no longer being maintained. The XML Schema Working Group is now using the public W3C instance of the Bugzilla issue-tracking system to manage comments on the XML Schema Recommendation. For current information on any of the items listed here, look for its number (e.g. "R-112") among the Bugzilla entries for XML Schema.

This document summarizes the comments on the XML Schema Recommendation. Comments received via the XML Schema Comments list, up until April 18, 2004, are recorded in this version of the document.

The process by which the XML Schema WG plans to handle these issues is described at http://www.w3.org/XML/2001/07/xmlschema-errataprocess.html.

Material reproduced from comments has been marked up, and obvious typos have been corrected. Postings and documents which raise several substantively distinct points have been silently divided among several comments. To consult the original postings, see the archive of the www-xml-schema-comments list.

Commentators are requested to review the entries for the comments they have made, and to check to make sure we have correctly understood and paraphrased their comment.

In addition to the postings to the XML Schema comments list, some postings to the XML Schema Interest-Group mailing list have been included here; this list is W3C-internal and only those with member access to the W3C web site will be able to follow the relevant hyperlinks.

Not all postings to the comments mailing list have resulted in entries in this list. For example, postings which ask for clarification and do not result in any errata, are not necessarily included in this list.

The status of each issue [at the time this document was closed] is recorded in the table. The status may be:

New
A new issue.
In progress
The WG is currently discussing the issue. The issue may or may not be classified. See the classification field for further info
Resolved
The issue has been classified and a resolution agreed upon by the WG. A note to the commentator may still be pending.
Errata Drafting
The issue has been classified and a resolution has been agreed upon by the WG. An editor or WG member is currently drafting text for the erratum.
Errata Proposed
Errata text has been drafted by an editor, and is awaiting review by the WG.
Errata Approved
Errata text has been approved by the WG, but is not yet in the Errata document
Closed
The issue is resolved, any relevant errata has been approved and added to the errata document. No further work is required for the issue

Issues have been assigned to clusters for convenience in managing discussion; cluster values preceded by '!' are highest priority, those preceded by '.' are middle priority, in the preparation of errata.

Num Cluster Part Status Classification Originator Responsible Description
R-1 . Date/Time 2 Errata drafting Error w/erratum Henry Zongaro Paul V. Biron Problem with dateTime values in 3.2.6.2
R-2 Editorial 0 Closed Editorial Dan Glickman Lisa Martin Primer states that there are 15 facets
R-3 ! Primer 0 Closed Clarification w/erratum Eddie Robertsson Priscilla Walmsley Primer states that all components must be repeated in restriction
R-4 Editorial 0 Closed Editorial Donald Gignac Lisa Martin Conflicting statements about Primer being normative/non-normative
R-5 ! Editorial 0 Closed Editorial Donald Gignac Priscilla Walmsley Typographical error in section 2.8 example
R-6 Editorial 0 Closed Editorial Donald Gignac Priscilla Walmsley Confusing table in the Primer
R-7 Unclustered (Closed) Closed Future Requirement Uwe Zeise Ashok Malhotra Request for runtime parameterization of types
R-8 ! Misc. simple types 1 Errata Drafting Error Martin Gudgin Henry S. Thompson Should finalDefault allow list, union?
R-9 Unclustered (Closed) 1 Closed Clarification w/erratum Henry Zongaro Henry S.Thompson minOccurs=0 on "all"
R-10 Editorial 2 Closed Editorial John G. de Freitas Lisa Martin Definition of bounded
R-11 Editorial 2 Closed Editorial Donald Gignac Lisa Martin Editorial error in section 4.1.2.3
R-12 Editorial 2 Closed Editorial Donald Gignac Lisa Martin Editorial error in section 4.1.2
R-13 Editorial 2 Closed Editorial Eliotte Harold Lisa Martin Typographical error in title of section 3.2.15.2
R-14 Editorial 2 Closed Editorial Panagiotis Reveliotis Lisa Martin Typographical error in section 3.2.7.1
R-15 Unclustered (Closed) 2 Closed Error Panagiotis Reveliotis Paul Biron Error in definition of ordered Schema Component
R-16 Editorial 2 Closed Editorial Eliotte Harold Lisa Martin Typographical error ("fragement") in section 3.2.17
R-17 Unclustered (Closed) 2 Closed Clarification w/erratum Martin Duerst Ashok Malhotra base64 and linebreaks every 76 characters
R-18 ! Misc. simple types 0,2 Closed Clarification/ Error Alexander Falk Priscilla Walmsley, Paul Biron Use of pattern facet for list type
R-19 Unclustered (Closed) 1 Closed Error Panagiotis Reveliotis Henry S. Thompson group element info item missing attributes
R-20 Editorial 1 Closed Editorial Panagiotis Reveliotis Lisa Martin Typographical error in section 3.4.2 example
R-21 Unclustered (Closed) 2 Closed Clarification w/Erratum Panagiotis Reveliotis Paul Biron Clarification required re: list itemType
R-22 ! Numeric Types 2 Closed Error Ashok Malhotra Ashok Malhotra/Paul V. Biron Floating Point Issues and IEEE
R-23 Unclustered (Closed) 1 Closed Clarification Mark Huffman Lisa Martin Restrictions of attributes specifying "use"
R-24 Unclustered (Closed) 1 Closed Future requirement Yan Leshinsky Henry S. Thompson Derivation by Restriction: pointless occurrences
R-25 . Misc. Structures 1 Errata Drafting Error w/erratum Satoshi Nakamura Henry S. Thompson Element locally valid: fixed value constraints
R-26 ! Editorial 1 Closed Editorial C. M. Sperberg-McQueen Henry S. Thompson Two typos in section 3.3.5 of Structures
R-27 Unclustered (Closed) 0 Closed Doc Suggestion Doug Bunting Lisa Martin Request for additional information in the Primer
R-28 ! Misc. Structures 1 Closed Error Satoshi Nakamura Henry S. Thompson Element locally valid (type): rule about "abstract"
R-29 ! Editorial 2 Closed Editorial Martin Duerst Paul V. Biron Remove request for comments from Datatypes
R-30 ! Misc. simple types 2 Closed Error Martin Duerst Paul V. Biron Request for clarification of regex notation
R-31 ! Misc. simple types 2 Closed Clarification w/Erratum James Clark Paul V. Biron anyURI and xml:base
R-32 . Cross-part 1 Closed Unclassified Jeff Rafter Unassigned Type of public attribute of notation
R-33 ! Identity Constraints 0,1 Closed Clarification/Error Neil Graham Priscilla Walmsley, Henry S. Thompson Request for clarification of identity constraint rules
R-34 ! Final and block 1 Closed Error Choi Jongwon Henry S. Thompson Potential problem with description of final for simpleType in Structures
R-35 Unclustered (Closed) 2 Closed Error Satoshi Nakamura Alexander Falk Regular expression grammar for charClass is ambiguous
R-36 ! Editorial 0 Closed Editorial Jason Stallion Priscilla Walmsley Font of text in section 2.5.2 of Primer incorrect
R-37 Editorial 2 Closed Editorial Tony Coates Lisa Martin The link to ISO 8601 in the Datatypes spec doesn't work
R-38 Numeric Types 2 Closed Clarification w/Erratum Kevin Yancey Paul V. Biron Missing constraint for fractionDigits?
R-39 Unclustered (Closed) 1 Closed Error Paul V. Biron Henry S. Thompson Error in the DTD for Schemas in Structures spec
R-40 ! Misc. simple types 2 Closed Clarification w/Erratum Paul V. Biron Paul V. Biron Clarification of the regex language in Datatypes
R-41 Misc. simple types 2 Errata Proposed Error Paul V. Biron Paul V. Biron Error in production 10 of regex in Datatypes
R-42 Unclustered (Closed) 1 Closed Future Requirement Achille Fokoue Henry S. Thompson Potential problem with particle derivation Choice:Choice rules
R-43 Primer 0 Closed Unclassified Donald Gignac Priscilla Walmsley Imprecise text in Table 1 of Primer
R-44 ! Editorial 0 Closed Editorial Donald Gignac Priscilla Walmsley Grammatical errors in section 5.6 of the Primer
R-45 ! Editorial 0 Closed Editorial Donald Gignac Priscilla Walmsley Inaccurate language in section 5.5 of Primer re: references to HTML
R-46 . Identity Constraints 1 Closed Error, Future Requirement Mary Holstege Henry S. Thompson Minor inconsistency in definition of Identity Constraints
R-47 !Type deriv. rules and groups 1 Closed Clarification w/erratum Henry Zongaro Henry S. Thompson Request for clarification of complex type derivation restriction rules for empty base
R-48 Date/Time 0,2 Closed Error Henry Zongaro Priscilla Walmsley, Ashok Malhotra/Paul V. Biron Lexical representation of gMonth is inconsistent wrt ISO 8601
R-49 Date/Time 2 In progress Unclassified Henry Zongaro Unassigned ISO 8601:2000 defines 0000 as a valid year
R-50 ! Primer 0 Closed Error Scott Means Priscilla Walmsley "appInfo" element in Primer vs. "appinfo" element in Structures
R-51 Primer 0 Closed Clarification Mark Hurley Unassigned Inaccurate text in section 2.3 of the Primer
R-52 ! Type deriv. rules and groups 1 Closed Error Sandy Gao Henry S. Thompson Missing constraint for indirect circular attribute group?
R-53 Type deriv. rules and groups 1 Closed Clarification Sandy Gao Henry S. Thompson Request for clarification of include
R-54 ! Type deriv. rules and groups 1 Closed Clarification w/erratum Sandy Gao Henry S. Thompson Request for clarification of ur-type
R-55 Editorial 0 Closed Editorial Bill Thompson Priscilla Walmsley Typo in table 2 of the Primer
R-56 ! Editorial 2 Errata Drafting Editorial Donald Gignac Paul V. Biron Grammatical error in section 2.5.2 of Datatypes spec
R-57 Editorial 1 Closed Editorial Donald Gignac Henry S. Thompson Inconsistent capitalization in section 2.1 of Structures
R-58 . Primer 0 Closed Editorial Donald Gignac Priscilla Walmsley Errors in example in Appendix C of Primer
R-59 Primer 0 Closed Unclassified Donald Gignac Priscilla Walmsley Suggested changes for Appendix C of Primer
R-60 ! Type deriv. rules and groups 1 Closed Error Henry S. Thompson Henry S. Thompson Problem with particle derivation rules and the Schema for Schemas
R-61 ! Editorial 2 Closed Error Thomas Broyer Paul V. Biron Typo in section D.3.1 "Sign Allowed" of Datatypes spec
R-62 Identity Constraints 1 Closed Error Henry S. Thompson Henry S. Thompson Whitespace and identity constraint XPath expressions
R-63 Unclustered 2 Closed Clarification w/erratum Donald Gignac Paul V. Biron Suggested change for union example in section 2.5.1.3 of Datatypes spec
R-64 Misc. Structures 1 Closed Error Asir Vedamuthu Henry S. Thompson Issue with complex type property mapping rules for content type
R-65 ! Wildcards 1 Closed Error Sandy Gao Henry S. Thompson Issues with the rules for wildcard union, subset, and intersection
R-66 ! Misc. simple types 1,2 Closed Error Asir Vedamuthu Paul V. Biron, Henry S. Thompson Magic built-in datatypes: ENTITY and ENTITIES
R-67 ! Type deriv. rules and groups 0,1 Closed Clarification w/erratum, Future Requirement Lisa Martin Priscilla Walmsley, Henry S. Thompson A question about type derivation and anonymous types
R-68 ! Type deriv. rules and groups 1 Closed Error Alexander Falk Henry S. Thompson Contradiction in Structures re: base for complexTypes with simpleContent
R-69 Misc. simple types 0,2 Closed Error Alexander Falk Priscilla Walmsley, Paul V. Biron Problem in the regex grammar for charRange
R-70 ! Editorial 2 Closed Editorial Eric van der Vlist Henry S. Thompson Typo in the Schema for Schemas
R-71 ! Editorial 1 Closed Editorial Henry S. Thompson Henry S. Thompson Editorial error in the text for Element Declarations Consistent
R-72 ! Editorial 1 Errata Drafting Editorial Elliotte Rusty Harold Henry S. Thompson Typo in appendix E of Structures
R-73 . Misc. Structures 1 Errata Drafting Clarification w/erratum Lisa Martin Henry S. Thompson Question about unions of attribute uses
R-74 ! Type deriv. rules and groups 1 Closed Error Henry S. Thompson Henry S. Thompson Missing constraint for circular substitution groups?
R-75 Misc. simple types 2 Closed Error Eric van der Vlist Paul V. Biron Potential problem with the rules for maxExclusive
R-76 Unclustered (Closed) 1 Closed Clarification Lisa Martin Lisa Martin Question about content type EMPTY
R-77 Identity Constraints 1 Errata Drafting Clarification w/erratum, Future Requirement Jeni Tennison Henry S. Thompson Issue to do with identity constraints and chameleon include
R-78 ! UPA and content models 1 Closed Error Sandy Gao Henry S. Thompson Issue to do with definition of substitution groups, block, and UPA
R-79 . Type deriv. rules and groups 1 Errata Drafting Error Sandy Gao Henry S. Thompson Ambiguity in statements about valid type derivation
R-80 . Wildcards 0,1 Closed Error Amy Moulton Priscilla Walmsley, Henry S. Thompson Meaning of ##other
R-81 ! Identity Constraints 0 Closed Error Priscilla Walmsley Priscilla Walmsley Error in Primer example of identity constraints
R-82 . Primer 0 Closed Unclassified Priscilla Walmsley Priscilla Walmsley Three editorial errors in the Primer
R-83 Misc. simple types 2 Closed Error Henry S. Thompson Paul V. Biron/Ashok Malhotra Token should exclude #xD from lexical and value spaces
R-84 . Final and block 1 Errata Drafting Clarification w/erratum Priscilla Walmsley Henry S. Thompson Can final="extension" for simpleType?
R-85 QNames 2 Errata Drafting Clarification w/erratum Eric Van der VList Henry S. Thompson Request for clarification of QName type
R-86 UPA and content models 1 Closed Clarification w/erratum Sandy Gao Henry S. Thompson Request for clarification of UPA
R-87 ! Misc. Structures 1 Closed Error Stanley Guan Henry S. Thompson Error in section 3.4.2 of Structures
R-88 ! Misc. simple types 2 Closed Clarification w/erratum Eric van der Vlist Ashok Malhotra, Paul V. Biron Suggested changes to clarify NOTATION
R-89 ! Misc. simple types 2 Closed Error Henry Zongaro Paul V. Biron, Ashok Malhotra Is a trailing decimal point permitted for integer?
R-90 ! Date/Time 2 Errata Drafting Error Henry Zongaro Ashok Malhotra/Paul V. Biron Questions about the lexical and canonical rep'ns of dateTime
R-91 Named Groups 1 New Unclassified Henry S. Thompson Unassigned Optional self-reference in group redefinition
R-92 Named Groups 1 New Unclassified Henry S. Thompson Unassigned Clarification required for group redefinition
R-93 Wildcards 1 Closed Error w/erratum Kohsuke Kawaguchi Henry S. Thompson Problem with derivation by restriction and anyAttribute
R-94 Identity Constraints 1 Errata Drafting Clarification w/erratum, Future requirement Khaled Noaman/Henry S. Thompson Henry S. Thompson Issues with identity constraints and derivation by restriction
R-95 Unclustered (Closed) 0 Closed Doc Suggestion Kenneth Geisshert Unassigned Request for PDF version of the Primer
R-96 Misc. Structures 1 Errata Drafting Error Henry S. Thompson Henry S. Thompson Problem with scope property of attributes
R-97 ! Misc. simple types 2 Closed Error Ashok Malhotra Paul V. Biron, Ashok Malhotra Problem with canonical rep'n of float/double
R-98 . Qnames 2 In progress Error Sandy Gao Paul V. Biron/Ashok Malhotra Question about the canonical rep'n of QName
R-99 ! Misc. simple types 2 Closed Error Sandy Gao Paul.V.Biron Issue re: the length facet for NMTOKENS, IDREFS, ENTITIES
R-100 ! UPA and content models 1 Closed Error Sandy Gao Henry S. Thompson Issue re: description of overlapping for UPA, Appendix H
R-101 ! UPA and content models 1 Closed Clarification w/erratum Sandy Gao Henry S. Thompson Issue re: UPA and groups
R-102 ! Type deriv. rules and groups 1,2 Closed Error Henry S. Thompson Henry S. Thompson, Paul V. Biron/Ashok Malhotra Errata in restriction constraints wrt simple type defns?
R-103 ! Editorial 1 Closed Editorial Ross Thompson Henry S. Thompson The term PSVI needs to be defined
R-104 ! Primer 0 Closed Clarification w/erratum Rieks van der Straaten Priscilla Walmsley Primer question re: integer and the fractionDigits facet
R-105 . Identity Constraints 1 Closed Future Requirement Henry S. Thompson Unassigned Comment re: identity constraints property in Schema component
R-106 ! QNames 2 Closed Clarification w/Erratum Anli Shundi Paul V. Biron, Ashok Malhotra Clarification requested re: facets for QName type
R-107 ! Misc. Structures 1 Closed Error Henry S. Thompson Henry S. Thompson Change required re: note in section 4.2.1 of Structures
R-108 Numeric Types 2 In progress Unclassified Michael Sperberg-McQueen Unassigned Clarification requested re: rounding of floats
R-109 ! Cross-part 1 Closed Error Martin Gudgin Henry S. Thompson Mismatch between Parts 1 and 2 in the area of facet constraints
R-110 ! Numeric Types 2 Closed Error Sandy Gao Paul V. Biron, Ashok Malhotra Error in example in section 4.3.11 of Datatypes?
R-111 Wildcards 1 New Unclassified Eric van der Vlist Unassigned Why are foreign attributes not permitted for appinfo and documentation?
R-112 . Misc. Structures 1 In progress Error w/erratum Sandy Gao Unassigned A question about QName Resolution (Schema Document)
R-113 ! UPA and content models 1 Closed Clarification w/erratum Lisa Martin Henry S. Thompson A question about all content models
R-114 QNames 1 In progress Unclassified Jonathan Marsh Unassigned Schema infoset fix-ups
R-115 . QNames 1,2 In progress Unclassified Ashok Malhotra Unassigned Validating attributes with default value of type QName
R-116 . Cross-part 2 Closed Error w/erratum Ross Thompson Paul V. Biron Question about the type of a pattern value
R-117 ! Misc. Structures 1 Closed Error w/erratum Henry S. Thompson Henry S. Thompson Problem with processContents for the ur-type
R-118 . Date/Time 2 Closed Error w/erratum Michael Kay Unassigned Questions about the value space for dateTime
R-119 ! Date/Time 2 Closed Clarification w/erratum Michael Kay Paul V. Biron, Ashok Malhotra Question about the value space for date
R-120 ! Date/Time 2 Closed Error Michael Kay Paul V. Biron, Ashok Malhotra Question about the canonical representation of date
R-121 ! Primer 0 Closed Error Jeffrey Stephenson/Henry S. Thompson Priscilla Walmsley Import example in section 5.4 of Primer incorrect
R-122 . Type deriv. rules and groups 1 Errata Drafting Error Eric van der Vlist Henry S. Thompson Issue re: restricting substitution groups
R-123 . Misc. Structures 1 Closed Clarification without erratum Mark Feblowitz Unassigned A question about redefining redefines
R-124 PSVI 1 Errata Drafting Editorial/Future Requirement Lisa Martin Henry S. Thompson A question about PSVI properties
R-125 ! Editorial 1 Closed Editorial Wojtek Murawski Henry S. Thompson Editorial error in section 4.3.2 of Structures
R-126 Primer 0 Closed Unclassified Simon Cox Priscilla Walmsley Suggested change for the Primer re: substitution group members
R-127 . Date/Time 2 Errata Drafting Clarification w/erratum Henry Zongaro Ashok Malhotra Distinction between 00:00:00 and 24:00:00 for time datatype?
R-110b !Numeric Types 2 Closed Error Henry Zongaro Paul V. Biron Does the fractionDigits facet apply to the value space or lexical space?
R-128 Misc. simple types 2 Errata Drafting Clarification w/erratum C.M. Sperberg-McQueen Dave Peterson Question re: leading zeros for gYearMonth and gMonth
R-129 ! Misc. Structures 1 Closed Error Henry S. Thompson Henry S. Thompson type of id attr on schema elt
R-130 ! Misc. simple types 2 Closed Error Lin Yeng Husband Paul V. Biron, Ashok Malhotra Pattern of language type in XMLSchema.xsd
R-131 ! Editorial 2 Closed Editorial Richard Emberson Paul V. Biron Typo in description of duration in datatypes
R-132 . Misc. simple types 2 Errata Drafting Error w/erratum Paul V. Biron Ashok Malhotra Equiv comparisons on anyURI
R-133 . Misc. Structures 1 Errata Drafting Error w/erratum Daniel Veillard Henry S. Thompson Regex for XPath in S4S invalid
R-134 . Misc. simple types 2 In progress Error w/erratum James Clark Paul V. Biron Treatment of ^ in regexes
R-135 ! Misc. simple types 2 Closed Error James Clark Paul V. Biron, Ashok Malhotra Question about surrogate characters in F.1.1
R-136 ! Unclustered 1 Closed Error Rahul Srivastava Henry S. Thompson Question about selector XPath expressions
R-137 ! Unclustered 1 Closed Error Jerome Simeon Henry S. Thompson Can substitution groups contain local elements?
R-138 ! Unclustered 1 Closed Clarification w/erratum Aung Aung Henry S. Thompson The S4S contains derivations with anySimpleType as the base
R-139 ! Unclustered 2 Closed Error James Clark Paul V. Biron, Ashok Malhotra Appendix D of datatypes does not permit 24:00 for date/time types
R-140 . Unclustered 2 In progress Error w/erratum James Clark Unassigned dateTime order relation and leap seconds
R-141 . Unclustered 2 In progress Error w/erratum James Clark Unassigned Changes suggested re: dateTime order relation
R-142 ! Unclustered 2 Closed Error w/erratum James Clark Ashok Malhotra, Paul V. Biron Order relation for gMonthDay, gMonth, gDay
R-143 ! Unclustered 1 Closed Error Henry S. Thompson Henry S. Thompson Subtle bug in schema doc. for schemas
R-144 . Unclustered 2 Errata Drafting Error w/erratum James Clark Ashok Malhotra Adding durations to dateTime
R-145 . Unclustered 2 Errata Drafting Error w/erratum James Clark Ashok Malhotra Leap second validation
R-146 . Unclustered 2 Closed Clarification James Clark Ashok Malhotra Double leap seconds
R-147 ! Unclustered 2 Closed Error James Clark Ashok Malhotra, Paul V. Biron Lexical form of duration components
R-148 . Unclustered 2 In progress Unclassified James Clark Asir Vedamuthu Trailing decimal point in seconds field of dateTime and time
R-149 ! Unclustered 2 Closed Clarification w/erratum James Clark Ashok Malhotra, Paul V. Biron Is +0 allowed as a nonPositiveInteger in lexical form?
R-150 ! Unclustered 2 Closed Clarification w/erratum Sandy Gao Ashok Malhotra Are international digit characters allowed for date/time types?
R-151 ! Unclustered 2 Closed Clarification w/erratum Sandy Gao Ashok Malhotra Questions about equal fundamental facet
R-152 ! Unclustered 2 Closed Error James Clark Unassigned When is T designator required with duration?
R-153 !Unclustered 1 Closed Error Walter Waterfeld Henry S. Thompson Is the public attribute of notation optional?
R-154 .Unclustered 1 Errata Drafting Editorial Andrew Watt Henry S. Thompson Typo in section 5.1 of Structures?
R-155 .Unclustered 0 Closed Editorial Priscilla Walmsley Unassigned 4 Typos in the Primer
R-156 !Unclustered 1 Closed Clarification w/Erratum Asir Vedamuthu Henry S. Thompson Question about mixed="true" and simpleContent
R-157 !Unclustered 1 Closed Clarification without erratum Ashok Malhotra Unassigned Question about non-deterministic content models
R-158 .Unclustered 1 Closed Future Requirement Asir Vedamuthu Unassigned topLevelAttribute and use=(optional|prohibited|required)
R-159 !Unclustered 1 Closed Error Henry S. Thompson Henry S. Thompson Bug in the spec wrt attribute defaults
R-160 !Unclustered 1 Closed Clarification without erratum Dave Hollander Paul V. Biron Question re: validity of type override with union type
R-161 !Unclustered 1 Closed Error James Clark Henry S. Thompson QName resolution to components with no target namespace
R-162 !Unclustered 1 Closed Error w/erratum John Verhaeg Henry S. Thompson Errors in section 3.14.6 of Structures
R-163 .Unclustered 1 Errata Drafting Clarification w/erratum; Future Requirement David Stephenson Henry S. Thompson Inconsistency between S4S and schema component information re: annotations
R-164 .Unclustered 0 Closed Doc Suggestion Ben Clemens Priscilla Walmsley Suggestion for change to Primer PO Example
R-165 .Unclustered 1 Errata Drafting Clarification w/erratum James Clark Henry S. Thompson Clarification requested for statement in Appendix H of Structures
R-166 .Unclustered 1 Closed Error w/eratum Richard Tobin Henry S. Thompson Question re: xsi:type and skip
R-167 !Unclustered 1 Closed Clarification without erratum/Future Requirement Richard Tobin Unassigned Question about assessment outcome for attributes
R-168 .Unclustered 1 Closed Clarification Richard Tobin Sandy Gao Question about error codes
R-169 !Unclustered 1 Closed Error w/erratum Paul V. Biron Henry S. Thompson Type of the public identifier of notations
R-170 !Unclustered 1,2 Closed Future Requirement Berthold Daum Unassigned Inconsistent use of the term "derived"
R-171 !Unclustered 1 Errata Drafting Error w/erratum Richard Tobin Henry S. Thompson Question about fixed value constraint on element
R-172 .Unclustered 1 Errata Drafting Clarification w/erratum; Future Requirement Neil Graham Henry S. Thompson Questions viz. when fields match element with the ur-type
R-173 !Unclustered 2 Closed Clarification without erratum John Mercado Ashok Malhotra Canonical form of duration
R-174 .Unclustered 1 Closed Future Requirement Elena Litani Unassigned Question re: PSVI document property
R-175 !Unclustered 2 Errata Approved Error w/erratum Michael Kay Ashok Malhotra Questions re: normalizedString
R-176 .Unclustered 1 In progress Unclassified Masayasu Ishikawa Unassigned Question about mixed in derivation by extension
R-177 .Unclustered 2 Errata Proposed Clarification w/erratum Ashok Malholtra Ashok Malhotra Should list of IDs be allowed?
R-178 Unclustered 1 New Unclassified Stanley Guan,Ashok Malholtra Unassigned Question about use and fixed for attributes
R-179 . Unclustered 2 Errata Drafting Error w/erratum Asir Vedamuthu Ashok Malhotra Defect in schema component model wrt enumeration and annotations
R-180 Unclustered 1 New Unclassified Sandy Gao Unassigned Question about the schema error code property in the PSVI
R-181 . Unclustered 1,2 Errata Drafting Error w/erratum Stefan Wachter Ashok Malhotra Question about equality of lists
R-182 . Unclustered 1,2 New Unclassified Stefan Wachter Unassigned Question about equality and union types
R-183 . Unclustered 1 New Unclassified Sandy Gao Unassigned Question about default values
R-184 . Unclustered 2 New Unclassified Henry S. Thompson Unassigned Question about pattern and union types
R-185 Unclustered 2 Errata Drafting Error w/erratum Jeremy Carroll Unassigned Question about cardinality of calendar types
R-186 . Unclustered 2 In progress Unclassified Sandy Gao Unassigned Constraints for min/maxIn/Exclusive facets
R-187 . Unclustered 1,2 New Unclassified Sandy Gao Unassigned Missing constraints
R-188 Unclustered 0 New Unclassified Arthur E. Salwin Unassigned Potential errors in the Primer
R-189 ! Unclustered 1 Errata Drafting Error Herve Verjus Henry S. Thompson Recursive simple type definitions
R-190 Unclustered 2 Closed Future Requirement Steven Taschuk Ashok Malhotra Truncation is not defined
R-191 ! Unclustered 1 Errata Drafting Error Sandy Gao Henry S. Thompson Question about e-props-correct.2
R-192 . Unclustered 2 Errata Proposed Error w/erratum Steven Taschuk Ashok Malhotra Revisiting issue about canonical form for duration
R-193 ! Unclustered 1 Errata Drafting Error w/erratum Lisa Martin Henry S. Thompson Question re: processContents=skip
R-194 ! Unclustered 1 Errata Drafting Clarification w/erratum Lisa Martin Unassigned Question re: processContents=skip
R-195 . Unclustered 2 In progress Error w/erratum Dave Peterson Unassigned Correct error in the description of order for dateTime
R-196 . Datatypes (General) 2 Errata approved Clarification w/erratum Francois Yergeau Ashok Malhotra Add health warning on use of whitespace facet on elements
R-197 Datatypes (General) 2 In progress Clarification w/erratum Noah Mendelsohn Unassigned Add warning on whitespace processing
R-198 ! Datatypes (General) 2 Closed Error, Defer to 1.1 Ed Merks Unassigned Problem with unions of unions
R-199 ! Datatypes (General) 2 Errata Drafting Error w/erratum Lisa Martin/Ed Merks Paul Biron, Henry Thompson Problem with final for simple types
R-200 ! Unclustered 1 Errata Drafting Error w/erratum Sandy Gao Henry Thompson Problem with erratum E1-18
R-201 ! Datatypes (General) 2 Closed Editorial Paul Biron Paul Biron The link to IETF INTERNET-DRAFT: IRIs in the Datatypes spec is wrong
R-202 Unclustered 1 New Unclassified Schema WG Unassigned How many components are there for complextype extensions?
R-203 Unclustered 2 New Unclassified Sandy Gao Unassigned Inconsistency with constraints on min/maxExclusive
R-204 Unclustered 1 New Unclassified Sandy Gao Unassigned ComplexType mapping rule issue: min=max=0
R-205 Unclustered 1 New Unclassified Sandy Gao Unassigned Question re: mixed on complexType and complexContent
R-206 Unclustered 1 Errata Drafting Clarification w/erratum Rainer Becker (via Henry S. Thompson) Henry S. Thompson Can fields identity nodes with types having simpleContent?
R-207 Unclustered 1 New Unclassified Dare Obasanjo Unassigned Question about wildcard restriction
R-208 Unclustered 2 New Unclassified Sandy Gao Unassigned Question about the lexical space of NOTATION types
R-209 Unclustered 1 New Unclassified Dmitry Trifonov Unassigned appinfo and documentation elements have no id attribute
R-210 Unclustered 0 New Unclassified Emmanuel Languillat Unassigned Ambiguity in the Primer
R-211 Unclustered 1 New Unclassified C.M. Sperberg-McQueen Unassigned The {attributes} property on the Annotation schema component
R-212 Unclustered 1 New Unclassified C.M. Sperberg-McQueen Unassigned Question about VR Element Locally Valid (Element) in Structures 3.3.4
R-213 Unclustered 1 New Unclassified Xan Gregg Unassigned Question about attribute wildcards and restriction
R-214 Unclustered 2 Errata Drafting Error w/erratum Sandy Gao Ashok Malhotra Question about the value space of double
R-215 Unclustered 1 Errata Drafting Error w/erratum Tim Hanson Henry S. Thompson Whitespace and identity constraints
R-216 Unclustered 1 New Unclassified Sandy Gao Unassigned Potential problem with Name and Type OK
R-217 Unclustered 1 New Unclassified Sandy Gao Unassigned Potential problem with Derivation Valid (Restriction, Complex)
R-218 Unclustered 1 Errata Approved Error w/ erratum Sandy Gao Henry S. Thompson Clarification required for complexContent extending simpleContent
R-219 Unclustered 1 New Unclassified Schema WG Unassigned Does section 3.11.1 of part 1 need to refer to list, union?
R-220 Unclustered 1 New Unclassified Henry S. Thompson Unassigned Problem with erratum E1-17
R-221 Unclustered 2 In progress Clarification w/erratum John Tebbutt Unassigned Question about decimal values with >18 digits
R-222 Unclustered 2 New Unclassified Schema WG Unassigned Should XML Schema continue to define the XMLSchema-datatypes namespace?
R-223 Unclustered 1 New Unclassified D. Schenk Unassigned Suggested change to an example in Structures
R-224 Unclustered 2 New Unclassified Michael Sperberg McQueen Unassigned Questions about metacharacters in regular expressions
R-225 Unclustered 1 New Unclassified Sandy Gao Unassigned Question about fixed element value with simple type
R-226 Unclustered 1 New Unclassified Henry S. Thompson Unassigned Must the content of schemaLocation be a resolvable URL?
R-227 Unclustered 1 New Unclassified Tim Hanson Unassigned identity constraints and xsi:nil
R-228 Unclustered 2 New Unclassified Anli Shundi Unassigned Suggestion for changes in fractionDigits example in part 2
R-229 Unclustered 2 New Unclassified Steve Hanna Unassigned Order relation on time
R-230 Unclustered 1 New Unclassified Tim Daplyn Unassigned Question on maxOccurs=0, particles and restriction
R-231 Unclustered 1,2 New Unclassified Henry S. Thompson Unassigned Enumeration restrictions are unclear
R-232 Unclustered 1 New Unclassified Michael Sperberg-McQueen Unassigned Vacuous Redefinition
R-233 Unclustered 1 New Unclassified Henry S. Thompson Unassigned Validation of xsi: attributes
R-234 Unclustered 1 New Unclassified Kazumi Saito Unassigned Anonymous global type elements of same name in model group
R-235 Unclustered 2 New Unclassified Arjohn Kampman Unassigned Canonical rep'n of -0.0
R-236 Unclustered 2 New Unclassified Dan Connolly Unassigned whitespace facet constrains value space of integer?
R-237 Unclustered 1 New Unclassified David Bau Unassigned Possible errors in the S4S
R-238 Unclustered 0 New Unclassified David Bau Unassigned Primer Section 2.3 - Empty Content
R-239 Unclustered 1 New Unclassified David Bau Unassigned Question re: Element Declarations Consistent
R-240 Unclustered 1 New Unclassified Alessandro Triglia Unassigned Question re: Particle Derivation OK (All/Choice/Sequence:Any -- NSRecurseCheckCardinality)
R-241 Unclustered 1 New Unclassified Michael Marchegay Unassigned Question re: Validation of an element restriction whose base type has the variety union
R-242 Unclustered 1 New Unclassified Michael Kay Unassigned Part 1: final attribute of simpleType
R-243 Unclustered 1 New Unclassified Henry S. Thompson Unassigned Can an attribute prohibited by restriction be added back through a subsequent extension?
R-244 Unclustered 2 New Unclassified Joseph Fialli Unassigned Clarification requested for Appendix E
R-245 Unclustered 1 New Unclassified Dan Small Unassigned Editorial error in section 3.1.4 of Structures
R-246 Unclustered 2 New Unclassified Walter Waterfeld Unassigned IDREFS and space
R-247 Unclustered 2 New Unclassified Walter Waterfeld Unassigned 2E PER: bracket missing in pattern for lexical space of xs:language
R-248 Unclustered 2 New Unclassified Anli Shundi Unassigned 2E PER: Typos in 2E Datatypes spec
R-249 Unclustered 2 New Unclassified Bob Foster Unassigned 2E PER: Objection to erratum E2-18
R-250 Unclustered 1 New Unclassified Eric J. Schwarzenbach Unassigned 2E PER: Comments on rcase-MapAndSum
R-251 Unclustered 2 New Unclassified Dave Peterson Unassigned 2E PER: Probable editorial problem, mix/maxExclusive facets
R-252 Unclustered 1 New Unclassified Henry S. Thompson Unassigned Final/block, transitivity and restriction
R-253 Unclustered 1 New Unclassified Henry S. Thompson, Noah Mendelsohn Unassigned Failure of schemaLocation to resolve for redefine
R-254 Unclustered 2 New Unclassified Xan Gregg Unassigned Clarify merge/union of facets
R-255 Unclustered 2 New Unclassified Xan Gregg Unassigned Value of pattern facet
R-256 Unclustered 1 New Unclassified Michael Kay Unassigned 2E PER: Attribute wildcards numbering problem
R-257 Unclustered 2 New Unclassified XML Schema WG Health warning needed about percent-escaping URIs
R-258 Unclustered 2 New Unclassified Sandy Gao Need to resolve contradiction regarding inclusive and exclusive bounds
R-259 Unclustered 2 New Unclassified Mary Holstege and XML Schema WG Are QNames without prefix bindings type-valid?

R-1. pfiComparingDurations: Problem with dateTime values in 3.2.6.2

Classification: Error w/erratum
Part: 2 (Datatypes)
Status: Errata drafting
Originator: Henry Zongaro

Description

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

There are problems comparing certain durations because of the choice of dateTime values listed in section 3.2.6.2 of the DataTypes spec. The problem arises out of the fact that there is no century year that is a leapyear between 399 BC and AD 399.

Resolution

Discussed again at the Feb. 12, 2004 telecon. See: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Feb/0066.html

Resolved to issue an erratum against 2e noting that algorithm is wrong and will be fixed next time (add requirement against 1.1)



R-2. pfiPrimerNumFacets: Primer states that there are 15 facets

Classification: Editorial
Part: 0 (Primer)
Status: Closed
Originator: Dan Glickman

Description

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

The Schema Primer states "XML Schema defines fifteen facets which are listed in Appendix B", but there are only 12 facets.

Resolution

An erratum will be added to the errata document indicating that there are twelve facets.

Erratum number is: E0-1.



R-3. pfiPrimerRestriction: Primer states that all components must be repeated in restriction

Classification: Clarification w/erratum
Part: 0 (Primer)
Status: Closed
Originator: Eddie Robertsson

Description

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

The Primer states: "Notice that types derived by restriction must repeat all the components of the base type definition that are to be included in the derived type". However, this is not true of attributes.

Resolution

An erratum will be added to the errata document indicating that only particle components need to be repeated.

Erratum E0-21 added.



R-4. pfiPrimerNormative: Conflicting statements about Primer being normative/non-normative

Classification: Editorial
Part: 0 (Primer)
Status: Closed
Originator: Donald Gignac

Description

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

The introduction of the Primer indicates that the Primer is non-normative, but the status section indicates it may be cited as a normative reference.

Resolution

An erratum will be added indicating that the text in the Status section be modified to remove any statement that the Primer may be referenced normatively.

Erratum number is: E0-2.



R-5. pfiPrimerTypo2.8: Typographical error in section 2.8 example

Classification: Editorial
Part: 0 (Primer)
Status: Closed
Originator: Donald Gignac

Description

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

In the example in section 2.8, the element name should be "item", for consistency with preceding text, and previous examples.

Resolution

An erratum will be added as proposed above.

Erratum E0-19 added.



R-6. pfiPrimerTable4.4: Confusing table in the Primer

Classification: Editorial
Part: 0 (Primer)
Status: Closed
Originator: Donald Gignac

Description

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

Various suggestions are made to improve the usability of the table in section 4.4.

Discussion

Martin will investigate possible ways to improve the format of the table. Also, the last entry of the table should probably indicate that a minOccurs, maxOccurs pair of (1,1) is a valid restriction of (1,1).

Resolution

Erratum E0-20 added.



R-7. pfiRuntimeTypes: Request for runtime parameterization of types

Classification: Future Requirement
Part:
Status: Closed
Originator: Uwe Zeise

Description

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

Henry's response: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001AprJun/0178.html

Resolution

This requirement will be passed to the Requirements Task Force to handle, and include in the requirements document.



R-8. pfiFinalDefault: Should finalDefault allow list, union?

Classification: Error
Part: 1 (Structures)
Status: Errata Drafting
Originator: Martin Gudgin

Description

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

Part 2 implies they are allowed, but Structures does not.

Discussion

Henry's response http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001AprJun/0284.html

Resolution

An erratum will be added that lists the Structures spec changes needed to reflect the additional valid finalDefault values.



R-9. pfiallGroup: minOccurs=0 on "all"

Classification: Clarification w/erratum
Part: 1 (Structures)
Status: Closed
Originator: Henry Zongaro

Description

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

Section 3.8.2 permits minOccurs=0 on an "all" element, but 3.7.2 and 3.8.6 (Schema Component Constraint: All Group Limited) prohibit the value from being zero for all uses.

Resolution

It was the intention that minOccurs=0 should be permitted on an "all" element. Erratum item E1-2 has been created in the Errata doc.



R-10. pfiBounded: Definition of bounded

Classification: Editorial
Part: 2 (Datatypes)
Status: Closed
Originator: John G. de Freitas

Description

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

The Datatypes spec states: "A datatype is bounded if its value space has either an inclusive upper bound or an exclusive upper bound and either an inclusive lower bound and an exclusive lower bound." Shouldn't the last "and" be "or"?

Resolution

An erratum will be added that reflects the proposed change.

Erratum number is: E2-3.



R-11. pfiUnionTypo: Editorial error in section 4.1.2.3

Classification: Editorial
Part: 2 (Datatypes)
Status: Closed
Originator: Donald Gignac

Description

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

Section 4.1.2.3, definition of {member type definitions} states: "If {variety} is union for any Simple Type Definition components resolved to above, then the that Simple Type Definition is replaced by its {member type definitions}. "

Resolution

An erratum will be added that corrects the grammatical error.

Erratum number is: E2-1.



R-12. pfifinalTypo: Editorial error in section 4.1.2

Classification: Editorial
Part: 2 (Datatypes)
Status: Closed
Originator: Donald Gignac

Description

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

Section 4.1.2, definition of {final} states:

"A set corresponding to the actual value of the final [attribute], if present, otherwise of the actual value of the finalDefault [attribute] the ancestor schema element information item, if present, otherwise the empty string, as follows: ". Shouldn't "of" be intserted in front of "the ancestor"?

Resolution

An erratum will be added that corrects the grammatical error. The "of" in "of the finalDefault" should be moved before "the ancestor".

Erratum number is: E2-4.



R-13. pfihexBinaryTypo: Typographical error in title of section 3.2.15.2

Classification: Editorial
Part: 2 (Datatypes)
Status: Closed
Originator: Eliotte Harold

Description

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

The title is "Canonical Rrepresentation".

Resolution

The spelling mistake will be corrected in an erratum.

Erratum number is: E2-2.



R-14. pfidateTimeTypo: Typographical error in section 3.2.7.1

Classification: Editorial
Part: 2 (Datatypes)
Status: Closed
Originator: Panagiotis Reveliotis

Description

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

The pargraph beginning with "The CCYY field..." should be changed to: "The CCYY field must have at least four digits, the MM, DD, hh, mm and ss fields exactly two digits each (not counting fractional seconds); leading zeroes must be used if the field would otherwise have too few digits."

Resolution

An erratum will be added which corrects this typographical error.

Erratum number is: E2-5.



R-15. pfiordered: Error in definition of ordered Schema Component

Classification: Error
Part: 2 (Datatypes)
Status: Closed
Originator: Panagiotis Reveliotis

Description

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

Section 4.2.2.1 states: "When {variety} is union, if {value} is true for every member of {member type definitions} and all members of {member type definitions} share a common ancestor, then {value} is true; else {value} is false." But, {value} can be "partial" or "total" but not "true".

Resolution

An erratum will be added to correct this text.



R-16. pfianyURITypo: Typographical error ("fragement") in section 3.2.17

Classification: Editorial
Part: 2 (Datatypes)
Status: Closed
Originator: Eliotte Harold

Description

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

"fragement" should be "fragment".

Erratum number is: E2-6.

Resolution

An erratum will be added correctly this spelling mistake.



R-17. pfibase64: base64 and linebreaks every 76 characters

Classification: Clarification w/erratum
Part: 2 (Datatypes)
Status: Closed
Originator: Martin Duerst

Description

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

Resolution

The WG has decided the following:

  1. The base64Binary type has no line length restriction on its lexical forms. So it's not a type error if the value contains (for example) 800 characters without any newline sequence.
  2. The lexical form of base64Binary data can contain any of the 65 characters in the "Base64 Alphabet", plus any characters recognized by the XML spec as whitespace. occur.
  3. An erratum will be created to clarify these rules and illustrate the grammar for the lexical and canonical forms of the datatype.

See item E2-9 in the Errata doc.



R-18. pfipattern: Use of pattern facet for list type

Classification: Clarification/ Error
Part: 0,2 (Primer, Datatypes)
Status: Closed
Originator: Alexander Falk

Description

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

A request for the clarification of how the pattern facet works for list datatypes. Also, the NMTOKENS, IDREFS and ENTITIES types do not list pattern as an acceptable facet.

Resolution

An erratum will be created to clarify the semantics of pattern for lists (the pattern applies to the whole list). The erratum will also add the pattern facet to the datatypes listed.

Issue also affects Primer - Erratum E0-18 added for Primer.

Proposed datatypes text: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0234.html

Reviewed and approved, with ammendments, at Oct. 25 concall.

Erratum E2-30 added.



R-19. pfigroup: group element info item missing attributes

Classification: Error
Part: 1 (Structures)
Status: Closed
Originator: Panagiotis Reveliotis

Description

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

The XML representation for the group element information item, in section 3.7.2, is missing the attributes "ref", "minOccurs", "maxOccurs".

Resolution

An erratum, E1-3, has been created to correct this.



R-20. pfitypeExampleTypo: Typographical error in section 3.4.2 example

Classification: Editorial
Part: 1 (Structures)
Status: Closed
Originator: Panagiotis Reveliotis

Description

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

In the example in section 3.4.2 of Structures, the references to types "xs:nonPositiveInteger" and "xs:non-positive-integer" should both be "xs:nonNegativeInteger".

Resolution

An erratum will be added to correct this.



R-21. pfiListitemType: Clarification required re: list itemType

Classification: Clarification w/Erratum
Part: 2 (Datatypes)
Status: Closed
Originator: Panagiotis Reveliotis

Description

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

Is the itemType of a list meant to be of "atomic" type ONLY or of EITHER "atomic" OR "union" type? Sections 2.5.1.2 and 4.1.2.2 of Datatypes appear to be contradictory.

Resolution

It was intended that the itemType be either atomic or union. An erratum will be added to clarify this.



R-22. pfiFloat: Floating Point Issues and IEEE

Classification: Error
Part: 2 (Datatypes)
Status: Closed
Originator: Ashok Malhotra

Description

The datatypes spec has some inconsistencies with IEEE with respect to certain special values (such as NaNs). Should it be modified to reflect IEEE semantics?

See http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001May/0030.html

Discussion

A straw poll was held for the following questions:

The results of the poll were summarized in the following meeting minutes: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Jul/0014.html

No firm decisions made to date.

Status 2002/01: Dave P. and Ashok Malhotra have proposed the following resolution/text: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Jan/0066.html

Further discussion: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Jan/0101.html

Resolution

The WG resolved that this should be classified as an error, and the editors are to prepare final wording for an erratum that reflects the decisions made at the 02/01 telecon: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Feb/0009.html

Proposed erratum text reviewed at the March 28 telecon. The WG noted a possible contradiction in the definition of zero in the erratum for R-22 with our decision on R-97 and concluded that this erratum text is not yet ready, and instructed the editors to deal with R-22 and R-97 in the same erratum.

Status 04/24: New erratum text proposed: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Mar/0131.html

Status 05/02: Revised text approved.

Erratum E2-40 added.



R-23. pfiattrRestrict: Restrictions of attributes specifying "use"

Classification: Clarification
Part: 1 (Structures)
Status: Closed
Originator: Mark Huffman

Description

The constraints listed for "derivation-ok-restriction" do not appear to prohibit the following: 

<xsd:complexType name="baseType">
     <xsd:attribute name="attrib1" type="xsd:string" use="prohibited"/>
<xsd:complexType>

<xsd:complexType name="restrictedType">
     <xsd:complexContent>
          <xsd:restriction base="baseType">
               <xsd:attribute name="attrib1" type="xsd:string" use="required"/>
          </xsd:restriction>
     </xsd:complexContent>
</xsd:complexType>

Shouldn't this be disallowed, since instances of the restricted type are not valid instances of the base?

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

Resolution

This restriction is already disallowed by the Structures spec. In the base type, there is no component for the attribute because of the use="prohibited". Given this, clause 2.2 of Schema Component Constraint: Derivation Valid (Restriction, Complex) applies and causes this example to be invalid.

No erratum is required.



R-24. pfipointless: Derivation by Restriction: pointless occurrences

Classification: Future requirement
Part: 1 (Structures)
Status: Closed
Originator: Yan Leshinsky

Description

The constraints for "Particle Valid (Restriction)" indicate that pointless occurrences of sequence, all and choice should be ignored. By doing so, it is possible that certain derived types which would otherwise be valid restrictions of their base types, become invalid.

See the following for more information, and an example: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001AprJun/0230.html

Note that Achille Fokoue posted another example illustrating this problem. See the following for more information: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JulSep/0111.html

Note also that a subsequent email on pointlessness was sent in by Gareth Sylvester-Bradley: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2003JulSep/0040.html

Discussion

The WG has discussed various solutions:

Resolution

The WG has decided that although the rules have some awkward results, they are not in error. It will be put on the list of issues to consider for a future revision of XML Schema.



R-25. pfifixedValidity: Element locally valid: fixed value constraints

Classification: Error w/erratum
Part: 1 (Structures)
Status: Errata Drafting
Originator: Satoshi Nakamura

Description

Clause 5.2.2.2 of "Validation Rule: Element Locally Valid (Element)" refers to {content type} in both of its sub-bullets. However, "content type" is defined for complex types only, and the element may have simple type. Should an editorial change be made to correct this?

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

Resolution

Discussed at the May 29,2003 telecon.

RESOLVED: classify R-25 as error with erratum

RESOLVED: ask editor to draft a fix to qualify existing cases with "if the actual type definition is complex" and add a new case for "simple"



R-26. pfiPSVITypos: Two typos in section 3.3.5 of Structures

Classification: Editorial
Part: 1 (Structures)
Status: Closed
Originator: C. M. Sperberg-McQueen

Description

In section 3.3.5, under the heading Schema Information Set Contribution: Assessment Outcome (Element), in the box labeled "PSVI Contributions for element information items", in item 1.1.3 for "unknown" read "notKnown".

In section 3.3.5, under the heading Schema Information Set Contribution: Element Validated by Type, in the second box of PSVI Contributions for element information items, for "simple thype definition" read "simple type definition".

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

Resolution

Proposed text, available at: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Aug/0005.html approved at Sept. 13 concall.

Erratum E1-12 added



R-27. pfiPrimerInfo: Request for additional information in the Primer

Classification: Doc Suggestion
Part: 0 (Primer)
Status: Closed
Originator: Doug Bunting

Description

This is a request for additional information in the Primer in the following areas:

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

Resolution

This documentation suggestion will be considered by the WG for a future revision of the specification.



R-28. pfiElemValidType: Element locally valid (type): rule about "abstract"

Classification: Error
Part: 1 (Structures)
Status: Closed
Originator: Satoshi Nakamura

Description

In the Structures spec, section 3.3.4 Element Locally Valid (Type), bullet 2 states:

"2 Its {abstract} must be false."

However, the type is not necessarily complex, and "abstract" is not a property of simple types.

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

Discussion

Discussed at the Apr. 26 telecon: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Apr/0084.html.

Resolution

The WG resolved to classify R-28 as an error and instruct the editor to draft an erratum, saying that the type in question may not have {abstract} = true, rather than saying it must have {abstract} = false)

Proposed text, available at: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Aug/0005.html approved at Sept. 13 concall.

Erratum E1-13 added



R-29. pfiDatatypesComments: Remove request for comments from Datatypes

Classification: Editorial
Part: 2 (Datatypes)
Status: Closed
Originator: Martin Duerst

Description

The Datatypes spec has a request for comments in the appendix describing regular expressions. Should this be removed?

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

Resolution

Proposed text: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0235.html

Discussed and approved at Oct. 24 telecon.

Erratum E2-31 added.



R-30. pfiregexXmlCharRef: Request for clarification of regex notation

Classification: Error
Part: 2 (Datatypes)
Status: Closed
Originator: Martin Duerst

Description

This is a request for clarification of the semantics of "XmlCharRef" in regular expressions.

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

Resolution

The WG agreed that the commentator is correct, and that the production for character reference should not be in the grammar.

Alexander Falk proposed the grammar change as part of mail http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Sep/0044.html.

Erratum item E2-18 was revised to incorporate this change.



R-31. pfianyURI: anyURI and xml:base

Classification: Clarification w/Erratum
Part: 2 (Datatypes)
Status: Closed
Originator: James Clark

Description

In the value space of anyURI, are URIs supposed to be absolutized using xml:base?

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

Resolution

The WG has agreed that URIs are not to be absolutized.

An erratum, E2-11, has been created that results in changes to 3.2.17 and the bibliographic reference, specifying that we refer normatively only to section 5.4, paragraph 3 of XLink.



R-32. pfipublic: Type of public attribute of notation

Classification: Unclassified
Part: 1 (Structures)
Status: Closed
Originator: Jeff Rafter

Description

The "XML Representation Summary" for notation indicates that the public identifier has a value of type anyURI. But the schema for schemas indicates that the public identifier is of a type derived from token.

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

Discussion

Discussed briefly at a telecon in 09/2001: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Sep/0017.html.

The WG decided it needed more preparation to determine the answer.

Resolution

Change made as part of erratum E1-16



R-33. pfiIdConstraint: Request for clarification of identity constraint rules

Classification: Clarification/Error
Part: 0,1 (Primer, Structures)
Status: Closed
Originator: Neil Graham

Description

Bullet 4.3 of section "Validation Rule: Identity-constraint Satisfied" states:

"If the {identity-constraint category} is keyref, then for each member of the qualified node set (call this the keyref member), there must be a node table associated with the {referenced key} in the [identity-constraint table] of the element information item (see Identity-constraint Table, which must be understood as logically prior to this clause of this constraint, below) and there must be an entry in that table whose key-sequence is equal to the keyref member's key-sequence member for member, as defined by Equal in [XML Schemas: Datatypes]."

Does this mean that the identity constraint referenced by the keyref must apply to the element the keyref is on or to one of its descendants, or may the identity constraint referenced by the keyref appear anywhere at all in the instance document?

If the former, the Primer contains an invalid example. Either way, this rule should be clarified.

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

Discussion

Henry's response: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001AprJun/0279.html

Resolution

The WG decided that the Structures spec needs a clarification of this constraint, and that the Primer has an example that is invalid. The commentator's interpretation is correct, namely, that the key or unique identity constraint to which a keyref refers must be within the scope of the element the keyref is on.

Erratum E0-22 added for Primer.

Structures erratum http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0313.html reviewed and approved at the Nov. 1 telecon.

Structures erratum E1-19 added



R-34. pfisimpleTypefinal: Potential problem with description of final for simpleType in Structures

Classification: Error
Part: 1 (Structures)
Status: Closed
Originator: Choi Jongwon

Description

Section 3.14.6 of Structures states the following for bullet 4:

If the {base type definition} is not the simple ur-type definition, all of the following must be true:

4.1 The definition must be a valid restriction as defined in Derivation Valid (Restriction, Simple).

4.2 If {variety} is not atomic, then the appropriate case among the following must be true:

However, lists and unions have the ur-type definition as a base.

And, shouldn't the following rules be stated?

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

Discussion

Henry's response: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001AprJun/0296.html

Resolution

The WG determined that the commentator is correct, and bullet 4 of Section 3.14.6 of Structures need to be modified to include the following rules:

Proposed text (E1-15) available at: http://www.w3.org/XML/Group/2002/09/xmlschema-1/structures-with-errata.html#coss-st

Revised text : http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Sep/att-0224/01-e1-15.html reviewed and approved at Oct. 3 telecon.

Erratum E1-22 added



R-35. pficharClassambig: Regular expression grammar for charClass is ambiguous

Classification: Error
Part: 2 (Datatypes)
Status: Closed
Originator: Satoshi Nakamura

Description

Productions [22] and [37] may cause the grammar to be ambiguous.

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

Discussion

There is an ambiguity. An erratum will be created to fix the problem.

Resolution

Erratum item E2-10 has been created.



R-36. pfiPrimerTextfont: Font of text in section 2.5.2 of Primer incorrect

Classification: Editorial
Part: 0 (Primer)
Status: Closed
Originator: Jason Stallion

Description

In section 2.5.2 of the Primer, the word "name" in the sentence beginning "Specifically, text appears between the elements..." should be rendered in monospaced font.

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

Resolution

Erratum E0-17 added.



R-37. pfiISO8601link: The link to ISO 8601 in the Datatypes spec doesn't work

Classification: Editorial
Part: 2 (Datatypes)
Status: Closed
Originator: Tony Coates

Description

The link "http://www.iso.ch/markete/8601.pdf" in the datatypes spec does not work.

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

Resolution

Erratum E2-42 added.



R-38. pfifractionDigits: Missing constraint for fractionDigits?

Classification: Clarification w/Erratum
Part: 2 (Datatypes)
Status: Closed
Originator: Kevin Yancey

Description

Is there a constraint missing for fractionDigits, indicating that the value in a restriction must be less than or equal to any such value in a base type definition?

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

Discussion

The WG has concluded that a constraint needs to be added, but the case where the base type does not specify a value needs to be examined. Paul Biron to review all constraints of this kind to ensure they make sense when the base type does not have a value, and to provide wording to handle such cases.

Resolution

Initial erratum for this particular case has been proposed:

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

PVB determined that no further errata was required.



R-39. pfiDTDforSchema: Error in the DTD for Schemas in Structures spec

Classification: Error
Part: 1 (Structures)
Status: Closed
Originator: Paul V. Biron

Description

The DTD for Schemas is missing the optional annotation child of extension.

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

Discussion

Paul also pointed out that the same problem occurs for simpleContent and complexContent.

Resolution

The WG agreed that the DTD for Schemas should be modified to include an optional annotation child for extension, simpleContent and complexContent.

Erratum item E1-4 has been created.



R-40. pfiregex: Clarification of the regex language in Datatypes

Classification: Clarification w/Erratum
Part: 2 (Datatypes)
Status: Closed
Originator: Paul V. Biron

Description

A request to add text to the appendix for regular expressions to clarify the matching algorithm and to indicate that implicit anchoring occurs for patterns.

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

Resolution

The WG agreed with the commentator that such a clarification should be made.

Final proposed text: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0243.html reviewed/approved at Oct. 24 telecon.

Erratum E2-32 added.



R-41. pfiregexProd10: Error in production 10 of regex in Datatypes

Classification: Error
Part: 2 (Datatypes)
Status: Errata Proposed
Originator: Paul V. Biron

Description

Production 10 should be modified to consider brace brackets as metacharacters.

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

Resolution

The WG agreed that the grammar should be modified as per the description above.

Alexander Falk proposed the grammar changes in message http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Sep/0044.html.



R-42. pfichoicechoice: Potential problem with particle derivation Choice:Choice rules

Classification: Future Requirement
Part: 1 (Structures)
Status: Closed
Originator: Achille Fokoue

Description

The particle derivation rules for "RecurseLax" appear to prohibit the following type derivation. Was this intentional, or should the rules be modified to permit such a derivation? The mail below suggests a possible modification of the rules.

<xs:complexType name="B">
 <xs:choice minOccurs="1" maxOccurs="1">
  <xs:group minOccurs="0" maxOccurs="1" ref="ChoiceGroup"/>
  <xs:element name="e"/>
 </xs:choice>
</xs:complexType>

<xs:complexType name="derived">
 <xs:complexContent>
  <xs:restriction base="xs:B">
   <xs:group minOccurs="0" maxOccurs="1" ref="ChoiceGroup"/>
  </xs:restriction>
 </xs:complexContent>
</xs:complexType>

<xs:group name="ChoiceGroup">
 <xs:choice>
  <xs:element name="e2"/>
  <xs:element name="e3"/>
 </xs:choice>
</xs:group>

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

Resolution

As per issue R-24, the WG has decided that although the rules have some awkward results, they are not in error. The issue will be added to a list of items to consider for a future revision of XML Schema.



R-43. pfiPrimerTable1: Imprecise text in Table 1 of Primer

Classification: Unclassified
Part: 0 (Primer)
Status: Closed
Originator: Donald Gignac

Description

Table 1 of the Primer shows some examples that contain default values for elements/attributes. The text in the "Notes" column should reflect the different semantics that occur for elements/attributes; as currently written, it could be misinterpreted.

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

Also see: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001OctDec/0114.html

Resolution

Proposed erratum available at: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Aug/0010.html

Text approved as ammended at Sept. 13 concall.

Erratum E0-29 added.



R-44. pfiPrimerSchemaLoc: Grammatical errors in section 5.6 of the Primer

Classification: Editorial
Part: 0 (Primer)
Status: Closed
Originator: Donald Gignac

Description

In the paragraph following the first example of section 5.6 of the Primer, "... where to find to an appropriate ..." should be "... where to find an appropriate ...". Also, the commentator suggests a rewording of the description of the schemaLocation attribute.

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

Resolution

Proposed erratum available at: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Aug/0010.html

Text approved at Sept. 13 concall.

Erratum E0-28 added.



R-45. pfiPrimerHTMLRef: Inaccurate language in section 5.5 of Primer re: references to HTML

Classification: Editorial
Part: 0 (Primer)
Status: Closed
Originator: Donald Gignac

Description

In Section 5.5 of the Primer, references to "HTML" should be "XHTML".

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

Resolution

Erratum E0-16 added.



R-46. pfiIdConstrAnnot: Minor inconsistency in definition of Identity Constraints

Classification: Error, Future Requirement
Part: 1 (Structures)
Status: Closed
Originator: Mary Holstege

Description

Section 3.11.1 of Structures, the schema component definition for identity constraints states that {fields} is a list of restricted XPath expressions, and that {selector} is a restricted XPath expression.

Section 3.11.2, the XML representation for <field> and <selector> allows an <annotation>. There is no schema component to which this annotation can adhere.

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

Discussion

Tentative resolution: http://www.w3.org/XML/Group/2001/10/xml-schema-ftf-minutes#ab1b3b3b3b1b2

Resolution

An erratum will be created specifying promotion, and the issue will be included in the candidate list of items to consider for 1.1

Proposed erratum, included in the following http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Aug/0005.html was approved at the Sept. 13 concall.

Erratum E1-14 added



R-47. pfiRestrictEmpty: Request for clarification of complex type derivation restriction rules for empty base

Classification: Clarification w/erratum
Part: 1 (Structures)
Status: Closed
Originator: Henry Zongaro

Description

Constraint 5.3 of "Schema Component Constraint: Derivation Valid (Restriction, Complex)" states:

"5.3 If the {content type} of the {base type definition} is mixed or the {content type} of the complex type definition itself is element-only, then the particle of the complex type definition itself must be a valid restriction of the particle of the {content type} of the {base type definition} as defined in Particle Valid (Restriction)."

Does the use of the definite article in the phrase "the particle of the {content type} of the {base type definition}" imply that the {content type} must have a particle, and must not be empty? If not, what prohobits the following:

  <xs:complexType name="rrr" />
  <xs:complexType name="sss">
    <xs:complexContent>
      <xs:restriction base="rrr">
        <xs:sequence>
          <xs:element name="dummy"/>
        </xs:sequence>
      </xs:restriction>
    </xs:complexContent>
  </xs:complexType>

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

Discussion

Tentative resolution: http://www.w3.org/XML/Group/2001/10/xml-schema-ftf-minutes#ab1b3b3b3b1b3

Resolution

The WG approved the tentative resolution above. An erratum will be created clarifying that the example is in error not because of constraint 5.3, but because of failure to match particles in one against the other.

Proposed erratum available at: http://www.w3.org/XML/Group/2002/09/xmlschema-1/structures-with-errata.html#derivation-ok-restriction

Sept. 20: RESOLVED: to accept E1-17 as amended (s/from a/by restricting a/).

Erratum E1-15 added.



R-48. pfiLexgMonth: Lexical representation of gMonth is inconsistent wrt ISO 8601

Classification: Error
Part: 0,2 (Primer, Datatypes)
Status: Closed
Originator: Henry Zongaro

Description

There appears to be a discrepancy between the lexical representation of gMonth in the "XML Schema: Datatypes" recommendation and the truncated representation of a month described in 5.2.1.3 of ISO 8601:1988. The former indicates that the lexical representation is "--MM--", while the latter specifies the truncated representation as "--MM".

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

Resolution

The WG has agreed this is an error.

Errata E0-15 and E2-12 added.



R-49. pfiYr0000: ISO 8601:2000 defines 0000 as a valid year

Classification: Unclassified
Part: 2 (Datatypes)
Status: In progress
Originator: Henry Zongaro

Description

ISO 8601:2000 defines 0000 to be a valid year, unlike the specification of dateTime in the "XML Schema: Datatypes" recommendation. Should dateTime follow ISO 8601:2000 in this respect?

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

Discussion

See:

http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JulSep/0098.html

http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JulSep/0100.html

http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JulSep/0101.html

Recent discussion: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002AprJun/0042.html



R-50. pfiappInfo: "appInfo" element in Primer vs. "appinfo" element in Structures

Classification: Error
Part: 0 (Primer)
Status: Closed
Originator: Scott Means

Description

The Primer shows the application information element as <appInfo> while Structures defines it as <appinfo>.

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

Discussion

Tentative resolution: http://www.w3.org/XML/Group/2001/10/xml-schema-ftf-minutes#ab1b3b3b3b1b4

Resolution

The Structures spec is correct. The editor will create an erratum for the Primer.

Erratum E0-14 added.



R-51. pfiPrimer2.3: Inaccurate text in section 2.3 of the Primer

Classification: Clarification
Part: 0 (Primer)
Status: Closed
Originator: Mark Hurley

Description

Section 2.3 of the Primer, paragraph 3 states:

"Suppose we wish to create a new type of integer called myInteger whose range of values is between 10000 and 99999 (inclusive). We base our definition on the built-in simple type integer, whose range of values also includes integers less than 10000 and greater than 99999."

The second sentence should read:

"We base our definition on the built-in simple type integer, whose range of values also includes integers greater than or equal to 10000 and less than or equal to 99999."

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

Resolution

The commentator misunderstood; the Primer is correct.



R-52. pfiCircularAttrGrp: Missing constraint for indirect circular attribute group?

Classification: Error
Part: 1 (Structures)
Status: Closed
Originator: Sandy Gao

Description

Constraint 3 of "Schema Representation Constraint: Attribute Group Definition Representation OK" prohibits direct circular attribute group references, but doesn't appear to prohibit indirect circular references.

See Issue 1 from the following mail: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JulSep/0121.html

Discussion

Tentative resolution: http://www.w3.org/XML/Group/2001/10/xml-schema-ftf-minutes#ab1b3b3b3b1b5

Resolution

The WG resolved that the constraint (at the component level) needs to be added. Erratum pending.

Proposed text: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0184.html reviewed and approved at Oct. 11 telecon.

Erratum E1-20 added



R-53. pfiInclude: Request for clarification of include

Classification: Clarification
Part: 1 (Structures)
Status: Closed
Originator: Sandy Gao

Description

Assuming schema document A includes schema documents B and C, where B has the same target namespace as A, and C has no target namespace. Which components may be referenced from any given component in A, B or C?

In particular, given the following table (where R(A,B)=Y means components in A may refer to components in B), what should the table entries be for any marked "?".

R A B C
A Y Y Y
B ? Y ?
C ? ? Y

From the spec, it ap