C. M. Sperberg-McQueen,
first of all, thanks for your concise feedback!
If I could, I'd tell the database creation dialog to index everything it can parse as XML and ignore the rest. But when the parser encounters ill-formed input, it issues an error message and aborts the creation of the database. (And then the message disappears, so the user doesn't know which file caused the problem. If you could change that, it would be great, but really that's a separate issue.)
Yes, this one is on our todo list; due to performance issues, the rollback of document insertions is avoided in the bulk loading process. In the current version of BaseX, however, the error message should include information on the documents/files that caused the exception.
Alternatively, I'd like to tell the creation dialog to use a filter that accepts either .xml files or .xsd files or .testSet files. But I can't figure out what notation to use for that. Since the example given ("*.xml") looks like a bash wildcard, I've tried "*.xml, *.xsd, *.testSet", and "*.xml,*.xsd,*.testSet" and "*.xml *.xsd *.testSet" and "*.{xml,xsd,testSet}", none of which match any files.
As this feature has been requested by others before, I've now added it, modified the frontend, and committed a new minor, stable release, which you find at
http://basex.org/maven/org/basex/basex/6.1.6/basex-6.1.6.jar
You can either use the GUI or one of the following BaseX commands to create the database on the XSD test suite:
set createfiler *.xml,*.xsd,*.testSet; create db /path/to/testSuite set createfiler "*.xml, *.xsd,*.testSet"; create db "/path/to/testSuite" XSDTestSuite
Guided by http://www.inf.uni-konstanz.de/dbis/basex/commands I then tried
add /home/xmlschema/xsts11/*/*.xsd
in the command area in the GUI, but it tells me the command ADD is not known. (Perhaps this is because I'm still using 5.7; perhaps ADD came later?)
Exactly; the ADD/DELETE commands have been introduced with BaseX 6.0 – and the syntax is subject to change, so your feedback is welcome and will be considered in our next steps. – To benefit from the best performance, however, it's always recommendable to use bulk loading; this is one reason why adding single documents hasn't been enforced in the frontend yet.
Hope this helps, feel free to ask for more, Christian ___________________________
Christian Gruen Universitaet Konstanz Department of Computer & Information Science D-78457 Konstanz, Germany Tel: +49 (0)7531/88-4449, Fax: +49 (0)7531/88-3577 http://www.inf.uni-konstanz.de/~gruen