ISO/IEC 9075-14:2003/Cor 1:2005

Information technology — Database languages — SQL — Part 14: XML-Related Specifications (SQL/XML) — Technical Corrigendum 1

Technologies de l'information — Langages de base de données — SQL — Partie 14: Spécifications relatives au XML (SQL/XML) — Rectificatif technique 1

General Information

• Status: Withdrawn
• Publication Date: 24-Nov-2005
• Withdrawal Date: 24-Nov-2005
• ICS: 35.060 - Languages used in information technology
• Technical Committee: ISO/IEC JTC 1/SC 32 - Data management and interchange
• Drafting Committee: ISO/IEC JTC 1/SC 32/WG 3 - Database language
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 12-Jun-2006

Relations

• Revised: ISO/IEC 9075-14:2006 - Information technology — Database languages — SQL — Part 14: XML-Related Specifications (SQL/XML)
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTERNATIONAL STANDARD ISO/IEC 9075-14:2003
TECHNICAL CORRIGENDUM 1
Published 2005-11-15
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE


Information technology — Database languages — SQL —
Part 14:
XML-Related Specifications (SQL/XML)
TECHNICAL CORRIGENDUM 1
Technologies de l'information — Langages de base de données — SQL —
Partie 14: Spécifications relatives au XML (SQL/XML)
RECTIFICATIF TECHNIQUE 1
Technical Corrigendum 1 to ISO/IEC 9075-14:2003 was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange.

Statement of purpose for rationale
A statement indicating the rationale for each change to ISO/IEC 9075-14:2003 is included. This is to inform the users of
ISO/IEC 9075-14:2003 why it was judged necessary to change the original wording. In many cases, the reason is editorial
or to clarify the wording; in some cases, it is to correct an error or an omission in the original wording.
Notes on numbering
Where this Technical Corrigendum introduces new Syntax, Access, General, and Conformance Rules, the new rules
have been numbered as follows:
Rules inserted between, for example, Rules 7) and 8) are numbered 7.1), 7.2), etc. [or 7)a.1), 7)a.2), etc.]. Those
inserted before Rule 1) are numbered 0.1), 0.2, etc.
Where this Technical Corrigendum introduces new subclauses, the new subclauses have been numbered as follows:
Subclauses inserted between, for example, 4.3.2 and 4.3.3 are numbered 4.3.2a, 4.3.2b, etc. Those inserted before,
for example, 4.3.1 are numbered 4.3.0, 4.3.0a, etc.
ICS 35.060 Ref. No. ISO/IEC 9075-14:2003/Cor.1:2005(E)
©  ISO/IEC 2005 – All rights reserved
Published in Switzerland

