Re: What is in workspace?

Bradley Sergeant (Bradley.Sergeant@merant.com)
Fri, 8 Oct 1999 13:46:31 -0700 

Message-ID: <F3B2A0DB2FC1D211A511006097FFDDF5343896@BEAVMAIL>
From: Bradley Sergeant <Bradley.Sergeant@merant.com>
To: "'Geoffrey M. Clemm'" <gclemm@tantalum.atria.com>,
Date: Fri, 8 Oct 1999 13:46:31 -0700 
Subject: RE: What is in workspace?

In writing up some of the versioning methods it occurred to me that the
verbiage might be more intuitive and easier to say if we changed the term
"working resource"  to "working revision".  Then you can talk about revision
selection rule and target revision, etc.  It makes it clearer that the
working copy is closely related to the revision history and not just a copy.
Just a thought.  I'm still using the term  "working resource" for now.

--Sarge

-----Original Message-----
From:	Geoffrey M. Clemm [mailto:gclemm@tantalum.atria.com]
Sent:	Thursday, October 07, 1999 8:17 PM
To:	ietf-dav-versioning@w3.org
Subject:	Re: What is in workspace?


   From: "Viktor Lioutyi" <Viktor_Lioutyi@i2.com>

   <gmc/> A common scenario is "label everything in my workspace with a
   particular label"....

   What does it mean "... everything in my workspace ..."?

<gmc/> Apologies ... I was being overly terse. I should have said
"label the revisions selected in my workspace for the members of a
particular collection".

   Workspace has a set of working revisions checked out in context of this
   workspace.

We would call them "working resources" (they don't become a revision until
you check them in).  Note that only revisions can have labels, not
working resources.

   Workspace has current activity, that has at least two different
associations
   with
   resources: latest in activity and modified in activity.
   Workspace has revision selection rule. This rule for each resource may
define a
   revision or nothing.

   Does workspace have a set of resources loaded into it? I didn't find it
in
   specification (but I'd like to).

A workspace owns a set of working resources (the ones checked out into
that workspace), and a revision selection rule.  A common implementation
for a workspace is to copy a bunch of files into a tree, and then redirect
requests for that workspace into that tree, but this is not required
by the protocol.

Cheers,
Geoff