-$Id: Changes,v 1.26 2002-12-09 17:01:03 mike Exp $
+$Id: Changes,v 1.29 2002-12-13 17:46:52 mike Exp $
Revision history for the CQL-Java package.
See the bottom of this file for a list of things still to do.
-0.5 (IN PROGRESS, currently at RC1)
+0.5 (IN PROGRESS, currently at RC2)
- Add an extra back-end method,
- byte[] toType1(Properties config)
+ byte[] toType1BER(Properties config)
which generates an opaque BER-encoded PDU suitable for
forwarding to Z39.50 server as a pasrt of a searchRequest
APDU. This was contributed by Ralph Levan <levan@oclc.org>
+ - Add srw.resultSet support to the toPFQ() method.
+ - Add new resultSetName() method to CQLNode and its
+ subclasses, returning the name of the referenced result-set
+ for a node that is just a result-set reference, and null for
+ anything else.
- Change regression-test rules for Adam's compiler to use his
new front-end cql2xcql instead of the old cqlparse3.
- Change the names of the anchoring properties in
etc/pqf.properties and the CQLTermNode code that examines
them, in accordance with Adam's PQF-renderer's behaviour.
This gives more flexibility in terms of generating
- attributes for end-of-field anchoring.
- - Fix comment in etc/pqf.properties (claimed that the Type-1
- "string" attribute was "phrase"). Just a documentation
- error.
+ attributes for end-of-field anchoring. Various other minor
+ tweaks to the pqf.properties file, mostly to the comments.
- Change the capitalisation of the project name from
"cql-java" to "CQL-Java". That doesn't really make any
difference to anything: in particular, file-names such as
"cql-java.jar" remain the same.
- - Recreate last-in-field support
- - Add srw.resultSet support to the toPFQ() method. I've not
- attempted this for the toType1() method: Ralph will have to
- do it.
0.4 Thu Nov 21 10:09:26 2002
- Add support for the new "phonetic" relation modifier,
--
### Still to do
+ - Test-harness option to use Type1 BER back-end.
+ - Case-insensitive matching for serverChoice and any other
+ special-case qualifiers. (Are the configured qualifiers
+ matched case-insensitively? They should be.)
+ - Prefix-aware matching for serverChoice, so that
+ >x="http://www.loc.gov/zing/srw/dc-indexes/v1.0/" x.resultSet=foo
+ does the right thing.
+ - Extend test-suite for PQF and BER renderers.
+ - Additional test-suite entries for things like
+ case-sensitivity.
+ - Add a new configuration file that allows arbitrary new
+ relations and relation modifiers to be defined.
- Fix the bug where "9x" is parsed as two tokens, a TT_NUMBER
followed by a TT_WORD. The problem here is that I don't
think it's actually possible to fix this without throwing
* Generate multi-word terms
* Generate prefix-mappings
+