[r17271]: apps / doc / data / roadmap.xml Maximize Restore History

Download this file

roadmap.xml    1090 lines (1090 with data), 48.9 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
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: roadmap.xml 17271 2012-10-08 15:00:16Z joewiz $ -->
<roadmap>
<title>eXist: Current State, Features and Roadmap</title>
<comment>Due to size restrictions, longer remarks on some of the listed topics are available in
separate documents. This is indicated with a reference.</comment>
<module>
<name>Document Storage</name>
<part>
<name>File size/complexity limits</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>Tested</test_coverage>
<progress>100</progress>
<event start="2006" end="2007" isDuration="true"/>
<who>wolf</who>
<remark>
<p> The numbering scheme at the core of eXist-db 1.0 did limit the maximum size of a
document to be stored within the database. In eXist releases 1.1 and later this
is fixed.</p>
</remark>
</part>
<part>
<name>Collection storage</name>
<status>Stable_redesign</status>
<priority>High</priority>
<test_coverage>No tests</test_coverage>
<progress>0</progress>
<event start="20071020T000000Z" end="20071020T000000Z" isDuration="true"/>
<who>wolf</who>
<remark>
<p>The current organization of collections and resources causes a number of problems
with respect to (a) locking, (b) query performance, (c) update performance.
Right now, documents are tightly bound to the collection in which they are
contained. Any operation on a document has to go through its parent collection.
As a result, locking and access control becomes quite complex as we need to take
care of the document and the collection.</p>
<p>There's also a direct dependency between the size of a collection (in terms of
the number of documents stored in it) and document update speed. If a collection
has a large number of documents, removing a single document becomes very
slow.</p>
<p>This problem can be solved by physically decoupling documents and
collections:</p>
<ul>
<li>a collection should be modelled as a logical unit, not a physical one.</li>
<li>current integer document ids should be replaced by hierarchical ids, which
model the entire collection/document path.</li>
<li>the link between the resource and the collection is only done through the
hierarchical document id.</li>
<li>locking and access control should be delegated to a central lock manager,
which just contains a map DocumentProxy -&gt; Lock</li>
</ul>
</remark>
</part>
<part>
<name>DOM Redesign</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>Tested</test_coverage>
<progress>100</progress>
<event start="20080201T000000Z" end="20080226T000000Z" task="20" isDuration="true"/>
<who>wolf</who>
<remark>
<p>eXist-db currently uses 2 DOM (document object model) implementations: one for nodes
stored in the db, and a different one for in-memory nodes constructed during an
XQuery. The two models can not be mixed. To process an XQuery expression on an
in-memory node, the query engine needs to create a temporary persistent copy.
This costs performance and did cause stability issues in the past.</p>
<p>To solve those problems, we are currently redesigning the in-memory DOM to
implement the same interfaces as the persistent DOM. The query engine should be
able to mix nodes of both models.</p>
<p class="update">The current SVN trunk can directly evaluate XQuery expressions on
the in-memory DOM, which solves all previous issues and contributes to the
overall stability of the db. Refer to <a href="http://atomic.exist-db.org/blogs/eXist/InMemoryFragments">this
article</a> for details.</p>
</remark>
</part>
<part>
<name>Allow metadata to be associated with a document</name>
<status>Open</status>
<priority>Avg</priority>
<test_coverage>N/A</test_coverage>
<progress>0</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Metadata could include system properties like last-modification date or
user-defined metadata. Preferably, metadata records should be ordinary XML
documents. The format should not be restricted.</p>
</remark>
</part>
</module>
<module>
<name>Indexing</name>
<remark>
<p>Since version 1.2, there are now alternative index configuration methods which
support the optimizer in rewriting a query for best performance. A new modularized
indexing architecture allows to plug in arbitrary new indexes into the indexing
pipeline. A N-gram and a spatial index module were added as prototypes to test the
new architecture.</p>
<p>There will be other index types added in the future, for example:</p>
<ul>
<li> combined path indexes to speed up frequently-used XPath expressions</li>
<li>indexes to support operations on atomic-values, e.g. in order-by expressions or
the distinct-values function</li>
<li>integration of specialized, external index types like the spatial index module
mentioned above.</li>
</ul>
</remark>
<part>
<name>Full text indexing</name>
<status>Beta</status>
<priority>Avg</priority>
<test_coverage>Tested</test_coverage>
<progress>75</progress>
<event start="20070907T000000Z" end="20071112T000000Z" duration="149760" isDuration="true"/>
<who>wolf</who>
<remark>
<p class="update">As of Oct 2008, a <a href="http://atomic.exist-db.org/blogs/eXist/LuceneIndexModule">new full
text index</a> is available. It is based on Lucene and eXist's new
modularized indexing architecture.</p>
</remark>
</part>
<part>
<name>XQuery and XPath Full Text 1.0</name>
<status>Open</status>
<priority>Avg</priority>
<test_coverage>N/A</test_coverage>
<progress>15</progress>
<who/>
<remark>
<p>Implement the W3C's full text extensions to XQuery, probably based on the new
Lucene index module (see above). Many features could be easily implemented on
top of Lucene.</p>
<p>The grammar for the full text extensions has already been merged into the XQuery
parser as part of a Google Summer of Code project and is available in an SVN
branch. It just needs to be filled with life.</p>
</remark>
</part>
<part>
<name>Range indexing</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>Tested</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Indexes on xml:id</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>Tested</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Currently stored in the structural index. Should be moved to the range index.</p>
<p class="update">As of version 1.2.4 and 1.3, xml:id values are stored in the range
index.</p>
</remark>
</part>
<part>
<name>N-gram</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>Tested</test_coverage>
<progress>100</progress>
<event start="20070201T000000Z" end="20070614T000000Z" isDuration="true"/>
<who>wolf</who>
<remark>
<p>When dealing with texts in many non-European languages, the token-based full-text
index produces insufficient results. Tokenization is currently based on Unicode
code points. Most chinese characters, for example, are thus stored as single
tokens. Users have to abuse the near() or phrase() function to search for
character sequences consisting of more than one character, which is quite slow.
It also means that real proximity searches are not available.</p>
<p> An N-gram based index would be much more suitable for these languages. It would
also allow additional functionality to be implemented, e.g. to deal with varying
spellings. The main question is how the N-gram index would integrate
conceptually with the existing full-text functions.</p>
<p class="update">A N-gram index based on the new modularized indexing architecture
is in SVN trunk as of July 2007 and in eXist 1.2 and later releases.</p>
</remark>
</part>
<part>
<name>Integration of other index types (e.g. Spatial indexes, external indexes)</name>
<status>Beta</status>
<priority>Avg</priority>
<test_coverage>N/A</test_coverage>
<progress>75</progress>
<event start="20070201T000000Z" end="20070614T000000Z" isDuration="true"/>
<who/>
<remark>
<p>eXist-db now offers spatial indexes in SVN trunk as of July 2007 and in version 1.2
and later releases.</p>
</remark>
</part>
<part>
<name>Index-support for order-by, distinct-values</name>
<status>Open</status>
<priority>Avg</priority>
<test_coverage>N/A</test_coverage>
<progress>0</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Order-by expressions and other functions that need to access atomized nodes are
not supported by indexes.</p>
</remark>
</part>
<part>
<name>Collation-driven indexing</name>
<status>Open</status>
<priority>Avg</priority>
<test_coverage>N/A</test_coverage>
<progress>0</progress>
<event start="2008" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Maybe part of FT index redesign.</p>
</remark>
</part>
</module>
<module>
<name>Transactions and Recovery</name>
<remark>
<p>The journal log and the recovery manager should be stable and are covered by
extensive tests. However, recovery failures can not be excluded entirely. The tests
can't reproduce every possible real-world scenario.</p>
<p>However, some steps remain for eXist-db to become a fully transactional database system.
Transaction support is currently limited to the functionality needed for crash
recovery. Though we maintain transactions internally, they are currently not exposed
to applications. Also, read operations are not transactional right now.</p>
<p>In order to allow user-defined ACID transactions with support for rollback, all index
files would need to be protected by the journaling log. The required functionality
is basically available, but the feature is currently not regarded as
high-priority.</p>
</remark>
<part>
<name>Journal log</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>Tested</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Recovery</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>Tested</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Internal transaction management</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>Tested</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Transactions are maintained internally, but they are not exposed to applications.
eXist does not yet support full ACID transactions. Read-only operations bypass
the transaction system.</p>
</remark>
</part>
<part>
<name>User-definable transactions</name>
<status>Open</status>
<priority>Low</priority>
<test_coverage>N/A</test_coverage>
<progress>0</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Journal logs are limited to critical data required for recovery. No transaction
rollbacks.</p>
</remark>
</part>
</module>
<module>
<name>Backup / Restore</name>
<part>
<name>Backup / Restore Tool</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>No tests</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Store configuration into backup</name>
<status>Open</status>
<priority>x</priority>
<test_coverage>No tests</test_coverage>
<progress>0</progress>
<who/>
<remark>
<p> The backup utility should also include a copy of the relevant server
configuration files (mainly conf.xml) into the created backup. Settings like
page size, additional XQuery or index modules etc. are important. </p>
</remark>
</part>
<part>
<name>DB repair tool</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>No tests</test_coverage>
<progress>100</progress>
<event start="20080101T000000Z" end="20080124T000000Z" task="19" isDuration="true"/>
<who>wolf</who>
<remark>
<p>Create a DB repair tool which can handle and resolve inconsistencies in the
database structure. It should be possible to recreate the db if at least
dom.dbx, collections.dbx and symbols.dbx are more or less intact. If a single
document is damaged, it could be filtered out.</p>
<p>As of version 1.2.4, eXist-db provides a <a href="http://exist-db.org/backup.html#consistency">consistency check and
repair</a> tool.</p>
</remark>
</part>
</module>
<module>
<name>Configuration</name>
<part>
<name>Dynamic configuration of the database via Java Management Extensions (JMX)</name>
<status>Open</status>
<priority>x</priority>
<test_coverage>No tests</test_coverage>
<progress>0</progress>
<event start="2008" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Main problem: access control and security.</p>
</remark>
</part>
</module>
<module>
<name>Node-level updates</name>
<part>
<name>XUpdate</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>Tested</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>XQuery Update Extensions</name>
<status>Stable_redesign</status>
<priority>x</priority>
<test_coverage>Tested</test_coverage>
<progress>75</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>eXist's XQuery Update Extensions were implemented before the first W3C drafts
were published. The differences between the W3C recommendation and our
implementation are not that big, though there are some subtle differences
concerning the processing model. In fact, the recommendation simplifies a few
issues.</p>
<p>
<a href="http://www.w3.org/TR/xquery-update-10/">http://www.w3.org/TR/xquery-update-10/</a>
</p>
</remark>
</part>
</module>
<module>
<name>Access-Control</name>
<remark>
<p>The currently implemented Unix-like access control scheme is sufficient to protect
resources and collections in a multi-user environment. However, it might be too
coarse-grained for some types of applications. A more dynamic ACL implementation
could help here. Right now, security management forms part of the database core.
This is unnecessary. A more modular architecture would allow different security
managers to be plugged in. It would be the responsibility of the security manager
implementation to handle ACL lists.</p>
<p>Since version 1.1, eXist-db supports the XACML standard for fine-grained access control
to stored XQueries, Java classes etc.</p>
</remark>
<part>
<name>User management</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>No tests</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Access control on resources and collections</name>
<status>Stable_redesign</status>
<priority>Avg</priority>
<test_coverage>No tests</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Need more dynamic ACL structures that can adapt to varying requirements.</p>
</remark>
</part>
<part>
<name>Access control on stored XQueries, XQuery functions and modules</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>incomplete</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Java binding </name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>N/A</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
</module>
<module>
<name>Schema Validation </name>
<part>
<name>Validate document against schema when indexing</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>No tests</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Validate document after node-level updates</name>
<status>Open</status>
<priority>Avg</priority>
<test_coverage>N/A</test_coverage>
<progress>0</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Locate schema's and DTDs stored in database</name>
<status>Beta</status>
<priority>High</priority>
<test_coverage>x</test_coverage>
<progress>90</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Support for catalog files in database</name>
<status>Beta</status>
<priority>High</priority>
<test_coverage>x</test_coverage>
<progress>90</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Manual validation against schema</name>
<status>Beta</status>
<priority>High</priority>
<test_coverage>Tested</test_coverage>
<progress>75</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>XQuery validation features</name>
<status>Open</status>
<priority>Avg</priority>
<test_coverage>N/A</test_coverage>
<progress>0</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Store PSVI with the node tree in the database</name>
<status>Open</status>
<priority>Low</priority>
<test_coverage>N/A</test_coverage>
<progress>0</progress>
<event start="20080201T000000Z" end="20080226T000000Z" task="16" isDuration="true"/>
<who>dizzzz</who>
<remark/>
</part>
<part>
<name>Static typing based on PSVI</name>
<status>Open</status>
<priority>Low</priority>
<test_coverage>N/A</test_coverage>
<progress>0</progress>
<event start="20080201T000000Z" end="20080226T000000Z" task="16" isDuration="true"/>
<who>dizzzz</who>
<remark/>
</part>
<part>
<name>Support for RelaxNG and Schematron</name>
<status>Open</status>
<priority>Low</priority>
<test_coverage>No tests</test_coverage>
<progress>0</progress>
<event start="20080317T000000Z" end="20080409T000000Z" task="24" isDuration="true"/>
<who>dizzzz</who>
<remark/>
</part>
</module>
<module>
<name>XQuery</name>
<remark>
<p>The XQuery engine as well as the standard function libraries should be updated to
align with the XQuery 1.0 recommendation. Basically, almost all core language
features are implemented, excluding schema related features, which are currently
beyond eXist's scope.</p>
<p>XQuery support in eXist-db is covered by the official W3C XQuery Test Suite (XQTS) 1.02.
Implementing the official XQTS XQuery test suite was a top priority in order to
guarantee standard conformance and avoid future regressions.</p>
</remark>
<part>
<name>Core XPath and XQuery</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>tested</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Updated to the XPath 2.0 and XQuery 1.0 recommendations. Stable, excluding
schema-related features.</p>
</remark>
</part>
<part>
<name>XPath and XQuery atomic value types</name>
<status>Stable</status>
<priority>Avg</priority>
<test_coverage>tested</test_coverage>
<progress>99.4</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
</part>
<part>
<name>XPath and XQuery function libraries</name>
<status>Stable</status>
<priority>High</priority>
<test_coverage>tested</test_coverage>
<progress>99.4</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Updated to XPath 2.0 and XQuery 1.0 recommendations. Stable, excluding
schema-related features.</p>
</remark>
</part>
<part>
<name>XPath and XQuery function libraries</name>
<status>Stable</status>
<priority>High</priority>
<test_coverage>tested</test_coverage>
<progress>99.4</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Updated to XPath 2.0 and XQuery 1.0 recommendations.</p>
</remark>
</part>
<part>
<name>XQuery serialization</name>
<status>Stable_redesign</status>
<priority>Avg</priority>
<test_coverage>tested</test_coverage>
<progress>80</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Though we implement most of the serialization options specified in the XQuery and
XSLT serialization spec, some options need to be reworked and should be covered
by tests.</p>
</remark>
</part>
<part>
<name>XQuery test suite ��� XQTS</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>N/A</test_coverage>
<progress>100</progress>
<event start="20070101T000000Z" end="20070730T000000Z" isDuration="true"/>
<who/>
</part>
<part>
<name>XQuery Optimizer</name>
<status>Stable</status>
<priority>High</priority>
<test_coverage>tested</test_coverage>
<progress>90</progress>
<event start="20080515T000000Z" end="20080609T000000Z" task="23" isDuration="true"/>
<who>wolf, perig</who>
<remark>
<p>With the 1.2 release, eXist-db features a new query-rewriting optimizer. It analyzes
the query at compile time and searches for optimizable subexpressions within the
query tree. If it finds an optimizable expression, the optimizer will modify the
query and wrap some special instructions around the optimizable code block.
Together with the new indexing features (see <a href="http://atomic.exist-db.org/wiki/blogs/eXist/NewIndexing">blog
article</a>, the optimizer can achieve dramatic improvements.</p>
<p>However, the optimizer is currently limited to predicate expressions. It does not
optimize e.g. "where" clauses in a FLWOR statement. The query-rewriting should
thus be extended to recognize other types of expressions beyond predicate
statements. In short, we need a better static analysis of the query.</p>
<p>Based on eXist's current indexes, it is also often difficult to decide if a
certain optimization path leads to performance improvements or not. Better index
statistics could help here. Also, there's a wide range of performance
optimizations which could be applied if we had appropriate statistics on node
distribution and frequency.</p>
<p class="update">As of Oct 2008, the current trunk has a statistics module, but it
is not yet used for real optimizations.</p>
</remark>
</part>
<part>
<name>Error reporting</name>
<status>Stable_redesign</status>
<priority>Avg</priority>
<test_coverage>N/A</test_coverage>
<progress>75</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Error reports by the XQuery parser and compiler need to be improved.</p>
</remark>
</part>
<part>
<name>Make function calls tail-recursive</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>70</test_coverage>
<progress>100</progress>
<event start="20070501T000000Z" end="20070502T000000Z" isDuration="true"/>
<who/>
<remark>
<p>Recursive functions may trigger a StackOverflowException. We need to handle
tail-recursion.</p>
<p class="update">No issues with recursive functions have been reported during the
past year. The tail recursion handling is reliable.</p>
</remark>
</part>
<part>
<name>Better Try-Catch</name>
<status>Stable</status>
<priority>Low</priority>
<test_coverage>0</test_coverage>
<progress>0</progress>
<who/>
<remark>
<p> eXist-db already provides a util:catch() function which basically corresponds to a
Java try-catch. The XQuery 1.1 draft also defines try-catch, but more closely
integrated with XQuery. It should not be too difficult to implement this in
eXist. See <a href="http://www.zorba-xquery.com/doc/zorba-0.9.2/zorba/html/trycatch.html">http://www.zorba-xquery.com/doc/zorba-0.9.2/zorba/html/trycatch.html</a>
for some examples. </p>
</remark>
</part>
<part>
<name>XQuery Debugger</name>
<status>Open</status>
<priority>High</priority>
<test_coverage>N/A</test_coverage>
<progress>75</progress>
<event start="20080315T000000Z" end="20080516T120000Z" duration="1440000" task="22" isDuration="true"/>
<who>ljo, dmitriy</who>
<remark>
<p>Remote debugging protocol - <a href="http://www.xdebug.org">DBGp</a></p>
<p>Command line debugger similar to jdb as prototype</p>
<p>Decide which functionality to expose.</p>
</remark>
</part>
<part>
<name>Drop and deprecate xmldb:collection()</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>tested</test_coverage>
<progress>100</progress>
<event start="20070907T000000Z" end="20070910T000000Z" duration="57600" task="5" isDuration="true"/>
<who>delirium</who>
</part>
<part>
<name>Move fn:document() to xmldb:document() and deprecate</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>tested</test_coverage>
<progress>100</progress>
<event start="20070907T000000Z" end="20070910T000000Z" duration="57600" task="6" isDuration="true"/>
<who>perig</who>
</part>
</module>
<module>
<name>XInclude</name>
<status>Stable</status>
<priority>Low</priority>
<test_coverage>No tests</test_coverage>
<progress>80</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>XInclude expansion happens at serialization time. Queries across the included
document fragments are not possible. Stable, but limited.</p>
</remark>
</module>
<module>
<name>Interfaces</name>
<part>
<name>XML:DB API</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>Tested</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>XML-RPC</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>Partially tested</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Exposes the entire database functionality.</p>
</remark>
</part>
<part>
<name>REST</name>
<status>Stable_redesign</status>
<priority>Low</priority>
<test_coverage>Partially tested</test_coverage>
<progress>90</progress>
<event start="20080501T000000Z" end="20080526T000000Z" task="21" isDuration="true"/>
<who>delirium</who>
<remark>
<p>Does not cover administrative functions, e.g. user-management and permissions.
Stable, but further functionality could be exposed.</p>
<p class="update">The XQuery API for Java (XQJ) implementation makes heavy use of
REST and improves the interface in some aspects. However, the XQJ branch has not
yet been merged into trunk.</p>
</remark>
</part>
<part>
<name>SOAP</name>
<status>Stable</status>
<priority>Low</priority>
<test_coverage>No tests</test_coverage>
<progress>90</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
</part>
<part>
<name>Cocoon Integration</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>No tests</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>General functionality tests required</p>
</remark>
</part>
<part>
<name>XQJ XQuery API for Java (JSR-225)</name>
<status>Beta</status>
<priority>Low</priority>
<test_coverage>N/A</test_coverage>
<progress>70</progress>
<event start="20071126T000000Z" end="20080114T000000Z" task="17" isDuration="true"/>
<who>allad, perig, ljo, dizzzz</who>
<remark>
<p>A nearly finished implementation of the XQuery API for Java (XQJ) is available in
SVN. It was started as a Google Summer of Code project in 2007 and provides two
XQJ drivers, one for embedded database access, one for remote access.</p>
<p>I recently invested some time to bring the branch into sync with the current
trunk. The remote database driver, which is based on the REST-style HTTP
interface of eXist, should already be pretty usable. The embedded driver needs
some redesign though (it breaks the test suite). However, it should not be too
much work to fix this and finally merge it into trunk. Open Tasks:</p>
<ul>
<li>integrate the official XQJ test suite</li>
<li>test for standard conformance</li>
<li>fix the embedded database driver</li>
<li>merge into trunk</li>
<li>performance tests</li>
</ul>
</remark>
</part>
<part>
<name>XForms filter</name>
<status>Beta</status>
<priority>Low</priority>
<test_coverage>N/A</test_coverage>
<progress>80</progress>
<event start="20070907T000000Z" end="20071015T000000Z" task="8" isDuration="true"/>
<who>delirium</who>
<remark/>
</part>
</module>
<module>
<name>Documentation</name>
<part>
<name>XQuery stored modules</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>N/A</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>calling XQuery scripts stored in the DB; import stored modules into a query
passed to the DB.</p>
</remark>
</part>
<part>
<name>WebDAV</name>
<status>Beta</status>
<priority>Avg</priority>
<test_coverage>N/A</test_coverage>
<progress>90</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Deployment</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>N/A</test_coverage>
<progress>100</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Integration with a servlet engine, Cocoon, stand-alone server, embedded use.</p>
</remark>
</part>
<part>
<name>Index creation, index configuration and query rewriting</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>N/A</test_coverage>
<progress>100</progress>
<event start="20071001T000000Z" end="20071018T000000Z" task="10" isDuration="true"/>
<who/>
<remark/>
</part>
<part>
<name>Validation</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>N/A</test_coverage>
<progress>100</progress>
<event start="20070907T000000Z" end="20070926T000000Z" task="4" isDuration="true"/>
<who>dizzzz</who>
<remark/>
</part>
<part>
<name>Trigger</name>
<status>Beta</status>
<priority>Low</priority>
<test_coverage>N/A</test_coverage>
<progress>0</progress>
<event start="20071210T000000Z" end="20071210T000000Z" task="9" duration="57600" isDuration="true"/>
<who>delirium</who>
<remark/>
</part>
<part>
<name>Searchable Documentation</name>
<status>Stable</status>
<priority>x</priority>
<test_coverage>N/A</test_coverage>
<progress>100</progress>
<who>wolf</who>
<event start="20071020T000000Z" end="20071031T000000Z" isDuration="true"/>
<remark>
<p>The documentation that comes with eXist-db should be made searchable. I started
working on a search interface which is based on eXist's own full text search
features.</p>
<p class="update">As of Oct. 2008, a <a href="http://demo.exist-db.org/search.xql">search function</a> is provided. It requires features only available in SVN
trunk though.</p>
</remark>
<who/>
</part>
<part>
<name>XQDoc integration</name>
<status>Alpha</status>
<priority>High</priority>
<test_coverage>Partially tested</test_coverage>
<progress>60</progress>
<event start="20071101T000000Z" end="20071126T000000Z" task="3" duration="" isDuration="true"/>
<who>ljo, wolf</who>
<remark>
<p>Migrate the function documentation to XQDoc. Use XQDoc to better document all
XQuery examples.</p>
</remark>
</part>
</module>
<module>
<name>Releases</name>
<part>
<name>1.2</name>
<status>Stable</status>
<priority>High</priority>
<test_coverage>N/A</test_coverage>
<progress>99</progress>
<event start="20071214T000000Z" end="20071214T000000Z" task="12" isDuration="false"/>
<who/>
<remark>
<p>Imperative release with new features from 2006���2007 to replace version 1.0-line.
The last release based on Java 1.4.</p>
</remark>
</part>
<part>
<name>1.4</name>
<status>Open</status>
<priority>Low</priority>
<test_coverage>N/A</test_coverage>
<progress>0</progress>
<event start="20080615T000000Z" end="20080615T000000Z" task="25" isDuration="false"/>
<who/>
<remark>
<p>Based on Java 5.</p>
</remark>
</part>
</module>
<module>
<name>Other Tasks</name>
<part>
<name>Complete New Sandbox Application</name>
<status>Beta</status>
<priority>Avt</priority>
<test_coverage>N/A</test_coverage>
<progress>70%</progress>
<event start="20071101T000000Z" end="20071122T000000Z" task="15" duration="460800" isDuration="true"/>
<who>wolf</who>
<remark>
<p> Some time ago we did a major rewrite of the sandbox application: <a href="http://demo.exist-db.org/sandbox2/sandbox.xql">http://demo.exist-db.org/sandbox2/sandbox.xql</a> It is nearly usable, but
the syntax-highlighting editor component is limited. In particular, it has no
support for safari. Also, the sandbox still uses util:eval to execute the
entered XQuery code. This works well for simple queries, but can have
side-effects if the query imports external modules or tries to access the http
context. For the purpose of the sandbox, it would be better to post the
user-supplied query to a dedicated servlet, which executes the code and sends
back a result. </p>
</remark>
</part>
<part>
<name>I18n</name>
<status>Open</status>
<priority>Low</priority>
<test_coverage>N/A</test_coverage>
<progress>20</progress>
<event start="20071020T000000Z" end="2008" isDuration="true"/>
<who/>
<remark>
<p>Provide translations for error messages, console outputs etc. At least, resource
bundles should be used, so others can translate them if they want.</p>
</remark>
</part>
<part>
<name>Clean up/upgrade libraries</name>
<status>Beta</status>
<priority>Low</priority>
<test_coverage>N/A</test_coverage>
<progress>60</progress>
<event start="20071212T000000Z" end="20071213T000000Z" isDuration="true"/>
<who/>
<remark>
<p>All libraries included with eXist need to be checked.</p>
</remark>
</part>
<part>
<name>Move to Java 5</name>
<status>Open</status>
<priority>Low</priority>
<test_coverage>N/A</test_coverage>
<progress>0</progress>
<event start="20071215T000000Z" end="20071215T000000Z" isDuration="false"/>
<who/>
<remark>
<p>Change build taget in switch for development branch 1.3 to Java 5 after eXist
version 1.2 is released.</p>
<p>This will make some more stuff easier. Especially since the jmx monitors and
junit 4 tests are by requirements targeted for Java 5 already.</p>
</remark>
</part>
<part>
<name>Move to ANTLR3 parser</name>
<status>Instable</status>
<priority>High</priority>
<test_coverage>N/A</test_coverage>
<progress>60</progress>
<event start="20080110T000000Z" end="20080228T000000Z" task="14" isDuration="true"/>
<who>ljo</who>
<remark>
<p>Change the parser to ANTLR3 which is better performant, LL* lookahead capable and
processes whitespace in a better manner than ANTLR2 which we currently are
using.</p>
<p>Maybe use gunit for testing?</p>
</remark>
</part>
<part>
<name>Move to AtomicWiki</name>
<status>Stable</status>
<priority>High</priority>
<test_coverage>N/A</test_coverage>
<progress>100</progress>
<event start="20071101T000000Z" end="20071122T000000Z" task="15" duration="460800" isDuration="true"/>
<who>wolf</who>
<remark>
<p>Change from the current spam-ridden and unmaintained wiki to our own Atom-based
AtomicWiki.</p>
</remark>
</part>
</module>
<legend>
<title>Legend</title>
<status>
<name>Open</name>
<description>Not yet started</description>
</status>
<status>
<name>Instable</name>
<description>Some work is necessary</description>
</status>
<status>
<name>Alpha</name>
<description>Implemented, but not tested</description>
</status>
<status>
<name>Beta</name>
<description>Tested, but not finished</description>
</status>
<status>
<name>Stable_redesign</name>
<description>Basically stable, but redesign might be necessary</description>
</status>
<status>
<name>Stable</name>
<description>No further work needed</description>
</status>
<progress>
<name>Percentage</name>
<description>Percentage of completion</description>
</progress>
<priority>
<name>Highest</name>
<description>Very important</description>
</priority>
<priority>
<name>High</name>
<description>Important</description>
</priority>
<priority>
<name>Avg</name>
<description>Nice to have</description>
</priority>
<priority>
<name>Low</name>
<description>Not very important</description>
</priority>
<priority>
<name>x</name>
<description>Not yet decided</description>
</priority>
</legend>
</roadmap>