Re: Compare reports
Tim Ellison OTT (Tim_Ellison@oti.com)
Wed, 06 Oct 1999 10:29:10 -0400
From: Tim_Ellison@oti.com (Tim Ellison OTT)
To: ietf-dav-versioning@w3.org (ietf-dav-versioning)
Message-ID: <1999Oct06.102751.1250.1343407@otismtp.ott.oti.com>
Date: Wed, 06 Oct 1999 10:29:10 -0400
Subject: RE: Compare reports
<jra> Well, I didn't say it would be useful, only what it might mean! </jra>
<tpe/> I know, and my reply was intended to be light hearted-no offense
intended!
<jra>
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.
[...snip...] If the RSRs pick the whole site, then this wouldn't be very
useful.
</jra>
<tpe>
Unless the RSR enumerates the resources it selects, (i.e. a config,
activity) the problem remains that it requires an entire site search for
candidates (e.g. an RSR of label or rev-id).
</tpe>
<jra>
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).
</jra>
<tpe/>ack.