This is not the errata document for the initial editon of XML Schema 1.0 published on 2 May 2001 -- that document is still available, but all the corrections recorded there have been incorporated into the proposed second edition of the W3C XML Schema Recommendation.
Comments on either edition should be sent to www-xml-schema-comments@w3.org (archive at http://lists.w3.org/Archives/Public/www-xml-schema-comments/).
IntroductionThis document records known errors in the XML Schema 1.0 Second Edition for which the XML Schema WG has approved fixes.
The errata are separated into 3 sections, corresponding to the 3 sections of the specification:
Errata for each part are numbered separately. Errata for Part 0 are numbered with a prefix beginning with "E0-", errata for Part 1 are identified by "E1-", and errata for Part 2 are numbered with "E2-". The errata within each section are classified as Error, Editorial or Clarification and listed in reverse chronological order of their date of publication. Three kinds of changes are highlighted: ↑new, added text↑, ↑changed text↑, and ↓deleted text↓.
Errata for Part 0 (Primer)None so far.
Errata for Part 1 (Structures) E1-56 ErrorThis change eliminates a contradiction in the XSD 1.0 specification concerning the interaction of default values for elements with complex types and the [schema normalized value] property of the post-schema-validation information set (PSVI). Informally: when the element has no content, its [schema normalized value] (if it has one) is supplied from the default value specified for the element's type, but character information items are not added to the element in the PSVI.
See Bugzilla entries 2632 Default value and [schema normalized value] and 6836 Default value and [schema normalized value] (for XSD 1.1 and 1.0 respectively).
This issue also affects the XDM Data Model and related specifications; see Bugzilla entry 2630 [DM] Default values of elements.
Revise the following sections as shown:
In Schema Information Set Contribution: Attribute Validated by Type, revise the description of [schema normalized value] as follows:
In the paragraph preceding the description of [member type definition namespace] etc., revise the text as follows.
Revise the seventh paragraph as shown:
{value constraint} establishes a default or fixed value for an element. If default is specified, and if the element being ·validated· is empty, then ↓the canonical form of the supplied constraint value becomes the [schema normalized value] of the ·validated· element in the ·post-schema-validation infoset·.↓ ↑for purposes of calculating the [schema normalized value] and other contributions to the ·post-schema-validation infoset· the element is treated as if the {value constraint}'s {lexical form} was used as the content of the element.↑ If fixed is specified, then the element's content must either be empty, in which case fixed behaves as default, or its value must match the supplied constraint value.
After the seventh paragraph, insert the following note:
↑
Note:When a default value is supplied and used, as described in the second sentence of the preceding paragraph, the default value is used to calculate the
[schema normalized value], etc., but the actual content of the element is not changed: the element contained no character information items in the input information set, and it contains none in the PSVI.
Also, as specified in its definition the
[schema normalized value]property is available only for elements whose governing type definition defines a simple type or a complex type with simple content; in the case of an element with mixed content, a default value can be specified but is not directly exposed in the
·post-schema-validation infoset·. (It can be found by examining the
[schema default]property of the element item; the default is applicable when the item's
[schema specified]property has the value
schema.)
↑
Revise the description of [schema normalized value] as follows:
In the paragraph preceding the description of [member type definition namespace] etc., revise the text as follows.
Revise the description of [schema specified] as follows.
None to date.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4