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

ZNG July 2003

Subject:

Re: 1.1 Versioning

From:

"Matthew J. Dovey" <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Wed, 30 Jul 2003 15:43:50 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (78 lines)

If we are going to do it this way - I think I would like to drop the
version number from the namespaces. This is going to be messy but we are
going to do it sometime (e.g. when we hit 2.0).

Most webservices to date, do the Rob approach of creating a new
namespace for the new server. A server which supports multiple versions
will do so at different URL endpoints (e.g. http://myserver.org/srw11
for SRW 1.1, http://myserver.org/srw10 for SRW 1.0.

At the moment there aren't any "good" or "well-adopted" strategies for
backwards compatible versions - although I know that some other
webservices are looking at the mechanism I was suggesting.

Matthew 

> -----Original Message-----
> From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]] 
> On Behalf Of Robert Sanderson
> Sent: Wednesday, July 30, 2003 2:46 PM
> To: [log in to unmask]
> Subject: Re: 1.1 Versioning
> 
> On Wed, 30 Jul 2003, Matthew J. Dovey wrote:
> > > How did OAI handle the 1.0, 1.1, 2.0 transitions?
> > "Is version 2.0 of OAI-PMH compatible with earlier versions?
> > OAI-PMH version 2.0 is not backward compatible.  Results from the
> 
> Ralph:
> > Maybe.  But, as the service gets more mature, the changes should be
> > smaller and maybe the choice will become easier.  My hope 
> is for rapid
> > stability.
> 
> I don't think we'd be doing anyone a great disservice by simply
> abandonning 1.0 so long as 1.1 clients can still talk to 1.0 
> servers with
> simple requests.  (By simple, I mean that they don't include 
> any of the
> 1.1 changes)
> 
> So I think we don't increment the namespace at all and all of the new
> fields go in to the existing namespace.  We can increment it at major
> versions if we feel the need.
> 
> That said, I think a version parameter might still be useful, 
> especially
> for SRU, but I'm in two minds about what it should default to.  If we
> abandon 1.0, then we can say that version defaults to the 
> latest release,
> then for the majority of clients and servers it's unneeded.  If it
> defaults to 1.0 then it's required on every transaction just 
> to benefit
> the people who aren't upgrading, which might be no one.
> 
> A 1.0 client can be pretty quickly retrofitted with the 
> version parameter
> to say 'I'm only 1.0 please be gentle' even though it wasn't 
> a valid param
> in 1.0 ... SRU 1.0 servers will simply put it in the unknown 
> fields and
> return a 1.0, but 1.0 SRW servers will fail the request with 
> a SOAP fault.
> The client can always catch that and take off the version parameter I
> suppose. *ponder*
> 
> Rob
> 
> --
>       ,'/:.          Dr Robert Sanderson ([log in to unmask])
>     ,'-/::::.        http://www.o-r-g.org/~azaroth/
>   ,'--/::(@)::.      Special Collections and Archives, extension 3142
> ,'---/::::::::::.    Nebmedes:  telnet: nebmedes.o-r-g.org 7777
> ____/:::::::::::::.                WWW: 
> http://nebmedes.o-r-g.org:8000/
> I L L U M I N A T I
> 
> 

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