index.html
79 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
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
<?xml version="1.0" encoding="utf-8"?>
<!--{xsl-query} XSLT Processor: SAXON 9.1.0.5 from Saxonica SAXON 9.1.0.5--><!--$show.diff.markup = 0--><!--{xmlspec} XSLT Processor: SAXON 9.1.0.5 from SaxonicaSAXON9.1.0.5 $show.diff.markup = 0-->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns:xs="http://www.w3.org/2001/XMLSchema" lang="EN" xmlns=
"http://www.w3.org/1999/xhtml" xml:lang="EN">
<head>
<meta name="generator" content=
"HTML Tidy for Windows (vers 14 February 2006), see www.w3.org" />
<title>XQuery Update Facility 1.0 Use Cases</title>
<style type="text/css">
/*<![CDATA[*/
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
div.issue
p.title { margin-left: -2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
li p { margin-top: 0.3em;
margin-bottom: 0.3em; }
sup small { font-style: italic;
color: #8F8F8F;
}
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}
div.issue { border-bottom-color: black;
border-bottom-style: solid;
border-bottom-width: 1pt;
margin-bottom: 20pt;
}
th.issue-toc-head { border-bottom-color: black;
border-bottom-style: solid;
border-bottom-width: 1pt;
}
table.small { font-size: x-small; }
a.judgment:visited, a.judgment:link { font-family: sans-serif;
color: black;
text-decoration: none }
a.processing:visited, a.processing:link { color: black;
text-decoration: none }
a.env:visited, a.env:link { color: black;
text-decoration: none }
/*]]>*/
</style>
<link rel="stylesheet" type="text/css" href=
"http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE.css" />
</head>
<body>
<div class="head">
<p><a href="http://www.w3.org/"><img src=
"http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width=
"72" /></a></p>
<h1><a name="title" id="title"></a>XQuery Update Facility 1.0 Use
Cases</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Working Group
Note 25 January 2011</h2>
<dl>
<dt>This version:</dt>
<dd><a href=
"http://www.w3.org/TR/2011/NOTE-xquery-update-10-use-cases-20110125/">
http://www.w3.org/TR/2011/NOTE-xquery-update-10-use-cases-20110125/</a></dd>
<dt>Latest version:</dt>
<dd><a href=
"http://www.w3.org/TR/xquery-update-10-use-cases/">http://www.w3.org/TR/xquery-update-10-use-cases/</a></dd>
<dt>Previous version:</dt>
<dd><a href=
"http://www.w3.org/TR/2008/CR-xquery-update-10-use-cases-20080314/">
http://www.w3.org/TR/2008/CR-xquery-update-10-use-cases-20080314/</a></dd>
<dt>Editors:</dt>
<!--xmlspec, match="author"-->
<dd>Ioana Manolescu, INRIA <a href=
"mailto:ioana.manolescu@inria.fr"><ioana.manolescu@inria.fr></a></dd>
<!--xmlspec, match="author"-->
<dd>Jonathan Robie, Red Hat <a href=
"mailto:jonathan.robie@redhat.com"><jonathan.robie@redhat.com></a></dd>
</dl>
<p class="copyright"><a href=
"http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup>
(<a href="http://www.csail.mit.edu/"><acronym title=
"Massachusetts Institute of Technology">MIT</acronym></a>, <a href=
"http://www.ercim.eu/"><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>
and <a href=
"http://www.w3.org/Consortium/Legal/copyright-documents">document
use</a> rules apply.</p>
</div>
<hr />
<div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2>
<p>This document specifies usage scenarios for the XQuery Update
Facility.</p>
</div>
<div>
<h2><a name="status" id="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. A list of current W3C publications and the latest
revision of this technical report can be found in the <a href=
"http://www.w3.org/TR/">W3C technical reports index</a> at
http://www.w3.org/TR/.</em></p>
<p>This is a <a href=
"http://www.w3.org/2005/10/Process-20051014/tr.html#tr-end">Working
Group Note</a> as described in the <a href=
"http://www.w3.org/2005/10/Process-20051014/tr.html">Process
Document</a>. It has been developed by the W3C <a href=
"http://www.w3.org/XML/Query/">XML Query Working Group</a>, which
is part of the <a href="http://www.w3.org/XML/Activity">XML
Activity</a>.</p>
<p>This document incorporates a number of use cases that guided the
development of <a href=
"http://www.w3.org/TR/xquery-update-10/">XQuery Update Facility
1.0</a> during its design and development.</p>
<p>Please report errors in this document using W3C's <a href=
"http://www.w3.org/Bugs/Public/">public Bugzilla system</a>
(instructions can be found at <a href=
"http://www.w3.org/XML/2005/04/qt-bugzilla">http://www.w3.org/XML/2005/04/qt-bugzilla</a>).
If access to that system is not feasible, you may send your
comments to the W3C XSLT/XPath/XQuery public comments mailing list,
<a href=
"mailto:public-qt-comments@w3.org">public-qt-comments@w3.org</a>.
It will be very helpful if you include the string “[UPDUC]” in the
subject line of your report, whether made in Bugzilla or in email.
Please use multiple Bugzilla entries (or, if necessary, multiple
email messages) if you have more than one comment to make. Archives
of the comments and responses are available at <a href=
"http://lists.w3.org/Archives/Public/public-qt-comments/">http://lists.w3.org/Archives/Public/public-qt-comments/</a>.</p>
<p>Publication as a <a href=
"http://www.w3.org/2005/10/Process-20051014/tr.html#tr-end">Working
Group Note</a> does not imply endorsement by the W3C Membership. At
the time of publication, work on this document was considered
complete and no further revisions are anticipated. It is a stable
document and may be used as reference material or cited from
another document. However, this document may be updated, replaced,
or made obsolete by other documents at any time.</p>
<p>This document was produced by a group operating under the
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
February 2004 W3C Patent Policy</a>. W3C maintains a <a href=
"http://www.w3.org/2004/01/pp-impl/18797/status#disclosures">public
list of any patent disclosures</a> made in connection with the
deliverables of the group; that page also includes instructions for
disclosing a patent. An individual who has actual knowledge of a
patent which the individual believes contains <a href=
"http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">
Essential Claim(s)</a> must disclose the information in accordance
with <a href=
"http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">
section 6 of the W3C Patent Policy</a>.</p>
</div>
<div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2>
<p class="toc">1 <a href="#use-cases-for-xquery-updates">Use Cases
for XQuery Updates</a><br />
    1.1 <a href="#rdb">Use Case "R" - Updating
Relational Data</a><br />
        1.1.1 <a href=
"#rdb-description">Description</a><br />
        1.1.2 <a href=
"#rdb-dtd">Document Type Definition (DTD)</a><br />
            1.1.2.1
<a href="#schema-for-users.xml">Schema for users.xml</a><br />
            1.1.2.2
<a href="#schema-for-items.xml">Schema for items.xml</a><br />
            1.1.2.3
<a href="#schema-for-bids.xml">Schema for bids.xml</a><br />
        1.1.3 <a href=
"#rdb-data">Input Data</a><br />
        1.1.4 <a href=
"#rdb-updates-results">Updates and Results</a><br />
            1.1.4.1
<a href="#rdb-updates-results-u1">Q1</a><br />
            1.1.4.2
<a href="#rdb-updates-results-u2">Q2</a><br />
            1.1.4.3
<a href="#rdb-updates-results-u3">Q3</a><br />
            1.1.4.4
<a href="#rdb-updates-results-u4">Q4</a><br />
            1.1.4.5
<a href="#rdb-updates-results-u5">Q5</a><br />
            1.1.4.6
<a href="#rdb-updates-results-u6">Q6</a><br />
            1.1.4.7
<a href="#rdb-updates-results-u7">Q7</a><br />
            1.1.4.8
<a href="#rdb-updates-results-q8">Q8</a><br />
            1.1.4.9
<a href="#rdb-updates-results-u9">Q9</a><br />
    1.2 <a href="#use-case-sync-addrbook">Use
Case "Address Book" - synchronizing address book entries</a><br />
        1.2.1 <a href=
"#use-case-sync-addrbook-input-data">Input Data</a><br />
        1.2.2 <a href=
"#addrbook-q1">Q1</a><br />
    1.3 <a href="#use-case-soap">Use Case
"SOAP" - processing messages</a><br />
        1.3.1 <a href=
"#use-case-soap-input-data">Input Data</a><br />
        1.3.2 <a href=
"#soap-q1">Q1</a><br />
    1.4 <a href="#use-case-namespaces">Use Case
"Namespaces" - moving elements from one namespace to
another</a><br />
        1.4.1 <a href=
"#use-case-ns-desc">Description</a><br />
        1.4.2 <a href=
"#use-case-ns-schema-grant-app">Schema for the grant
application</a><br />
        1.4.3 <a href=
"#ns-input-data">Input Data</a><br />
        1.4.4 <a href=
"#ns-q1">Q1</a><br />
    1.5 <a href="#use-case-parts">Use case
"Parts" - modifying recursive documents</a><br />
        1.5.1 <a href=
"#use-case-parts-input">Input data</a><br />
        1.5.2 <a href=
"#use-case-parts-q1">Q1</a><br />
        1.5.3 <a href=
"#use-case-parts-q2">Q2</a><br />
        1.5.4 <a href=
"#use-case-parts-q3">Q3</a><br />
        1.5.5 <a href=
"#use-case-parts-q4">Q4</a><br />
        1.5.6 <a href=
"#use-case-parts-q6">Q6</a><br />
    1.6 <a href="#use-case-nil">Use case
"Nil"</a><br />
        1.6.1 <a href=
"#use-case-nil-schema">XML Schema</a><br />
        1.6.2 <a href=
"#use-case-nil-input-data">Sample input data
("employees.xml")</a><br />
        1.6.3 <a href=
"#use-case-nil-q1">Q1</a><br /></p>
<h3><a name="appendices" id="appendices"></a>Appendices</h3>
<p class="toc">A <a href="#references">Normative
References</a><br />
B <a href="#id-revisions-log">Revision Log</a>
(Non-Normative)<br />
    B.1 <a href="#id-log-pending">Changes in
internal WD</a><br />
    B.2 <a href="#id-log-28aug2007">28 Aug 2007
Publication</a><br /></p>
</div>
<hr />
<div class="body">
<div class="div1">
<h2><a name="use-cases-for-xquery-updates" id=
"use-cases-for-xquery-updates"></a>1 Use Cases for XQuery
Updates</h2>
<p>The use cases listed below were created by the <a href=
"http://www.w3.org/XML/Query/">XML Query Working Group</a> to
illustrate important applications for an XML update facility. Each
use case is focused on a specific application area, and contains a
Document Type Definition (DTD) and example input data. Each use
case specifies a set of updates that might be applied to the input
data, and the expected resulting value of the modified input for
each update. Since the English description of each query is
concise, the expected results form an important part of the
definition of each update directive. These use cases are inspired
by the <a href=
"http://www.w3.org/TR/2011/NOTE-xquery-update-10-requirements-20110125/">
W3C XQuery Update Facility Requirements</a> document.</p>
<p>These use cases represent a snapshot of an ongoing work. Some
important application areas and important operations are not yet
adequately covered by a use case. The XML Query Working Group
reserves the right to add, delete, or modify individual queries or
whole use cases as the work progresses. The presence of a query in
this set of use cases does not necessarily indicate that the query
will be expressible in the XQuery Update Facility to be created by
the XML Query Working Group.</p>
<div class="div2">
<h3><a name="rdb" id="rdb"></a>1.1 Use Case "R" - Updating
Relational Data</h3>
<p>One important use of an XML update language will be to update
data stored in relational databases. This use case describes a set
of such possible updates.</p>
<div class="div3">
<h4><a name="rdb-description" id="rdb-description"></a>1.1.1
Description</h4>
<p>This use case is based on performing updates on the data used in
Use Case "R" from the <a href="#xquery-use-cases">[XML Query Use
Cases]</a>. The sample data from this Use Case is copied below for
convenience, and exactly match the data found in the XQuery 1.0 Use
Cases. Instead of DTDs, we describe this data with W3C XML
Schemas.</p>
<p>The data represents a relational database used by an online
auction. The auction maintains a USERS table containing information
on registered users, each identified by a unique userid, who can
either offer items for sale or bid on items. An ITEMS table lists
items currently or recently for sale, with the userid of the user
who offered each item. A BIDS table contains all bids on record,
keyed by the userid of the bidder and the item number of the item
to which the bid applies.</p>
<p>The three tables used by the online auction are below, with
their column-names indicated in parentheses.</p>
<div class="exampleInner">
<pre>
USERS ( USERID, NAME, RATING )
ITEMS ( ITEMNO, DESCRIPTION, OFFERED_BY,
START_DATE, END_DATE, RESERVE_PRICE )
BIDS ( USERID, ITEMNO, BID, BID_DATE )
</pre></div>
</div>
<div class="div3">
<h4><a name="rdb-dtd" id="rdb-dtd"></a>1.1.2 Document Type
Definition (DTD)</h4>
<p>This use case is based on three separate input documents named
users.xml, items.xml, and bids.xml. Each of the documents
represents one of the tables in the relational database described
above, using the following DTDs:</p>
<div class="div4">
<h5><a name="schema-for-users.xml" id=
"schema-for-users.xml"></a>1.1.2.1 Schema for users.xml</h5>
<div class="exampleInner">
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:element name="users">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="user_tuple"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="user_tuple">
<xs:complexType>
<xs:sequence>
<xs:element ref="userid"/>
<xs:element ref="name"/>
<xs:element minOccurs="0" ref="rating"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="userid" type="xs:string"/>
<xs:element name="name" type="xs:string"/>
<xs:element name="rating" type="xs:string"/>
</xs:schema>
</pre></div>
</div>
<div class="div4">
<h5><a name="schema-for-items.xml" id=
"schema-for-items.xml"></a>1.1.2.2 Schema for items.xml</h5>
<div class="exampleInner">
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:element name="items">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="item_tuple"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="item_tuple">
<xs:complexType>
<xs:sequence>
<xs:element ref="itemno"/>
<xs:element ref="description"/>
<xs:element ref="offered_by"/>
<xs:element minOccurs="0" ref="start_date"/>
<xs:element minOccurs="0" ref="end_date"/>
<xs:element minOccurs="0" ref="reserve_price"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="itemno" type="xs:string"/>
<xs:element name="description" type="xs:string"/>
<xs:element name="offered_by" type="xs:string"/>
<xs:element name="start_date" type="xs:string"/>
<xs:element name="end_date" type="xs:string"/>
<xs:element name="reserve_price" type="xs:string"/>
</xs:schema>
</pre></div>
</div>
<div class="div4">
<h5><a name="schema-for-bids.xml" id=
"schema-for-bids.xml"></a>1.1.2.3 Schema for bids.xml</h5>
<div class="exampleInner">
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:element name="bids">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="bid_tuple"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="bid_tuple">
<xs:complexType>
<xs:sequence>
<xs:element ref="userid"/>
<xs:element ref="itemno"/>
<xs:element ref="bid"/>
<xs:element ref="bid_date"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="userid" type="xs:string"/>
<xs:element name="itemno" type="xs:string"/>
<xs:element name="bid" type="xs:string"/>
<xs:element name="bid_date" type="xs:string"/>
</xs:schema>
</pre></div>
</div>
</div>
<div class="div3">
<h4><a name="rdb-data" id="rdb-data"></a>1.1.3 Input Data</h4>
<p>The following data is an excerpt of the initial state for Q1. In
this particular use case, each update begins with the state
resulting from the prior update.</p>
<div class="exampleInner">
<pre>
<items>
<item_tuple>
<itemno>1001</itemno>
<description>Red Bicycle</description>
<offered_by>U01</offered_by>
<start_date>1999-01-05</start_date>
<end_date>1999-01-20</end_date>
<reserve_price>40</reserve_price>
</item_tuple>
<em> ... Snip ... </em>
</items>
<users>
<user_tuple>
<userid>U01</userid>
<name>Tom Jones</name>
<rating>B</rating>
</user_tuple>
<em> ... Snip ... </em>
</users>
<bids>
<bid_tuple>
<userid>U02</userid>
<itemno>1001</itemno>
<bid>35</bid>
<bid_date>1999-01-07</bid_date>
</bid_tuple>
<bid_tuple>
<em> ... Snip ... </em>
</bids>
</pre></div>
<p>The entire data set is represented by the following tables:</p>
<table border="1" summary="Data set table">
<caption>USERS</caption>
<thead>
<tr>
<td>USERID</td>
<td>NAME</td>
<td>RATING</td>
</tr>
</thead>
<tbody>
<tr>
<td>U01</td>
<td>Tom Jones</td>
<td>B</td>
</tr>
<tr>
<td>U02</td>
<td>Mary Doe</td>
<td>A</td>
</tr>
<tr>
<td>U03</td>
<td>Dee Linquent</td>
<td>D</td>
</tr>
<tr>
<td>U04</td>
<td>Roger Smith</td>
<td>C</td>
</tr>
<tr>
<td>U05</td>
<td>Jack Sprat</td>
<td>B</td>
</tr>
<tr>
<td>U06</td>
<td>Rip Van Winkle</td>
<td>B</td>
</tr>
</tbody>
</table>
<table border="1" summary="Data set table">
<caption>ITEMS</caption>
<thead>
<tr>
<td>ITEMNO</td>
<td>DESCRIPTION</td>
<td>OFFERED_BY</td>
<td>START_DATE</td>
<td>END_DATE</td>
<td>RESERVE_PRICE</td>
</tr>
</thead>
<tbody>
<tr>
<td>1001</td>
<td>Red Bicycle</td>
<td>U01</td>
<td>1999-01-05</td>
<td>1999-01-20</td>
<td>40</td>
</tr>
<tr>
<td>1002</td>
<td>Motorcycle</td>
<td>U02</td>
<td>1999-02-11</td>
<td>1999-03-15</td>
<td>500</td>
</tr>
<tr>
<td>1003</td>
<td>Old Bicycle</td>
<td>U02</td>
<td>1999-01-10</td>
<td>1999-02-20</td>
<td>25</td>
</tr>
<tr>
<td>1004</td>
<td>Tricycle</td>
<td>U01</td>
<td>1999-02-25</td>
<td>1999-03-08</td>
<td>15</td>
</tr>
<tr>
<td>1005</td>
<td>Tennis Racket</td>
<td>U03</td>
<td>1999-03-19</td>
<td>1999-04-30</td>
<td>20</td>
</tr>
<tr>
<td>1006</td>
<td>Helicopter</td>
<td>U03</td>
<td>1999-05-05</td>
<td>1999-05-25</td>
<td>50000</td>
</tr>
<tr>
<td>1007</td>
<td>Racing Bicycle</td>
<td>U04</td>
<td>1999-01-20</td>
<td>1999-02-20</td>
<td>200</td>
</tr>
<tr>
<td>1008</td>
<td>Broken Bicycle</td>
<td>U01</td>
<td>1999-02-05</td>
<td>1999-03-06</td>
<td>25</td>
</tr>
</tbody>
</table>
<table border="1" summary="Data set table">
<caption>BIDS</caption>
<thead>
<tr>
<td>USERID</td>
<td>ITEMNO</td>
<td>BID</td>
<td>BID_DATE</td>
</tr>
</thead>
<tbody>
<tr>
<td>U02</td>
<td>1001</td>
<td>35</td>
<td>1999-01-07</td>
</tr>
<tr>
<td>U04</td>
<td>1001</td>
<td>40</td>
<td>1999-01-08</td>
</tr>
<tr>
<td>U02</td>
<td>1001</td>
<td>45</td>
<td>1999-01-11</td>
</tr>
<tr>
<td>U04</td>
<td>1001</td>
<td>50</td>
<td>1999-01-13</td>
</tr>
<tr>
<td>U02</td>
<td>1001</td>
<td>55</td>
<td>1999-01-15</td>
</tr>
<tr>
<td>U01</td>
<td>1002</td>
<td>400</td>
<td>1999-02-14</td>
</tr>
<tr>
<td>U02</td>
<td>1002</td>
<td>600</td>
<td>1999-02-16</td>
</tr>
<tr>
<td>U03</td>
<td>1002</td>
<td>800</td>
<td>1999-02-17</td>
</tr>
<tr>
<td>U04</td>
<td>1002</td>
<td>1000</td>
<td>1999-02-25</td>
</tr>
<tr>
<td>U02</td>
<td>1002</td>
<td>1200</td>
<td>1999-03-02</td>
</tr>
<tr>
<td>U04</td>
<td>1003</td>
<td>15</td>
<td>1999-01-22</td>
</tr>
<tr>
<td>U05</td>
<td>1003</td>
<td>20</td>
<td>1999-02-03</td>
</tr>
<tr>
<td>U01</td>
<td>1004</td>
<td>40</td>
<td>1999-03-05</td>
</tr>
<tr>
<td>U03</td>
<td>1007</td>
<td>175</td>
<td>1999-01-25</td>
</tr>
<tr>
<td>U05</td>
<td>1007</td>
<td>200</td>
<td>1999-02-08</td>
</tr>
<tr>
<td>U04</td>
<td>1007</td>
<td>225</td>
<td>1999-02-12</td>
</tr>
</tbody>
</table>
<p>The underlying database system has the following referential
integrity constraints:</p>
<ul>
<li>
<p>A foreign key on the BIDS table requires that BIDS.USERID
contains a value that is found in USERS.USERID</p>
</li>
<li>
<p>A foreign key on the BIDS table requires that BIDS.ITEMNO
contains a value that is found in ITEMS.ITEMNO</p>
</li>
</ul>
</div>
<div class="div3">
<h4><a name="rdb-updates-results" id=
"rdb-updates-results"></a>1.1.4 Updates and Results</h4>
<div class="div4">
<h5><a name="rdb-updates-results-u1" id=
"rdb-updates-results-u1"></a>1.1.4.1 Q1</h5>
<p>Add a new user (with no rating) to the users.xml view.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
insert nodes
<user_tuple>
<userid>U07</userid>
<name>Annabel Lee</name>
</user_tuple>
into doc("users.xml")/users
</pre></div>
<p><em>Expected resulting content of users.xml:</em></p>
<div class="exampleInner">
<pre>
<users>
<user_tuple>
<userid>U01</userid>
<name>Tom Jones</name>
<rating>B</rating>
</user_tuple>
<user_tuple>
<userid>U02</userid>
<name>Mary Doe</name>
<rating>A</rating>
</user_tuple>
<em> ... Snip ... </em>
<user_tuple>
<userid>U06</userid>
<name>Rip Van Winkle</name>
<rating>B</rating>
</user_tuple>
<user_tuple>
<userid>U07</userid>
<name>Annabel Lee</name>
</user_tuple>
</users>
</pre></div>
</div>
<div class="div4">
<h5><a name="rdb-updates-results-u2" id=
"rdb-updates-results-u2"></a>1.1.4.2 Q2</h5>
<p>Enter a bid for user Annabel Lee on February 1st, 1999 for 60
dollars on item 1001.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
let $uid :=
doc("users.xml")/users/user_tuple[name="Annabel Lee"]/userid
return
insert nodes
<bid_tuple>
<userid>{data($uid)}</userid>
<itemno>1001</itemno>
<bid>60</bid>
<bid_date>1999-02-01</bid_date>
</bid_tuple>
into doc("bids.xml")/bids
</pre></div>
<p><em>Expected resulting content of bids.xml:</em></p>
<div class="exampleInner">
<pre>
<bids>
<bid_tuple>
<userid>U02</userid>
<itemno>1001</itemno>
<bid>35</bid>
<bid_date>1999-01-07</bid_date>
</bid_tuple>
<bid_tuple>
<userid>U04</userid>
<itemno>1001</itemno>
<bid>40</bid>
<bid_date>1999-01-08</bid_date>
</bid_tuple>
<em> ... Snip ... </em>
<bid_tuple>
<userid>U01</userid>
<itemno>1002</itemno>
<bid>400</bid>
<bid_date>1999-02-14</bid_date>
</bid_tuple>
<em> ... Snip ... </em>
<bid_tuple>
<userid>U04</userid>
<itemno>1007</itemno>
<bid>225</bid>
<bid_date>1999-02-12</bid_date>
</bid_tuple>
<bid_tuple>
<userid>U07</userid>
<itemno>1001</itemno>
<bid>60</bid>
<bid_date>1999-02-01</bid_date>
</bid_tuple>
</bids>
</pre></div>
</div>
<div class="div4">
<h5><a name="rdb-updates-results-u3" id=
"rdb-updates-results-u3"></a>1.1.4.3 Q3</h5>
<p>Insert a new bid for Annabel Lee on item 1002, adding 10% to the
best bid received so far for this item.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
let $uid := doc("users.xml")/users/user_tuple[name="Annabel Lee"]/userid
let $topbid := max(doc("bids.xml")/bids/bid_tuple[itemno=1002]/bid)
return
insert nodes
<bid_tuple>
<userid>{data($uid)}</userid>
<itemno>1002</itemno>
<bid>{$topbid*1.1}</bid>
<bid_date>1999-02-01</bid_date>
</bid_tuple>
into doc("bids.xml")/bids
</pre></div>
<p><em>Expected resulting content of bids.xml:</em></p>
<div class="exampleInner">
<pre>
<bids>
<bid_tuple>
<userid>U02</userid>
<itemno>1001</itemno>
<bid>35</bid>
<bid_date>1999-01-07</bid_date>
</bid_tuple>
<em> ... Snip ... </em>
<bid_tuple>
<userid>U01</userid>
<itemno>1002</itemno>
<bid>400</bid>
<bid_date>1999-02-14</bid_date>
</bid_tuple>
<em> ... Snip ... </em>
<bid_tuple>
<userid>U04</userid>
<itemno>1007</itemno>
<bid>225</bid>
<bid_date>1999-02-12</bid_date>
</bid_tuple>
<em> ... Snip ... </em>
<bid_tuple>
<userid>U07</userid>
<itemno>1002</itemno>
<bid>1320</bid>
<bid_date>1999-03-05</bid_date>
</bid_tuple>
</bids>
</pre></div>
<p>The best bid for item 1002 had been at 1200, thus Annabel's bid
is at 1320.</p>
</div>
<div class="div4">
<h5><a name="rdb-updates-results-u4" id=
"rdb-updates-results-u4"></a>1.1.4.4 Q4</h5>
<p>Set Annabel Lee's rating to B.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
let $user := doc("users.xml")/users/user_tuple[name="Annabel Lee"]
return
if ($user/rating)
then replace value of node $user/rating with "B"
else insert node <rating>B</rating> into $user
</pre></div>
<p><em>Expected resulting content of users.xml:</em></p>
<div class="exampleInner">
<pre>
<users>
<user_tuple>
<userid>U01</userid>
<name>Tom Jones</name>
<rating>B</rating>
</user_tuple>
<user_tuple>
<userid>U02</userid>
<name>Mary Doe</name>
<rating>A</rating>
</user_tuple>
<em> ... Snip ... </em>
<user_tuple>
<userid>U06</userid>
<name>Rip Van Winkle</name>
<rating>B</rating>
</user_tuple>
<user_tuple>
<userid>U07</userid>
<name>Annabel Lee</name>
<rating>B</rating>
</user_tuple>
</users>
</pre></div>
</div>
<div class="div4">
<h5><a name="rdb-updates-results-u5" id=
"rdb-updates-results-u5"></a>1.1.4.5 Q5</h5>
<p>Place a bid for Annabel Lee on item 1007, adding 10% to the best
bid received so far on that item, but only if the bid amount does
not exceed a given limit. The first query illustrates the desired
behavior if the limit is exceeded.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
let $uid := doc("users.xml")/users/user_tuple[name="Annabel Lee"]/userid
let $topbid := max(doc("bids.xml")/bids/bid_tuple[itemno=1007]/bid)
where $topbid*1.1 <= 200
return
insert nodes
<bid_tuple>
<userid>{data($uid)}</userid>
<itemno>1007</itemno>
<bid>{$topbid*1.1}</bid>
<bid_date>1999-02-01</bid_date>
</bid_tuple>
into doc("bids.xml")/bids
</pre></div>
<p><em>Expected resulting content of bids.xml:</em></p>
<div class="exampleInner">
<pre>
<bids>
<bid_tuple>
<userid>U02</userid>
<itemno>1001</itemno>
<bid>35</bid>
<bid_date>1999-01-07</bid_date>
</bid_tuple>
<em> ... Snip ... </em>
<bid_tuple>
<userid>U04</userid>
<itemno>1007</itemno>
<bid>225</bid>
<bid_date>1999-02-12</bid_date>
</bid_tuple>
</bids>
</pre></div>
<p>In the above, adding 10% to the best bid on item 1007 would have
required a bid of 237, which is more than the allowed limit of 200.
Thus, the bids.xml document does not change.</p>
<p>Place a bid for Annabel Lee on item 1007, adding 10% to the best
bid received so far on that item, but only if the bid amount does
not exceed 500. This illustrates the behavior when the resulting
value is within the limit.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
let $uid := doc("users.xml")/users/user_tuple[name="Annabel Lee"]/userid
let $topbid := max(doc("bids.xml")/bids/bid_tuple[itemno=1007]/bid)
where $topbid*1.1 <= 500
return
insert nodes
<bid_tuple>
<userid>{data($uid)}</userid>
<itemno>1007</itemno>
<bid>{$topbid*1.1}</bid>
<bid_date>1999-02-01</bid_date>
</bid_tuple>
into doc("bids.xml")/bids
</pre></div>
<p><em>Expected resulting content of bids.xml</em></p>
<div class="exampleInner">
<pre>
<bids>
<bid_tuple>
<userid>U02</userid>
<itemno>1001</itemno>
<bid>35</bid>
<bid_date>1999-01-07</bid_date>
</bid_tuple>
<em> ... Snip ... </em>
<bid_tuple>
<userid>U04</userid>
<itemno>1007</itemno>
<bid>225</bid>
<bid_date>1999-02-12</bid_date>
</bid_tuple>
<bid_tuple>
<userid>U07</userid>
<itemno>1007</itemno>
<bid>237</bid>
<bid_date>1999-04-01</bid_date>
</bid_tuple>
</bids>
</pre></div>
</div>
<div class="div4">
<h5><a name="rdb-updates-results-u6" id=
"rdb-updates-results-u6"></a>1.1.4.6 Q6</h5>
<p>Erase user Dee Linquent and the corresponding associated items
and bids.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
let $user := doc("users.xml")/users/user_tuple[name="Dee Linquent"]
let $items := doc("items.xml")/items/item_tuple[offered_by=$user/userid]
let $bids := doc("bids.xml")/bids/bid_tuple[userid=$user/userid]
return (
delete nodes $user,
delete nodes $items,
delete nodes $bids
)
</pre></div>
<p>An alternative solution is:</p>
<div class="exampleInner">
<pre>
let $user := doc("users.xml")/users/user_tuple[name="Dee Linquent"]
let $items := doc("items.xml")/items/item_tuple[offered_by=$user/userid]
let $bids := doc("bids.xml")/bids/bid_tuple[userid=$user/userid]
return
delete nodes $user, $items, $bids
</pre></div>
<p>The two solutions above highlight the fact that a list of delete
operations is equivalent to deleting the list of nodes obtained by
concatenating the operands on which the deletes applied.</p>
<p><em>Expected resulting content of items.xml:</em></p>
<div class="exampleInner">
<pre>
<items>
<item_tuple>
<itemno>1001</itemno>
<description>Red Bicycle</description>
<offered_by>U01</offered_by>
<start_date>1999-01-05</start_date>
<end_date>1999-01-20</end_date>
<reserve_price>40</reserve_price>
</item_tuple>
<em> ... Snip ... </em>
<item_tuple>
<itemno>1004</itemno>
<description>Tricycle</description>
<offered_by>U01</offered_by>
<start_date>1999-02-25</start_date>
<end_date>1999-03-08</end_date>
<reserve_price>15</reserve_price>
</item_tuple>
<item_tuple>
<itemno>1007</itemno>
<description>Racing bicycle</description>
<offered_by>U04</offered_by>
<start_date>1999-01-20</start_date>
<end_date>1999-02-20</end_date>
<reserve_price>200</reserve_price>
</item_tuple>
<item_tuple>
<itemno>1008</itemno>
<description>Broken bicycle</description>
<offered_by>U01</offered_by>
<start_date>1999-02-05</start_date>
<end_date>1999-03-06</end_date>
<reserve_price>25</reserve_price>
</item_tuple>
</items>
</pre></div>
<p>In the above, items 1005 and 1006, offered by user Dee Linquent,
have been erased; item 1007 now directly follows item 1004. Notice
that the whole subtrees rooted at the corresponding
<item_tuple> elements have been erased.</p>
<p><em>Expected resulting content of users.xml:</em></p>
<div class="exampleInner">
<pre>
<users>
<user_tuple>
<userid>U01</userid>
<name>Tom Jones</name>
<rating>B</rating>
</user_tuple>
<user_tuple>
<userid>U02</userid>
<name>Mary Doe</name>
<rating>A</rating>
</user_tuple>
<user_tuple>
<userid>U04</userid>
<name>Roger Smith</name>
<rating>C</rating>
</user_tuple>
<em> ... Snip ... </em>
<user_tuple>
<userid>U06</userid>
<name>Rip Van Winkle</name>
<rating>B</rating>
</user_tuple>
</users>
</pre></div>
<p>In the above, user Dee Linquent has been erased.</p>
<p><em>Expected resulting content of bids.xml:</em></p>
<div class="exampleInner">
<pre>
<bids>
<bid_tuple>
<userid>U02</userid>
<itemno>1001</itemno>
<bid>35</bid>
<bid_date>1999-01-07</bid_date>
</bid_tuple>
<bid_tuple>
<userid>U04</userid>
<itemno>1001</itemno>
<bid>40</bid>
<bid_date>1999-01-08</bid_date>
</bid_tuple>
<em> ... Snip ... </em>
<bid_tuple>
<userid>U02</userid>
<itemno>1002</itemno>
<bid>600</bid>
<bid_date>1999-02-16</bid_date>
</bid_tuple>
<bid_tuple>
<userid>U04</userid>
<itemno>1002</itemno>
<bid>1000</bid>
<bid_date>1999-02-25</bid_date>
</bid_tuple>
<em> ... Snip ... </em>
<bid_tuple>
<userid>U04</userid>
<itemno>1007</itemno>
<bid>225</bid>
<bid_date>1999-02-12</bid_date>
</bid_tuple>
</bids>
</pre></div>
<p>No bids had been placed on items 1005 and 1006 offered by user
Dee Linquent. However, Dee Linquent had placed a bid on item 1002;
this bid has been erased.</p>
</div>
<div class="div4">
<h5><a name="rdb-updates-results-u7" id=
"rdb-updates-results-u7"></a>1.1.4.7 Q7</h5>
<p>Add the element <comment>This is a bargain
!</comment> as the last child of the <item> element
describing item 1002.</p>
<p><em>Solution in the XQuery Update Facility</em></p>
<div class="exampleInner">
<pre>
declare revalidation strict;
insert nodes
<comment>This is a bargain !</comment>
as last into doc("items.xml")/items/item_tuple[itemno=1002]
</pre></div>
<p><em>Expected resulting content of items.xml:</em> The same as
the original contents.</p>
<p>The items.xml document is unchanged and an error is raised. This
update can not be applied without rendering the document invalid
with respect to its schema.</p>
</div>
<div class="div4">
<h5><a name="rdb-updates-results-q8" id=
"rdb-updates-results-q8"></a>1.1.4.8 Q8</h5>
<p>Place a bid for Annabel Lee on item 1010, which does not exist
in "items.xml". In this query, we assume that a referential
integrity constraint in the underlying database system requires
that no bid can be placed on an item unless it exists in the
database.</p>
<p><em>Solution in XQuery:</em></p>
<div class="exampleInner">
<pre>
let $uid := doc("users.xml")/users/user_tuple[name="Annabel Lee"]/userid
return
insert nodes
<bid_tuple>
<userid>{data($uid)}</userid>
<itemno>1010</itemno>
<bid>60</bid>
<bid_date>2006-04-23</bid_date>
</bid_tuple>
into doc("bids.xml")/bids
</pre></div>
<p><em>Expected resulting content of bids.xml:</em>the same as the
original contents.</p>
<p>This update violates the previously-mentioned referential
integrity constraint. Therefore, its execution raises a dynamic
error (see <a href=
"http://www.w3.org/TR/xquery/#id-kinds-of-errors">Kinds of
Errors</a> in the XQuery specification).</p>
</div>
<div class="div4">
<h5><a name="rdb-updates-results-u9" id=
"rdb-updates-results-u9"></a>1.1.4.9 Q9</h5>
<p>Add a bid for Annabel Lee on item 1002, at a price 5 dollars
below the current highest bid. A trigger in the underlying database
ensures that a bid cannot be made at a lower price than the highest
bid made so far on that item.</p>
<p><em>Solution in XQuery:</em></p>
<div class="exampleInner">
<pre>
let $uid := doc("users.xml")/users/user_tuple[name="Annabel Lee"]/userid
let $topbid := max(doc("bids.xml")//bid_tuple[itemno=1002]/bid)
return
insert nodes
<bid_tuple>
<userid>{data($uid)}</userid>
<itemno>1002</itemno>
<bid>{$topbid - 5.00}</bid>
<bid_date>2006-04-23</bid_date>
</bid_tuple>
into doc("bids.xml")/bids
</pre></div>
<p><em>Expected resulting content of bids.xml:</em> the same as the
original contents.</p>
<p>This update causes the previously mentioned trigger to return an
error. Therefore, its execution will raise a dynamic error (see
<a href="http://www.w3.org/TR/xquery/#id-kinds-of-errors">Kinds of
Errors</a> in the XQuery specification).</p>
</div>
</div>
</div>
<div class="div2">
<h3><a name="use-case-sync-addrbook" id=
"use-case-sync-addrbook"></a>1.2 Use Case "Address Book" -
synchronizing address book entries</h3>
<p>In this scenario, an address book is synchronized among a
central archive and two local copies. This scenario is inspired by
the Unison file synchronizer. During synchronization, Address book
entries with the same <em>name</em> element are considered to be
the same entry. The order of entries is irrelevant. For simplicity,
we assume that entries may be modified, but not inserted or
deleted. When the two copies are synchronized, their state is saved
into an archival version. Synchronization is performed as
follows:</p>
<ul>
<li>
<p>If an entry in one of the two copies is different from the
archived one, but the other copy matches the archive, the modified
copy is propagated to the archive and to the other copy.</p>
</li>
<li>
<p>If both copies differ from the archive, but they do not both
modify the same element in the entry, or they modify the same
element but the modified elements have the same value, then the
changes from each copy are propagated to both the archive and the
other copy.</p>
</li>
<li>
<p>If the copies have each modified the same entry, but modified it
in different ways, a problem is reported in the log, and neither
the archive nor the copies are changed. (For simplicity, we do not
attempt to merge updates.)</p>
</li>
</ul>
<p>The XQuery Update Facility is sufficient for the problem as
scoped above. For more complex scenarios, the XQuery Scripting
Extensions will simplify programming by allowing variable
assignment and the ability to view the results of prior updates
within a query.</p>
<div class="div3">
<h4><a name="use-case-sync-addrbook-input-data" id=
"use-case-sync-addrbook-input-data"></a>1.2.1 Input Data</h4>
<p>This section describes the data prior to synchronization.</p>
<p><em>archive.xml</em>: The central archive, before
synchronization.</p>
<div class="exampleInner">
<pre>
<archived-agenda>
<last-synch-time>2005-10-05T10:00</last-synch-time>
<entry>
<name>Benjamin</name>
<contact>benjamin@inria.fr</contact>
</entry>
<entry>
<name>Dario</name>
<contact>dario@uni-pisa.it</contact>
</entry>
<entry>
<name>Anthony</name>
<contact>tony@uni-toulon.fr</contact>
</entry>
</archived-agenda>
</pre></div>
<p><em>log.xml</em>: The central log, before synchronization.</p>
<div class="exampleInner">
<pre>
<log>
</log>
</pre></div>
<p><em>copy1.xml</em>: The first modified copy of the address
book.</p>
<p>In this copy, Benjamin's contact has changed from INRIA to
University of Versailles, Dario has moved from University of Pisa
to University of Paris Sud, and Anthony has moved from University
of Toulon to the ENA.</p>
<div class="exampleInner">
<pre>
<agenda-version>
<entry>
<name>Benjamin</name>
<contact>benjamin@uni-versailles.fr</contact>
</entry>
<entry>
<name>Dario</name>
<contact>dario@uni-parissud.fr</contact>
</entry>
<entry>
<name>Anthony</name>
<contact>tony@ena.fr</contact>
</entry>
</agenda-version>
</pre></div>
<p><em>copy2.xml</em>: The second modified copy of the address
book.</p>
<p>In this copy, Benjamin has also moved to University of
Versailles, Dario has not moved, and Anthony has moved to the EHESS
instead of the ENA:</p>
<div class="exampleInner">
<pre>
<agenda-version>
<entry>
<name>Benjamin</name>
<contact>benjamin@uni-versailles.fr</contact>
</entry>
<entry>
<name>Dario</name>
<contact>dario@uni-pisa.it</contact>
</entry>
<entry>
<name>Anthony</name>
<contact>tony@ehess.fr</contact>
</entry>
</agenda-version>
</pre></div>
</div>
<div class="div3">
<h4><a name="addrbook-q1" id="addrbook-q1"></a>1.2.2 Q1</h4>
<p>Synchronize the three logs as described in the description of
this use case.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
for $a in doc("archive.xml")/archived-agenda/entry,
$v1 in doc("copy1.xml")/agenda-version/entry,
$v2 in doc("copy2.xml")/agenda-version/entry
where $a/name = $v1/name
and $v1/name = $v2/name
return
if ($a/contact = $v1/contact and $v1/contact=$v2/contact)
then ()
else
if ($v1/contact = $v2/contact)
then replace value of node $a/contact with $v1/contact
else
if ($a/contact = $v1/contact)
then (
replace value of node $a/contact with $v2/contact,
replace value of node $v1/contact with $v2/contact
)
else
if ($a/contact = $v2/contact)
then (
replace value of node $a/contact with $v1/contact,
replace value of node $v2/contact with $v1/contact
)
else (
insert node
<fail>
<arch>{ $a }</arch>
<v1>{ $v1 }</v1>
<v2>{ $v2 }</v2>
</fail>
into doc("log.xml")/log
)
,
replace value of node doc("archive.xml")/*/last-synch-time
with current-dateTime()
</pre></div>
<p><em>Expected Results:</em></p>
<p><em>Expected results of the agenda synchronization</em>: A
synchronization of the two versions of the agenda made on April
23th, 2006, at noon, should have the following impact on the
archive, versions, and log.</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>In the following XML results, the comments (shown in italic
font) were not created by the update directives, and are not part
of the result documents. They have been added to explain where each
part of a result document comes from.</p>
</div>
<p><em>archive.xml</em></p>
<div class="exampleInner">
<pre>
<archived-agenda>
<last-synch-time>2006-04-23T12:00</last-synch-time>
<entry>
<name>Benjamin</name>
<em> copied from the modified entries </em>
<contact>benjamin@uni-versailles.fr</contact>
</entry>
<entry>
<name>Dario</name>
<em> copied from first modified version </em>
<contact>dario@uni-parissud.fr</contact>
</entry>
<entry>
<name>Anthony</name>
<em>unchanged due to conflict </em>
<contact>tony@uni-toulon.fr</contact>
</entry>
</archived-agenda>
</pre></div>
<p><em>log.xml</em></p>
<div class="exampleInner">
<pre>
<log>
<em> update failure details </em>
<fail>
<arch>
<em> archived agenda version </em>
<entry>
<name>Anthony</name>
<contact>tony@uni-toulon.fr</contact>
</entry>
</arch>
<v1>
<em> first modified version </em>
<entry>
<name>Anthony</name>
<contact>tony@ena.fr</contact>
</entry>
</v1>
<v2>
<em> second modified version </em>
<entry>
<name>Anthony</name>
<contact>tony@ehess.fr</contact>
</entry>
</v2>
</fail>
</log>
</pre></div>
<p><em>copy1.xml</em></p>
<div class="exampleInner">
<pre>
<agenda-version>
<entry>
<name>Benjamin</name>
<em> kept after synchronization </em>
<contact>benjamin@uni-versailles.fr</contact>
</entry>
<entry>
<em> kept after synchronization </em>
<name>Dario</name>
<contact>dario@uni-parissud.fr</contact>
</entry>
<entry>
<em> kept after synchronization failure </em>
<name>Anthony</name>
<contact>tony@ena.fr</contact>
</entry>
</agenda-version>
</pre></div>
<p><em>copy2.xml</em></p>
<div class="exampleInner">
<pre>
<agenda-version>
<entry>
<em> kept after synchronization </em>
<name>Benjamin</name>
<contact>benjamin@uni-versailles.fr</contact>
</entry>
<entry>
<em> value taken from the other modified version </em>
<name>Dario</name>
<contact>dario@uni-parissud.fr</contact>
</entry>
<entry>
<em> kept after synchronization failure </em>
<name>Anthony</name>
<contact>tony@ehess.fr</contact>
</entry>
</agenda-version>
</pre></div>
</div>
</div>
<div class="div2">
<h3><a name="use-case-soap" id="use-case-soap"></a>1.3 Use Case
"SOAP" - processing messages</h3>
<p>This use case processes the message found in Example 1 of the
<a href="#SOAPPrimer">[SOAP Version 1.2 Part 0:Primer]</a> to
produce the message found in Example 2. The original message is not
modified, but the new message is a modified copy of the
original.</p>
<div class="div3">
<h4><a name="use-case-soap-input-data" id=
"use-case-soap-input-data"></a>1.3.1 Input Data</h4>
<p>The input data is taken directly from Example 1 of the <a href=
"#SOAPPrimer">[SOAP Version 1.2 Part 0:Primer]</a>.</p>
<div class="exampleInner">
<pre>
<?xml version='1.0' ?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Header>
<m:reservation
xmlns:m="http://travelcompany.example.org/reservation"
env:role="http://www.w3.org/2003/05/soap-envelope/role/next"
env:mustUnderstand="true">
<m:reference>uuid:093a2da1-q345-739r-ba5d-pqff98fe8j7d
</m:reference>
<m:dateAndTime>2001-11-29T13:20:00.000-05:00
</m:dateAndTime>
</m:reservation>
<n:passenger
xmlns:n="http://mycompany.example.com/employees"
env:role="http://www.w3.org/2003/05/soap-envelope/role/next"
env:mustUnderstand="true">
<n:name>Åke Jógvan Øyvind</n:name>
</n:passenger>
</env:Header>
<env:Body>
<p:itinerary
xmlns:p="http://travelcompany.example.org/reservation/travel">
<p:departure>
<p:departing>New York</p:departing>
<p:arriving>Los Angeles</p:arriving>
<p:departureDate>2001-12-14</p:departureDate>
<p:departureTime>late afternoon</p:departureTime>
<p:seatPreference>aisle</p:seatPreference>
</p:departure>
<p:return>
<p:departing>Los Angeles</p:departing>
<p:arriving>New York</p:arriving>
<p:departureDate>2001-12-20</p:departureDate>
<p:departureTime>mid-morning</p:departureTime>
<p:seatPreference/>
</p:return>
</p:itinerary>
<q:lodging
xmlns:q="http://travelcompany.example.org/reservation/hotels">
<q:preference>none</q:preference>
</q:lodging>
</env:Body>
</env:Envelope>
</pre></div>
<p>Moreover, we assume the dynamic context associates to "airports"
the following sequence:</p>
<div class="exampleInner">
<pre>
<AIRPORT><CITY>New York</CITY><CODE>JFK</CODE></AIRPORT>
<AIRPORT><CITY>New York</CITY><CODE>LGA</CODE></AIRPORT>
<AIRPORT><CITY>New York</CITY><CODE>EWR</CODE></AIRPORT>
<AIRPORT><CITY>Los Angeles</CITY><CODE>LAX</CODE></AIRPORT>
<AIRPORT><CITY>San Francisco</CITY><CODE>SFO</CODE></AIRPORT>
</pre></div>
</div>
<div class="div3">
<h4><a name="soap-q1" id="soap-q1"></a>1.3.2 Q1</h4>
<p>Check to see if the airports are unambiguously specified in the
incoming message. Produce a SOAP response by transforming the
incoming message, modifying the time and date to the current time,
and replacing the body with a request to clarify which airport
should be used for New York City.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
declare namespace
env="http://www.w3.org/2003/05/soap-envelope";
declare namespace
m="http://travelcompany.example.org/reservation";
declare namespace
n="http://mycompany.example.com/employees";
declare namespace
p="http://travelcompany.example.org/reservation/travel";
(: A clarification is needed only if there are no
: airports or more than one for a given city. If
: there is precisely one, there is no need to
: ask for information on that city.
:)
declare function local:airportChoices($city as xs:string)
{
let $airports := collection("airports")[CITY = $city]
return
if (count($airports) = 0)
then
<error> No airports found for {$city}!</error>
else if (count($airports) > 1)
then
<airportChoices>
{
for $c in $airports/CODE
return (string( $c ), " ")
}
</airportChoices>
else ()
};
(: Make sure that each airport is unambiguous. If there is
: more than one airport for a city, ask for clarification.
:
: The primer only shows the error condition, so it is not
: clear what to do if there are no errors. Here, we simply
: return the airports in the itinerary.
:)
declare function local:airports($in as element(env:Envelope))
{
let $departureDeparting :=
$in//p:departure/p:departing
let $departureDepartingAirports :=
collection("airports")[CITY = $departureDeparting]
let $departureArriving :=
$in//p:departure/p:arriving
let $departureArrivingAirports :=
collection("airports")[CITY = $departureArriving]
let $returnDeparting :=
$in//p:return/p:departing
let $returnDepartingAirports :=
collection("airports")[CITY = $returnDeparting]
let $returnArriving :=
$in//p:return/p:arriving
let $returnArrivingAirports :=
collection("airports")[CITY = $returnArriving]
return
if ( count($departureDepartingAirports)=0 or
count($departureDepartingAirports)>1 or
count($departureArrivingAirports)=0 or
count($departureArrivingAirports)>1 or
count($returnDepartingAirports)=0 or
count($returnDepartingAirports)>1 or
count($returnArrivingAirports)=0 or
count($returnArrivingAirports)>1 )
then
<p:itineraryClarification>
<p:departure>
<p:departing>
{ local:airportChoices($departureDeparting) }
</p:departing>
<p:arriving>
{ local:airportChoices($departureArriving) }
</p:arriving>
</p:departure>
<p:return>
<p:departing>
{ local:airportChoices($returnDeparting) }
</p:departing>
<p:arriving>
{ local:airportChoices($returnArriving) }
</p:arriving>
</p:return>
</p:itineraryClarification>
else
<p:itinerary>
<p:departure>
<p:departing>{$departureDeparting}</p:departing>
<p:arriving>{$departureArriving}</p:arriving>
</p:departure>
<p:return>
<p:departing>{$returnDeparting}</p:departing>
<p:arriving>{$returnArriving}</p:arriving>
</p:return>
</p:itinerary>
};
declare variable $msg external;
copy $out := $msg/env:Envelope
modify (
replace value of node $out//m:dateAndTime
with fn:current-dateTime(),
replace node $out//env:Body
with <env:Body>
{ local:airports($out) }
</env:Body>
)
return $out
</pre></div>
<p><em>Expected Result (from <a href="#SOAPPrimer">[SOAP Version
1.2 Part 0:Primer]</a>):</em></p>
<div class="exampleInner">
<pre>
<env:Envelope
xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Header>
<m:reservation
xmlns:m="http://travelcompany.example.org/reservation"
env:role="http://www.w3.org/2003/05/soap-envelope/role/next"
env:mustUnderstand="true">
<m:reference>uuid:093a2da1-q345-739r-ba5d-pqff98fe8j7d
</m:reference>
<m:dateAndTime>2001-11-29T13:35:00.000-05:00
</m:dateAndTime>
</m:reservation>
<n:passenger xmlns:n="http://mycompany.example.com/employees"
env:role="http://www.w3.org/2003/05/soap-envelope/role/next"
env:mustUnderstand="true">
<n:name>Åke Jógvan Øyvind</n:name>
</n:passenger>
</env:Header>
<env:Body>
<p:itineraryClarification
xmlns:p="http://travelcompany.example.org/reservation/travel">
<p:departure>
<p:departing>
<p:airportChoices>
JFK LGA EWR
</p:airportChoices>
</p:departing>
</p:departure>
<p:return>
<p:arriving>
<p:airportChoices>
JFK LGA EWR
</p:airportChoices>
</p:arriving>
</p:return>
</p:itineraryClarification>
</env:Body>
</env:Envelope>
</pre></div>
</div>
</div>
<div class="div2">
<h3><a name="use-case-namespaces" id="use-case-namespaces"></a>1.4
Use Case "Namespaces" - moving elements from one namespace to
another</h3>
<p>This use case shows how (parts of) the elements in a document
may be moved from one namespace to another.</p>
<div class="div3">
<h4><a name="use-case-ns-desc" id="use-case-ns-desc"></a>1.4.1
Description</h4>
<p>An agriculture company and an university research lab are making
a joint proposal to the National Agricultural Research Agency. An
initial proposal has been made by cut and paste out of snippets
provided by the two partners. Before being submitted, the proposal
has to be moved to the National Agricultural Research Agency (NARA)
namespace.</p>
</div>
<div class="div3">
<h4><a name="use-case-ns-schema-grant-app" id=
"use-case-ns-schema-grant-app"></a>1.4.2 Schema for the grant
application</h4>
<p>The grant application document must conform to the following
schema:</p>
<div class="exampleInner">
<pre>
<xsd:schema xmlns:xsd='http://www.w3.org/2001/XMLSchema'
targetNamespace="http://www.anr.fr/nara"
elementFormDefault="qualified">
<xsd:element name='grant'>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref='name'/>
<xsd:element ref='lab' minOccurs='0' maxOccurs='unbounded'/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='lab'>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref='address' minOccurs='0' maxOccurs='1'/>
<xsd:choice minOccurs='0' maxOccurs='unbounded'>
<xsd:element ref='researcher'/>
<xsd:element ref='PhD'/>
<xsd:element ref='engineer'/>
<xsd:element ref='lab' minOccurs="0" maxOccurs="unbounded"/>
</xsd:choice>
</xsd:sequence>
<xsd:attribute name='name' type='xsd:string' use='required'/>
</xsd:complexType>
</xsd:element>
<xsd:element name='PhD'>
<xsd:complexType>
<xsd:attribute name='advisor' type='xsd:IDREF' use='required'/>
</xsd:complexType>
</xsd:element>
<xsd:element name='researcher'>
<xsd:complexType>
<xsd:attribute name='rid' type='xsd:ID' use='required'/>
<xsd:attribute name='name' type='xsd:string' use='required'/>
<xsd:attribute name='position' type='xsd:string' use='required'/>
</xsd:complexType>
</xsd:element>
<xsd:element name='engineer'>
<xsd:complexType>
<xsd:attribute name='name' type='xsd:string' use='required'/>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</pre></div>
</div>
<div class="div3">
<h4><a name="ns-input-data" id="ns-input-data"></a>1.4.3 Input
Data</h4>
<p>The initial draft produced by the participants, "grant.xml", has
the following content. The use of namespaces reflects the
cut-and-paste approach used to create it:</p>
<div class="exampleInner">
<pre>
<?xml version='1.0' ?>
<grant xmlns:nara="http://www.anr.fr/nara">
<nara:lab name="AgroPlus">
<nara:address>Saclay, France</nara:address>
<nara:researcher rid="r1" name="Fred"
position="technical staff"/>
<nara:researcher rid="r2" name="Liz"
position="lab assistant" />
<coop:PhD
xmlns:coop="http://www.gouv.fr/univ-industry-coop/"
name="Marie" advisor="r1"/>
<agro:lab xmlns:agro="http://www.agroplus.com"
name="Dairy Dept">
<agro:engineer name="Marc"/>
</agro:lab>
</nara:lab>
<univ:lab xmlns:univ="http://www.education.gouv.fr"
name="Food Engineering Dept, Orsay U.">
<univ:address>Orsay, France</univ:address>
<univ:researcher rid="r3" name="Henry"
position="associate professor"/>
<univ:PhD name="Robert" advisor="r3"/>
<PhD name="Julia" advisor="r1"/>
</univ:lab>
</grant>
</pre></div>
</div>
<div class="div3">
<h4><a name="ns-q1" id="ns-q1"></a>1.4.4 Q1</h4>
<p>Move all elements into the NARA namespace
("http://www.anr.fr/nara").</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
declare namespace nara = "http://www.anr.fr/nara";
for $e in doc("grant.xml")//*
where not (namespace-uri($e) eq "http://www.anr.fr/nara")
return
rename node $e
as QName("http://www.anr.fr/nara",
concat("nara:",local-name($e)))
</pre></div>
<p><em>Expected Result:</em></p>
<div class="exampleInner">
<pre>
<nara:grant xmlns:nara="http://www.anr.fr/nara">
<nara:lab name="AgroPlus">
<nara:address>Saclay, France</nara:address>
<nara:researcher rid="r1" name="Fred"
position="technical staff"/>
<nara:researcher rid="r2" name="Liz"
position="lab assistant" />
<nara:PhD
xmlns:coop="http://www.gouv.fr/univ-industry-coop/"
name="Marie" advisor="r1"/>
<nara:lab name="Dairy Dept">
<nara:engineer name="Marc"/>
</nara:lab>
</nara:lab>
<nara:lab name="Food Engineering Dept, Orsay U.">
<nara:address>Orsay, France</nara:address>
<nara:researcher rid="r3" name="Henry"
position="associate professor"/>
<nara:PhD name="Robert" advisor="r3"/>
<nara:PhD name="Julia" advisor="r1"/>
</nara:lab>
</nara:grant>
</pre></div>
</div>
</div>
<div class="div2">
<h3><a name="use-case-parts" id="use-case-parts"></a>1.5 Use case
"Parts" - modifying recursive documents</h3>
<p>This use case illustrates modifications to documents having a
recursive structure.</p>
<div class="div3">
<h4><a name="use-case-parts-input" id=
"use-case-parts-input"></a>1.5.1 Input data</h4>
<p>Each update in this use case applies on the following documents.
In these examples, we assume each update is applied to a fresh copy
of the original data.</p>
<p>Document "part-tree.xml":</p>
<div class="exampleInner">
<pre>
<parttree>
<part partid="0" name="car">
<part partid="1" name="engine">
<part partid="3" name="piston"/>
</part>
<part partid="2" name="door">
<part partid="4" name="window"/>
<part partid="5" name="lock"/>
</part>
</part>
<part partid="10" name="skateboard">
<part partid="11" name="board"/>
<part partid="12" name="wheel"/>
</part>
<part partid="20" name="canoe"/>
</parttree>
</pre></div>
<p>Document "part-list.xml":</p>
<div class="exampleInner">
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?>
<partlist>
<part partid="0" name="car"/>
<part partid="1" partof="0" name="engine"/>
<part partid="2" partof="0" name="door"/>
<part partid="3" partof="1" name="piston"/>
<part partid="4" partof="2" name="window"/>
<part partid="5" partof="2" name="lock"/>
<part partid="10" name="skateboard"/>
<part partid="11" partof="10" name="board"/>
<part partid="12" partof="10" name="wheel"/>
<part partid="20" name="canoe"/>
</partlist>
</pre></div>
</div>
<div class="div3">
<h4><a name="use-case-parts-q1" id="use-case-parts-q1"></a>1.5.2
Q1</h4>
<p>Delete all parts in "part-tree.xml".</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
delete nodes doc("part-tree.xml")//part
</pre></div>
<p><em>Expected resulting document "part-tree.xml":</em></p>
<div class="exampleInner">
<pre>
<parttree/>
</pre></div>
</div>
<div class="div3">
<h4><a name="use-case-parts-q2" id="use-case-parts-q2"></a>1.5.3
Q2</h4>
<p>Delete all parts belonging to a car in "part-tree.xml", leaving
the car itself.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
delete nodes doc("part-tree.xml")//part[@name="car"]//part
</pre></div>
<p><em>Expected resulting document "part-tree.xml":</em></p>
<div class="exampleInner">
<pre>
<parttree>
<part partid="0" name="car"/>
<part partid="10" name="skateboard">
<part partid="11" name="board"/>
<part partid="12" name="wheel"/>
</part>
<part partid="20" name="canoe"/>
</parttree>
</pre></div>
</div>
<div class="div3">
<h4><a name="use-case-parts-q3" id="use-case-parts-q3"></a>1.5.4
Q3</h4>
<p>Delete all parts belonging to a car in "part-list.xml", leaving
the car itself.</p>
<p><em>Solution 1 in the XQuery Update Facility (leveraging
"part-tree.xml"):</em></p>
<div class="exampleInner">
<pre>
for $pt in doc("part-tree.xml")//part[@name="car"]//part,
$pl in doc("part-list.xml")//part
where $pt/@partid eq $pl/@partid
return
delete nodes $pl
</pre></div>
<p><em>Solution 2 (using a recursive updating function):</em></p>
<div class="exampleInner">
<pre>
declare updating function
local:delete-subtree($p as element(part))
{
for $child in doc("part-list.xml")//part
where $p/@partid eq $child/@partof
return (
delete nodes $child,
local:delete-subtree($child)
)
};
for $p in doc("part-list.xml")//part[@name="car"]
return
local:delete-subtree($p)
</pre></div>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>Because this data is not covered by a schema, an implementation
that supports static typing will raise an error for the comparison
<code>$p/@partid eq $child/@partof</code>. This can be solved by
creating a schema for the data and importing it into the query.</p>
</div>
<p><em>Expected Result:</em></p>
<div class="exampleInner">
<pre>
<partlist>
<part partid="0" name="car"/>
<part partid="10" name="skateboard"/>
<part partid="11" partof="10" name="board"/>
<part partid="12" partof="10" name="wheel"/>
<part partid="20" name="canoe"/>
</partlist>
</pre></div>
</div>
<div class="div3">
<h4><a name="use-case-parts-q4" id="use-case-parts-q4"></a>1.5.5
Q4</h4>
<p>Add a radio to the car in "part-tree.xml", using a part number
that hasn't been taken.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
let $next := max(doc("part-tree.xml")//@partid) + 1
return
insert nodes <part partid="{$next}" name="radio"/>
into
doc("part-tree.xml")//part[@partid=0 and @name="car"]
</pre></div>
<p><em>Expected Result:</em></p>
<div class="exampleInner">
<pre>
<parttree>
<part partid="0" name="car">
<part partid="21" name="radio"/>
<part partid="1" name="engine">
<part partid="3" name="piston"/>
</part>
<part partid="2" name="door">
<part partid="4" name="window"/>
<part partid="5" name="lock"/>
</part>
</part>
<part partid="10" name="skateboard">
<part partid="11" name="board"/>
<part partid="12" name="wheel"/>
</part>
<part partid="20" name="canoe"/>
</parttree>
</pre></div>
<p><em>Note:</em>The position of the new element with respect to
its siblings is implementation-dependent. If position is
significant, and the user wants to ensure the element appears last,
for example, "as last" should be used, as in the following
query:</p>
<div class="exampleInner">
<pre>
let $next := max(doc("part-tree.xml")//@partid) + 1
return
insert nodes <part partid="{$next}" name="radio"/>
as last
into doc("part-tree.xml")//part[@partid=0 and @name="car"]
</pre></div>
</div>
<div class="div3">
<h4><a name="use-case-parts-q6" id="use-case-parts-q6"></a>1.5.6
Q6</h4>
<p>The head office has adopted a new numbering scheme. In
"part-tree.xml", add 1000 to all part numbers for cars, 2000 to all
part numbers for skateboards, and 3000 to all part numbers for
canoes.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
for $keyword at $i in ("car", "skateboard", "canoe"),
$parent in doc("part-tree.xml")//part[@name=$keyword]
let $descendants := $parent//part
for $p in ($parent, $descendants)
return
replace value of node $p/@partid with $i*1000+$p/@partid
</pre></div>
<p><em>Expected result:</em></p>
<div class="exampleInner">
<pre>
<parttree>
<part partid="1000" name="car">
<part partid="1021" name="radio"/>
<part partid="1001" name="engine">
<part partid="1003" name="piston"/>
</part>
<part partid="1002" name="door">
<part partid="1004" name="window"/>
<part partid="1005" name="lock"/>
</part>
</part>
<part partid="2010" name="skateboard">
<part partid="2011" name="board"/>
<part partid="2012" name="wheel"/>
</part>
<part partid="3020" name="canoe"/>
</parttree>
</pre></div>
</div>
</div>
<div class="div2">
<h3><a name="use-case-nil" id="use-case-nil"></a>1.6 Use case
"Nil"</h3>
<p>This use case demonstrates transform expressions which construct
modified copies of some data, which must remain valid according to
the original schema. In this use case, keeping the modified copy
valid requires adding an xsi:nil attribute.</p>
<div class="div3">
<h4><a name="use-case-nil-schema" id=
"use-case-nil-schema"></a>1.6.1 XML Schema</h4>
<p>A employees data set is described by the following XML
Schema:</p>
<div class="exampleInner">
<pre>
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema
targetNamespace="http://www.example.com/employees"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xsd:element name="employees">
<xsd:complexType>
<xsd:element name="employee" minOccurs="0"
maxOccurs="unbounded">
<xsd:complexType>
<xsd:attribute name="mgr" type="xsd:boolean"
default="false"/>
<xsd:attribute name="dept" type="xsd:string"/>
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="salary" type="xsd:decimal"
nillable="true"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</pre></div>
</div>
<div class="div3">
<h4><a name="use-case-nil-input-data" id=
"use-case-nil-input-data"></a>1.6.2 Sample input data
("employees.xml")</h4>
<div class="exampleInner">
<pre>
<employees>
<employee mgr="true" dept="Toys">
<name>Smith</name>
<salary>100000</salary>
</employee>
<employee dept="Toys">
<name>Jones</name>
<salary>60000</salary>
</employee>
<employee mgr="true" dept="Shoes">
<name>Roberts</name>
<salary>150000</salary>
</employee>
</employees>
</pre></div>
</div>
<div class="div3">
<h4><a name="use-case-nil-q1" id="use-case-nil-q1"></a>1.6.3
Q1</h4>
<p>Return all managers, omitting their salaries for confidentiality
reasons. The returned document must be valid according to its XML
Schema, so the query adds an xsi:nil attribute with value "true" to
the salary element.</p>
<p><em>Solution in the XQuery Update Facility:</em></p>
<div class="exampleInner">
<pre>
for $e in doc("employees.xml")//employee
where $e/@manager = true()
return
copy $emp := $e
modify (
replace value of node $emp/salary with "" ,
insert nodes (attribute xsi:nil {"true"})
into $emp/salary
)
return $emp
</pre></div>
<p><em>Expected result:</em></p>
<div class="exampleInner">
<pre>
<employee mgr="true" dept="Toys">
<name>Smith</name>
<salary xsi:nil="true"/>
</employee>
<employee mgr="true" dept="Shoes">
<name>Roberts</name>
<salary xsi:nil="true"/>
</employee>
</pre></div>
</div>
</div>
</div>
</div>
<div class="back">
<div class="div1">
<h2><a name="references" id="references"></a>A Normative
References</h2>
<dl>
<dt class="label"><span><a name="xquery" id="xquery"></a>XQuery
1.0</span></dt>
<dd>
<div><a href="http://www.w3.org/TR/xquery/"><cite>XQuery 1.0: An
XML Query Language (Second Edition)</cite></a>, Don Chamberlin,
Anders Berglund, Scott Boag, <em>et. al.</em>, Editors. World Wide
Web Consortium, 14 December 2010. This version is
http://www.w3.org/TR/2010/REC-xquery-20101214/. The <a href=
"http://www.w3.org/TR/xquery/">latest version</a> is available at
http://www.w3.org/TR/xquery/.</div>
</dd>
<dt class="label"><span><a name="xquery-use-cases" id=
"xquery-use-cases"></a>XML Query Use Cases</span></dt>
<dd>
<div><a href="http://www.w3.org/TR/xquery-use-cases/"><cite>XML
Query Use Cases</cite></a>, Jonathan Robie, Don Chamberlin, Peter
Fankhauser, <em>et. al.</em>, Editors. World Wide Web Consortium,
23 March 2007. This version is
http://www.w3.org/TR/2007/NOTE-xquery-use-cases-20070323/. The
<a href="http://www.w3.org/TR/xquery-use-cases/">latest version</a>
is available at http://www.w3.org/TR/xquery-use-cases/.</div>
</dd>
<dt class="label"><span><a name="xquery-update-10-requirements" id=
"xquery-update-10-requirements"></a>XQuery Update Facility 1.0
Requirements</span></dt>
<dd>
<div><a href=
"http://www.w3.org/TR/xquery-update-10-requirements/"><cite>XQuery
Update Facility 1.0 Requirements</cite></a>, Don Chamberlin and
Jonathan Robie, Editors. World Wide Web Consortium, 25 January
2011. This version is
http://www.w3.org/TR/2011/NOTE-xquery-update-10-requirements-20110125/.
The <a href=
"http://www.w3.org/TR/xquery-update-10-requirements/">latest
version</a> is available at
http://www.w3.org/TR/xquery-update-10-requirements/.</div>
</dd>
<dt class="label"><span><a name="xquery-update-10" id=
"xquery-update-10"></a>XQuery Update Facility 1.0</span></dt>
<dd>
<div><a href="http://www.w3.org/TR/xquery-update-10/"><cite>XQuery
Update Facility 1.0</cite></a>, Don Chamberlin, Jonathan Robie,
Michael Dyck, <em>et. al.</em>, Editors. World Wide Web Consortium,
25 January 2011. This version is
http://www.w3.org/TR/2011/PR-xquery-update-10-20110125/. The
<a href="http://www.w3.org/TR/xquery-update-10/">latest version</a>
is available at http://www.w3.org/TR/xquery-update-10/.</div>
</dd>
<dt class="label"><span><a name="SOAPPrimer" id=
"SOAPPrimer"></a>SOAP Version 1.2 Part 0:Primer</span></dt>
<dd>
<div>World Wide Web Consortium. <em>SOAP Version 1.2 Part 0:
Primer</em> W3C Recommendation 24 June 2003. See <a href=
"http://www.w3.org/TR/2003/REC-soap12-part0-20030624/">http://www.w3.org/TR/2003/REC-soap12-part0-20030624/</a>.</div>
</dd>
</dl>
</div>
<div class="div1">
<h2><a name="id-revisions-log" id="id-revisions-log"></a>B Revision
Log (Non-Normative)</h2>
<p>This log records the substantive changes that have been made to
this document since the Working Draft of 8 May 2006. Minor
editorial changes are not included in this log.</p>
<div class="div2">
<h3><a name="id-log-pending" id="id-log-pending"></a>B.1 Changes in
internal WD</h3>
<ul>
<li>
<p>Clarified that the "application constraint" in 1.1.4.8 Q8 is a
database integrity constraint, and added the constraint to the
description of the data, in response to
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3796#add_comment.</p>
</li>
</ul>
</div>
<div class="div2">
<h3><a name="id-log-28aug2007" id="id-log-28aug2007"></a>B.2 28 Aug
2007 Publication</h3>
<ul>
<li>
<p>Clarified that updates for Use Case "R" are cumulative (see
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3567#c1).</p>
</li>
<li>
<p>Fixed update conflict in Use Case "Address", and clarified that
some things would be easier using updates together with the
Scripting Extensions (see
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3578#c1).</p>
</li>
<li>
<p>Fixed several errors in Use Case "SOAP" (see
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3578#c3).</p>
</li>
<li>
<p>Fixed Use Case "R" Q4 so that it tests to see whether a rating
already exists (see
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3578#c4).</p>
</li>
<li>
<p>Fixed Use Case "Parts" Q3, fixing several bugs, see
(http://www.w3.org/Bugs/Public/show_bug.cgi?id=3578#c6).</p>
</li>
</ul>
</div>
</div>
</div>
</body>
</html>