Support srw.resultSet in toPQF(). NOT yet in toType1()

[cql-java-moved-to-github.git] / Changes

diff --git a/Changes b/Changes
index cbb96f3..06d0cee 100644 (file)
--- a/Changes
+++ b/Changes
@@ -1,9 +1,34 @@
-$Id: Changes,v 1.18 2002-11-20 22:50:18 mike Exp $
+$Id: Changes,v 1.26 2002-12-09 17:01:03 mike Exp $
 
-Revision history for the "cql-java" package.
+Revision history for the CQL-Java package.
 See the bottom of this file for a list of things still to do.
 
-0.4  (IN PROGRESS)
+0.5  (IN PROGRESS, currently at RC1)
+       - Add an extra back-end method,
+               byte[] toType1(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>
+       - 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.
+       - 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,
          including its mapping in "etc/pqf.properties".
        - Make prefix-maps bind loosely, so that ``>dc=x a and b''
@@ -17,8 +42,8 @@ See the bottom of this file for a list of things still to do.
          of either a <searchClause> or a <triple>.
        - Include test/regression/xmlpp.pl in the distribution: this
          may now be used for testing whether a CQL compiler produces
-         _equivalent_ XCQL to the what's in the regression test,
-         rather than requiring byte-identical output.
+         _equivalent_ XCQL to what's in the regression test, rather
+         than requiring byte-identical output.
        - Include the reference XCQL output in the distribution, for
          the regression test suite to run against.
        - Change build process so that javadoc documentation is built
@@ -93,18 +118,12 @@ See the bottom of this file for a list of things still to do.
          followed by a TT_WORD.  The problem here is that I don't
          think it's actually possible to fix this without throwing
          out StreamTokenizer and rolling our own, which we absolutely
-         _don't_ want to do.
-       - Add srw.resultSet support to the toPFQ() method.
-       - Write "overview" file for the javadoc documentation.
+       - Fix term-to-PQF translation to omit empty properties
+         (for the broken Korean server)
+       - Write "package.html" file for the javadoc documentation.
        - Some niceties for the cql-decompiling back-end:
          * Don't emit redundant parentheses.
          * Don't put spaces around relations that don't need them.
-       - Consider the utility of yet another back-end that translates
-         a CQLNode tree into JZKit's representation of a Type-1 query
-         tree.  That would be nice so that CQL could become a JZKit
-         query-type; but you could achieve the same effect by
-         generating PQF, and running that through JZKit's existing
-         PQN-to-Type-1 compiler.
        - Many refinements to the random query generator:
          * Generate relation modifiers
          * Proximity support