---------------------- Page: 1 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
ii ©  ISO/IEC 2005 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
Contents Page
Foreword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4 Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4.2 XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4.2.3 Operations involving XML values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4.3 Data analysis operations (involving tables). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4.3.1 Aggregate functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
4.8 Overview of mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4.8.3 Mapping SQL data types to XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4.8.4 Mapping SQL data types to XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4.8.5 Visibility of columns, tables, and schemas in mappings from SQL to XML . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4.8.6 Mapping an SQL table to XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.8.7 Mapping an SQL schema to XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.8.8 Mapping an SQL catalog to XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.8.10 Mapping XML Names to SQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6 Scalar expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8 Predicates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
9 Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.4 Mapping an SQL schema to an XML document and an XML Schema document . . . . . . . . . . . . . . . . . . . . . . 9
9.5 Mapping an SQL catalog to an XML document and an XML Schema document . . . . . . . . . . . . . . . . . . . . . 10
9.6 Mapping an SQL table to XML Schema data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.7 Mapping an SQL schema to XML Schema data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.12 Mapping an SQL table to an XML element or an XML forest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.15 Mapping SQL data types to XML Schema data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.16 Mapping values of SQL data types to values of XML Schema data types . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.17 Mapping XML Names to SQL s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
10 Additional common rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.3 Determination of identical values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.8 Determination of [namespace name] property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.9 Determination of [namespace attributes] property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.10 Determination of the [in-scope namespaces] property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
©  ISO/IEC 2005 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
10.11 Determination of [whitespace element content] property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
10.13 Serialization of an XML value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
10.14 Parsing a character string as an XML value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
10.15 Retrieval assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
10.16 Store assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
11 Additional common elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
11.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
18 Embedded SQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
18.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Annex B Implementation-defined elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
iv ©  ISO/IEC 2005 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
Tables
Table Page
1.1 Constraining facets of XML Schema integer types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
©  ISO/IEC 2005 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
vi ©  ISO/IEC 2005 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
Information technology — Database languages — SQL —
Part 14:
XML-Related Specifications (SQL/XML)
TECHNICAL CORRIGENDUM 1
Foreword
1. Rationale:Remove incorrect reference to obsolete part.
th th
In the 6 paragraph, delete the 5 bullet.
4 Concepts
4.2 XML
4.2.3 Operations involving XML values
1. Rationale:Editorial.
st
Replace the 1 paragraph with:
is an operator that returns an XML value given an XML element name, an optional list
of XML attributes, and an optional list of values as the content of the new element. The value of element content> can be any value that has a mapping to an XML value.
4.3 Data analysis operations (involving tables)
4.3.1 Aggregate functions
1. Rationale:XMLAGG concatenates all kinds of XML information items, not just elements.
Replace the bulleted item with:
Add to the bulleted list following the 7th paragraph
©  ISO/IEC 2005 – All rights reserved 1

---------------------- Page: 7 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
— If XMLAGG is specified, then an XML value formed by concatenating the [children] property of
the XML root information item from the evaluated for each row that
qualifies.
4.8 Overview of mappings
4.8.3 Mapping SQL data types to XML
1. Rationale:Add an allowance for distinct types, and correct an improper characterization of XMLT as “XML
Schema built-in data type”.
st nd
Replace the 1 sentence of the 2 paragraph with:
In general, each SQL predefined type, distinct type, or domain SQLT is mapped to the XML Schema type
XMLT that is the closest analog to SQLT.
4.8.4 Mapping SQL data types to XML
1. Rationale:Add an exception for structured and reference types to the description of the supported value
space mapping.
st st
Replace the 1 sentence of the 1 paragraph with:
For each SQL type or domain SQLT, with the exception of structured types and reference types, there is
also a mapping of values of type SQLT to the value space of the corresponding XML Schema type.
4.8.5 Visibility of columns, tables, and schemas in mappings from SQL to XML
1. Rationale:Correct the definition of XML visible column.
nd
Replace the last sentence of the 2 paragraph with:
A column C of table T is an XML visible column of T for authorization identifier U if C is a visible column
of T for authorization identifier U and the declared type of C is not an XML unmappable data type.
2 ©  ISO/IEC 2005 – All rights reserved

