From: jamsden@us.ibm.com To: ietf-dav-versioning@w3.org Message-ID: <85256801.00759AF5.00@d54mta03.raleigh.ibm.com> Date: Tue, 5 Oct 1999 17:23:36 -0400 Subject: Re: Compare reports Well, I didn't say it would be useful, only what it might mean! But really, I suspect a workspace will often correspond to a limited subset of a whole site, the revisions selected by a configuration for example. Comparing my workspace with yours when our RSR's are pretty similar would show what we've been working on, and give us an indication of how complex the merge might be. If the RSRs pick the whole site, then this wouldn't be very useful. I have no problem taking it out. Note Workspace.differencesWith(Configuration aConfiguration) in the model returns the differences between the workspace and the configuration measured in activities. This says what things have been done in this workspace that are different than a configuration, and might need to be included in the next revision of that configuration. By giving the differences in activities rather than individual revisions, the report is much smaller and may be more meaningful. We never included a method Workspace.differencesWith(Workspace). Tim_Ellison@oti.com (Tim Ellison OTT) on 10/05/99 04:45:11 PM To: ietf-dav-versioning@w3.org (ietf-dav-versioning) cc: Subject: Re: Compare reports <jm> - For Workspaces??? (What does it mean to compare to workspaces?) </jm> <jra> What different revisions would be selected? </jra> <tpe> Eeek!, "for all versioned resources known to the server, which would select different revisions by these two workspaces" ?? I don't see that comparing workspaces makes any sense. </tpe>