Next message: Tim Ellison/OTT/OTI: "Re: Extending Target-Selector"
To: ietf-dav-versioning@w3.org
Message-ID: <OFF577D65D.377BFE10-ON8525689D.005C50C3@ott.oti.com>
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
Date: Thu, 9 Mar 2000 12:08:22 -0500
Subject: Defaults
When is request is received that does not specify the Workspace: and/or
Revision-Selector:, the revision selection seems quite complicated.
Here's my interpretation (refs from 03.1 protocol doc):
(1) (a) For each versioned collection being resolved, first use the
collection's default workspace to pick a revision/working collection (ref.
10.1.1).
(b) If there is no default workspace specified for the collection,
choose the default revision (ref. 8.1).
(c) If there is no default revision specified use the 'server
determined default workspace' (ref. 9.1).
(d) If there is still no revision selected then the reference is not
found.
(2) For the final resource being resolved, first consider the
Revision-Selector in preference to anything else (ref. 7.2 & 3.3.3). If
there is no Revision-Selector then use the resolution strategy of step (1)
Section 3.3.3 says that the default-revision shoul donly be used if "no
Workspace: or Revision-Selector: header is specified" -- I don't see how
that fits in :-(
Sounds a bit complicated doesn't it?
Why do we want default workspaces for each collection, and default
revisions for each resource?
Comments.
Tim