---------------------- Page: 8 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
4.8.6 Mapping an SQL table to XML
1. Rationale:Clarify the requirements for arguments to be supplied to the invocation of a Subclause.
Replace Note 4 with:
NOTE 4 — This part of this International Standard specifies no syntax for invoking the mapping specified in Subclause 9.3,
“Mapping an SQL table to XML and an XML Schema document”. This specification is intended to be used by applications and
referenced by other standards. It is the responsibility of any such application or other standard to ensure that the correct number
of arguments as well as a valid value for each argument are supplied for this mapping.
2. Rationale:Use correct XML Schema terminology.
th
Replace the 4 paragraph with:
Some of the XML Schema type definitions and element declarations may contain annotations to represent
SQL metadata that is not directly relevant to XML. It is implementation-defined whether these annotations
are generated.
4.8.7 Mapping an SQL schema to XML
1. Rationale:Clarify the requirements for arguments to be supplied to the invocation of a Subclause.
Replace Note 5 with:
NOTE 5 — This part of this International Standard specifies no syntax for invoking the mapping specified in Subclause 9.4,
“Mapping an SQL schema to an XML document and an XML Schema document”. This specification is intended to be used by
applications and referenced by other standards. It is the responsibility of any such application or other standard to ensure that the
correct number of arguments as well as a valid value for each argument are supplied for this mapping.
2. Rationale:Use correct XML Schema terminology.
th
Replace the 4 paragraph with:
Some of the XML Schema type definitions and element declarations may contain annotations to represent
SQL metadata that is not directly relevant to XML. It is implementation-defined whether these annotations
are generated.
4.8.8 Mapping an SQL catalog to XML
1. Rationale:Clarify the requirements for arguments to be supplied to the invocation of a Subclause.
Replace Note 6 with:
NOTE 6 — This part of this International Standard specifies no syntax for invoking the mapping specified in Subclause 9.5,
“Mapping an SQL catalog to an XML document and an XML Schema document”. This specification is intended to be used by
applications and referenced by other standards. It is the responsibility of any such application or other standard to ensure that the
correct number of arguments as well as a valid value for each argument are supplied for this mapping.
©  ISO/IEC 2005 – All rights reserved 3

---------------------- Page: 9 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
2. Rationale:Use correct XML Schema terminology.
th
Replace the 4 paragraph with:
Some of the XML Schema type definitions and element declarations may contain annotations to represent
SQL metadata that is not directly relevant to XML. It is implementation-defined whether these annotations
are generated.
4.8.10 Mapping XML Names to SQL
1. Rationale:Clarify the requirements for arguments to be supplied to the invocation of a Subclause.
Replace Note 7 with:
NOTE 7 — This part of this International Standard specifies no syntax for invoking the mapping specified in Subclause 9.17,
“Mapping XML Names to SQL s”. This specification is intended to be used by applications and referenced by other
standards. It is the responsibility of any such application or other standard to ensure that the correct number of arguments as well
as a valid value for each argument are supplied for this mapping.
6 Scalar expressions
6.9
1. Rationale:The value of an attribute may not be given by a distinct type whose source type is XML.
Replace Syntax Rule 3) c) with:
3) .
c) The declared type of AV shall be either a distinct type whose source type is not XML, or a
i
predefined type other than XML.
2. Rationale:Partially escaped mapping of SQL identifiers is not applicable for explicitly specified attribute name>s.
Replace Syntax Rule 3) d) i) with:
3) .
d) .
i) If A contains an AN , then let ANC be AN .
i i i i
4 ©  ISO/IEC 2005 – All rights reserved

---------------------- Page: 10 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
3. Rationale:Editorial. Remove double "not"
Replace Syntax Rule 3) f) with:
3) .
f) ANC shall not be equivalent to 'xmlns', and ANC shall not have an XML QName prefix that
i i
is equivalent to 'xmlns'.
4. Rationale:Partially escaped mapping of SQL identifiers is not applicable for explicitly specified element name>s.
Replace Syntax Rule 5) with:
5) Let EN be the character representation of . EN shall be an XML QName.
5. Rationale:A collection type of an unmappable type is not mappable.
Replace Syntax Rule 7) with:
7) For each XEC, the declared type of XEC shall be a predefined type, a distinct
type, or a collection type that is not based on an XML unmappable data type.
6. Rationale:Invoke Subclause 9.16, “Mapping values of SQL data types to values of XML Schema data types”,
with the correct number of parameters.
Replace General Rule 3) a) with:
3) .
a) Let CAV be the result of applying the General Rules of Subclause 9.16, “Mapping values of
i
SQL data types to values of XML Schema data types”, to AV , “absent” as NULLS, and False
i
as CHARMAPPING, resulting in a character string CAV of Unicode characters.
i
7. Rationale:Clarify what the value of the [normalized value] property is.
Replace General Rule 3) b) iv) with:
3) .
b) .
iv) The [normalized value] is CAV .
i
8. Rationale:Invoke Subclause 9.16, “Mapping values of SQL data types to values of XML Schema data types”,
with the correct number of parameters.
©  ISO/IEC 2005 – All rights reserved 5

