W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 1997

RE: Server-generated version ids

From: Barbara Bazemore <barbarab@pcdocs.com>
Date: Fri, 23 May 1997 16:29:06 -0400
Message-ID: <c=US%a=_%p=pcdocs%l=EXCHANGE-BOS-970523202906Z-1958@exchange-tlh.pcdocs.com>
To: "'Larry Masinter'" <masinter@parc.xerox.com>, "'Yaron Goland'" <yarong@microsoft.com>
Cc: "'w3c-dist-auth@w3.org'" <w3c-dist-auth@w3.org>
I believe people writing clients would be well served with a variation 
of Larry's suggested requirement:

	"A client with appropriate access rights shall be able to save a 
document on the server using a standard request. The server may use an 
existing URL or generate a new one to uniquely describe the saved 
document.  In either case, the server must provide an easy, standard 
way for the client to discover the URL of the document that was 

From:  Yaron Goland [SMTP:yarong@microsoft.com]
Sent:  Thursday, May 22, 1997 10:04 PM
To:  Barbara Bazemore; 'Larry Masinter'
Cc:  'w3c-dist-auth@w3.org'
Subject:  RE: Server-generated version ids

We can't even be sure there will be version IDs. There is absolutely 
requirement for one in DAV because all versions are required to be
uniquely identified by URLs. This is the sort of issue that needs to 
argued out in implementation. The requirement is that Versions must 
identifiable by a URL, it is up to the spec to decide if having two
identifiers is useful.

> -----Original Message-----
> From:	Larry Masinter [SMTP:masinter@parc.xerox.com]
> Sent:	Wednesday, May 21, 1997 8:45 AM
> To:	Barbara Bazemore
> Cc:	'w3c-dist-auth@w3.org'
> Subject:	Re: Server-generated version ids
> Judy Slein:
> >4. Server-generated version ids: Is there a requirement for 
> to be
> >able to request that the server generate an id for a new version?
> (
> Barbara Bazemore:
> > Consider this issue from the client's point of view.  The client
> asks
> > the server to save a document as a new version.  The server
> generates
> > a new version id.  The client now wants to reference the new
> version.
> > How does the client find out what the new version id is?
> Perhaps there's a way of rewriting the requirement so that it
> focuses on the intent rather than the mechanism:
> "A simple client should be able to create new versions and 
>  the new version in a way that is transparent to the way in which
>  version IDs are generated, coded, or parsed. For example, if a 
>  saves a document as a new version and the server generates a new
> version
>  ID, the client should be given or be able to easily discover the
>  version ID of the  newly generated version."
> Larry
> --
> http://www.parc.xerox.com/masinter
Received on Friday, 23 May 1997 16:28:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:10 UTC