index.html
37.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<!--* DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" *-->
<html lang="EN">
<!--* $Id $-->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
<title>Requirements for XML Schema 1.1</title>
<style type="text/css">
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
li p { margin-top: 0.3em;
margin-bottom: 0.3em; }
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
</style>
<link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD.css" />
<!--* <link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"> *-->
</head>
<body>
<div class="head"><p><a href="http://www.w3.org/">
<img width="72" height="48" alt="W3C"
src="http://www.w3.org/Icons/w3c_home" /></a></p>
<h1><a id="title" name="title"></a>Requirements for XML Schema 1.1</h1>
<h2><a id="w3c-doctype" name="w3c-doctype"></a>W3C Working Draft 21 January 2003</h2>
<dl><dt>This version:</dt>
<dd><a href="http://www.w3.org/TR/2003/WD-xmlschema-11-req-20030121/"
>http://www.w3.org/TR/2003/WD-xmlschema-11-req-20030121/</a>
</dd>
<dt>Latest version:</dt>
<dd><a href="http://www.w3.org/TR/xmlschema-11-req/"
>http://www.w3.org/TR/xmlschema-11-req/</a></dd>
<dt>Editors:</dt>
<dd>Charles Campbell <a href="mailto:campbelc@acm.org"
><campbelc@acm.org></a></dd>
<dd>Ashok Malhotra, Microsoft
<a href="mailto:ashokma@microsoft.com"
><ashokma@microsoft.com></a></dd>
<dd>Priscilla Walmsley <a href="mailto:pwalmsley@datypic.com"
><pwalmsley@datypic.com></a></dd>
</dl>
<p class="copyright"><a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"
>Copyright</a> ©2003 <a href="http://www.w3.org/" ><acronym
title="World Wide Web Consortium">W3C</acronym></a ><sup>®</sup>
(<a href="http://www.lcs.mit.edu/" ><acronym title="Massachusetts
Institute of Technology" >MIT</acronym></a>, <a
href="http://www.ercim.org/" ><acronym title="European Research
Consortium for Informatics and Mathematics" >ERCIM</acronym></a>, <a
href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer"
>liability</a>, <a
href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks"
>trademark</a>, <a
href="http://www.w3.org/Consortium/Legal/copyright-documents">document
use</a> and <a
href="http://www.w3.org/Consortium/Legal/copyright-software">software
licensing</a> rules apply.</p>
</div>
<hr />
<div>
<h2><a id="abstract" name="abstract"></a>Abstract</h2>
<p>This document contains a list of requirements and desiderata for
version 1.1 of XML Schema.</p>
</div><div>
<h2><a id="status" name="status"></a>Status of this Document</h2>
<p><em>This section describes the status of this document at the time
of its publication. Other documents may supersede this document. The
latest status of this document series is maintained at the
W3C.</em></p>
<p>This is a W3C Working Draft for review by W3C Members and other
interested parties. It is a draft document and may be updated,
replaced or made obsolete by other documents at any time. It is
inappropriate to use W3C Working Drafts as reference material or to
cite them as other than "work in progress". This is work in progress
and its publication does not imply endorsement by the W3C
membership.</p>
<p>Since the XML Schema Recommendation (<a
href="http://www.w3.org/TR/xmlschema-0/">Part 0: Primer</a>, <a
href="http://www.w3.org/TR/xmlschema-1/">Part 1: Structures</a>, and
<a href="http://www.w3.org/TR/xmlschema-2/">Part 2: Datatypes</a>) was
first published in May, 2001, it has gained acceptance as the primary
technology for specifying and constraining the structure of XML
documents. Users have employed XML Schema for a wide variety of
purposes in many, many different situations. In doing so, they have
uncovered some errors and requested some clarifications. They have
also requested additional functionality.</p>
<p>Most of the errors and clarifications are addressed in the
published errata and will be integrated into XML Schema 1.0 Second
Edition, to be published shortly. Additional functionality and any
remaining errors and clarifications will be addressed in XML Schema
1.1 and XML Schema 2.0.
</p>
<p>This document discusses the requirements for version 1.1 of XML
Schema.</p>
<p>The requirements included in this document were culled from public
and member-only messages sent to the XML Schema Working Group. Each
message was acknowledged. The requirements were then discussed by the
Working Group and accepted requirements were classified into the three
categories described in <a href="#Intro"><b>1
Introduction</b></a>.</p>
<p>It is the intention of the Working Group that this requirement
gathering and classification should continue and that updated versions
of this document should be published from time to time. This is
<em>not</em> a Last-Call publication of this Working Draft.</p>
<p>This document has been produced by the <a
href="http://www.w3.org/XML/Schema">W3C XML Schema Working Group</a>
as part of the W3C <a href="http://www.w3.org/XML/Activity">XML
Activity</a>. The authors of this document are the members of the XML
Schema Working Group.</p>
<p>Patent disclosures relevant to this specification may be found on
the XML Schema Working Group's patent disclosure page at <a
href="http://www.w3.org/2002/11/xml-schema-IPR-statements.html"
>http://www.w3.org/2002/11/xml-schema-IPR-statements.html</a>.</p>
<p>Please report comments on this document to <a
href="mailto:www-xml-schema-comments@w3.org">www-xml-schema-comments@w3.org</a>
(<a
href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/">archive</a>).
A list of current W3C Recommendations and other technical documents
can be found at <a
href="http://www.w3.org/TR/">http://www.w3.org/TR</a>.</p> </div><div
class="toc">
<h2><a id="contents" name="contents"></a>Table of Contents</h2>
<p class="toc">1 <a href="#Intro">Introduction</a>
<br />2 <a href="#N40009E">Structures Requirements and Desiderata</a>
<br /> 2.1 <a href="#N4000A1">Complex Types</a>
<br /> 2.1.1 <a href="#N4000A4">Requirements</a>
<br /> 2.1.2 <a href="#N4000BD">Desiderata</a>
<br /> 2.1.3 <a href="#N4000C5">Opportunistic Desiderata</a>
<br /> 2.2 <a href="#N4000FC">Constraints and Keys</a>
<br /> 2.2.1 <a href="#N4000FF">Requirements</a>
<br /> 2.2.2 <a href="#N40011D">Desiderata</a>
<br /> 2.2.3 <a href="#N40012B">Opportunistic Desiderata</a>
<br /> 2.3 <a href="#N400139">PSVI</a>
<br /> 2.3.1 <a href="#N40013C">Requirements</a>
<br /> 2.3.2 <a href="#N400144">Desiderata</a>
<br /> 2.4 <a href="#N40014C">Restrictions</a>
<br /> 2.4.1 <a href="#N40014F">Requirements</a>
<br /> 2.5 <a href="#N40017D">Structures (General)</a>
<br /> 2.5.1 <a href="#N400180">Desiderata</a>
<br /> 2.5.2 <a href="#N40018E">Opportunistic Desiderata</a>
<br /> 2.6 <a href="#N4001A7">Substitution Groups</a>
<br /> 2.6.1 <a href="#N4001AA">Requirements</a>
<br /> 2.6.2 <a href="#N4001B8">Desiderata</a>
<br /> 2.7 <a href="#N4001C6">Wildcards</a>
<br /> 2.7.1 <a href="#N4001C9">Requirements</a>
<br /> 2.7.2 <a href="#N4001F3">Opportunistic Desiderata</a>
<br />3 <a href="#N40020B">Datatypes Requirements and Desiderata</a>
<br /> 3.1 <a href="#N40020E">Datatypes (General)</a>
<br /> 3.1.1 <a href="#N400211">Requirements</a>
<br /> 3.1.2 <a href="#N40023D">Desiderata</a>
<br /> 3.1.3 <a href="#N400274">Opportunistic Desiderata</a>
<br /> 3.2 <a href="#N4002A9">Date and Time Types</a>
<br /> 3.2.1 <a href="#N4002AC">Requirements</a>
<br /> 3.2.2 <a href="#N40030F">Desiderata</a>
<br /> 3.3 <a href="#N400321">Numeric Types</a>
<br /> 3.3.1 <a href="#N400324">Requirements</a>
<br /> 3.3.2 <a href="#N40033C">Desiderata</a>
<br /> 3.3.3 <a href="#N40035B">Opportunistic Desiderata</a>
<br /></p>
</div>
<hr />
<div class="body"><div class="div1">
<h2><a id="Intro" name="Intro"></a>1 Introduction</h2>
<p>This document contains a list of requirements and desiderata for XML
Schema 1.1. These issues have been collected from e-mail lists and minutes
of telcons and meetings, as well as from the various issues lists
that the XML Schema Working Group has created during its lifetime. Links
are provided for further information.</p>
<p>The items in this document are divided into three categories:</p>
<ul>
<li><p>A <em>requirement</em> must be met in XML Schema 1.1.</p></li>
<li><p>A <em>desideratum</em> should be met in XML Schema
1.1.</p></li>
<li><p>An <em>opportunistic desideratum</em> may be met in XML Schema
1.1.</p></li>
</ul>
</div>
<div class="div1">
<h2><a id="N40009E" name="N40009E"></a>2 Structures Requirements and Desiderata</h2>
<div class="div2">
<h3><a id="N4000A1" name="N4000A1"></a>2.1 Complex Types</h3><div class="div3">
<h4><a id="N4000A4" name="N4000A4"></a>2.1.1 Requirements</h4><div class="div3">
<h4><a id="N4000A7" name="N4000A7"></a>2.1.1.1 Clarify behavior for attributes that are both fixed and prohibited (RQ-121)</h4><p>Clarify the expected processor behavior if an attribute has both use="prohibited", and a fixed value specified.</p><p>See (member-only link)
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Sep/0122.html">
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Sep/0122.html</a>
.</p></div><div class="div3">
<h4><a id="N4000B2" name="N4000B2"></a>2.1.1.2 Clarify identity of anonymous types (RQ-125)</h4><p>We need to be clear where the XML Schema spec depends on component identity. We need a language to talk about identity of types,
in general, and particularly with respect to anonymous types.
Can an inherited type have an anonymous type? Are anonymous types that appear multiple types in a model group the same type?
</p><p>See (member-only link)
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0248.html">
minutes of 10/24 telcon</a>
.</p></div></div><div class="div3">
<h4><a id="N4000BD" name="N4000BD"></a>2.1.2 Desiderata</h4><div class="div3">
<h4><a id="N4000C0" name="N4000C0"></a>2.1.2.1 Simplify final and block (RQ-26)</h4><p>Eliminate or simplify the interactions between final and block.</p></div></div><div class="div3">
<h4><a id="N4000C5" name="N4000C5"></a>2.1.3 Opportunistic Desiderata</h4><div class="div3">
<h4><a id="N4000C8" name="N4000C8"></a>2.1.3.1 Improve named model group syntax (RQ-35)</h4><p>Clean up named model group syntax and component.</p><p>See
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0339.html">
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0339.html</a>
.</p></div><div class="div3">
<h4><a id="N4000D3" name="N4000D3"></a>2.1.3.2 Allow local references (RQ-36)</h4><p>Change the XML representation (and possibly the component structure) of local element declarations to at least allow, if not require, all particles to be references, with scope, i.e. put the local declarations directly under <complexType></p><p>Proposal</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Nov/0100.html">
Asir Vedamuthu (member-only link)</a>
</p></li></ul></div><div class="div3">
<h4><a id="N4000E2" name="N4000E2"></a>2.1.3.3 Provide normalized value for complex/mixed elements (RQ-37)</h4><p>Provide a [schema normalized value] for all valid element infoitems, not just those of simple type, and address the question of typing the characters in mixed content.</p></div><div class="div3">
<h4><a id="N4000E7" name="N4000E7"></a>2.1.3.4 Allow complex types more than one ID attribute (RQ-105)</h4><p>Relax the constraint that a complex type may contain at most one attribute of type ID.</p><p>See
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JulSep/0069.html">
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JulSep/0069.html</a>
.</p><p>Proposal</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Dec/0072.html">
Henry Thompson. (member-only link)</a>
</p></li></ul></div></div></div>
<div class="div2">
<h3><a id="N4000FC" name="N4000FC"></a>2.2 Constraints and Keys</h3><div class="div3">
<h4><a id="N4000FF" name="N4000FF"></a>2.2.1 Requirements</h4><div class="div3">
<h4><a id="N400102" name="N400102"></a>2.2.1.1 Provide schema component for selector/field annotations (RQ-14)</h4><p>The XML representation for field and selector allows an annotation, but there is no schema component to which this annotation can adhere. This inconsistency must be resolved.</p><p>See
<a href="http://www.w3.org/2001/05/xmlschema-rec-comments#pfiIdConstrAnnot">
http://www.w3.org/2001/05/xmlschema-rec-comments#pfiIdConstrAnnot</a>
: R-46.</p></div><div class="div3">
<h4><a id="N40010D" name="N40010D"></a>2.2.1.2 Correct restriction of identity constraints (RQ-15)</h4><p>Resolve the issues associated with restricting types whose elements include identity constraints. Specifically, (1) the rule must changed to state that the restricted type must have a superset rather than a subset of identity constraints, (2) the term superset must be clearly defined, and (3) there must be a way to redefine identity constraints in the restricted type without causing duplicate name problems.</p><p>See
<a href="http://www.w3.org/2001/05/xmlschema-rec-comments#pfiIdConsRestrict">
http://www.w3.org/2001/05/xmlschema-rec-comments#pfiIdConsRestrict</a>
: R-94.</p></div><div class="div3">
<h4><a id="N400118" name="N400118"></a>2.2.1.3 Include the identity constraints in the schema component (RQ-16)</h4><p>Add an [identity constraints] property of the
schema component, which contains all the identity constraint
components, just as the [type definitions] property contains all the
type definition components.</p></div></div><div class="div3">
<h4><a id="N40011D" name="N40011D"></a>2.2.2 Desiderata</h4><div class="div3">
<h4><a id="N400120" name="N400120"></a>2.2.2.1 Add co-constraints (RQ-38)</h4><p>Add the ability to define and enforce co-constraints on attribute values, or on attribute values and sub-elements. For example, if attribute a has value foo, the attribute b must have one of the values fuzz, duz, or buzz; but if attribute a has value bar, the attribute b must have one of the values car, far, or tar. Or: if attribute href occurs, the element must be empty; if it does not occur, then it must have type phrase-level-content.</p><p>See
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0040.html">
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0040.html</a>
: LC-193 Response.</p></div></div><div class="div3">
<h4><a id="N40012B" name="N40012B"></a>2.2.3 Opportunistic Desiderata</h4><div class="div3">
<h4><a id="N40012E" name="N40012E"></a>2.2.3.1 Add key constraints based on element types (RQ-33)</h4><p>Key constraints to restrict which element types can be pointed to: Allow a schema author use key constaints to specify that a value (which otherwise behaves like an SGML or XML ID) is restricted to pointing at one (or more) particular element type(s)?</p><p>See (member-only link)
<a href="http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#typed-refs">
http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#typed-refs</a>
: LC-151.</p></div></div></div>
<div class="div2">
<h3><a id="N400139" name="N400139"></a>2.3 PSVI</h3><div class="div3">
<h4><a id="N40013C" name="N40013C"></a>2.3.1 Requirements</h4><div class="div3">
<h4><a id="N40013F" name="N40013F"></a>2.3.1.1 Correctly handle annotations in the PSVI (RQ-19)</h4><p>Systematise and correct the handling of annotations and out-of-bound attributes in the PSVI.</p></div></div><div class="div3">
<h4><a id="N400144" name="N400144"></a>2.3.2 Desiderata</h4><div class="div3">
<h4><a id="N400147" name="N400147"></a>2.3.2.1 Add normalized default value for attributes (RQ-22)</h4><p>Add a [normalized value] property to the constructed attribute infoitem which arises when a default value is applied.</p></div></div></div>
<div class="div2">
<h3><a id="N40014C" name="N40014C"></a>2.4 Restrictions</h3><div class="div3">
<h4><a id="N40014F" name="N40014F"></a>2.4.1 Requirements</h4><div class="div3">
<h4><a id="N400152" name="N400152"></a>2.4.1.1 Address problems with pointless occurrences rule (RQ-11)</h4><p>Revise the derivation of complex-type restriction so as to eliminate the problems with pointless occurrences. Currently, it eliminates some derivations that should otherwise be valid.</p><p>See
<a href="http://www.w3.org/2001/05/xmlschema-rec-comments#pfipointless">
http://www.w3.org/2001/05/xmlschema-rec-comments#pfipointless</a>
: R-24.</p><p>Proposal</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0149.html">
Microsoft proposals, item 1.2 (member-only link)</a>
</p></li></ul></div><div class="div3">
<h4><a id="N400167" name="N400167"></a>2.4.1.2 Resolve choice:choice derivation issues (RQ-12)</h4><p>Revise the particle derivation rules so as to eliminate the problems with choice/choice rules.</p><p>See
<a href="http://www.w3.org/2001/05/xmlschema-rec-comments#pfichoicechoice">
http://www.w3.org/2001/05/xmlschema-rec-comments#pfichoicechoice</a>
: R-42.</p></div><div class="div3">
<h4><a id="N400172" name="N400172"></a>2.4.1.3 Redo restriction rules (RQ-17)</h4><p>Remove the current rules on derivation by restriction; define legal restrictions in terms of their effect on the language, not in terms of a structural relationship between the base type and the derived type.</p><p>See (member-only link)
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2001May/0018.html">
http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2001May/0018.html</a>
.</p></div></div></div>
<div class="div2">
<h3><a id="N40017D" name="N40017D"></a>2.5 Structures (General)</h3><div class="div3">
<h4><a id="N400180" name="N400180"></a>2.5.1 Desiderata</h4><div class="div3">
<h4><a id="N400183" name="N400183"></a>2.5.1.1 First class objects (RQ-23)</h4><p>Define an algorithm for generating a URI for any construct in a schema (or, possibly, in a schema document), thus making schema constructs first-class objects in the Web. Minimally the algorithm should cover element( type)s, attributes, simple types, complex types, and notations. Optionally it may also cover other constructs such as named groups and items in enumerations of legal values.</p><p>See
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002AprJun/0025.html">
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002AprJun/0025.html</a>
.</p></div></div><div class="div3">
<h4><a id="N40018E" name="N40018E"></a>2.5.2 Opportunistic Desiderata</h4><div class="div3">
<h4><a id="N400191" name="N400191"></a>2.5.2.1 Address localization issues in Structures (RQ-29)</h4><p>Address localization concerns regarding Part 1: Structures.</p><p>See (member-only link)
<a href="http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#i18n-str-misdirected">
http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#i18n-str-misdirected</a>
: LC-206.</p></div><div class="div3">
<h4><a id="N40019C" name="N40019C"></a>2.5.2.2 Add inline schemas (RQ-34)</h4><p>Specify a manner in which schema documents can be included in-line in instances.</p><p>See (member-only link)
<a href="http://www.w3.org/XML/Group/xmlschema-current/issues.html#inlineSchemaInfo">
http://www.w3.org/XML/Group/xmlschema-current/issues.html#inlineSchemaInfo</a>
: Issue 42.</p></div></div></div>
<div class="div2">
<h3><a id="N4001A7" name="N4001A7"></a>2.6 Substitution Groups</h3><div class="div3">
<h4><a id="N4001AA" name="N4001AA"></a>2.6.1 Requirements</h4><div class="div3">
<h4><a id="N4001AD" name="N4001AD"></a>2.6.1.1 Improve interaction between exclusions and disallowed substitutions (RQ-10)</h4><p>Improve interaction between substitution group exclusions and disallowed substitutions in the element component.</p><p>See (member-only link)
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Apr/0049.html">
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Apr/0049.html</a>
.</p></div></div><div class="div3">
<h4><a id="N4001B8" name="N4001B8"></a>2.6.2 Desiderata</h4><div class="div3">
<h4><a id="N4001BB" name="N4001BB"></a>2.6.2.1 Allow an element to be in more than one substitution group (RQ-99)</h4><p>Allow an element declaration to be in more than one substitution group.</p><p>See (member-only link)
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2002Sep/0016.html">
http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2002Sep/0016.html</a>
.</p></div></div></div>
<div class="div2">
<h3><a id="N4001C6" name="N4001C6"></a>2.7 Wildcards</h3><div class="div3">
<h4><a id="N4001C9" name="N4001C9"></a>2.7.1 Requirements</h4><div class="div3">
<h4><a id="N4001CC" name="N4001CC"></a>2.7.1.1 Improve interaction between wildcards and substitution groups (RQ-7)</h4><p>Address problems with the interaction between wildcards and substitution groups. Specifically, resolve the bug where if complex type A has a wildcard, and B restricts A, then it can restrict the wildcard to a set of elements that match the wildcard. Not all elements in the substitution groups of those elements necessarily match the wildcard - so B is not a subset of A.</p><p>See (member-only link)
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Apr/0047.html">
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Apr/0047.html</a>
.</p></div><div class="div3">
<h4><a id="N4001D7" name="N4001D7"></a>2.7.1.2 Expand wildcard namespace constraints (RQ-9)</h4><p>The namespace constraints on wildcards must be more expressive in order to be able to express the union or intersection of any two wildcards. Specifically, it must be possible to express "any namespace except those in the following list."</p><p>See
<a href="http://www.w3.org/2000/12/xmlschema-crcomments.html#wildcard-minus">
http://www.w3.org/2000/12/xmlschema-crcomments.html#wildcard-minus</a>
: CR-20.</p><p>Proposals</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0149.html">
Microsoft proposals, item 1.3 (member-only link)</a>
</p></li><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0163.html">
Asir Vedamuthu (member-only link)</a>
</p></li></ul></div></div><div class="div3">
<h4><a id="N4001F3" name="N4001F3"></a>2.7.2 Opportunistic Desiderata</h4><div class="div3">
<h4><a id="N4001F6" name="N4001F6"></a>2.7.2.1 Allow typed wildcards (RQ-97)</h4><p>Allow a wildcard to indicate that it will allow any element that conforms to a specified type.</p><p>See
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JanMar/1137.html">
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JanMar/1137.html</a>
.</p><p>Proposal</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Nov/0150.html">
Xan Gregg (member-only link)</a>
</p></li></ul></div></div></div>
</div>
<div class="div1">
<h2><a id="N40020B" name="N40020B"></a>3 Datatypes Requirements and Desiderata</h2>
<div class="div2">
<h3><a id="N40020E" name="N40020E"></a>3.1 Datatypes (General)</h3><div class="div3">
<h4><a id="N400211" name="N400211"></a>3.1.1 Requirements</h4><div class="div3">
<h4><a id="N400214" name="N400214"></a>3.1.1.1 Address localization issues with datatypes (RQ-4)</h4><p>Address localization concerns regarding Part 2: Datatypes.</p><p>See (member-only link)
<a href="http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#i18n-dt-misdirected">
http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#i18n-dt-misdirected</a>
: LC-207.</p></div><div class="div3">
<h4><a id="N40021F" name="N40021F"></a>3.1.1.2 Specify unit of length for all primitive types (RQ-6)</h4><p>Unit of length must be defined for the all primitive types, including anyURI, QName, and NOTATION.</p><p>See
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0391.html">
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0391.html</a>
.</p></div><div class="div3">
<h4><a id="N40022A" name="N40022A"></a>3.1.1.3 Restricting away canonical forms (RQ-126)</h4><p>See (member-only link)
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Nov/0186.html">
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Nov/0186.html</a>
.</p><p>Proposal</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Nov/0186.html">
Dave Peterson and subsequent thread (member-only links)</a>
</p></li></ul></div></div><div class="div3">
<h4><a id="N40023D" name="N40023D"></a>3.1.2 Desiderata</h4><div class="div3">
<h4><a id="N400240" name="N400240"></a>3.1.2.1 Provide regex or BNF for all primitive types (RQ-21)</h4><p>Provide regular expressions or BNF productions to express (1) the valid lexical representations and (2) the canonical lexical representation of each primitive built-in type.</p><p>Proposal</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Mar/0199.html">
Alexander Falk (member-only link)</a>
</p></li></ul></div><div class="div3">
<h4><a id="N40024F" name="N40024F"></a>3.1.2.2 Systematic treatment of fundamental facets (RQ-24)</h4><p>Make the treatment of
fundamental facets more systematic. Define canonical forms for all
types, and specify the rules for generating the canonical form, given
a value. Clarify the status of
anySimpleType and define its value space (if any). Clarify the
assignment of types to nodes in the absence of relevant schema
components. Distinguish our
identity relation from the mathematical relation of quantitative
equality.</p></div><div class="div3">
<h4><a id="N400254" name="N400254"></a>3.1.2.3 Interactions with legacy types (RQ-25)</h4><p>Interaction between uniqueness and referential integrity constraints on legacy types and union types.</p><p>See
<a href="http://www.w3.org/2000/12/xmlschema-crcomments.html">
http://www.w3.org/2000/12/xmlschema-crcomments.html#idrefinunion</a>
: CR-50 (broken link).</p></div><div class="div3">
<h4><a id="N40025F" name="N40025F"></a>3.1.2.4 Make consistent use of the term "derived" (RQ-120)</h4><p>XML Schema Part 1 (Structure) and XML Schema Part 2 (Datatypes)
have different notions of "derived" for simple types, specifically with regard to list and union types.</p><p>See
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JulSep/0014.html">
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JulSep/0014.html</a>
.</p><p>Proposal</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JulSep/0014.html">
Berthold Daum</a>
</p></li></ul></div></div><div class="div3">
<h4><a id="N400274" name="N400274"></a>3.1.3 Opportunistic Desiderata</h4><div class="div3">
<h4><a id="N400277" name="N400277"></a>3.1.3.1 Allow abstract simple types (RQ-32)</h4><p>Allow abstract simple types.</p><p>See
<a href="http://www.w3.org/2000/12/xmlschema-crcomments.html#abstract-simples">
http://www.w3.org/2000/12/xmlschema-crcomments.html#abstract-simples</a>
: CR-47.</p><p>Proposals</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Nov/0246.html">
Dave Peterson (member-only link)</a>
</p></li><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0149.html">
Microsoft proposals, item 2.2 (member-only link)</a>
</p></li></ul></div><div class="div3">
<h4><a id="N400293" name="N400293"></a>3.1.3.2 Add URI datatype (RQ-108)</h4><p>Add a "URI" type that allows only a URI, not a URI reference. The current anyURI type allows a URI reference.</p><p>See
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JanMar/1141.html">
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JanMar/1141.html</a>
.</p></div><div class="div3">
<h4><a id="N40029E" name="N40029E"></a>3.1.3.3 Support extensible enumerations (RQ-112)</h4><p>Support for extensible enumerations such as allowed in Java.</p><p>See
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JanMar/1130.html">
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JanMar/1130.html</a>
.</p></div></div></div>
<div class="div2">
<h3><a id="N4002A9" name="N4002A9"></a>3.2 Date and Time Types</h3><div class="div3">
<h4><a id="N4002AC" name="N4002AC"></a>3.2.1 Requirements</h4><div class="div3">
<h4><a id="N4002AF" name="N4002AF"></a>3.2.1.1 Specify canonical representation of duration (RQ-2)</h4><p>There must be a canonical representation of duration, and a process for calculating the canonical representation from any other lexical representation. Currently, a period of one day and a period of 24 hours are considered two different values in the value space. They should be considered two different lexical representations of the same value.</p><p>See (member-only link)
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Jan/0215.html">
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Jan/0215.html</a>
. See also
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JulSep/0102.html">
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JulSep/0102.html</a>
: R-170.</p><p>Proposals</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0149.html">
Microsoft proposals, item 1.1 (member-only link)</a>
</p></li><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-query-operators/2002Dec/0002.html">
Michael Kay (member-only link)</a>
</p></li></ul></div><div class="div3">
<h4><a id="N4002CF" name="N4002CF"></a>3.2.1.2 Address localization issues with date and time types (RQ-3)</h4><p>Address localization concerns regarding the date and time types.</p><p>See (member-only link)
<a href="http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#i18n-datetime">
http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#i18n-datetime</a>
: LC-221.</p></div><div class="div3">
<h4><a id="N4002DA" name="N4002DA"></a>3.2.1.3 Time zone normalization crosses date line (RQ-13)</h4><p>Resolve the issue that relates to timezone normalization resulting in a time crossing over the date line.</p><p>See
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0366.html">
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0366.html</a>
.</p></div><div class="div3">
<h4><a id="N4002E5" name="N4002E5"></a>3.2.1.4 Define value space for dateTime more precisely (RQ-122)</h4><p>The definition of the dateTime value space does not reference a part
of ISO 8601 that defines dateTime values, only lexical representations. The reference should be corrected,
and the recommendation should explain or fix the fuzziness and/or gaps in the definitions referenced.</p><p>See (member-only link)
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0258.html">
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0258.html</a>
.</p><p>Proposal</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/att-0363/00-part">
Dave Peterson erratum for R-120 (member-only link)</a>
</p></li></ul></div><div class="div3">
<h4><a id="N4002FA" name="N4002FA"></a>3.2.1.5 Allow year 0000 in date-related types (RQ-123)</h4><p>The year 0000 should be allowed in the types date, dateTime, gYear and gYearMonth.</p><p>See (member-only link)
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0258.html">
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0258.html</a>
.</p><p>Proposal</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/att-0363/00-part">
Dave Peterson erratum for R-120 (member-only link)</a>
</p></li></ul></div></div><div class="div3">
<h4><a id="N40030F" name="N40030F"></a>3.2.2 Desiderata</h4><div class="div3">
<h4><a id="N400312" name="N400312"></a>3.2.2.1 Provide ordered duration types (RQ-20)</h4><p>Provide totally ordered duration types, specifically one that is expressed only in years and months, and one that is expressed only in days, hours, minutes, and seconds (ignoring leap seconds.) Possibly define other totally ordered duration types such as day/hour/minute and hour/minute/second duration.</p><p>Proposal</p><ul><li><p>yearMonthDuration and dayTimeDuration as defined in
<a href="http://www.w3.org/TR/xquery-operators/">
XQuery and XPath Function and Operators</a>
</p></li></ul></div></div></div>
<div class="div2">
<h3><a id="N400321" name="N400321"></a>3.3 Numeric Types</h3><div class="div3">
<h4><a id="N400324" name="N400324"></a>3.3.1 Requirements</h4><div class="div3">
<h4><a id="N400327" name="N400327"></a>3.3.1.1 Specify canonical representation of float and double (RQ-1)</h4><p>The canonical representation of float and double must be refined because it currently maps several lexical representations into a single legal value. Specifically, the description of the canonical representation must address (1) signed exponents, and (2) trailing zeroes in the mantissa.</p><p>See (member-only link)
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Mar/0184.html">
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Mar/0184.html</a>
.</p><p>Proposal</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Nov/0196.html">
Ashok Malhotra and subsequent thread (member-only links)</a>
</p></li></ul></div></div><div class="div3">
<h4><a id="N40033C" name="N40033C"></a>3.3.2 Desiderata</h4><div class="div3">
<h4><a id="N40033F" name="N40033F"></a>3.3.2.1 Provide decimal type that retains trailing zeroes (RQ-31)</h4><p>Provide a datatype which retains trailing zeroes in the lexical representation of decimal numbers.</p><p>See
<a href="http://www.w3.org/2000/12/xmlschema-crcomments.html#canonical-decimals">http://www.w3.org/2000/12/xmlschema-crcomments.html#canonical-decimals</a>
: CR-42.</p><p>Proposals</p><ul><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0051.html">
Dave Peterson and Mike Cowlishaw (member-only link)</a>
</p></li><li><p>
<a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Dec/att-0045/01-precisionDecimal.html">
Latest from Dave Peterson (member-only link)</a>
</p></li></ul></div></div><div class="div3">
<h4><a id="N40035B" name="N40035B"></a>3.3.3 Opportunistic Desiderata</h4><div class="div3">
<h4><a id="N40035E" name="N40035E"></a>3.3.3.1 Allow scientific notation for decimals (RQ-28)</h4><p>Allow scientific notation for decimals.</p><p>See
<a href="http://www.w3.org/2000/12/xmlschema-crcomments.html#scientific-decimals">
http://www.w3.org/2000/12/xmlschema-crcomments.html#scientific-decimals</a>
: CR-23.</p></div><div class="div3">
<h4><a id="N400369" name="N400369"></a>3.3.3.2 Allow negative fractionDigits (RQ-30)</h4><p>Allow negative values for the fractionDigits facet.</p><p>See
<a href="http://www.w3.org/2000/12/xmlschema-crcomments.html#negative-scale">
http://www.w3.org/2000/12/xmlschema-crcomments.html#negative-scale</a>
: CR-22.</p></div></div></div>
</div>
</div>
</body>
</html>
<!-- Keep this comment at the end of the file
Local variables:
mode:"xml"
sgml-default-dtd-file:"/SGML/Public/Emacs/xhtml10.ced"
sgml-omittag:t
sgml-shorttag:t
End:
-->