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  December 2003

ZNG December 2003

Subject:

Re: requirements and expectations

From:

Mike Taylor <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Tue, 23 Dec 2003 16:05:38 GMT

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (55 lines)

> Date: Tue, 23 Dec 2003 10:19:44 -0500
> From: "Ray Denenberg, Library of Congress" <[log in to unmask]>
>
> I want to know how people feel about how we should state what srw does and
> does not require.  For example, in the result set section:
> http://www.loc.gov/z3950/agency/zing/srw1-1/result-sets.html
>
> "SRW does not require the support of persistent result sets that may be
> accessed by a client in subsequent requests. It does require the server to
> state whether or not it supports them, ....."
>
> I think  the "does not require" part is fine.  However I would prefer
> (second sentence) "It does require..." changed to "It does expect...".

I think the current wording is fine.  A server that does not state
whether or not it supports persistent result sets is not an SRW
server.

> Because I'm not sure where this "requirement" would (or whether it
> should) be expressed.

Right there in the spec!  You just quoted it!

> I would like srw to continue along the lines of publishing a "base
> profile"
>       http://www.loc.gov/z3950/agency/zing/srw1-1/base-profile.html
> and avoiding a formal "conformance" section (the base profile will
> serve effectively as conformance in most cases, that's what
> customers will point vendors to, but for some who want to implement
> less than the base profile, we don't have to deal with the
> philosophical question of whether they're doing srw or not).  And
> this is basically what we agreed to at the September meeting.
>
> Is everyone comfortable with this?

I don't understand why it's preferable to specifying what is and isn't
conforming behaviour.  I can't see the advantage to the world in
having a situation where there are servers out there and no-one's
really sure whether what they're doing is SRW or not.

My personal preference: no conformance section, no base profile, just
the specification itself.  If a server does what specification says,
it's an SRW server, if it doesn't it's not.  Anything else just
confuses the issue.

 _/|_    _______________________________________________________________
/o ) \/  Mike Taylor  <[log in to unmask]>  http://www.miketaylor.org.uk
)_v__/\  "Who needs to worry about a 10^-15 chance of an MD5 collision
         when the chance of the programmer screwing up seems to be
         about fifty-fifty?" -- Mark-Jason Dominus.

--
Listen to my wife's new CD of kids' music, _Child's Play_, at
        http://www.pipedreaming.org.uk/childsplay/

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