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: Betr.: SRW/U/CQL Proposals for next version

From:

Mike Taylor <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Wed, 1 Jun 2005 14:58:50 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (57 lines)

> Date: Wed, 1 Jun 2005 14:56:17 +0200
> From: Theo van Veen <[log in to unmask]>
>
> Feedback on SRU 1.2 proposals:

Thanks for this, Theo.

> - For level 0 conformance I would prefer to let it be the clients
> responsibility not to send unsupported queries. Level 0 should lower
> the implementation barrier and the requirement that a diagnostic is
> returned for unsupported queries requires the query to be parsed
> only for the diagnostics and not for functionality.

No, that's not the intention.  The idea is that all the server is
required to do is check that the query is a legitimate single-term
query (e.g. either contains no spaces and quotes, or is surrounded by
quotes with all internal quotes bashslash-escaped) -- and throw tyhe
"unsupported query" diagnostic if not.  This can be done with a regexp
or two: the goal of Level Zero was specifically to make it possible
for servers to claim _some_ degree of SRW conformation without needing
a CQL parser.

> - I would prefer the exchoed request to be very strongly recommended
> to allow clients to rely on it. I found that the use of Mozilla
> extensions that support SRU queries can become quite powerful when
> some context information can be "stored" in the response via the
> echoed request data.

I have no feeling on this one way or the other.

> I have an additional proposal:
>
> I expect that the availability of recordSchema's can be record
> specific. An optional field indicating for a record the possible
> recordSchema's would allow the client to request the right
> recordSchema.

This sounds like an excellent candidate for an extension.

> As nextRecordPosition is eliminated the use of recordPosition should
> be recommended very strongly. Besides that it makes it easier for
> clients to handle situations that a record is skipped for example
> because it is not available in the right recordShcema.

Sounds reasonable enough to me.  (Although of course servers may not
just omit records -- they must replace them with surrogate diagnostic
records.)

 _/|_    ___________________________________________________________________
/o ) \/  Mike Taylor  <[log in to unmask]>  http://www.miketaylor.org.uk
)_v__/\  "_Apatosaurus_ sort of looks like a pro wrestler when most of
         the other sauropods tend to look like ballerinas" -- Matt Wedel.

--
Listen to free demos of soundtrack music for film, TV and radio
        http://www.pipedreaming.org.uk/soundtrack/

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