> -----Original Message-----
> From: Raj Kumar [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 16, 2001 6:54 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Implementation of Delta V
>
>
> hi mathias,
> I have some questions about your implementation of
> version-control and
> report methods.
Ok, so I will try to answer them. But I have to say, that there are open
points left.
> Did you make use of the Rational Rose class models that
> are available on
> the Delta V web site when coding these methods. More
> specifically did you
> write any new classes like Resource,Versionable Resource,
> Version History
> etc that are part of these models.
No, I didn't write new classes for resources. I think for "Basic Versioning
Package" (includes only report and version-control) it is not needed.
Instead we used the existing descriptors (NodeRevsionDescriptor and
NodeRevsionDescriptors). I think NodeRevisionDescriptor was assigned to
contain version resources. As NodeRevsionDescriptors was able to store many
NodeRevisionDescriptor, we decided that it would be a good idea to make it
the version history resource.
To do so, we had to introduce properties to NodeRevsionDescriptors. For
implementing Basic Versioning Package it is not needed, that there is a
unique uri for the version history, so we skipped this problem for later.
But I think, that there should be no major problem. The version-controlled
resource should be identical to version-able resource plus a checked-in
attribute to identify the last version. So we put its property into
NodeRevisionDescriptors.
> What were the values of the auto-version property on the version
> controlled resources that you allowed?
Currently it's <checkout-checkin/>. But I think we will implement the others
too.
> Are the versions of the resource stored in the same
> namespace as the
> version controlled resources or were they stored in a
> different namespace?
??? Hope I answered this one allready or will do it in this mail.
> What was the mechanism used to generate a URI for a version?
This one is a little tricky. Currently the URI of a version ist the URI of
the version-controlled resource plus appending an illeagal character +
version and the NodeRevisionNumber.
Example: if a version controlled resource exists with the following URI
http://www.webdav.org/slide/files/foo.html
its first version would have an URI like this:
http://www.webdav.org/slide/files/foo.html|version/1.0
This could be conform to the draft. But we have to think about a better one,
because I'm not quiet sure.
>
> It would help me a lot if you can answer the above questions.
> thanks,
> rajkumar
Regards,
Mathias
