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  August 2008

ZNG August 2008

Subject:

SRU/CQL 2.0: Invitation to participate in OASIS SWS TC Development

From:

"Ray Denenberg, Library of Congress" <[log in to unmask]>

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Wed, 27 Aug 2008 14:42:28 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (92 lines)

SRU Implementors:

The OASIS Search Web Services Technical Committee (SWS TC) invites your
participation in the development of SRU/CQL 2.0.

We have begun accumulating suggestions for 2.0 features; additional
suggestions are welcome.  We are also currently gathering requirements for
geospatial  and LOM applications.

 Among the suggested 2.0 features are:

1. Allow Non-XML Record Representations
Many formats do not map easily into XML, for example multimedia, images, and
even complex text formats. The suggestion is to allow non-xml serialized
data in the response, as well as value by reference. These would be signaled
by additional values for the recordPacking parameter. For example
recordPacking="base64" or recordPacking="uri".

2. Proximity
 deprecate the PROX BOOLEAN operator and instead represent proximity by two
methods:

 -- Adding a relation: 'window'.
examples:
 * dc.title window/distance<5/unit=word "fries salt vinegar"
  (fries, salt, and vinegar all within a span of 5 words)
 *dc.title window/distance<5/unit=word ((fish and fries) and (salt or
vinegar))
 (fish and chips and one of salt or vinegar, in a 5 word window)
 * dc.title window/distance=2/unit=word/ordered "fries salt "
 (fries followed by salt with 2 words between)

-- Adding a boolean modifier 'prox' which acts the same as the current
boolean, however can be attached to either AND (the current style of
proximity) or  NOT for negative proximity.
Example:
* "fish and" not/prox chips
   ("fish and" followed by anything other than chips)



3. Faceted Searching ("scan" a result set)
One might search a library database for books about a particular topic, and
then see how many records there are in different time period


4. Result Set Size
Allow the client to indicate how much effort the server should take to
determine or estimate the number of records in the result set. Similarly,
allow the response to estimate accuracy of  the result-set-size reported.
The server may be able to determine the exact number of records, or provide
a realistic estimate, but it may be an expensive process. The server might
prefer not go through that process unless the client requests that it does
so. Or the client might want to explicitly request that the server go
through, or not go through, that process. The client might want the first 10
records, or any 10 records, regardless of how many records there are. In
that case if the server goes through the process of determining how many
records there are, it may go through an expensive process for nothing. There
is also the special case where the server cannot determine or estimate the
number of records in the result set. In that case it might be useful to have
a special value or some way to indicate this condition.


5. Multiple Query Types
CQL is currently the only query type used by SRU but there could be other
query types as well, for example, Parameterized Query and XQuery.


6.  Eliminate the Version and Operation Parameters
These two parameters  are based on the assumption that the same base URL
might be used for different operations and versions. Instead, different base
URLs should be used.


7. Alternative Response Formats
Allow the client to request that the response be supplied in a specific
format, for example ATOM.


********

We invite those interested in the development of 2.0 to join the committee.
However all of these (and further) proposed features will be discussed on
this list, as well as on the public OASIS listserv for the Committee.  So if
you are unable to join the committee there is still ample opportunity to
participate.

Rob Sanderson will be the lead Technical Committee member for this 2.0
activity.

--Ray Denenberg

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