W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > January to March 2003

RE: Relationship between scopes and version histories

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 6 Feb 2003 13:55:42 +0100
To: "Wallmer, Martin" <Martin.Wallmer@softwareag.com>, <www-webdav-dasl@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCCEJFGGAA.julian.reschke@gmx.de>

> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Wallmer, Martin
> Sent: Thursday, February 06, 2003 11:25 AM
> To: 'Julian Reschke'; www-webdav-dasl@w3.org
> Subject: RE: Relationship between scopes and version histories
>
> Hi,
>
> just to clarify:
>
> 1. If a resource in scope has versions, the server SHOULD take care of
> versions as well.
> 2. If the client specifies <d:include-versions />, the server MUST take
care
> of versions or MUST reject the request.
> 3. If the user does not want to get versions, he must specify <not
> xmlns="DAV:"><is-defined><version-name /></is-defined></not> ...
>
> Is my understanding correct?

Exactly.

> However, a defined "switch" (include - exclude) could be a good hint for
the
> server in terms of performance, so I'd prefer a <d:exclude-versions/> as
> well.
>
> Alternatively the server should only include the versions, if
> <d:include-versions /> is specified.
>
> Does this make sense?

I don't like that, because I'd prefer to keep the definition of "scope"
intact. If versions happen to be in the namespace scope, they should be in
scope of the search as well. Thus the proposal to add a specific element
that *extends* the scope of the query.

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Thursday, 6 February 2003 07:56:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:09 GMT