We can't even be sure there will be version IDs. There is absolutely no
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 be
argued out in implementation. The requirement is that Versions must be
identifiable by a URL, it is up to the spec to decide if having two
identifiers is useful.
Yaron
> -----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 clients
> to be
> >able to request that the server generate an id for a new version?
> (5.9.2.8)
>
> 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 reference
> 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 client
> 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