RE: Open Issues - Versioning

1. Yes. This issue will be further explored in the context of
distributed versioning, even though it occurs on centralized versioning
systems.
2. These links all are defined in the specification, though I think
predecessor got dropped on the editing floor. The NextVersion gives the
successor relationship and TreeHandle provides the versioning tree
identifier.
3. That is authentication and is orthogonal to this specification.

		Yaron

>-----Original Message-----
>From:	Judith Slein [SMTP:slein@wrc.xerox.com]
>Sent:	Friday, February 07, 1997 12:44 PM
>To:	Jim Whitehead
>Cc:	w3c-dist-auth@w3.org
>Subject:	Re: Open Issues - Versioning
>
>Here are some more versioning questions that we discussed informally during
>the break at the Irvine meeting:
>
>1.  Does the versioning model allow a given resource to belong to multiple
>version trees?
>
>2.  It needs to be possible to navigate from each version to its
>predecessor.  It also needs to be possible to find out for any resource
>which version tree(s) it belongs to. 
>
>3. There needs to be some mechanism for guaranteeing that the person who is
>checking something in is the same one who checked it out.   
>
>--Judy
>Name:			Judith A. Slein
>E-Mail:			slein@wrc.xerox.com
>Internal Phone:  	8*222-5169
>External Phone:		(716) 422-5169
>Fax:			(716) 265-7133
>MailStop:		128-29E
>

Received on Saturday, 8 February 1997 00:09:25 UTC