<br><tt><font size=2>Russ Nelson <nelson@crynwr.com> wrote on 31/08/2011
03:43:28 PM:<br>
<br>
> What about the people who didn't agree to the CT, but whose data is
in<br>
> the public domain?<br>
<br>
Hi Russ,</font></tt>
<br>
<br><tt><font size=2>The suggestion here is to streamline a process, more
than determine policy.. That is to..</font></tt>
<br>
<br><tt><font size=2>1. Automatically hide trivial changes to objects originally
created by those who have agreed to the CT by people who have specifically
declined them.</font></tt>
<br>
<br><tt><font size=2>And/Or</font></tt>
<br>
<br><tt><font size=2>2. When edits made by those who have specifically
declined the CT are manually reverted, allow them to be hidden from the
history of the object, so the object can then be determined to be fully
CT-compliant throughout its history.</font></tt>
<br>
<br><tt><font size=2>If our objective is a CT-compliant data-set, I see
both of these things as advancing us towards that objective, doing little
or no damage, saving us considerable manual effort in some areas, and saving
the history of objects where we can. It also may avoid unnecessarily large
data removal at a later stage.</font></tt>
<br>
<br><tt><font size=2>To address your question specifically, what happens
to data placed in the public domain by the author on the wiki, who then
specifically declines the CT? Well in the first case, if the edits
are just a trivial modification to a fully CT-compliant version - I'd say
just hide them. In the second case, where a CT-compliant editor has
decided to revert the edits made by one of our ambivalent PD editors, they
are being reverted anyway, so the only concern is the state of the history
of the object and not the state of the object itself. The editor
when choosing whether to revert currently could just as well decide to
copy and upload to avoid the possibility of contamination, with the effect
of losing all the history connection to the object. Which is preferable?
I'd say hiding the history of the edit by ambivalent PD contributor
is preferable to losing all connection, so I'd recommend that.</font></tt>
<br>
<br><tt><font size=2>Ian.</font></tt>