Remove old proximity-specific parsing code.

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

diff --git a/Changes b/Changes
index e20ba63..536515e 100644 (file)
--- a/Changes
+++ b/Changes
@@ -1,9 +1,37 @@
-$Id: Changes,v 1.28 2002-12-12 15:03:50 mike Exp $
+$Id: Changes,v 1.36 2007-06-27 22:44:13 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 RC2)
+1.0  [IN PROGRESS]
+       - Support for CQL version 1.2 as described at
+          http://www.loc.gov/standards/sru/next-version.html
+         based on support for version 1.1 as described at
+          http://www.loc.gov/standards/sru/cql/
+         Since this is a significant leap forward, the version
+         numbering increases to the next major version.
+       - "Qualifiers" renamed as "indexes" throughout, to match what
+         is now universal CQL terminology.
+
+       PLEASE NOTE THE FOLLOWING INCOMPATIBLE API CHANGES
+       - The class UnknownQualifierException is replaced by
+         UnknownIndexException.
+       - The CQLTermNode method getQualifier() is replaced by
+         getIndex().
+
+0.7  Thu Sep  4 22:51:11 2003
+       - Support for profiled relations and relation modifiers:
+         recognise any non-key word as a relation or modifier, 
+         rejecting those that are not of the form <prefix>.<name>
+         since these must be explicitly tied to a "context" (what
+         used to be called a qualifier-set or index-set).
+
+0.6  Tue Jul 29 23:33:56 2003
+       - Include Ralph's fix for CQLTermNode::toType1BER() to prevent
+         it surrounding multi-word terms in quotes when encoded into
+         BER packet.
+
+0.5  Wed Feb  5 15:50:57 2003
        - Add an extra back-end method,
                byte[] toType1BER(Properties config)
          which generates an opaque BER-encoded PDU suitable for
@@ -113,6 +141,18 @@ See the bottom of this file for a list of things still to do.
 --
 
 ### 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
@@ -133,3 +173,4 @@ See the bottom of this file for a list of things still to do.
          * Generate multi-word terms
          * Generate prefix-mappings
 
+