The ambiguity comes in if the two post-conditions are read in isolation. The fact that they define different semantics for the DAV:auto-update property led me to believe that they may also define different semantics for the other properties like DAV:checked-out.
So, in reality:
DAV:create-working-resource-from-checked-in-version (VCR URL, DAV:apply-to-version)
working-resource <-- DAV:create-working-resource(VCR::DAV:checked-in)
working-resource::DAV:auto-update <-- VCR URL
Probably some redundancy would have made it clearer.
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Geoffrey M Clemm
Sent: Wednesday, September 15, 2004 1:51 PM
Subject: Re: DAV:checked-out property of a working-resource
Girish wrote on 09/15/2004 05:34:16 AM:
> What should be the DAV:checked-out property of a working resource,
> when the working resource was created due to a CHECKOUT on a > version-controlled-resource with DAV:apply-to-version? Should it be
> equal to the DAV:checked-in property of the version-controlled-
> resource at the time the CHECKOUT was done?
The semantics of CHECKOUT to create a working resource is defined
in section 9.3 "CHECKOUT Method (applied to a version)".
Postcondition DAV:create-working-resource-from-checked-in-version states:
request-URL identified a version-controlled resource, and
DAV:apply-to-version is specified in the request body, the
CHECKOUT is applied to the DAV:checked-in version of the version-
controlled resource, and not the version-controlled resource
Postcondition DAV:create-working-resource st ates:
The DAV:checked-out property of the new
working resource MUST identify the version that was checked out.
So since the CHECKOUT is applied to the DAV:checked-in version and the
DAV:checked-out property identifies the version that was checked out,
then yes, the DAV:checked-out property of the new working resource
identifies the DAV:checked-in version.
Is there something in the spec that led you to believe otherwise?
Sign-up for Ads Free at Mail.com