RE: Relationship between scopes and version histories

Issue added as:

http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-latest.html#rfc
.issue.scope-vs-versions

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Julian Reschke
> Sent: Thursday, February 06, 2003 1:56 PM
> To: Wallmer, Martin; www-webdav-dasl@w3.org
> Subject: RE: Relationship between scopes and version histories
>
>
>
> > 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 Friday, 7 February 2003 06:44:02 UTC