LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  September 2002

ZNG September 2002

Subject:

cql relation proposal

From:

Ray Denenberg <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Mon, 30 Sep 2002 13:58:48 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (74 lines)

I propose the following for the cql relation.
Having read everyone's position, I know this won't
completely satisfy anyone, but it seems a
reasonable compromise to me.

dc.title matches (string)     means exact match
dc.title =  (word1 word2 word3)       means
adjacent words
dc.title ~  (word1 word2 word3)       means
similar words
dc.title  *  (word1 word2 word3)      means all
words
dc.title  +   (word1 word2 word3)      means any
words
dc.title stem (word1 word2 word3)   means stem/any
words
dc.title fuzzy (word1 word2 word3)   means
fuzzy/any words

Points
1. There's no reason to say, e.g.:
"dc.title =~ (word1 word2)"  when
"dc.title  ~  (word1 word2)"  will do just fine.
That should solve the problem of what does >~
mean.

2. Further on the equal-sign, that the current cql
definintion says:

relation ::= numeric-relation|"fuzzy"|
"stem"|"relevance"
numeric-relation::="<"|">"|"<="|">="|"="|"<>"

By this definition "=" is a numeric relation.  I
strongly feel that it should either be a numeric
relation or used for strings/words, but not both.
Above it's the latter, which would mean take "="
out of the mathematical relation list. Or can
someone give an example where we need mathematical
equality?  If so then we should come with an
alternative symbol for "=" for word adjacency.

3. Implicit in this proposal is that we don't have
separate (abstract) word and string index names.
i.e. just dc.title, not dc.titleWord and
dc.titleString.  This would apply to all dc
elements. Bath would remain as defined.

4. For stem and fuzzy, I don't know if it should
be any or all (pick one). If it's any, then if you
want to do all you have to construct booleans.

5.
Robert Sanderson wrote:

> Designing CQL such that it maps onto attributes
> rather than being easy to
> understand and construct is counter productive
> IMO.

I see no reason why we can't do both, giving
priority to the latter, and modifying AA if we
find it necessary.  For example I  don't believe
we need to tokenize an anchor (i.e. take it out of
the term) to be able to cite how it maps to
Z39.50.  We simply need to have rules for turning
a cql query into a Z39.50 query.  One of those
rules could be "if there is a left-anchor
character at the beginning of the field, turn that
into first-in-field".


--Ray

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager