> I'd encourage you to use Delta-V. It already allows for resources
> "normally" not being under version control, and a "new command" (the
> VERSION-CONTROL method) to bring a resource under version-control.
>
> There is also provision for auto-versioning based on modification and,
> optionally, lock state transition.
>
> A server is only required to implement basic versioning to be Delta-V
> compliant -- indeed there will be very few, if any, servers implementing
> the entire specification. The working group have tried to reduce the
basic
> versioning functionality to the minimum coherent set of behavior that is
> useful and consistent with the extensions added by advanced versioning.
>
> If there is some more fundamental set of services that you can imagine
then
> please send in your suggestions. I hope there is no room for new
> "compatible" commands.
Thanks for the details.
I'm committed to have Slide fully support basic Delta V (at least).
I don't know yet when work will start on that part, but I would definitely
appreciate any help and / or advice you could provide with implementing
Delta V.
Thanks,
Remy
