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  June 2005

ZNG June 2005

Subject:

Re: Proposals for next version

From:

"Oldroyd, Bill" <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Tue, 21 Jun 2005 12:26:34 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (96 lines)

Ray,

This may be too late for your discussions. However my comments are :

CQL. 1. While I recognise that many SRU/W applications will be
generating the query by software, my principal interest is with queries
entered directly by the user. A main issue is that CQL does not allow
queries to comprise more than one term without the terms being enclosed
in quotes. Using quotes in this way is not familiar to most users. The
manner in which CQL query is parsed should reflect this.

CQL 2. The use of commonly occurring terms "all", "any" etc. to define
operations and indexes is again confusing to most users. Google and MSN
set an example in tokenising the functions by adding a colon at the end
of the word, e.g. site: . I think it would be better is we followed this
example in CQL. I realise that index names are set in Explain so this
can be achieved at present, but I suggest we make it a recommendation.

CQL 3. We have started to create records that contain structure or
contain links to related records, for example a bound volume of
manuscripts containing a manuscript containing an illustration. It is
not clear to me if CQL contains functions which would allow a search to
match attributes in all three objects, for example "bound volume of
manuscripts with provenance x, manuscripts created in the y, with
illustrations containing z". I wonder if implementations of FRBR will
require similar queries against works, expressions and manifestations
and make this a more pressing requirement.

[In general terms I think this means a search must be expressed as
record type X with attribute Y has relation of type Z to record type A
with attribute B.]

CQL 4. I am not sure about the purpose of "level". If some search
services require a simpler language then I think it better to define
that language separate for CQL and offer it as a parameter in the
Explain response. Perhaps this is a way of dealing with my request in
CQL 1.

SORT  - OK.

Record Identifier. - OK

NextRecordPosition - No, because it is tedious to find this number using
XSLT and it is easy for the server to add it to the response. (But I
wouldn't die for it :-))

Client and server identifiers. Not sure what this means, but if it means
that a response should include the URL of the server I am strongly for
this as otherwise if copies of a response are moved or processed outside
the context in which they were obtained, there is no way of knowing
where the response came from.

RecordXPath. I am not aware of the proposal.

XCQL Parameter. OK.

---

I hope the Forum is a success. I am sorry I cannot join in this time.

Bill


-----Original Message-----
From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]] On Behalf
Of Ray Denenberg, Library of Congress
Sent: 15 June 2005 18:36
To: [log in to unmask]
Subject: Proposals for next version

Please note that there are proposals on the table for the next version
of
SRW/U/CQL (either 1.2 or 2.0). See
http://www.loc.gov/z3950/agency/zing/srw/next-version.html

These are on the agenda for discussion at the ZING Forum next week in
Chicago.



--Ray

**************************************************************************
 
Experience the British Library online at www.bl.uk
 
Help the British Library conserve the world's knowledge. Adopt a Book. www.bl.uk/adoptabook
 
**************************************************************************
 
The information contained in this e-mail is confidential and may be legally privileged. It is intended for the addressee(s) only. If you are not the intended recipient, please delete this e-mail and notify the [log in to unmask] : The contents of this e-mail must not be disclosed or copied without the sender's consent. 
 
The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the British Library. The British Library does not take any responsibility for the views of the author. 
 
**************************************************************************

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