CHECKOUT method and activity-set

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

CHECKOUT method and activity-set

Werner Donné

Hi,

The linear-activity preconditions states: "If there is a request
activity set, unless DAV:unreserved is specified, the selected
version MUST be a descendant of all other versions of that version
history that select that activity.".

What should happen if there are no versions yet in the version
history with a given activity in their activity-set? It is then
not possible to select a version which is a descendant of all
other versions in that activity. It could be resolved by adding
the given activity in the activity-set of the latest version in
another activity.

According to section 13.2.1, however, a server may refuse an
update of the activity-set property. How can such a server then
the first version in a new activity?

Regards,

Werner.
--
Werner Donné  --  Re
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803 e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: CHECKOUT method and activity-set

Manfred Baedke

Hi Werner,

> What should happen if there are no versions yet in the version
> history with a given activity in their activity-set? It is then
> not possible to select a version which is a descendant of all
> other versions in that activity. It could be resolved by adding
> the given activity in the activity-set of the latest version in
> another activity.
>  

The selected version in fact _is_ a descendant of all versions contained
in the empty set. That is pretty much the same as the principle "ex
falso quodlibet".

Regards,
Manfred