---------------------- Page: 11 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
Replace General Rule 4) a) ii) with:
4) .
a) .
ii) Otherwise, let XMLV be the result of applying the General Rules of Subclause 9.16,
j
“Mapping values of SQL data types to values of XML Schema data types”, to EC ,
j
“absent” as NULLS, and True as the CHARMAPPING. XMLV is a character string
j
of Unicode characters. Let CEC be the result of
j
XMLPARSE ( CONTENT XMLV PRESERVE WHITESPACE )
j
9. Rationale:Correct the definition of the [element whitespace content] property.
Replace General Rule 6) with:
6) For each XML character information item CI that is included in the [children] property of EI, the
[element content whitespace] property is set as follows:
Case:
a) If the [character code] property of CI is a white space character, as defined in [XML] section
2.10, “White space handling”, then Unknown.
b) Otherwise, False.
6.10
1. Rationale:A collection type of an unmappable type is not mappable.
Replace Syntax Rule 2) b) with:
2) .
b) Let FV be the immediately contained in F . The declared type of FV
i i i
shall neither be an XML unmappable type, nor be based on an XML unmappable type.
2. Rationale:Partially escaped mapping of SQL identifiers is not applicable for explicitly specified element name>s.
Replace Syntax Rule 2) c) i) with:
2) .
c) .
i) If F contains a FEN , then let FNC be FEN .
i i i i
6 ©  ISO/IEC 2005 – All rights reserved

---------------------- Page: 12 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
3. Rationale:Invoke Subclause 9.16, “Mapping values of SQL data types to values of XML Schema data types”,
with the correct number of parameters.
Replace General Rule 2) b) ii) 2) B) with:
2) .
b) .
ii) .
2) .
B) Otherwise, let CS be result of applying the General Rules of
i
Subclause 9.16, “Mapping values of SQL data types to values of XML
Schema data types”, to V , “absent” as NULLS, and True as the
i
CHARMAPPING. Let C be the result of
i
XMLPARSE ( CONTENT CS PRESERVE WHITESPACE )
i
4. Rationale:Correct the definition of the [element whitespace content] property.
Replace General Rule 2) b) ii) 5) with:
2) .
b) .
ii) .
5) For each XML character information item CI that is included in the [children]
property of E , the [element content whitespace] property is set as follows:
i
Case:
A) If the [character code] property of CI is a white space character, as defined
in [XML] section 2.10, “White space handling”, then Unknown.
B) Otherwise, False.
6.11
1. Rationale:Specify the result if the input is null.
Replace General Rule 4) with:
4) Case:
a) If V is the null value, then the result of is the null value.
©  ISO/IEC 2005 – All rights reserved 7

---------------------- Page: 13 ----------------------
ISO/IEC 9075-14:2003/Cor.1:2005(E)
b) Otherwise, the The result of is determined by applying the General Rules of
Subclause 10.14, “Parsing a character string as an XML value”, with DC as SYNTAX, V as
TEXT, and WO as OPTION.
6.12
1. Rationale:Specify the result if the input is null.
Replace General Rule 1) with:
1) If the value of the is the null value, then the result of is the
null value.
1.1) Otherwise, let V be a variable whose value is identical to the value of the .
2. Rationale:Specify the result if the input is null.
Replace General Rule 2) b) with:
2) .
b) If the value of the is not the null value, then the value of the value expression>.
NOTE 8.1 — If the value of the is the null value, then the value of the [version] property
is not changed.
8 Predicates
8.2
1. Rationale:Correct the rules for how 's value is determined.
Replace General Rule 2) with:
2) Case:
a)
...