view Side-By-Side changes

Network Working Group                                    J. F. Reschke, Editor
Internet Draft Ed.
Internet-Draft                                                greenbytes
Expires: December 2003 April 9, 2004                                          S. Reddy
                                                                  Oracle
                                                                J. Davis
                                                     Intelligent Markets
                                                               A. Babich
                                                                 Filenet
                                                               June
                                                        October 10, 2003


                             WebDAV SEARCH
                     draft-reschke-webdav-search-04
                     draft-reschke-webdav-search-05

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that other
   groups may also distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress". progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt. http://
   www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire in December 2003. on April 9, 2004.

Copyright Notice

   Copyright (C) The Internet Society (2003). All Rights Reserved.

Abstract

   This document specifies a set of methods, headers, properties and
   content-types composing WebDAV SEARCH, an application of the HTTP/1.1



Reschke, et al.           Expires December 2003                 [Page 1]

Internet Draft                WebDAV SEARCH                    June 2003
   protocol to efficiently search for DAV resources based upon a set of
   client-supplied criteria.

   Distribution of this document is unlimited. Please send comments to
   the Distributed Authoring and Versioning (WebDAV) DASL mailing list



Reschke, et al.          Expires April 9, 2004                  [Page 1]

Internet-Draft               WebDAV SEARCH                  October 2003


   at www-webdav-dasl@w3.org, www-webdav-dasl@w3.org [1], which may be joined by sending a
   message with subject "subscribe" to www-webdav-dasl-request@w3.org. www-webdav-dasl-request@w3.org
   [2]. Discussions of the WebDAV DASL mailing list are archived at URL:
   http://www.w3.org/pub/WWW/Archives/Public/www-webdav-dasl/.










































Reschke, et al.           Expires December 2003                 [Page 2]

Internet Draft                WebDAV SEARCH                    June 2003


   Table of Contents

      Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . .   1

Table of Contents  . . . . . . . . . . . . . . . . . . . . . .   3
      1

   1.     Introduction . . . . . . . . . . . . . . . . . . . . . . . .   6   5
   1.1    DASL . . . . . . . . . . . . . . . . . . . . . . . . . .   6 .   5
   1.2    Relationship to DAV  . . . . . . . . . . . . . . . . . .   6 .   5
   1.3    Terms  . . . . . . . . . . . . . . . . . . . . . . . . .   6 .   5
   1.4    Notational Conventions . . . . . . . . . . . . . . . . . .   7
   1.5    Editorial note on usage of 'DAV:' namespace  . . . . . . .   7
   1.6    An Overview of DASL at Work  . . . . . . . . . . . . . .   7
      2 .   8
   2.     The SEARCH Method  . . . . . . . . . . . . . . . . . . . . .   8   9
   2.1    Overview . . . . . . . . . . . . . . . . . . . . . . . .   8 .   9
   2.2    The Request  . . . . . . . . . . . . . . . . . . . . . .   8 .   9
   2.2.1  The Request-URI  . . . . . . . . . . . . . . . . . .   8 . . .   9
   2.2.2  The Request Body . . . . . . . . . . . . . . . . . .   8
        2.3 The DAV:searchrequest XML Element  . . . . . . . . . . .   9
        2.4
   2.3    The Successful 207 (Multistatus) Response  . . . . . . .   9
          2.4.1 .  10
   2.3.1  Extending the PROPFIND Response  . . . . . . . . . .   9
          2.4.2 . . .  10
   2.3.2  Example: A Simple Request and Response . . . . . . . . . .  10
          2.4.3
   2.3.3  Example: Result Set Truncation . . . . . . . . . . .  11
        2.5 Unsuccessful Responses . . . . . . . . . . . . . . . . .  12
        2.6 Invalid Scopes . . .  11
   2.4    Unsuccessful Responses . . . . . . . . . . . . . . . . . .  12
          2.6.1 Indicating  13
   2.4.1  Example of an Invalid Scope  . . . . . . . . . . . .  12
          2.6.2 Example of an Invalid Scope  . . . . . . . . . . . .  13
      3
   3.     Discovery of Supported Query Grammars  . . . . . . . . . . .  14
   3.1    The OPTIONS Method . . . . . . . . . . . . . . . . . . . .  14
   3.2    The DASL Response Header . . . . . . . . . . . . . . . . .  14
   3.3    DAV:supported-query-grammar-set (protected)  . . . . . . .  15
   3.4    Example: Grammar Discovery . . . . . . . . . . . . . . . .  15
      4
   4.     Query Schema Discovery: QSD  . . . . . . . . . . . . . . . .  18
   4.1    Additional SEARCH semantics  . . . . . . . . . . . . . . .  18
   4.1.1  Example of query schema discovery  . . . . . . . . . . . .  19
      5
   5.     The DAV:basicsearch Grammar  . . . . . . . . . . . . . . . .  21
   5.1    Introduction . . . . . . . . . . . . . . . . . . . . . . .  21
   5.2    The DAV:basicsearch DTD  . . . . . . . . . . . . . . . . .  21
   5.2.1  Example Query  . . . . . . . . . . . . . . . . . . . . . .  22
   5.3    DAV:select . . . . . . . . . . . . . . . . . . . . . . . .  23
   5.4    DAV:from . . . . . . . . . . . . . . . . . . . . . . . . .  23
   5.4.1  Relationship to the Request-URI  . . . . . . . . . . . . .  24
   5.4.2  Scope  . . . . . . . . . . . . . . . . . . . . . . .  24 . . .  24
   5.5    DAV:where  . . . . . . . . . . . . . . . . . . . . . . . .  24
   5.5.1  Use of Three-Valued Logic in Queries . . . . . . . . . . .  24
   5.5.2  Handling Optional operators  . . . . . . . . . . . . . . .  24
   5.5.3  Treatment of NULL Values . . . . . . . . . . . . . .  25 . . .  24
   5.5.4  Treatment of properties with mixed/element content . . . .  25
   5.5.5  Example: Testing for Equality  . . . . . . . . . . . . . .  25
   5.5.6  Example: Relative Comparisons  . . . . . . . . . . .  26 . . .  25



Reschke, et al.          Expires April 9, 2004                  [Page 2]

Internet-Draft               WebDAV SEARCH                  October 2003


   5.6    DAV:orderby  . . . . . . . . . . . . . . . . . . . . . . .  26



Reschke, et al.           Expires December 2003                 [Page 3]

Internet Draft                WebDAV SEARCH                    June 2003
   5.6.1  Comparing Natural Language Strings . . . . . . . . .  27 . . .  26
   5.6.2  Example of Sorting . . . . . . . . . . . . . . . . .  27 . . .  26
   5.7    Boolean Operators: DAV:and, DAV:or, and DAV:not  . . . . .  27
   5.8    DAV:eq . . . . . . . . . . . . . . . . . . . . . . . . .  28 .  27
   5.9    DAV:lt, DAV:lte, DAV:gt, DAV:gte . . . . . . . . . . . .  28 .  27
   5.10   DAV:literal  . . . . . . . . . . . . . . . . . . . . . .  28 .  27
   5.11   DAV:typed-literal (optional) . . . . . . . . . . . . . . .  28
        5.12
   5.11.1 Example for typed numerical comparison . . . . . . . . . .  28
   5.12   Support for matching xml:lang attributes on properties . .  29
   5.12.1 DAV:language-defined (optional)  . . . . . . . . . . . . .  29
   5.12.2 DAV:language-matches (optional)  . . . . . . . . . . . . .  29
   5.12.3 Example of language-aware matching . . . . . . . . . . . .  29
   5.13   DAV:is-collection  . . . . . . . . . . . . . . . . . . . .  30
   5.13.1 Example of DAV:is-collection . . . . . . . . . . . . . . .  30
   5.14   DAV:is-defined . . . . . . . . . . . . . . . . . . . . . .  30
   5.15   DAV:like . . . . . . . . . . . . . . . . . . . . . . .  31 . .  30
   5.15.1 Syntax for the Literal Pattern . . . . . . . . . . . . . .  31
   5.15.2 Example of DAV:like  . . . . . . . . . . . . . . . . . . .  31
   5.16   DAV:contains . . . . . . . . . . . . . . . . . . . . .  32 . .  31
   5.16.1 Result scoring (DAV:score element) . . . . . . . . . . . .  32
   5.16.2 Ordering by score  . . . . . . . . . . . . . . . . .  33 . . .  32
   5.16.3 Examples . . . . . . . . . . . . . . . . . . . . .  33 . . . .  32
   5.17   Limiting the result set  . . . . . . . . . . . . . . . .  34 .  33
   5.17.1 Relationship to result ordering  . . . . . . . . . .  34 . . .  33
   5.18   The "caseless" 'caseless' XML attribute . . . . . . . . . . . . .  34 . .  33
   5.19   Query schema for DAV:basicsearch . . . . . . . . . . .  35 . .  34
   5.19.1 DTD for DAV:basicsearch QSD  . . . . . . . . . . . .  35
          5.19.2 DAV:propdesc Element  . . . . . . . .  34
   5.19.2 DAV:propdesc Element . . . . . . .  35
            5.19.2.1 DAV:any-other-property . . . . . . . . . . . .  36  34
   5.19.3 The DAV:datatype Property Description  . . . . . . .  36 . . .  35
   5.19.4 The DAV:searchable Property Description  . . . . . .  37 . . .  35
   5.19.5 The DAV:selectable Property Description  . . . . . .  37 . . .  36
   5.19.6 The DAV:sortable Property Description  . . . . . . .  37 . . .  36
   5.19.7 The DAV:caseless Property Description  . . . . . . .  38 . . .  36
   5.19.8 The DAV:operators XML Element  . . . . . . . . . . .  38 . . .  36
   5.19.9 Example of Query Schema for DAV:basicsearch  . . . .  38
      6 . . .  37
   6.     Internationalization Considerations  . . . . . . . . . . . .  40
      7  38
   7.     Security Considerations  . . . . . . . . . . . . . . . . .  39
   7.1    Implications of XML External Entities  .  41
      8 Scalability . . . . . . . . .  39
   8.     Scalability  . . . . . . . . . . . . . . .  42
      9 Authentication . . . . . . . .  40
   9.     Authentication . . . . . . . . . . . . . . .  43
      10 . . . . . . .  41
   10.    IANA Considerations  . . . . . . . . . . . . . . . . . . .  42
   11.    Contributors .  44
      11 Copyright . . . . . . . . . . . . . . . . . . . . . .  43
   12.    Acknowledgements . . .  45
      12 Intellectual Property . . . . . . . . . . . . . . . . . .  44
          Normative References .  46
      13 Acknowledgements . . . . . . . . . . . . . . . . . .  45
          Informative References . . .  47
      Normative References . . . . . . . . . . . . . . .  46
          Authors' Addresses . . . . . .  48
      Informative References . . . . . . . . . . . . . .  47
   A.     Three-Valued Logic in DAV:basicsearch  . . . . . .  48
      Author's Addresses . . . .  48



Reschke, et al.          Expires April 9, 2004                  [Page 3]

Internet-Draft               WebDAV SEARCH                  October 2003


   B.     Change Log (to be removed by RFC Editor before
          publication) . . . . . . . . . . . . . . . . . .  49
      A Three-Valued Logic in DAV:basicsearch . . . . .  50
   B.1    From draft-davis-dasl-protocol-xxx . . . . . .  51
      B Change Log . . . . . .  50
   B.2    since start of draft-reschke-webdav-search . . . . . . . .  51
   B.3    since draft-reschke-webdav-search-00 . . . . . . . . . . .  53
        B.1 From draft-davis-dasl-protocol-xxx
   B.4    since draft-reschke-webdav-search-01 . . . . . . . . . . .  53
        B.2
   B.5    since start of draft-reschke-webdav-search draft-reschke-webdav-search-02 . . . . . . . . . . .  54
        B.3
   B.6    since draft-reschke-webdav-search-00 draft-reschke-webdav-search-03 . . . . . . . . . .  56



Reschke, et al.           Expires December 2003                 [Page 4]

Internet Draft                WebDAV SEARCH                    June 2003


        B.4 .  54
   B.7    since draft-reschke-webdav-search-01 draft-reschke-webdav-search-04 . . . . . . . . . . .  55
   C.     Resolved issues (to be removed by RFC Editor before
          publication) . . . . . . . . . . . . . . . . . . . . . . .  56
        B.5 since draft-reschke-webdav-search-02
   C.1    1.3-import-condition-code-terminology  . . . . . . . . . .  56
        B.6 since draft-reschke-webdav-search-03
   C.2    1.3-import-requirements-terminology  . . . . . . . . . . .  56
   C.3    1.3-import-DTD-terminology . . . . . . . . . . . . . . .  57
      Index .  56
   C.4    invalid-scope  . . . . . . . . . . . . . . . . . . . . . .  56
   C.5    JW24d  . . . . . . . . . . . . . . . . . . . . . . . . . .  57
   C.6    scope-vs-versions  . . . . . . . . . . . . . . . . . . . .  58















































Reschke, et al.           Expires December 2003                 [Page 5]

Internet Draft                WebDAV SEARCH                    June 2003


1 Introduction


1.1 DASL

   This document
   C.7    DB2/DB7  . . . . . . . . . . . . . . . . . . . . . . . . .  58
   D.     Open issues (to be removed by RFC Editor before
          publication) . . . . . . . . . . . . . . . . . . . . . . .  61
   D.1    1.3-apply-condition-code-terminology . . . . . . . . . . .  61
   D.2    2.4-multiple-uris  . . . . . . . . . . . . . . . . . . . .  61
   D.3    result-truncation  . . . . . . . . . . . . . . . . . . . .  61
   D.4    qsd-optional . . . . . . . . . . . . . . . . . . . . . . .  62
   D.5    5.1-name-filtering . . . . . . . . . . . . . . . . . . . .  62
   D.6    5.4.2-multiple-scope . . . . . . . . . . . . . . . . . . .  63
   D.7    5.4.2-scope-vs-redirects . . . . . . . . . . . . . . . . .  63
   D.8    language-comparison  . . . . . . . . . . . . . . . . . . .  63
   D.9    JW16b/JW24a  . . . . . . . . . . . . . . . . . . . . . . .  63
   D.10   typed-literal  . . . . . . . . . . . . . . . . . . . . . .  64
          Index  . . . . . . . . . . . . . . . . . . . . . . . . . .  65
          Intellectual Property and Copyright Statements . . . . . .  67



















Reschke, et al.          Expires April 9, 2004                  [Page 4]

Internet-Draft               WebDAV SEARCH                  October 2003


1. Introduction

1.1 DASL

   This document defines WebDAV SEARCH, an application of HTTP/1.1
   forming a lightweight search protocol to transport queries and result
   sets and allows clients to make use of server-side search facilities.
   It is based on the expired draft for WebDAV DASL [DASL]. [DASLREQ]
   describes the motivation for DASL.

   DASL will minimize the complexity of clients so as to facilitate
   widespread deployment of applications capable of utilizing the DASL
   search mechanisms.

   DASL consists of:

   o  the SEARCH method,

   o  the DASL response header,

   o  the DAV:searchrequest XML element,

   o  the DAV:query-schema-discovery XML element,

   o  the DAV:basicsearch XML element and query grammar, and

   o  the DAV:basicsearchschema XML element.

   For WebDAV-compliant servers, it also defines a new live property
   DAV:supported-query-grammar-set.

1.2 Relationship to DAV

   DASL relies on the resource and property model defined by [RFC2518].
   DASL does not alter this model. Instead, DASL allows clients to
   access DAV-modeled resources through server-side search.

1.3 Terms

   This document uses the terms defined in [RFC2616], in [RFC2518], in
   [RFC3253] and in this section.

   Criteria

      An expression against which each resource in the search scope is
      evaluated.

   Query



Reschke, et al.          Expires April 9, 2004                  [Page 5]

Internet-Draft               WebDAV SEARCH                  October 2003


      A query is a combination of a search scope, search criteria,
      result record definition, sort specification, and a search
      modifier.

   Query Grammar

      A set of definitions of XML elements, attributes, and constraints
      on their relations and values that defines a set of queries and
      the intended semantics.

   Query Schema

      A listing, for any given grammar and scope, of the properties and
      operators that may be used in a query with that grammar and scope.

   Result

      A result is a result set, optionally augmented with other
      information describing the search as a whole.

   Result Record

      A description of a resource. A result record is a set of
      properties, and possibly other descriptive information.

   Result Record Definition

      A specification of the set of properties to be returned in the
      result record.

   Result Set

      A set of records, one for each resource for which the search
      criteria evaluated to True.

   Scope

      A set of resources to be searched.

   Search Modifier

      An instruction that governs the execution of the query but is not
      part of the search scope, result record definition, the search
      criteria, or the sort specification. An example of a search
      modifier is one that controls how much time the server can spend
      on the query before giving a response.

   Sort Specification



Reschke, et al.          Expires April 9, 2004                  [Page 6]

Internet-Draft               WebDAV SEARCH                  October 2003


      A specification of an ordering on the result records in the result
      set.


1.4 Notational Conventions

   The augmented BNF used by this document to describe protocol elements
   is exactly the same as the one described in Section 2.1 of [RFC2616].
   Because this augmented BNF uses the basic production rules provided
   in Section 2.2 of [RFC2616], those rules apply to this document as
   well.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT"
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   This document uses XML DTD fragments as a purely notational
   convention. WebDAV request and response bodies can not be validated
   due to the specific extensibility rules defined in section 23 of
   [RFC2518] and due to the fact that all XML elements defined by this
   specification use the XML namespace name "DAV:". In particular:

   1.  element names use the "DAV:" namespace,

   2.  element ordering is irrelevant unless explicitly stated,

   3.  extension elements (elements not already defined as valid child
       elements) may be added anywhere, except when explicitly stated
       otherwise,

   4.  extension attributes (attributes not already defined as valid for
       this element) may be added anywhere, except when explicitly
       stated otherwise.

   When an XML element type in the "DAV:" namespace is referenced in
   this document outside of the context of an XML fragment, the string
   "DAV:" will be prefixed to the element type.

   Similarily, when an XML element type in the namespace "http://
   www.w3.org/2001/XMLSchema" is referenced in this document outside of
   the context of an XML fragment, the string "xs:" will be prefixed to
   the element type.

1.5 Editorial note on usage of 'DAV:' namespace

   *Note that this draft currently defines elements and properties in
   the WebDAV namespace "DAV:" which it shouldn't do as it isn't a work
   item of the WebDAV working group. The reason for this is the desire



Reschke, et al.          Expires April 9, 2004                  [Page 7]

Internet-Draft               WebDAV SEARCH                  October 2003


   for some kind of backward compatibility to the expired DASL drafts
   and the assumption that the draft may become an official RFC
   submission of the WebDAV working group at a later point of time.*

1.6 An Overview of DASL at Work

   One can express the basic usage of DASL in the following steps:

   o  The client constructs a query using the DAV:basicsearch grammar.

   o  The client invokes the SEARCH method on a resource that will
      perform the search (the search arbiter) and includes a text/xml or
      application/xml request entity that contains the query.

   o  The search arbiter performs the query.

   o  The search arbiter sends the results of the query back to the
      client in the response. The server MUST send an entity that
      matches the [RFC2518] PROPFIND response.
































Reschke, et al.          Expires April 9, 2004                  [Page 8]

Internet-Draft               WebDAV SEARCH                  October 2003


2. The SEARCH Method

2.1 Overview

   The client invokes the SEARCH method to initiate a server-side
   search. The body of the request defines the query. The server MUST
   emit an entity matching the [RFC2518] PROPFIND response.

   The SEARCH method plays the role of transport mechanism for the query
   and the result set. It does not define the semantics of the query.
   The type of the query defines the semantics.

2.2 The Request

   The client invokes the SEARCH method on the resource named by the
   Request-URI.

2.2.1 The Request-URI

   The Request-URI identifies the search arbiter. Any HTTP resource may
   function as search arbiter. It is not a new type of resource (in the
   sense of DAV:resourcetype as defined in [RFC2518]), nor does it have
   to be a WebDAV-compliant resource.

   The SEARCH method defines no relationship between the arbiter and the
   scope of the search, rather the particular query grammar used in the
   query defines the relationship. For example, a query grammar may
   force the request-URI to correspond exactly to the search scope.

2.2.2 The Request Body

   The server MUST process a text/xml or application/xml request body,
   and MAY process request bodies in other formats. See [RFC3023] for
   guidance on packaging XML in requests.

   Marshalling:

      If a request body with content type text/xml or application/xml is
      included, it MUST be either a DAV:searchrequest or a
      DAV:query-schema-discovery XML element. It's single child element
      identifies the query grammar.

      For DAV:searchrequest, the definition of search criteria, the
      result record, and any other details needed to perform the search
      depend on the individual search grammar.

      For DAV:query-schema-discovery, the semantics is defined in
      Section 4.



Reschke, et al.          Expires April 9, 2004                  [Page 9]

Internet-Draft               WebDAV SEARCH, SEARCH                  October 2003


   Preconditions:

      (DAV:search-grammar-discovery-supported): when an application of HTTP/1.1
   forming XML request body
      is present and has a lightweight DAV:query-schema-discovery document element,
      the server MUST support the query schema discovery mechanism
      described in Section 4.

      (DAV:search-grammar-supported): when an XML request body is
      present, the search protocol grammar identified by the document element's
      child element must be a supported search grammar.

      (DAV:search-scope-valid): the supplied search scope must be valid.
      There can be various reasons for a search scope to transport queries and result
   sets be invalid,
      including unsupported URI schemes and allows clients communication problems.
      Servers MAY add [RFC2518] compliant DAV:response elements as
      content to make use of server-side the condition element indicating the precise reason for
      the failure.


2.3 The Successful 207 (Multistatus) Response

   If the server returns 207 (Multistatus), then the search facilities.
   It is based on proceeded
   successfully and the expired draft response MUST match that of a PROPFIND. The
   results of this method SHOULD NOT be cached.

   There MUST be one DAV:response for WebDAV DASL [DASL]. [DASLREQ]
   describes each resource that matched the motivation
   search criteria. For each such response, the DAV:href element
   contains the URI of the resource, and the response MUST include a
   DAV:propstat element.

   Note that for DASL.

   DASL will minimize each matching resource found there may be multiple URIs
   within the complexity search scope mapped to it. In this case, a server SHOULD
   report all of clients these URIs. Clients can use the live property
   DAV:resource-id defined in [BIND] to identify possible duplicates.

2.3.1 Extending the PROPFIND Response

   A response MAY include more information than PROPFIND defines so long
   as to facilitate
   widespread deployment of applications capable of utilizing the DASL
   search mechanisms.

   DASL consists of:

   o extra information does not invalidate the SEARCH method,

   o PROPFIND response.
   Query grammars SHOULD define how the DASL response header,

   o matches the DAV:searchrequest PROPFIND
   response.

2.3.2 Example: A Simple Request and Response

   This example demonstrates the request and response framework. The
   following XML element,

   o document shows a simple (hypothetical) natural language
   query. The name of the DAV:queryschema property,

   o query element is natural-language-query in the DAV:basicsearch
   XML element and namespace "http://example.com/foo". The actual query grammar, and

   o is "Find the DAV:basicsearchschema XML element.



Reschke, et al.          Expires April 9, 2004                 [Page 10]

Internet-Draft               WebDAV SEARCH                  October 2003


   locations of good Thai restaurants in Los Angeles". For WebDAV-compliant servers, it also defines this
   hypothetical query, the arbiter returns two properties for each
   selected resource.

    >> Request:

   SEARCH / HTTP/1.1
   Host: example.org
   Content-Type: application/xml
   Content-Length: xxx

   <?xml version="1.0" encoding="UTF-8"?>
   <D:searchrequest xmlns:D="DAV:" xmlns:F="http://example.com/foo">
     <F:natural-language-query>
       Find the locations of good Thai restaurants in Los Angeles
     </F:natural-language-query>
   </D:searchrequest>

    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="UTF-8"?>
   <D:multistatus xmlns:D="DAV:"
      xmlns:R="http://example.org/propschema">
     <D:response>
       <D:href>http://siamiam.test/</D:href>
       <D:propstat>
         <D:prop>
           <R:location>259 W. Hollywood</R:location>
           <R:rating><R:stars>4</R:stars></R:rating>
         </D:prop>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
   </D:multistatus>


2.3.3 Example: Result Set Truncation

   A server MAY limit the number of resources in a new live property
   DAV:supported-query-grammar-set.


1.2 Relationship reply, for example to DAV

   DASL relies on
   limit the resource and property model defined by [RFC2518].
   DASL does not alter this model. Instead, DASL allows clients to
   access DAV-modeled amount of resources through server-side search.


1.3 Terms

   This draft uses expended in processing a query. If it
   does so, the reply MUST use status code 207, return a DAV:multistatus
   response body and indicate a status of 507 (Insufficient Storage) for
   the terms defined in [RFC2616], [RFC2518], and
   [DASLREQ]. search arbiter URI. It SHOULD include the partial results.




Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 6]

Internet Draft 11]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


1.4 Notational Conventions

   The augmented BNF used by this document to describe protocol elements


   When a result set is exactly truncated, there may be many more resources that
   satisfy the same as search criteria but that were not examined.

   If partial results are included and the one described client requested an ordered
   result set in Section 2.1 of [RFC2616].
   Because this augmented BNF uses the basic production rules provided
   in Section 2.2 of [RFC2616], those rules apply to this document as
   well.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT"
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document original request, then any partial results that are to
   returned MUST be interpreted ordered as described in [RFC2119].

   When an XML element type in the "DAV:" namespace is referenced in
   this document outside of the context of an XML fragment, client directed.

   Note that the string
   "DAV:" will partial results returned MAY be prefixed to any subset of the element type.

   Note
   result set that this draft currently defines elements and properties in would have satisfied the original query.

    >> Request:

   SEARCH / HTTP/1.1
   Host: example.net
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

    ... the query goes here ...

    >> Response:

   HTTP/1.1 207 Multistatus
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="utf-8"?>
   <D:multistatus xmlns:D="DAV:">
     <D:response>
       <D:href>http://www.example.net/sounds/unbrokenchain.au</D:href>
       <D:propstat>
         <D:prop/>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://tech.mit.test/archive96/photos/Lesh1.jpg</D:href>
       <D:propstat>
         <D:prop/>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://example.net</D:href>
       <D:status>HTTP/1.1 507 Insufficient Storage</D:status>
       <D:responsedescription xml:lang="en">
          Only first two matching records were returned
       </D:responsedescription>
     </D:response>



Reschke, et al.          Expires April 9, 2004                 [Page 12]

Internet-Draft               WebDAV namespace "DAV:", which it shouldn't do as it isn't SEARCH                  October 2003


   </D:multistatus>


2.4 Unsuccessful Responses

   If a work
   item of the WebDAV working group. The reason for this is SEARCH request could not be executed or the desire
   for some kind of backward compatibility attempt to execute
   it resulted in an error, the expired DASL drafts
   and the assumption that server MUST indicate the draft may become failure with an official RFC
   submission of the WebDAV working group at
   appropriate status code and SHOULD add a later point of time.

   Similarily, when an XML element type response body as defined in
   [RFC3253], section 1.6. Unless otherwise stated, condition elements
   are empty, however specific conditions element MAY include additional
   child elements that describe the namespace
   "http://www.w3.org/2001/XMLSchema" is referenced error condition in this document
   outside of the context more detail.

2.4.1 Example of an XML fragment, the string "xs:" will be
   prefixed to the element type.


1.5 An Overview of DASL at Work

   One can express the basic usage of DASL in Invalid Scope

   In the following steps:

   o  The client constructs example below, a query using the DAV:basicsearch grammar.

   o  The client invokes request failed because the SEARCH method on scope identifies a
   HTTP resource that will
      perform the search (the search arbiter) and includes a text/xml or
      application/xml request entity that contains was not found.

    >> Response:

   HTTP/1.1 409 Conflict
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="UTF-8"?>
   <d:error xmlns:d="DAV:">
     <d:search-scope-valid>
       <d:response>
         <d:href>http://www.example.com/X</d:href>
         <d:status>HTTP/1.1 404 Object Not Found</d:status>
       </d:response>
     </d:search-scope-valid>
   </d:error>



















Reschke, et al.          Expires April 9, 2004                 [Page 13]

Internet-Draft               WebDAV SEARCH                  October 2003


3. Discovery of Supported Query Grammars

   Servers MUST support discovery of the query.

   o  The query grammars supported by a
   search arbiter performs the query.

   o  The search resource.

   Clients can determine which query grammars are supported by an
   arbiter sends by invoking OPTIONS on the results of search arbiter. If the query back to resource
   supports SEARCH, then the
      client DASL response header will appear in the
   response. The server MUST send an entity that
      matches DASL response header lists the supported grammars.

   Servers supporting the [RFC2518] PROPFIND response.







Reschke, et al.           Expires December 2003                 [Page 7]

Internet Draft WebDAV extensions [RFC3253] and/or [ACL] MUST
   also

   o  report SEARCH                    June 2003


2 in the live property DAV:supported-method-set for
      all search arbiter resources and

   o  support the live property DAV:supported-query-grammar-set as
      defined in Section 3.3.


3.1 The SEARCH OPTIONS Method


2.1 Overview

   The client invokes the SEARCH OPTIONS method allows the client to initiate discover if a server-side
   search. The body of the request defines the query. The server MUST
   emit an entity matching resource
   supports the [RFC2518] PROPFIND response.

   The SEARCH method plays the role of transport mechanism for the query and to determine the result set. It does not define the semantics of the query.
   The type list of the query defines the semantics.


2.2 The Request search
   grammars supported for that resource.

   The client invokes issues the SEARCH OPTIONS method on the against a resource named by the
   Request-URI.


2.2.1 The Request-URI

   The Request-URI identifies the search arbiter. Any HTTP resource may
   function as search arbiter. It This is not a new type of resource (in the
   sense normal invocation of DAV:resourcetype as OPTIONS defined in [RFC2518]), nor does it have
   to be
   [RFC2616].

   If a WebDAV-compliant resource.

   The SEARCH method defines no relationship between the arbiter and the
   scope of the search, rather resource supports the particular query grammar used in SEARCH method, then the
   query defines server MUST list
   SEARCH in the relationship. For example, OPTIONS response as defined by [RFC2616].

   DASL servers MUST include the FOO query grammar
   may force DASL header in the request-URI to correspond exactly to OPTIONS response.
   This header identifies the search scope.


2.2.2 grammars supported by that
   resource.

3.2 The Request Body DASL Response Header

   DASLHeader = "DASL" ":" Coded-URL-List
   Coded-URL-List : Coded-URL [ "," Coded-URL-List ]
   Coded-URL ; defined in section 9.4 of [RFC2518]

   The DASL response header indicates server MUST process a text/xml or application/xml request body,
   and MAY process request bodies in other formats. See [RFC3023] support for
   guidance on packaging XML a query grammar
   in requests.

   If the client sends OPTIONS method. The value is a text/xml or application/xml body, it MUST
   include URI that indicates the DAV:searchrequest XML element. The DAV:searchrequest XML
   element identifies type of
   grammar. Note that although the query URI can be used to identify each
   supported search grammar, defines the criteria, there is not necessarily a direct
   relationship between the
   result record, URI and any other details needed to perform the search. XML element name that can be



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 8]

Internet Draft 14]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


2.3 The DAV:searchrequest


   used in XML Element based SEARCH requests (the element name itself is
   identified by it's namespace name (a URI reference) and the element's
   local name).

   This header MAY be repeated.

    For example:

   DASL: <http://foobar.test/syntax1>
   DASL: <http://akuma.test/syntax2>
   DASL: <DAV:basicsearch>
   DASL: <http://example.com/foo/natural-language-query>


3.3 DAV:supported-query-grammar-set (protected)

   This WebDAV property is required for any server supporting either
   [RFC3253] and/or [ACL] and identifies the XML based query grammars
   that are supported by the search arbiter resource.

   <!ELEMENT supported-query-grammar-set (supported-query-grammar*)>
   <!ELEMENT supported-query-grammar grammar>
   <!ELEMENT searchrequest grammar ANY>

   ANY >



   The DAV:searchrequest XML element contains value: a single XML element that
   defines the query. The name of the query grammar element defines the type of
   the query. The value of

3.4 Example: Grammar Discovery

   This example shows that element defines the query itself.


2.4 The Successful 207 (Multistatus) Response

   If the server returns 207 (Multistatus), then the supports search proceeded
   successfully and on the response MUST match that of a PROPFIND. The
   results of this method SHOULD NOT be cached.

   There MUST be one DAV:response for each /somefolder
   resource that matched the
   search criteria. For each such response, the DAV:href element
   contains the URI of with the resource, query grammars: DAV:basicsearch, http://
   foobar.test/syntax1 and the response MUST include a
   DAV:propstat element. http://akuma.test/syntax2. Note that for each matching resource found there may be multiple URIs
   within the search scope mapped to it. In this case, a server SHOULD
   report all of these URIs. Clients can use the live property
   DAV:resource-id defined in [BIND] to identify possible duplicates.

   In addition, the every
   server MAY include DAV:response items in the reply
   where the DAV:href element contains a URI that is not a matching
   resource, e.g. that of a scope or the query arbiter. Each such
   response item MUST NOT contain a DAV:propstat element, and MUST
   contain a DAV:status element (unless no property was selected).


2.4.1 Extending the PROPFIND Response

   A response MAY include more information than PROPFIND defines so long
   as the extra information does not invalidate the PROPFIND response.
   Query grammars SHOULD define how the response matches support DAV:basicsearch.

    >> Request:

   OPTIONS /somefolder HTTP/1.1
   Host: example.org

    >> Response:

   HTTP/1.1 200 OK
   Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE
   Allow: MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, SEARCH
   DASL: <DAV:basicsearch>
   DASL: <http://foobar.test/syntax1>
   DASL: <http://akuma.test/syntax2>

   This example shows the PROPFIND
   response. equivalent taking advantage of a server's



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 9]

Internet Draft 15]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


2.4.2 Example: A Simple Request and Response

   This example demonstrates the request and response framework. The
   following XML document shows a simple (hypothetical) natural language
   query. The name of the query element is natural-language-query in the
   XML namespace "http://example.com/foo". The actual query is "Find the
   locations of good Thai restaurants in Los Angeles". For this
   hypothetical query, the arbiter returns two properties


   support for each
   selected resource. DAV:supported-method-set and
   DAV:supported-query-grammar-set.

    >> Request:

   SEARCH /

   PROPFIND /somefolder HTTP/1.1
   Host: example.org
   Depth: 0
   Content-Type: application/xml text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="UTF-8"?>
   <D:searchrequest xmlns:D="DAV:" xmlns:F="http://example.com/foo">
     <F:natural-language-query>
       Find encoding="UTF-8" ?>
   <propfind xmlns="DAV:">
     <prop>
       <supported-query-grammar-set/>
       <supported-method-set/>
     </prop>
   </propfind>

    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="utf-8" ?>
   <multistatus xmlns="DAV:">
    <response>
     <href>http://example.org/somefolder</href>
     <propstat>
      <prop>
       <supported-query-grammar-set>
        <supported-query-grammar>
         <grammar><basicsearch/></grammar>
        </supported-query-grammar>
        <supported-query-grammar>
         <grammar><syntax1 xmlns="http://foobar.test" /></grammar>
        </supported-query-grammar>
        <supported-query-grammar>
         <grammar><syntax2 xmlns="http://akuma.test/"/></grammar>
        </supported-query-grammar>
       </supported-query-grammar-set>
       <supported-method-set>
        <supported-method name="COPY" />
        <supported-method name="DELETE" />
        <supported-method name="GET" />
        <supported-method name="HEAD" />
        <supported-method name="LOCK" />



Reschke, et al.          Expires April 9, 2004                 [Page 16]

Internet-Draft               WebDAV SEARCH                  October 2003


        <supported-method name="MKCOL" />
        <supported-method name="MOVE" />
        <supported-method name="OPTIONS" />
        <supported-method name="POST" />
        <supported-method name="PROPFIND" />
        <supported-method name="PROPPATCH" />
        <supported-method name="PUT" />
        <supported-method name="SEARCH" />
        <supported-method name="TRACE" />
        <supported-method name="UNLOCK" />
       </supported-method-set>
      </prop>
      <status>HTTP/1.1 200 OK</status>
     </propstat>
    </response>
   </multistatus>

   Note that the locations query grammar element names marshalled as part of good Thai restaurants the
   DAV:supported-query-grammar-set can be directly used as element names
   in Los Angeles
     </F:natural-language-query>
   </D:searchrequest>




   >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="UTF-8"?>
   <D:multistatus xmlns:D="DAV:"
      xmlns:R="http://example.org/propschema">
     <D:response>
       <D:href>http://siamiam.test/</D:href>
       <D:propstat>
         <D:prop>
           <R:location>259 W. Hollywood</R:location>
           <R:rating><R:stars>4</R:stars></R:rating>
         </D:prop>
       </D:propstat>
     </D:response>
   </D:multistatus> an XML based query.































Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 10]

Internet Draft 17]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


2.4.3 Example: Result Set Truncation

   A server


4. Query Schema Discovery: QSD

   Servers MAY limit support the number discovery of resources in the schema for a reply, query grammar.

   The DASL response header and the DAV:supported-query-grammar-set
   property provide means for example clients to
   limit discover the amount set of resources expended in processing query
   grammars supported by a resource. This alone is not sufficient
   information for a client to generate a query. If it For example, the
   DAV:basicsearch grammar defines a set of queries consisting of a set
   of operators applied to a set of properties and values, but the
   grammar itself does so, not specify which properties may be used in the reply MUST use status code 207, return
   query. QSD for the DAV:basicsearch grammar allows a DAV:multistatus
   response body client to
   discover the set of properties that are searchable, selectable, and indicate
   sortable. Moreover, although the DAV:basicsearch grammar defines a status
   minimal set of 507 (Insufficient Storage) operators, it is possible that a resource might
   support additional operators in a query. For example, a resource
   might support a optional operator that can be used to express
   content-based queries in a proprietary syntax. QSD allows a client to
   discover these operators and their syntax. The set of discoverable
   quantities will differ from grammar to grammar, but each grammar can
   define a means for
   the search arbiter URI. It SHOULD include the partial results.

   When a result set is truncated, there may client to discover what can be many more resources that
   satisfy discovered.

   In general, the search criteria but that were not examined.

   If partial results are included schema for a given query grammar depends on both the
   resource (the arbiter) and the client requested an ordered
   result scope. A given resource might have
   access to one set in the original request, then any partial results that are
   returned MUST be ordered as the client directed.

   Note that the partial results returned MAY be any subset of the
   result properties for one potential scope, and another
   set that would have satisfied for a different scope. For example, consider a server able to
   search two distinct collections, one holding cooking recipes, the original query.


   >> Request:

   SEARCH / HTTP/1.1
   Host: example.net
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

    ...
   other design documents for nuclear weapons. While both collections
   might support properties such as author, title, and date, the query goes here ...




   >> Response:

   HTTP/1.1 207 Multistatus
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="utf-8"?>
   <D:multistatus xmlns:D="DAV:">
     <D:response>
       <D:href>http://www.example.net/sounds/unbrokenchain.au</D:href>
       <D:propstat>
         <D:prop/>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://tech.mit.test/archive96/photos/Lesh1.jpg</D:href>



Reschke, et al.           Expires December 2003                [Page 11]

Internet Draft                WebDAV SEARCH                    June 2003


       <D:propstat>
         <D:prop/>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://example.net</D:href>
       <D:status>HTTP/1.1 507 Insufficient Storage</D:status>
       <D:responsedescription xml:lang="en">
          Only first two matching records were returned
       </D:responsedescription>
     </D:response>
   </D:multistatus>




2.5 Unsuccessful Responses

   If an error occurred that prevented execution of
   might also define properties such as calories and preparation time,
   while the second defined properties such as yield and applicable
   patents. Two distinct arbiters indexing the query, same collection might
   also have access to different properties. For example, the recipe
   collection mentioned above might also indexed by a value-added server MUST indicate
   that also stored the failure with names of chefs who had tested the appropriate status code and
   SHOULD include a DAV:multistatus element to point out errors
   associated with scopes.

   400 Bad Request. The recipe. Note
   also that the available query could schema might also depend on other
   factors, such as the identity of the principal conducting the search,
   but these factors are not be executed. The request may be
   malformed (not valid XML for example). Additionally, exposed in this can be used protocol.

4.1 Additional SEARCH semantics

   Each query grammar supported by DASL defines its own syntax for invalid scopes and search redirections.

   422 Unprocessable entity. The
   expressing the possible query could not be executed. If schema. A client retrieves the schema
   for a
   application/xml or text/xml request entity was provided, then it may
   have been well-formed but may have contained an unsupported or
   unimplemented given query operator.


2.6 Invalid Scopes


2.6.1 Indicating grammar on an Invalid Scope

   A client may submit arbiter resource with a given scope that
   by invoking the SEARCH method on that arbiter may be unable to query.
   The inability to query may be due to network failure, administrative
   policy, security, etc. This raises the condition described as an
   "invalid scope".

   To indicate an invalid scope, the server MUST respond with that grammar and
   scope and with a 400 (Bad
   Request). root element of DAV:query-schema-discovery rather
   than DAV:searchrequest.




Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 12]

Internet Draft 18]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   Marshalling:

      The response includes request body MUST be DAV:query-schema-discovery element.

   <!ELEMENT query-schema-discovery ANY>
   ANY value: XML element defining a valid query

      The response body with takes the form of a RFC2518 DAV:multistatus element. Each
      element, where DAV:response in is extended to hold the DAV:multistatus identifies returned query
      grammar inside a scope. To indicate
   that DAV:query-schema container element.

   <!ELEMENT response (href, ((href*, status)|(propstat+)),
     query-schema?, responsedescription?) >
   <!ELEMENT query-schema ANY>

   The content of this scope container is an XML element whose name and syntax
   depend upon the grammar, and whose value may (and likely will) vary
   depending upon the source grammar, arbiter, and scope.

4.1.1 Example of query schema discovery

   In this example, the error, arbiter is recipes.test, the server MUST include grammar is
   DAV:basicsearch, the DAV:scopeerror element.


2.6.2 Example of an Invalid Scope scope is also recipes.test.

    >> Response: Request:

   SEARCH / HTTP/1.1 400 Bad-Request
   Host: recipes.test
   Content-Type: text/xml; charset="utf-8" application/xml
   Content-Length: xxx

   <?xml version="1.0" encoding="UTF-8"?>

   <d:multistatus xmlns:d="DAV:">
     <d:response>
       <d:href>http://www.example.com/X</d:href>
         <d:status>HTTP/1.1 404 Object Not Found</d:status>
       <d:scopeerror/>
     </d:response>
   </d:multistatus> version="1.0"?>
   <query-schema-discovery xmlns="DAV:">
     <basicsearch>
       <from>
         <scope>
           <href>http://recipes.test</href>
           <depth>infinity</depth>
         </scope>
       </from>
     </basicsearch>
   </query-schema-discovery>

    >> Response:

   HTTP/1.1 207 Multistatus
   Content-Type: application/xml
   Content-Length: xxx



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 13]

Internet Draft 19]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


3 Discovery of Supported Query Grammars

   Servers MUST support discovery of


   <?xml version="1.0"?>
   <multistatus xmlns="DAV:">
     <response>
       <href>http://recipes.test</href>
       <status>HTTP/1.1 200 OK</status>
       <query-schema>
         <basicsearchschema>
           <!-- (See section "Query schema for DAV:basicsearch" for
           the actual contents) -->
         </basicsearchschema>
       </query-schema>
     </response>
   </multistatus>

   The query grammars supported by a schema for DAV:basicsearch is defined in Section 5.19.




































Reschke, et al.          Expires April 9, 2004                 [Page 20]

Internet-Draft               WebDAV SEARCH                  October 2003


5. The DAV:basicsearch Grammar

5.1 Introduction

   DAV:basicsearch uses an extensible XML syntax that allows clients to
   express search arbiter resource.

   Clients can determine which query grammars requests that are supported by an
   arbiter by invoking OPTIONS on generally useful for WebDAV
   scenarios. DASL-extended servers MUST accept this grammar, and MAY
   accept other grammars.

   DAV:basicsearch has several components:

   o  DAV:select provides the search arbiter. If result record definition.

   o  DAV:from defines the resource
   supports SEARCH, then scope.

   o  DAV:where defines the DASL response header will appear in criteria.

   o  DAV:orderby defines the
   response. The DASL response header lists sort order of the supported grammars.

   Servers supporting result set.

   o  DAV:limit provides constraints on the query as a whole.


5.2 The DAV:basicsearch DTD

   <!ELEMENT basicsearch   (select, from, where?, orderby?, limit?) >

   <!ELEMENT select        (allprop | prop) >

   <!ELEMENT from          (scope) >
   <!ELEMENT scope         (href, depth) >

   <!ENTITY %comp_ops      "eq | lt | gt| lte | gte">
   <!ENTITY %log_ops       "and | or | not">
   <!ENTITY %special_ops   "is-collection | is-defined">
   <!ENTITY %string_ops    "like">
   <!ENTITY %content_ops   "contains">

   <!ENTITY %all_ops       "%comp_ops; | %log_ops; | %special_ops; |
                            %string_ops; | %content_ops;">

   <!ELEMENT where         ( %all_ops; ) >

   <!ELEMENT and           ( ( %all_ops; ) +) >

   <!ELEMENT or            ( ( %all_ops; ) +) >

   <!ELEMENT not           ( %all_ops; ) >




Reschke, et al.          Expires April 9, 2004                 [Page 21]

Internet-Draft               WebDAV extensions [RFC3253] and/or [ACL] MUST
   also

   o  report SEARCH in                  October 2003


   <!ELEMENT lt            (prop, literal) >
   <!ATTLIST lt            caseless   (yes|no) >

   <!ELEMENT lte           (prop, literal) >
   <!ATTLIST lte           caseless   (yes|no) >

   <!ELEMENT gt            (prop, literal) >
   <!ATTLIST gt            caseless   (yes|no) >

   <!ELEMENT gte           (prop, literal) >
   <!ATTLIST gte           caseless   (yes|no) >

   <!ELEMENT eq            (prop, literal) >
   <!ATTLIST eq            caseless   (yes|no) >

   <!ELEMENT literal       (#PCDATA)>

   <!ELEMENT is-defined    (prop) >

   <!ELEMENT like          (prop, literal) >
   <!ATTLIST like          caseless   (yes|no) >

   <!ELEMENT contains      (#PCDATA)>

   <!ELEMENT orderby       (order+) >
   <!ELEMENT order         ((prop | score), (ascending | descending)?)
   <!ATTLIST order         caseless   (yes|no) >
   <!ELEMENT ascending     EMPTY>
   <!ELEMENT descending    EMPTY>

   <!ELEMENT limit         (nresults) >
   <!ELEMENT nresults      (#PCDATA) >


5.2.1 Example Query

   This query retrieves the live property DAV:supported-method-set content length values for all search arbiter resources and

   o  support the live property DAV:supported-query-grammar-set as
      defined in section3.3.


3.1 The OPTIONS Method

   The OPTIONS method allows the client to discover if a resource
   supports the SEARCH method and to determine the list of search
   grammars supported for that resource.

   The client issues the OPTIONS method against a resource named by the
   Request-URI. This is a normal invocation of OPTIONS defined in
   [RFC2616].

   If a resource supports the SEARCH method, then the server MUST list
   SEARCH in the OPTIONS response as defined by [RFC2616].

   DASL servers MUST include the DASL header in the OPTIONS response.
   This header identifies
   located under the search grammars supported by that
   resource.


3.2 The DASL Response Header


   >> Response:

   DASLHeader = "DASL" ":" Coded-URL-List
   Coded-URL-List : Coded-URL [ "," Coded-URL-List ]
   Coded-URL ; defined in section 9.4 of [RFC2518] server's "/container1/" URI namespace whose length
   exceeds 10000.

   <d:searchrequest xmlns:d="DAV:">
     <d:basicsearch>
       <d:select>
         <d:prop><d:getcontentlength/></d:prop>
       </d:select>
       <d:from>
         <d:scope>
           <d:href>/container1/</d:href>



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 14]

Internet Draft 22]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   The DASL response header indicates server support for


           <d:depth>infinity</d:depth>
         </d:scope>
       </d:from>
       <d:where>
         <d:gt>
           <d:prop><d:getcontentlength/></d:prop>
           <d:literal>10000</d:literal>
         </d:gt>
       </d:where>
         <d:orderby>
           <d:order>
           <d:prop><d:getcontentlength/></d:prop>
           <d:ascending/>
         </d:order>
       </d:orderby>
     </d:basicsearch>
   </d:searchrequest>


5.3 DAV:select

   DAV:select defines the result record, which is a query grammar set of properties
   and values. This document defines two possible values: DAV:allprop
   and DAV:prop, both defined in [RFC2518] and revised in [RFC3253].

5.4 DAV:from

   <!ELEMENT scope            (href, depth, include-versions?) >
   <!ELEMENT include-versions EMPTY >

   DAV:from defines the OPTIONS method. query scope. This contains exactly one DAV:scope
   element. The value is a URI that scope element contains mandatory DAV:href and DAV:depth
   elements.

   DAV:href indicates the type of
   grammar. Note that although the URI can be used to identify each
   supported search grammar, there use as a scope.

   When the scope is not necessarily a direct
   relationship between collection, if DAV:depth is "0", the URI and search
   includes only the XML element name that can be
   used in XML based SEARCH requests (the element name itself collection. When it is
   identified by it's namespace name (a URI reference) and "1", the element's
   local name).

   This header MAY be repeated.


   For example:

   DASL: <http://foobar.test/syntax1>
   DASL: <http://akuma.test/syntax2>
   DASL: <DAV:basicsearch>
   DASL: <http://example.com/foo/natural-language-query>




3.3 DAV:supported-query-grammar-set (protected)

   This WebDAV property is required for any server supporting either
   [RFC3253] and/or [ACL] and identifies search includes the XML based query grammars
   that are supported by
   (toplevel) members of the search arbiter resource.




   <!ELEMENT supported-query-grammar-set (supported-query-grammar*)>

   <!ELEMENT supported-query-grammar grammar>

   <!ELEMENT grammar ANY>



   ANY value: a query grammar element type


3.4 Example: Grammar Discovery

   This example shows that collection. When it is "infinity", the server supports
   search on includes all recursive members of the /somefolder
   resource with collection. When the query grammars: DAV:basicsearch,
   http://foobar.test/syntax1 and http://akuma.test/syntax2. Note that
   every server MUST support DAV:basicsearch.



Reschke, et al.           Expires December 2003                [Page 15]

Internet Draft                WebDAV SEARCH                    June 2003


   >> Request:

   OPTIONS /somefolder HTTP/1.1
   Host: example.org




   >> Response:

   HTTP/1.1 200 OK
   Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE
   Allow: MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, SEARCH
   DASL: <DAV:basicsearch>
   DASL: <http://foobar.test/syntax1>
   DASL: <http://akuma.test/syntax2>



   This example shows
   scope is not a collection, the equivalent taking advantage depth is ignored and the search
   applies just to the resource itself.

   When the child element DAV:include-versions is present, the search
   scope will include all versions (see [RFC3253], section 2.2.1) of a server's all
   version-controlled resources in scope. Servers that do support for DAV:supported-method-set and DAV:supported-query-grammar-
   set.


   >> Request:

   PROPFIND /somefolder HTTP/1.1
   Host: example.org
   Depth: 0
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="UTF-8" ?>
   <propfind xmlns="DAV:">
     <prop>
       <supported-query-grammar-set/>
       <supported-method-set/>
     </prop>
   </propfind>




   >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx
   versioning but do not support the DAV:include-versions feature MUST
   signal an error if it is used in a query.



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 16]

Internet Draft 23]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   <?xml version="1.0" encoding="utf-8" ?>
   <multistatus xmlns="DAV:">
    <response>
     <href>http://example.org/somefolder</href>
     <propstat>
      <prop>
       <supported-query-grammar-set>
        <supported-query-grammar>
         <grammar><basicsearch/></grammar>
        </supported-query-grammar>
        <supported-query-grammar>
         <grammar><syntax1 xmlns="http://foobar.test" /></grammar>
        </supported-query-grammar>
        <supported-query-grammar>
         <grammar><syntax2 xmlns="http://akuma.test/"/></grammar>
        </supported-query-grammar>
       </supported-query-grammar-set>
       <supported-method-set>
        <supported-method name="COPY" />
        <supported-method name="DELETE" />
        <supported-method name="GET" />
        <supported-method name="HEAD" />
        <supported-method name="LOCK" />
        <supported-method name="MKCOL" />
        <supported-method name="MOVE" />
        <supported-method name="OPTIONS" />
        <supported-method name="POST" />
        <supported-method name="PROPFIND" />
        <supported-method name="PROPPATCH" />
        <supported-method name="PUT" />
        <supported-method name="SEARCH" />
        <supported-method name="TRACE" />
        <supported-method name="UNLOCK" />
       </supported-method-set>
      </prop>
      <status>HTTP/1.1 200 OK</status>
     </propstat>
    </response>
   </multistatus>



   Note


5.4.1 Relationship to the Request-URI

   If the DAV:scope element is an absolute URI, the scope is exactly
   that URI.

   If the DAV:scope element is  is an absolute URI reference, the scope
   is taken to be relative to the request-URI.

5.4.2 Scope

   A Scope can be an arbitrary URI.

   Servers, of course, may support only particular scopes. This may
   include limitations for particular schemes such as "http:" or "ftp:"
   or certain URI namespaces.

5.5 DAV:where

   The DAV:where element defines the query grammar search condition for inclusion of
   resources in the result set. The value of this element names marshalled is an XML
   element that defines a search operator that evaluates to one of the
   Boolean truth values TRUE, FALSE, or UNKNOWN. The search operator
   contained by DAV:where may itself contain and evaluate additional
   search operators as part operands, which in turn may contain and evaluate
   additional search operators as operands, etc. recursively.

5.5.1 Use of Three-Valued Logic in Queries

   Each operator defined for use in the
   DAV:supported-query-grammar-set can be directly used where clause that returns a
   Boolean value MUST evaluate to TRUE, FALSE, or UNKNOWN. The resource
   under scan is included as element names a member of the result set if and only if
   the search condition evaluates to TRUE.

   Consult Appendix A for details on the application of three-valued
   logic in query expressions.

5.5.2 Handling Optional operators

   If a query contains an XML based query. operator that is not supported by the server,
   then the server MUST respond with a 422 (Unprocessable Entity) status
   code.

5.5.3 Treatment of NULL Values

   If a PROPFIND for a property value would yield a non-2xx (see
   [RFC2616], section 10.2) response for that property, then that
   property is considered NULL.




Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 17]

Internet Draft 24]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


4 Query Schema Discovery: QSD

   Servers MAY support the discovery of the schema for


   NULL values are "less than" all other values in comparisons.

   Empty strings (zero length strings) are not NULL values. An empty
   string is "less than" a query grammar. string with length greater than zero.

   The DASL response header and the DAV:supported-query-grammar-set
   property provide means for clients DAV:is-defined operator is defined to discover test if the set value of query
   grammars supported by a resource. This alone
   property is NULL.

5.5.4 Treatment of properties with mixed/element content

   Comparisons of properties that do not sufficient
   information have simple types (text-only
   content) is out-of-scope for a client to generate a query. For example, the
   DAV:basicsearch grammar defines a set of queries consisting of a set
   of standard operators applied to a set of properties defined for
   DAV:basicsearch and values, but the
   grammar itself does not specify which properties may therefore is defined to be used in UNKNOWN (as per
   Appendix A). For querying the
   query. QSD DAV:resourcetype property, see Section
   5.13.

5.5.5 Example: Testing for Equality

   The example shows a single operator (DAV:eq) applied in the DAV:basicsearch grammar allows criteria.

   <d:where>
     <d:eq>
       <d:prop>
         <d:getcontentlength/>
       </d:prop>
       <d:literal>100</d:literal>
     </d:eq>
   </d:where>

5.5.6 Example: Relative Comparisons

   The example shows a client to
   discover more complex operation involving several
   operators (DAV:and, DAV:eq, DAV:gt) applied in the set of properties criteria. This
   DAV:where expression matches those resources that are searchable, selectable, and
   sortable. Moreover, although "image/gifs"
   over 4K in size.

   <D:where>
     <D:and>
       <D:eq>
         <D:prop>
           <D:getcontenttype/>
         </D:prop>
         <D:literal>image/gif</D:literal>
       </D:eq>
       <D:gt>
         <D:prop>
           <D:getcontentlength/>
         </D:prop>



Reschke, et al.          Expires April 9, 2004                 [Page 25]

Internet-Draft               WebDAV SEARCH                  October 2003


         <D:literal>4096</D:literal>
       </D:gt>
     </D:and>
   </D:where>

5.6 DAV:orderby

   The DAV:orderby element specifies the DAV:basicsearch grammar defines a
   minimal set ordering of operators, it is possible that the result set. It
   contains one or more DAV:order elements, each of which specifies a resource might
   support additional operators
   comparison between two items in the result set. Informally, a query. For example, a resource
   might support
   comparison specifies a optional operator test that can be used to express
   content-based queries determines whether one resource
   appears before another in a proprietary syntax. QSD allows a client to
   discover these operators and their syntax. the result set. Comparisons are applied in
   the order they occur in the DAV:orderby element, earlier comparisons
   being more significant.

   The set of discoverable
   quantities will differ comparisons defined here use only a single property from grammar to grammar, but each grammar can
   define a means for a client to discover what can be discovered.

   In general,
   resource, compared using the schema for a given query grammar depends on both same ordering as the
   resource (the arbiter) and DAV:lt operator
   (ascending) or DAV:gt operator (descending). If neither direction is
   specified, the scope. A given resource might have
   access default is DAV:ascending.

   In the context of the DAV:orderby element, null values are considered
   to one set collate before any actual (i.e., non null) value, including
   strings of properties zero length (this is compatible with [SQL99]).

5.6.1 Comparing Natural Language Strings

   Comparisons on strings take into account the language defined for one potential scope, and another
   set
   that property. Clients MAY specify the language using the xml:lang
   attribute. If no language is specified either by the client or
   defined for that property by the server or if a comparison is
   performed on strings of two different scope. For example, consider a server able languages, the results are
   undefined.

   The "caseless" attribute may be used to
   search two distinct collections, one holding cooking recipes, indicate case-sensitivity for
   comparisons.

5.6.2 Example of Sorting

   This sort orders first by last name of the
   other design documents for nuclear weapons. While both collections
   might support properties such as author, title, and date, the first
   might also define properties such as calories and preparation time,
   while then by size,
   in descending order, so that for each author, the second defined properties such as yield largest works
   appear first.

   <d:orderby>
     <d:order>
       <d:prop><r:lastname/></d:prop>
       <d:ascending/>
     </d:order>
     <d:order>



Reschke, et al.          Expires April 9, 2004                 [Page 26]

Internet-Draft               WebDAV SEARCH                  October 2003


       <d:prop><d:getcontentlength/></d:prop>
       <d:descending/>
     </d:order>
   </d:orderby>

5.7 Boolean Operators: DAV:and, DAV:or, and applicable
   patents. Two distinct arbiters indexing the same collection might
   also have access to different properties. For example, the recipe
   collection mentioned above might also indexed by DAV:not

   The DAV:and operator performs a value-added server
   that also stored logical AND operation on the names of chefs who had tested
   expressions it contains.

   The DAV:or operator performs a logical OR operation on the recipe. Note
   also that values it
   contains.

   The DAV:not operator performs a logical NOT operation on the available query schema might also depend values
   it contains.

5.8 DAV:eq

   The DAV:eq operator provides simple equality matching on other
   factors, such as property
   values.

   The "caseless" attribute may be used with this element.

5.9 DAV:lt, DAV:lte, DAV:gt, DAV:gte

   The DAV:lt, DAV:lte, DAV:gt, and DAV:gte operators provide
   comparisons on property values, using less-than, less-than or equal,
   greater-than, and greater-than or equal respectively. The "caseless"
   attribute may be used with these elements.

5.10 DAV:literal

   DAV:literal allows literal values to be placed in an expression.

   White space in literal values is significant in comparisons. For
   consistency with [RFC2518], clients SHOULD NOT specify the identity attribute
   "xml:space" (section 2.10 of the principal conducting the search,
   but these factors are not exposed in [XML]) to override this protocol.


4.1 Additional SEARCH semantics

   Each query grammar supported by DASL defines its own syntax for
   expressing behaviour.

   In comparisons, the possible query schema. A client retrieves contents of DAV:literal SHOULD be treated as
   string, with the schema following exceptions:

   o  when operand for a given query grammar on an arbiter resource comparison with a given scope
   by invoking the SEARCH method on that arbiter with that grammar and
   scope and DAV:getcontentlength
      property, it SHOULD be treated as an integer value (the behaviour
      for non-integer values is undefined),

   o  when operand for a comparison with a root element of DAV:query-schema-discovery rather
   than DAV:searchrequest. DAV:creationdate or
      DAV:getlastmodified property, it SHOULD be treated as a date value
      in the ISO-8601 subset defined for the DAV:creationdate property



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 18]

Internet Draft 27]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   Marshalling:

      The request body MUST be DAV:query-schema-discovery element.



         <!ELEMENT query-schema-discovery ANY>
         ANY value: XML element defining


      ([RFC2518], section 13.1).

   o  when operand for a valid query




      The response body takes the form of comparison with a RFC2518 DAV:multistatus
      element, where DAV:response property for which the type
      is extended known, it MAY be treated according to hold the returned query
      grammar inside this type.


5.11 DAV:typed-literal (optional)

   There are situations in which a DAV:query-schema container element.



         <!ELEMENT response (href, ((href*, status)|(propstat+)),
           query-schema?, responsedescription?) > client may want to force a comparison
   not to be string-based (as defined for DAV:literal). In these cases,
   a typed comparison can be enforced by using DAV:typed-literal
   instead.

   <!ELEMENT query-schema ANY> typed-literal (#PCDATA)>

   The content of this container data type is an XML element whose name and syntax
   depend upon specified using the grammar, and whose value may (and likely will) vary
   depending upon xsi:type attribute defined in
   [XS1], section 2.6.1. If the grammar, arbiter, and scope.


4.1.1 type is not specified, it defaults to
   "xs:string".

   A server MUST reject a request with an unknown type.

5.11.1 Example for typed numerical comparison

   Consider a set of query schema discovery

   In this example, the arbiter is recipes.test, resources with the grammar is
   DAV:basicsearch, dead property "edits" in the scope is also recipes.test.


   >> Request:

   SEARCH / HTTP/1.1
   Host: recipes.test
   Content-Type: application/xml
   Content-Length: xxx

   <?xml version="1.0"?>
   <query-schema-discovery xmlns="DAV:">
     <basicsearch>
       <from>
   namespace "http://ns.example.org":

                        +-----+----------------+
                        | URI | property value |
                        +-----+----------------+
                        | /a  | "-1"           |
                        |     |                |
                        | /b  | "01"           |
                        |     |                |
                        | /c  | "3"            |
                        |     |                |
                        | /d  | "test"         |
                        |     |                |
                        | /e  | (undefined)    |
                        +-----+----------------+

   The expression

   <lt xmlns="DAV:"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <prop><edits xmlns="http://ns.example.org"/></prop>
     <typed-literal xsi:type="xs:integer">3</typed-literal>
   </lt>



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 19]

Internet Draft 28]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


         <scope>
           <href>http://recipes.test</href>
           <depth>infinity</depth>
         </scope>
       </from>
     </basicsearch>
   </query-schema-discovery>




   >> Response:

   HTTP/1.1 207 Multistatus
   Content-Type: application/xml
   Content-Length: xxx

   <?xml version="1.0"?>
   <multistatus xmlns="DAV:">
     <response>
       <href>http://recipes.test</href>
       <status>HTTP/1.1 200 OK</status>
       <query-schema>
         <basicsearchschema>
           <!-- (See section "Query schema for DAV:basicsearch"


   will evaluate to TRUE for the actual contents) -->
         </basicsearchschema>
       </query-schema>
     </response>
   </multistatus>



   The query schema resources "/a" and "/b" (their property
   values can be parsed as type xs:number, and the numerical comparison
   evaluates to true), to FALSE for "/c" (property value is compatible,
   but numerical comparison evaluates to false) and UNKNOWN for DAV:basicsearch "/d" and
   "/e" (the property either is defined in section5.19.

















Reschke, et al.           Expires December 2003                [Page 20]

Internet Draft                WebDAV SEARCH                    June 2003


5 undefined, or its value can not be
   parsed as xs:number).

5.12 Support for matching xml:lang attributes on properties

   The DAV:basicsearch Grammar


5.1 Introduction

   DAV:basicsearch uses an extensible XML syntax that allows clients following two optional operators can be used to express search requests that are generally useful
   conditions on the language of a property value (as expressed using
   the xml:lang attribute).

5.12.1 DAV:language-defined (optional)

   <!ELEMENT language-defined (prop)>

   This operator evaluates to TRUE if the language for WebDAV
   scenarios. DASL-extended servers MUST accept this grammar, and MAY
   accept other grammars.

   DAV:basicsearch has several components:



   o  DAV:select provides the result record definition.

   o  DAV:from defines value of the scope.

   o  DAV:where defines
   given property is known, FALSE if it isn't and UNKNOWN if the criteria.

   o  DAV:orderby defines
   property itself is not defined.

5.12.2 DAV:language-matches (optional)

   <!ELEMENT language-matches (prop, literal)>

   This operator evaluates to TRUE if the sort order language for the value of the result set.

   o  DAV:limit provides constraints on
   given property is known and matches the query as language name given in the
   <literal> element, FALSE if it doesn't match and UNKNOWN if the
   property itself is not defined.

   Languages are considered to match if they are the same, or if the
   language of the property value is a whole.


5.2 The DAV:basicsearch DTD




   <!ELEMENT basicsearch   (select, from, where?, orderby?, limit?) >

   <!ELEMENT select        (allprop | prop) >

   <!ELEMENT from          (scope) >
   <!ELEMENT scope         (href, depth) >

   <!ENTITY %comp_ops      "eq | lt | gt| lte | gte">
   <!ENTITY %log_ops       "and | sublanguage of the language
   specified in the <literal> element (see [XPATH], section 4.3, "lang
   function").

5.12.3 Example of language-aware matching

   The expression below will evaluate to TRUE if the property "foobar"
   exists and it's language is either unknown, English or | not">
   <!ENTITY %special_ops   "is-collection | is-defined">
   <!ENTITY %string_ops    "like">
   <!ENTITY %content_ops   "contains">

   <!ENTITY %all_ops       "%comp_ops; | %log_ops; | %special_ops; |
                            %string_ops; | %content_ops;">

   <!ELEMENT where         ( %all_ops; ) > a sublanguage
   of English.

   <or xmlns="DAV:">
     <not>
       <language-defined>
         <prop><foobar/></prop>
       </language-defined>
     </not>
     <language-matches>



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 21]

Internet Draft 29]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   <!ELEMENT and           ( ( %all_ops; ) +) >

   <!ELEMENT or            ( ( %all_ops; ) +) >

   <!ELEMENT not           ( %all_ops; ) >

   <!ELEMENT lt            (prop, literal) >
   <!ATTLIST lt            caseless   (yes|no) >

   <!ELEMENT lte           (prop, literal) >
   <!ATTLIST lte           caseless   (yes|no) >

   <!ELEMENT gt            (prop, literal) >
   <!ATTLIST gt            caseless   (yes|no) >

   <!ELEMENT gte           (prop, literal) >
   <!ATTLIST gte           caseless   (yes|no) >

   <!ELEMENT eq            (prop, literal) >
   <!ATTLIST eq            caseless   (yes|no) >

   <!ELEMENT literal       (#PCDATA)>

   <!ELEMENT is-defined    (prop) >

   <!ELEMENT like          (prop, literal) >
   <!ATTLIST like          caseless   (yes|no) >

   <!ELEMENT


       <prop><foobar/></prop>
       <literal>en</literal>
     </language-matches>
   </or>


5.13 DAV:is-collection

   The DAV:is-collection operator allows clients to determine whether a
   resource is a collection (that is, whether it's DAV:resourcetype
   element contains      (#PCDATA)>

   <!ELEMENT orderby       (order+) >
   <!ELEMENT order         ((prop | score), (ascending | descending)?)
   <!ATTLIST order         caseless   (yes|no) >
   <!ELEMENT ascending     EMPTY>
   <!ELEMENT descending    EMPTY>

   <!ELEMENT limit         (nresults) >
   <!ELEMENT nresults      (#PCDATA) >




5.2.1 Example Query

   This query retrieves the content length values element DAV:collection).

   Rationale: This operator is provided in lieu of defining generic
   structure queries, which would suffice for this and for many more
   powerful queries, but seems inappropriate to standardize at this
   time.

5.13.1 Example of DAV:is-collection

   This example shows a search criterion that picks out all and only the
   resources
   located under in the server's "/container1/" URI namespace whose length
   exceeds 10000. scope that are collections.

   <where xmlns="DAV:">
     <is-collection/>
   </where>

5.14 DAV:is-defined

   The DAV:is-defined operator allows clients to determine whether a
   property is defined on a resource. The meaning of "defined on a
   resource" is found in Section 5.5.3.

   Example:

   <d:is-defined>
     <d:prop><x:someprop/></d:prop>
   </d:is-defined>

5.15 DAV:like

   The DAV:like is an optional operator intended to give simple
   wildcard-based pattern matching ability to clients.

   The operator takes two arguments.

   The first argument is a DAV:prop element identifying a single
   property to evaluate.




Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 22]

Internet Draft 30]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   <d:searchrequest xmlns:d="DAV:">
     <d:basicsearch>
       <d:select>
         <d:prop><d:getcontentlength/></d:prop>
       </d:select>
       <d:from>
         <d:scope>
           <d:href>/container1/</d:href>
           <d:depth>infinity</d:depth>
         </d:scope>
       </d:from>
       <d:where>
         <d:gt>
           <d:prop><d:getcontentlength/></d:prop>
           <d:literal>10000</d:literal>
         </d:gt>
       </d:where>
         <d:orderby>
           <d:order>
           <d:prop><d:getcontentlength/></d:prop>
           <d:ascending/>
         </d:order>
       </d:orderby>
     </d:basicsearch>
   </d:searchrequest>




5.3 DAV:select

   DAV:select defines the result record, which


   The second argument is a set DAV:literal element that gives the pattern
   matching string.

5.15.1 Syntax for the Literal Pattern

   Pattern := [wildcard] 0*( text [wildcard] )
   wildcard := exactlyone | zeroormore
   text := 1*( <character> | escapesequence )
   exactlyone : = "_"
   zeroormore := "%"
   escapechar := "\"
   escapesequence := "\" ( exactlyone | zeroormore | escapechar )
   character: valid XML characters (see section 2.2 of properties
   and values. This document defines two possible values: DAV:allprop
   and DAV:prop, both defined in [RFC2518] and revised in [RFC3253].


5.4 DAV:from

   DAV:from defines [XML]),
              minus ( exactlyone | zeroormore | escapechar )

   The value for the literal is composed of wildcards separated by
   segments of text. Wildcards may begin or end the query scope. This contains literal.

   The "_" wildcard matches exactly one DAV:scope
   element. character.

   The scope element contains mandatory DAV:href "%" wildcard matches zero or more characters

   The "\" character is an escape sequence so that the literal can
   include >"_" and DAV:depth
   elements.

   DAV:href indicates "%". To include the URI to use as a scope.

   When "\" character in the scope pattern,
   the escape sequence "\\" is used.

5.15.2 Example of DAV:like

   This example shows how a collection, if DAV:depth is "0", the search
   includes only the collection. When it client might use DAV:like to identify those
   resources whose content type was a subtype of image.

   <D:where>
     <D:like caseless="yes">
       <D:prop><D:getcontenttype/></D:prop>
       <D:literal>image/%</D:literal>
     </D:like>
   </D:where>

5.16 DAV:contains

   The DAV:contains operator is "1", the an optional operator that provides
   content-based search includes capability. This operator implicitly searches
   against the
   (toplevel) members text content of the collection. When it a resource, not against content of
   properties. The DAV:contains operator is "infinity", intentionally not overly
   constrained, in order to allow the
   search includes all recursive members of server to do the collection. When best job it can
   in performing the search.

   The DAV:contains operator evaluates to a Boolean value. It evaluates



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 23]

Internet Draft 31]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   scope is not a collection, the depth is ignored and the search
   applies just to the resource itself.


5.4.1 Relationship


   to TRUE if the Request-URI

   If content of the DAV:scope element is an absolute URI, resource satisfies the scope is exactly
   that URI.

   If search.
   Otherwise, It evaluates to FALSE.

   Within the DAV:scope element is is an absolute URI reference, DAV:contains XML element, the scope client provides a phrase: a
   single word or whitespace delimited sequence of words. Servers MAY
   ignore punctuation in a phrase. Case-sensitivity is taken to be relative left to the request-URI.


5.4.2 Scope

   A Scope can be an arbitrary URI.

   Servers, of course,
   server.

   The following things may support only particular scopes. This or may
   include limitations for particular schemes not be done as part of the search:
   Phonetic methods such as "http:" "soundex" may or "ftp:" may not be used. Word
   stemming may or certain URI namespaces.


5.5 DAV:where

   The DAV:where element defines the search condition for inclusion may not be performed. Thesaurus expansion of
   resources in the result set. words
   may or may not be done. Right or left truncation may or may not be
   performed. The value of this element is an XML
   element that defines a search operator that evaluates to one of the
   Boolean truth values TRUE, FALSE, may be case insensitive or UNKNOWN. case sensitive. The search operator
   contained by DAV:where
   word or words may itself contain and evaluate additional
   search operators as operands, which in turn or may contain and evaluate
   additional search operators not be interpreted as operands, etc. recursively.


5.5.1 Use of Three-Valued Logic in Queries

   Each operator defined for use names. Multiple words
   may or may not be required to be adjacent or "near" each other.
   Multiple words may or may not be required to occur in the where clause that returns a
   Boolean value MUST evaluate to TRUE, FALSE, same order.
   Multiple words may or UNKNOWN. may not be treated as a phrase. The resource
   under scan is included search may
   or may not be interpreted as a member of request to find documents "similar" to
   the result set if and only if string operand.

5.16.1 Result scoring (DAV:score element)

   Servers SHOULD indicate scores for the search DAV:contains condition evaluates by
   adding a DAV:score XML element to TRUE.

   Consult appendixA for details on the application of three-valued
   logic DAV:response element. It's
   value is defined only in query expressions.


5.5.2 Handling Optional operators

   If the context of a particular query contains an operator that result.
   The value is not supported by the server,
   then the server MUST respond with a 422 (Unprocessable Entity) status



Reschke, et al.           Expires December 2003                [Page 24]

Internet Draft                WebDAV SEARCH                    June 2003


   code.


5.5.3 Treatment of NULL Values

   If a PROPFIND for string representing the score, an integer from zero to
   10000 inclusive, where a property higher value would yield indicates a non-2xx (see
   [RFC2616], section 10.2) response higher score (e.g.
   more relevant).

   Modified DTD fragment for that property, then that
   property is considered NULL.

   NULL values are "less than" all other values DAV:propstat:

   <!ELEMENT response (href, ((href*, status)|(propstat+)),
                       responsedescription?, score?) >
   <!ELEMENT score    (#PCDATA) >

   Clients should note that, in comparisons.

   Empty strings (zero length strings) are not NULL values. An empty
   string is "less than" a string with length greater than zero.

   The DAV:isdefined operator general, it is defined not meaningful to test if compare
   the value of a
   property is NULL.


5.5.4 Treatment numeric values of properties with mixed/element content

   Comparisons scores from two different query results unless
   both were executed by the same underlying search system on the same
   collection of properties that do not have simple types (text-only
   content) is out-of-scope for resources.

5.16.2 Ordering by score

   To order search results by their score, the standard operators defined for
   DAV:basicsearch and therefore is defined to DAV:score element may be UNKNOWN (as per
   appendixA). For querying
   added as child to the DAV:resourcetype property, see
   section5.13.


5.5.5 Example: Testing for Equality

   The example shows DAV:orderby element (in place of a single operator (DAV:eq) applied in the criteria.




   <d:where>
     <d:eq>
       <d:prop>
         <d:getcontentlength/>
       </d:prop>
       <d:literal>100</d:literal>
     </d:eq>
   </d:where> DAV:prop
   element).

5.16.3 Examples




Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 25]

Internet Draft 32]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


5.5.6 Example: Relative Comparisons


   The example below shows a more complex operation involving several
   operators (DAV:and, DAV:eq, DAV:gt) applied in search for the criteria. This
   DAV:where expression matches those phrase "Peter Forsberg".

   Depending on its support for content-based searching, a server MAY
   treat this as a search for documents that contain the words "Peter"
   and "Forsberg".

   <D:where>
     <D:contains>Peter Forsberg</D:contains>
   </D:where>

   The example below shows a search for resources that are "image/gifs"
   over 4K in size. contain "Peter"
   and "Forsberg".

   <D:where>
     <D:and>
       <D:eq>
         <D:prop>
           <D:getcontenttype/>
         </D:prop>
         <D:literal>image/gif</D:literal>
       </D:eq>
       <D:gt>
         <D:prop>
           <D:getcontentlength/>
         </D:prop>
         <D:literal>4096</D:literal>
       </D:gt>
       <D:contains>Peter</D:contains>
       <D:contains>Forsberg</D:contains>
     </D:and>
   </D:where>




5.6 DAV:orderby

5.17 Limiting the result set

   <!ELEMENT limit (nresults) >
   <!ELEMENT nresults (#PCDATA)> ;only digits

   The DAV:orderby DAV:limit XML element specifies contains requested limits from the ordering client
   to limit the size of the result set. It
   contains one reply or more DAV:order elements, each amount of which specifies effort expended by the
   server. The DAV:nresults XML element contains a
   comparison between two items requested maximum
   number of DAV:response elements to be returned in the response body.
   The server MAY disregard this limit. The value of this element is an
   integer.

5.17.1 Relationship to result set. Informally, a
   comparison specifies a test that determines whether one resource
   appears before another in ordering

   If the result set. Comparisons set is both limited by DAV:limit and ordered according
   to DAV:orderby, the results that are applied included in the response
   document must be those that order they occur in the DAV:orderby element, earlier comparisons
   being more significant. highest.

5.18 The comparisons defined here use only a single property from each
   resource, compared using the same ordering as the DAV:lt operator
   (ascending) or DAV:gt operator (descending). If neither direction is
   specified, the default is DAV:ascending.

   In the context 'caseless' XML attribute

   The "caseless" attribute allows clients to specify caseless matching
   behaviour instead of the DAV:orderby element, null character-by-character matching for
   DAV:basicsearch operators.

   The possible values for "caseless" are considered
   to collate before any actual (i.e., non null) value, including
   strings of zero length (this "yes" or "no". The default
   value is compatible with [SQL99]). server-specified. Caseless matching SHOULD be implemented as
   defined in [CaseMap].




Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 26]

Internet Draft 33]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


5.6.1 Comparing Natural Language Strings

   Comparisons on strings take into account


   Support for the language defined "caseless" attribute is optional. A server should
   respond with a status of 422 if it is used but cannot be supported.

5.19 Query schema for DAV:basicsearch

   The DAV:basicsearch grammar defines a search criteria that property. Clients MAY specify is a
   Boolean-valued expression, and allows for an arbitrary set of
   properties to be included in the language using result record. The result set may be
   sorted on a set of property values. Accordingly the xml:lang
   attribute. If no language is specified DTD for schema
   discovery for this grammar allows the server to express:

   1.  the set of properties that may be either by the client searched, returned, or
       used to sort, and a hint about the data type of such properties

   2.  the set of optional operators defined for that property by the server or if resource.


5.19.1 DTD for DAV:basicsearch QSD

   <!ELEMENT basicsearchschema  (properties, operators)>
   <!ELEMENT any-other-property EMPTY>
   <!ELEMENT properties         (propdesc*)>
   <!ELEMENT propdesc           (prop|any-other-property), datatype?,
                                 searchable?, selectable?, sortable?,
                                 caseless?)>
   <!ELEMENT operators          (opdesc*)>
   <!ELEMENT opdesc             ANY>
   <!ELEMENT operand-literal    EMPTY>
   <!ELEMENT operand-property   EMPTY>

   The DAV:properties element holds a comparison is
   performed on strings list of two different languages, the results are
   undefined. descriptions of
   properties.

   The "caseless" attribute DAV:operators element describes the optional operators that may
   be used to indicate case-sensitivity for
   comparisons.


5.6.2 Example of Sorting

   This sort orders first by last name in a DAV:where element.

5.19.2 DAV:propdesc Element

   Each instance of a DAV:propdesc element describes the author, and then by size, property or
   properties in descending order, so that for each author, the largest works DAV:prop element it contains. All subsequent
   elements are descriptions that apply to those properties. All
   descriptions are optional and may appear first.




   <d:orderby>
     <d:order>
       <d:prop><r:lastname/></d:prop>
       <d:ascending/>
     </d:order>
     <d:order>
       <d:prop><d:getcontentlength/></d:prop>
       <d:descending/>
     </d:order>
   </d:orderby>




5.7 Boolean Operators: DAV:and, DAV:or, in any order. Servers SHOULD
   support all the descriptions defined here, and DAV:not MAY define others.

   DASL defines five descriptions. The DAV:and operator performs first, DAV:datatype, provides a logical AND operation on
   hint about the
   expressions it contains.

   The DAV:or operator performs a logical OR operation on type of the values it
   contains.

   The DAV:not operator performs property value, and may be useful to a logical NOT operation on the values
   it contains.
   user interface prompting for a value. The remaining four
   (DAV:searchable, DAV:selectable, DAV:sortable, and DAV:caseless)



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 27]

Internet Draft 34]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


5.8 DAV:eq

   The DAV:eq operator provides simple equality matching on


   identify portions of the query (DAV:where, DAV:select, and
   DAV:orderby, respectively). If a property
   values.

   The "caseless" attribute may has a description for a
   section, then the server MUST allow the property to be used with this element.


5.9 DAV:lt, DAV:lte, DAV:gt, DAV:gte

   The DAV:lt, DAV:lte, DAV:gt, and DAV:gte operators provide
   comparisons on in that
   section. These descriptions are optional. If a property values, using less-than, less-than or equal,
   greater-than, and greater-than does not have
   such a description, or equal respectively. The "caseless"
   attribute may be used with these elements.


5.10 DAV:literal

   DAV:literal allows literal values is not described at all, then the server MAY
   still allow the property to be placed in an expression.

   White space in literal values is significant used in comparisons. For
   consistency with [RFC2518], clients SHOULD NOT specify the attribute
   "xml:space" (section 2.10 corresponding section.

5.19.2.1 DAV:any-other-property

   This element can be used in place of [XML]) DAV:prop to override this behaviour.

   In comparisons, the contents describe properties
   of DAV:literal SHOULD be treated as
   string, with the following exceptions:

   o  when operand for a comparison with a DAV:getcontentlength
      property, it SHOULD WebDAV properties not mentioned in any other DAV:prop element. For
   instance, this can be treated as an integer value (the behaviour
      for non-integer values is undefined),

   o  when operand used to indicate that all other properties are
   searchable and selectable without giving details about their types (a
   typical scenario for dead properties).

5.19.3 The DAV:datatype Property Description

   The DAV:datatype element contains a comparison with single XML element that provides
   a DAV:creationdate or
      DAV:getlastmodified hint about the domain of the property, it SHOULD which may be treated as useful to a
   user interface prompting for a date value to be used in a query. Datatypes
   are identified by an element name. Where appropriate, a server SHOULD
   use the ISO-8601 subset simple datatypes defined for the DAV:creationdate property
      ([RFC2518], in [XS2].

   <!ELEMENT datatype ANY >

   Examples from [XS2], section 13.1).

   o  when operand for a comparison with a property for which 3:

                +----------------+---------------------+
                | Qualified name | Example             |
                +----------------+---------------------+
                | xs:boolean     | true, false, 1, 0   |
                |                |                     |
                | xs:string      | Foobar              |
                |                |                     |
                | xs:dateTime    | 1994-11-05T08:15:5Z |
                |                |                     |
                | xs:float       | .314159265358979E+1 |
                |                |                     |
                | xs:integer     | -259, 23            |
                +----------------+---------------------+

   If the data type
      is known, it MAY be treated according to this type.


5.11 DAV:typed-literal (optional)

   There are situations in which a client may want to force of a comparison property is not given, then the data type
   defaults to be string-based (as defined for DAV:literal). In these cases,
   a typed comparison can be enforced by using DAV:typed-literal
   instead. xs:string.

5.19.4 The DAV:searchable Property Description

   <!ELEMENT searchable EMPTY>




Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 28]

Internet Draft 35]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   <!ELEMENT typed-literal (#PCDATA)>



   The data type


   If this element is specified using present, then the xsi:type attribute defined in
   [XS1], section 2.6.1. If server MUST allow this property
   to appear within a DAV:where element where an operator allows a
   property. Allowing a search does not mean that the type property is not specified,
   guaranteed to be defined on every resource in the scope, it defaults only
   indicates the server's willingness to
   "xs:string".

   A server MUST reject a request with an unknown type.


5.12 Example for typed numerical comparison

   Consider a set of resources with check.

5.19.5 The DAV:selectable Property Description

   <!ELEMENT selectable EMPTY>

   This element indicates that the dead property "edits" may appear in the
   namespace "http://ns.example.org":




   URI DAV:select
   element.

5.19.6 The DAV:sortable Property Description

   This element indicates that the property value

   /a     "-1"
   /b     "01"
   /c     "3"
   /d     "test"
   /e     (undefined) may appear in the
   DAV:orderby element.

   <!ELEMENT sortable EMPTY>

5.19.7 The expression




   <lt xmlns="DAV:"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <prop><edits xmlns="http://ns.example.org"/></prop>
     <typed-literal xsi:type="xs:integer">3</typed-literal>
   </lt>



   will evaluate DAV:caseless Property Description

   This element only applies to TRUE for the resources "/a" properties whose data type is
   "xs:string" and "/b" (their property
   values can be parsed derived data types as type xs:number, per the DAV:datatype property
   description. Its presence indicates that compares performed for
   searches, and the numerical comparison
   evaluates to true), to FALSE comparisons for "/c" (property value ordering results on the string
   property will be caseless (the default is compatible,
   but numerical comparison evaluates to false) and UNKNOWN fot "/d" character-by-character).

   <!ELEMENT caseless EMPTY>

5.19.8 The DAV:operators XML Element

   The DAV:operators element describes every optional operator supported
   in a query. (Mandatory operators are not listed since they are
   mandatory and
   "/e" (the property permit no variation in syntax.). All optional operators
   that are supported MUST be listed in the DAV:operators element. The
   listing for an operator consists of the operator (as an empty
   element), followed by one element for each operand. The operand MUST
   be either DAV:operand-property or DAV:operand-literal, which indicate
   that the operand in the corresponding position is undefined, a property or its value can not a
   literal value, respectively. If an operator is polymorphic (allows
   more than one operand syntax) then each permitted syntax MUST be
   listed separately.

   <operators xmlns='DAV:'>
     <opdesc>
       <like/><operand-property/><operand-literal/>
     </opdesc>



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 29]

Internet Draft 36]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   parsed as xs:number).


5.13 DAV:is-collection


   </operators>


5.19.9 Example of Query Schema for DAV:basicsearch

   <D:basicsearchschema xmlns:D="DAV:"
     xmlns:xs="http://www.w3.org/2001/XMLSchema"">
     <D:properties>
       <D:propdesc>
         <D:prop><D:getcontentlength/></D:prop>
         <D:datatype><xs:nonNegativeInteger/></D:datatype>
         <D:searchable/><D:selectable/><D:sortable/>
       </D:propdesc>
       <D:propdesc>
         <D:prop><D:getcontenttype/><D:displayname/></D:prop>
         <D:searchable/><D:selectable/><D:sortable/>
       </D:propdesc>
       <D:propdesc>
         <D:prop><fstop xmlns="http://jennicam.org"/></D:prop>
         <D:selectable/>
       </D:propdesc>
       <D:propdesc>
         <D:any-other-property/>
         <D:searchable/><D:selectable/>
       </D:propdesc>
     </D:properties>
     <D:operators>
       <D:opdesc>
         <D:like/><D:operand-property/><D:operand-literal/>
       </D:opdesc>
     </D:operators>
   </D:basicsearchschema>

   This response lists four properties. The DAV:is-collection operator allows clients to determine whether a
   resource is a collection (that is, whether it's DAV:resourcetype
   element contains datatype of the element DAV:collection).

   Rationale: This operator last three
   properties is provided in lieu of defining generic
   structure queries, which would suffice for this and for many more
   powerful queries, but seems inappropriate not given, so it defaults to standardize at this
   time.


5.13.1 Example of DAV:is-collection

   This example shows a search criterion that picks out all xs:string. All are
   selectable, and only the
   resources first three may be searched. All but the last may
   be used in a sort. Of the scope that are collections.




   <where xmlns="DAV:">
     <is-collection/>
   </where>




5.14 optional DAV operators, DAV:is-defined and
   DAV:like are supported.

   Note: The DAV:is-defined operator allows clients to determine whether a
   property is schema discovery defined on a resource. The meaning here does not provide for
   discovery of "defined on a
   resource" is found in section5.5.3.


   Example:

   <d:is-defined>
     <d:prop><x:someprop/></d:prop>
   </d:is-defined> supported values of the "caseless" attribute. This may
   require that the reply also list the mandatory operators.









Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 30]

Internet Draft 37]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


5.15 DAV:like

   The DAV:like is an optional operator intended to give simple
   wildcard-based pattern matching ability to clients.

   The operator takes two arguments.

   The first argument is a DAV:prop element identifying a single
   property to evaluate.

   The second argument is a DAV:literal element that gives the pattern
   matching string.


5.15.1 Syntax for


6. Internationalization Considerations

   Properties may be language-tagged using the Literal Pattern




   Pattern := [wildcard] 0*( text [wildcard] )
   wildcard := exactlyone | zeroormore
   text := 1*( <character> | escapesequence )
   exactlyone : = "_"
   zeroormore := "%"
   escapechar := "\"
   escapesequence := "\" ( exactlyone | zeroormore | escapechar )
   character: valid XML characters xml:lang attribute (see
   [RFC2518], section 2.2 of [XML]),
              minus ( exactlyone | zeroormore | escapechar )



   The value for the literal is composed of wildcards separated by
   segments of text. Wildcards may begin or end the literal.

   The "_" wildcard matches exactly one character.

   The "%" wildcard matches zero or more characters 4.4). The "


5.15.2 Example of DAV:like

   This example shows how a client might use DAV:like optional operators DAV:language-defined
   (Section 5.12.1) and DAV:language-matches (Section 5.12.2) allow to identify those
   resources whose content type was a subtype of image.
   express conditions on the language tagging information.













































Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 31]

Internet Draft 38]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   <D:where>
     <D:like caseless="yes">
       <D:prop><D:getcontenttype/></D:prop>
       <D:literal>image/%</D:literal>
     </D:like>
   </D:where>




5.16 DAV:contains

   The DAV:contains operator is an optional operator that provides
   content-based search capability.


7. Security Considerations

   This operator implicitly searches
   against the text content of a resource, not against content of
   properties. The DAV:contains operator section is intentionally not overly
   constrained, in order provided to allow the server detail issues concerning security
   implications of which DASL applications need to do the best job it can
   in performing be aware. All of the search.

   The DAV:contains operator evaluates to a Boolean value. It evaluates
   security considerations of HTTP/1.1 also apply to TRUE if the content DASL. In addition,
   this section will include security risks inherent in searching and
   retrieval of the resource satisfies the search.
   Otherwise, It evaluates properties and content.

   A query must not allow one to FALSE.

   Within the DAV:contains XML element, the client provides a phrase: a
   single word retrieve information about values or whitespace delimited sequence
   existence of words. Servers MAY
   ignore punctuation properties that one could not obtain via PROPFIND. (e.g.
   by use in DAV:orderby, or in expressions on properties.)

   A server should prepare for denial of service attacks. For example a phrase. Case-sensitivity
   client may issue a query for which the result set is left expensive to the
   server.

   The following things may
   calculate or may not transmit because many resources match or must be done as part
   evaluated.

7.1 Implications of the search:
   Phonetic methods such XML External Entities

   XML supports a facility known as "soundex" may or may not be used. Word
   stemming may or may not be performed. Thesaurus expansion "external entities", defined in
   section 4.2.2 of words
   may or may not be done. Right or left truncation may or may not be
   performed. The search may be case insensitive or case sensitive. The
   word or words may or may not [XML], which instruct an XML processor to retrieve
   and perform an inline include of XML located at a particular URI. An
   external XML entity can be interpreted as names. Multiple words
   may used to append or may not modify the document type
   declaration (DTD) associated with an XML document. An external XML
   entity can also be required used to be adjacent or "near" each other.
   Multiple words may or may include XML within the content of an XML
   document. For non-validating XML, such as the XML used in this
   specification, including an external XML entity is not be required by
   [XML]. However, [XML] does state that an XML processor may, at its
   discretion, include the external XML entity.

   External XML entities have no inherent trustworthiness and are
   subject to occur all the attacks that are endemic to any HTTP GET request.
   Furthermore, it is possible for an external XML entity to modify the
   DTD, and hence affect the final form of an XML document, in the same order.
   Multiple words may worst
   case significantly modifying its semantics, or may not exposing the XML
   processor to the security risks discussed in [RFC3023]. Therefore,
   implementers must be treated as a phrase. The search may
   or may not aware that external XML entities should be interpreted
   treated as a request to find documents "similar" to
   the string operand.


5.16.1 Result scoring (DAV:score element)

   Servers SHOULD indicate scores for untrustworthy.

   There is also the DAV:contains condition by
   adding scalability risk that would accompany a DAV:score widely
   deployed application which made use of external XML element to the DAV:response element. It's
   value entities. In this
   situation, it is defined only in possible that there would be significant numbers of
   requests for one external XML entity, potentially overloading any
   server which fields requests for the context of a particular query result.
   The value is a string representing resource containing the score, an integer from zero to
   10000 inclusive, where a higher value indicates a higher score (e.g. external
   XML entity.






Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 32]

Internet Draft 39]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   more relevant).


   Modified DTD fragment for DAV:propstat:

   <!ELEMENT response (href, ((href*, status)|(propstat+)),
                       responsedescription?, score?) >
   <!ELEMENT score    (#PCDATA) >



   Clients should note that, in general, it is


8. Scalability

   Query grammars are identified by URIs. Applications SHOULD not meaningful
   attempt to compare
   the numeric values of scores from two different query results unless
   both were executed by the same underlying search system on the same
   collection of resources.


5.16.2 Ordering by score

   To order search results by their score, the DAV:score element may be
   added as child retrieve these URIs even if they appear to the DAV:orderby element (in place of a DAV:prop
   element).


5.16.3 Examples

   The example below shows a search for the phrase "Peter Forsberg".

   Depending on its support for content-based searching, a server MAY
   treat this as a search for documents be retrievable
   (for example, those that contain begin with "http://")














































Reschke, et al.          Expires April 9, 2004                 [Page 40]

Internet-Draft               WebDAV SEARCH                  October 2003


9. Authentication

   Authentication mechanisms defined in WebDAV will also apply to DASL.
















































Reschke, et al.          Expires April 9, 2004                 [Page 41]

Internet-Draft               WebDAV SEARCH                  October 2003


10. IANA Considerations

   This document uses the words "Peter"
   and "Forsberg".




   <D:where>
     <D:contains>Peter Forsberg</D:contains>
   </D:where>



   The example below shows a search for resources that contain "Peter"
   and "Forsberg".




   <D:where> namespace defined by [RFC2518] for XML
   elements. All other IANA considerations mentioned in [RFC2518] are
   also applicable to DASL.














































Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 33]

Internet Draft 42]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


     <D:and>
       <D:contains>Peter</D:contains>
       <D:contains>Forsberg</D:contains>
     </D:and>
   </D:where>




5.17 Limiting the result set




   <!ELEMENT limit (nresults) >
   <!ELEMENT nresults (#PCDATA)> ;only digits



   The DAV:limit XML element contains requested limits from the client
   to limit the size of


11. Contributors

   This document is based on prior work on the reply or amount of effort expended DASL protocol done by the
   server. The DAV:nresults XML element contains a requested maximum
   number of DAV:response elements to be returned in the response body.
   The server MAY disregard this limit. The value of this element is an
   integer.


5.17.1 Relationship to result ordering

   If
   WebDAV DASL working group until the result set is both limited year 2000 -- namely by DAV:limit Alan
   Babich, Jim Davis, Rick Henderson, Dale Lowry, Saveen Reddy and ordered according
   to DAV:orderby, the results that are included in the response
   Surendra Reddy.













































Reschke, et al.          Expires April 9, 2004                 [Page 43]

Internet-Draft               WebDAV SEARCH                  October 2003


12. Acknowledgements

   This document must be those that order highest.


5.18 The "caseless" XML attribute

   The "caseless" attribute allows clients to specify caseless matching
   behaviour instead of character-by-character matching for
   DAV:basicsearch operators.

   The possible values for "caseless" are "yes" or "no". The default
   value is server-specified. Caseless matching SHOULD be implemented as
   defined in [CaseMap].

   Support for the "caseless" attribute is optional. A server should
   respond with a status of 422 if it is used but cannot be supported. has benefited from thoughtful discussion by Lisa
   Dusseault, Sung Kim, Elias Sinderson, Martin Wallmer, Jim Whitehead
   and Kevin Wiggen.














































Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 34]

Internet Draft 44]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


5.19 Query schema for DAV:basicsearch

   The DAV:basicsearch grammar defines a search criteria that is a
   Boolean-valued expression,


Normative References

   [ACL]      Clemm, G., Hopkins, A., Sedlar, E. and allows J. Whitehead,
              "WebDAV Access Control Protocol", ID
              draft-ietf-webdav-acl-12, October 2003, <http://
              www.webdav.org/acl/protocol/draft-ietf-webdav-acl-12.htm>.

   [RFC2119]  Bradner, S., "Key words for an arbitrary set of
   properties to be included use in the result record. The result set may be
   sorted on a set of property values. Accordingly the DTD for schema
   discovery for this grammar allows the server to express:



   1. the set of properties that may be either searched, returned, or
      used RFCs to sort, Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2518]  Goland, Y., Whitehead, E., Faizi, A., Carter, S. and a hint about the data type of such properties

   2. the set of optional operators defined by the resource.


5.19.1 DTD D.
              Jensen, "HTTP Extensions for DAV:basicsearch QSD




   <!ELEMENT basicsearchschema  (properties, operators)>
   <!ELEMENT any-other-property EMPTY>
   <!ELEMENT properties         (propdesc*)>
   <!ELEMENT propdesc           (prop|any-other-property), datatype?,
                                 searchable?, selectable?, sortable?,
                                 caseless?)>
   <!ELEMENT operators          (opdesc*)>
   <!ELEMENT opdesc             ANY>
   <!ELEMENT operand-literal    EMPTY>
   <!ELEMENT operand-property   EMPTY>



   The DAV:properties element holds a list of descriptions of
   properties.

   The DAV:operators element describes the optional operators that may
   be used in a DAV:where element.


5.19.2 DAV:propdesc Element

   Each instance of a DAV:propdesc element describes the property or
   properties in the DAV:prop element it contains. All subsequent
   elements are descriptions that apply to those properties. All
   descriptions are optional and may appear in any order. Servers SHOULD
   support all the descriptions defined here, Distributed Authoring --
              WEBDAV", RFC 2518, February 1999.

   [RFC2616]  Fielding, R., Gettys, J., Mogul, J., Nielsen, H.,
              Masinter, L., Leach, P. and MAY define others.



Reschke, et al.           Expires December 2003                [Page 35]

Internet Draft                WebDAV SEARCH T. Berners-Lee, "Hypertext
              Transfer Protocol -- HTTP/1.1", RFC 2616, June 2003


   DASL defines five descriptions. The first, DAV:datatype, provides a
   hint about the type of the property value, 1999.

   [RFC3023]  Makoto, M., St.Laurent, S. and may be useful D. Kohn, "XML Media Types",
              RFC 3023, January 2001.

   [RFC3253]  Clemm, G., Amsden, J., Ellison, T., Kaler, C. and J.
              Whitehead, "Versioning Extensions to a
   user interface prompting for a value. The remaining four
   (DAV:searchable, DAV:selectable, DAV:sortable, WebDAV", RFC 3253,
              March 2002.

   [XML]      Bray, T., Paoli, J., Sperberg-McQueen, C. and DAV:caseless)
   identify portions of the query (DAV:where, DAV:select, E. Maler,
              "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C
              REC-xml, October 2000, <http://www.w3.org/TR/2000/
              REC-xml-20001006>.

   [XMLNS]    Bray, T., Hollander, D. and
   DAV:orderby, respectively). If a property has a description for a
   section, then the server MUST allow the property to be used in that
   section. These descriptions are optional. If a property does not have
   such a description, or is not described at all, then the server MAY
   still allow the property to be used in the corresponding section.


5.19.2.1 DAV:any-other-property

   This element can be used A. Layman, "Namespaces in place of DAV:prop to describe properties
   of
              XML", W3C REC-xml-names, January 1999, <http://www.w3.org/
              TR/REC-xml-names>.

   [XPATH]    Clark, J. and S. DeRose, "XML Path Language (XPath)
              Version 1.0", W3C REC REC-xpath, November 1999, <http://
              www.w3.org/TR/xpath>.

   [XS1]      Thompson, H., Beech, D., Maloney, M., Mendelsohn, N. and
              World Wide Web Consortium, "XML Schema Part 1:
              Structures", W3C XS1, May 2001, <http://www.w3.org/TR/
              xmlschema-1/>.

   [XS2]      Biron, P., Malhotra, A. and World Wide Web Consortium,
              "XML Schema Part 2: Datatypes", W3C XS2, May 2001, <http:/
              /www.w3.org/TR/xmlschema-2/>.





Reschke, et al.          Expires April 9, 2004                 [Page 45]

Internet-Draft               WebDAV properties not mentioned in any other DAV:prop element. For
   instance, this can be used to indicate that all other properties are
   searchable SEARCH                  October 2003


Informative References

   [BIND]     Clemm, G., Crawford, J., Reschke, J., Slein, J. and selectable without giving details about their types (a
   typical scenario for dead properties).


5.19.3 The DAV:datatype Property Description

   The DAV:datatype element contains a single XML element that provides
   a hint about the domain of the property, which may be useful J.
              Whitehead, "Binding Extensions to a
   user interface prompting WebDAV", ID
              draft-ietf-webdav-bind-02, June 2003, <http://
              www.webdav.org/bind/draft-ietf-webdav-bind-02.htm>.

   [CaseMap]  Davis, M., "Case Mappings", Unicode Techical Reports 21,
              February 2001, <http://www.unicode.org/unicode/reports/
              tr21>.

   [DASL]     Reddy, S., Lowry, D., Reddy, S., Henderson, R., Davis, J.
              and A. Babich, "DAV Searching & Locating", ID
              draft-dasl-protocol-00, July 1999, <http://www.webdav.org/
              dasl/protocol/draft-dasl-protocol-00.html>.

   [DASLREQ]  Davis, J., Reddy, S. and J. Slein, "Requirements for a value to be used in a query. Datatypes
   are identified by an element name. Where appropriate, a server SHOULD
   use the simple datatypes defined in [XS2].




   <!ELEMENT datatype ANY >



   Examples from [XS2], section 3:




   Qualified name      Example

   xs:boolean          true, false, 1, 0
   xs:string           Foobar
   xs:dateTime         1994-11-05T08:15:5Z
   xs:float            .314159265358979E+1
   xs:integer          -259, 23 DAV
              Searching and Locating", ID draft-dasl-requirements-01,
              February 1999, <http://www.webdav.org/dasl/requirements/
              draft-dasl-requirements-01.html>.

   [SQL99]    Milton, J., "Database Language SQL Part 2: Foundation
              (SQL/Foundation)", ISO ISO/IEC 9075-2:1999 (E), July 1999.




























Reschke, et al.          Expires April 9, 2004                 [Page 46]

Internet-Draft               WebDAV SEARCH                  October 2003


URIs

   [1]   <mailto:www-webdav-dasl@w3.org>

   [2]   <mailto:www-webdav-dasl-request@w3.org?subject=subscribe>

   [3]   <http://lists.w3.org/Archives/Public/www-webdav-dasl/
         2003JanMar/0042.html>

   [4]   <http://lists.w3.org/Archives/Public/www-webdav-dasl/
         2003JulSep/0012.html>

   [5]   <http://lists.w3.org/Archives/Public/www-webdav-dasl/
         1999AprJun/0002.html>

   [6]   <http://lists.w3.org/Archives/Public/www-webdav-dasl/
         2002AprJun/0047.html>

   [7]   <http://lists.w3.org/Archives/Public/www-webdav-dasl/
         1999OctDec/0023.html>

   [8]   <http://lists.w3.org/Archives/Public/www-webdav-dasl/
         2002JanMar/0163.html>

   [9]   <http://lists.w3.org/Archives/Public/www-webdav-dasl/
         2003JulSep/0002.html>

   [10]  <http://lists.w3.org/Archives/Public/www-webdav-dasl/
         2003JulSep/0012.html>

   [11]  <http://lists.w3.org/Archives/Public/www-webdav-dasl/
         2003OctDec/0010.html>

   [12]  <http://lists.w3.org/Archives/Public/www-webdav-dasl/
         2002JanMar/0122.html>

   [13]  <http://lists.w3.org/Archives/Public/www-webdav-dasl/
         1999AprJun/0002.html>













Reschke, et al.          Expires April 9, 2004                 [Page 47]

Internet-Draft               WebDAV SEARCH                  October 2003


Authors' Addresses

   Julian F. Reschke (editor)
   greenbytes GmbH
   Salzmannstrasse 152
   Muenster, NW  48159
   Germany

   Phone: +49 251 2807760
   Fax:   +49 251 2807761
   EMail: julian.reschke@greenbytes.de
   URI:   http://greenbytes.de/tech/webdav/


   Surendra Reddy
   Oracle Corporation
   600 Oracle Parkway, M/S 6op3
   Redwoodshores, CA  94065

   Phone: +1 650 506 5441
   EMail: Surendra.Reddy@oracle.com


   Jim Davis
   Intelligent Markets
   410 Jessie Street 6th floor
   San Francisco, CA  94103

   EMail: jrd3@alum.mit.edu


   Alan Babich
   FileNET Corp.
   3565 Harbor Blvd.
   Costa Mesa, CA  92626

   Phone: +1 714 327 3403
   EMail: ababich@filenet.com













Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 36]

Internet Draft 48]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   If the data type of a property is not given, then the data type
   defaults to xs:string.


5.19.4 The DAV:searchable Property Description




   <!ELEMENT searchable EMPTY>



   If this element


Appendix A. Three-Valued Logic in DAV:basicsearch

   ANSI standard three valued logic is present, then used when evaluating the server MUST allow this property
   to appear within a DAV:where element where an operator allows a
   property. Allowing a search does not mean that the property is
   guaranteed to be
   condition (as defined on every resource in the scope, it only
   indicates the server's willingness to check.


5.19.5 The DAV:selectable Property Description




   <!ELEMENT selectable EMPTY>



   This element indicates that the property may appear in the DAV:select
   element.


5.19.6 The DAV:sortable Property Description

   This element indicates that the property may appear ANSI standard SQL specifications, for
   example in the
   DAV:orderby element.




   <!ELEMENT sortable EMPTY>









Reschke, et al.           Expires December 2003                [Page 37]

Internet Draft                WebDAV SEARCH                    June 2003


5.19.7 The DAV:caseless Property Description

   This element only applies to properties whose data type ANSI X3.135-1992, section 8.12, pp. 188-189, section 8.2,
   p. 169, General Rule 1)a), etc.).

   ANSI standard three valued logic is
   "xs:string" and derived data types as per the DAV:datatype property
   description. Its presence indicates that compares performed for
   searches, and undoubtedly the comparisons for ordering results on most widely
   practiced method of dealing with the string
   property will be caseless (the default is character-by-character).




   <!ELEMENT caseless EMPTY>




5.19.8 The DAV:operators XML Element

   The DAV:operators element describes every optional operator supported issues of properties in the
   search condition not having a query. (Mandatory operators are value (e.g., being null or not listed since they are
   mandatory defined)
   for the resource under scan, and permit no variation in syntax.). All optional operators
   that are supported MUST be listed with undefined expressions in the DAV:operators element. The
   listing for an operator consists of the operator (as an empty
   element), followed
   search condition (e.g., division by one element zero, etc.). Three valued logic
   works as follows.

   Undefined expressions are expressions for each operand. The operand MUST
   be either DAV:operand-property or DAV:operand-literal, which indicate
   that the operand in value of the corresponding position
   expression is not defined. Undefined expressions are a property or a
   literal value, respectively. If an operator is polymorphic (allows
   more than one operand syntax) then each permitted syntax MUST be
   listed separately.




   <operators xmlns='DAV:'>
     <opdesc>
       <like/><operand-property/><operand-literal/>
     </opdesc>
   </operators>




5.19.9 Example of Query Schema for DAV:basicsearch




   <D:basicsearchschema xmlns:D="DAV:"



Reschke, et al.           Expires December 2003                [Page 38]

Internet Draft                WebDAV SEARCH                    June 2003


     xmlns:xs="http://www.w3.org/2001/XMLSchema"">
     <D:properties>
       <D:propdesc>
         <D:prop><D:getcontentlength/></D:prop>
         <D:datatype><xs:nonNegativeInteger/></D:datatype>
         <D:searchable/><D:selectable/><D:sortable/>
       </D:propdesc>
       <D:propdesc>
         <D:prop><D:getcontenttype/><D:displayname/></D:prop>
         <D:searchable/><D:selectable/><D:sortable/>
       </D:propdesc>
       <D:propdesc>
         <D:prop><fstop xmlns="http://jennicam.org"/></D:prop>
         <D:selectable/>
       </D:propdesc>
       <D:propdesc>
         <D:any-other-property/>
         <D:searchable/><D:selectable/>
       </D:propdesc>
     </D:properties>
     <D:operators>
       <D:opdesc>
         <D:like/><D:operand-property/><D:operand-literal/>
       </D:opdesc>
     </D:operators>
   </D:basicsearchschema>



   This response lists four properties. The datatype completely
   separate concept from the truth value UNKNOWN, which is, in fact,
   well defined. Property names and literal constants are considered
   expressions for purposes of this section. If a property in the last three
   properties is
   current resource under scan has not given, so it defaults been set to xs:string. All are
   selectable, and a value, then the first three may be searched. All but
   value of that property is undefined for the last may resource under scan. DASL
   1.0 has no arithmetic division operator, but if it did, division by
   zero would be used in an undefined arithmetic expression.

   If any subpart of an arithmetic, string, or datetime subexpression is
   undefined, the whole arithmetic, string, or datetime subexpression is
   undefined.

   There are no manifest constants to explicitly represent undefined
   number, string, or datetime values.

   Since a sort. Of Boolean value is ultimately returned by the optional DAV operators, DAV:isdefined search condition,
   arithmetic, string, and
   DAV:like datetime expressions are supported.

   Note: The schema discovery defined here does not provide for
   discovery of supported values always arguments to
   other operators. Examples of the "caseless" attribute. This may
   require operators that convert arithmetic,
   string, and datetime expressions to Boolean values are the reply also list the mandatory operators.













Reschke, et al.           Expires December 2003                [Page 39]

Internet Draft                WebDAV SEARCH                    June 2003


6 Internationalization Considerations

   Clients six
   relational operators ("greater than", "less than", "equals", etc.).
   If either or both operands of a relational operator have undefined
   values, then the opportunity relational operator evaluates to tag properties when they are stored
   in a language. The server SHOULD read this language-tagging by
   examining UNKNOWN. Otherwise,
   the xml:lang attribute on any properties stored on a
   resource. relational operator evaluates to TRUE or FALSE, depending upon
   the outcome of the comparison.

   The xml:lang attribute specifies a nationalized collation sequence
   when properties Boolean operators DAV:and, DAV:or and DAV:not are compared.

   Comparisons when this attribute differs have undefined order. evaluated
   according to the following rules:

   UNKNOWN and UNKNOWN = UNKNOWN

   UNKNOWN or UNKNOWN = UNKNOWN




Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 40]

Internet Draft 49]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


7 Security Considerations

   This section is provided to detail issues concerning security
   implications of which DASL applications need to be aware. All of the
   security considerations of HTTP/1.1 also apply to DASL. In addition,
   this section will include security risks inherent in searching


   not UNKNOWN = UNKNOWN

   UNKNOWN and
   retrieval of resource properties TRUE = UNKNOWN

   UNKNOWN and content.

   A query must not allow one to retrieve information about values or
   existence of properties that one could not obtain via PROPFIND. (e.g.
   by use in DAV:orderby, FALSE = FALSE

   UNKNOWN and UNKNOWN = UNKNOWN

   UNKNOWN or in expressions on properties.)

   A server should prepare for denial of service attacks. For example a
   client may issue a query for which the result set is expensive to
   calculate TRUE = TRUE

   UNKNOWN or transmit because many resources match FALSE = UNKNOWN

   UNKNOWN or must UNKNOWN = UNKNOWN






































Reschke, et al.          Expires April 9, 2004                 [Page 50]

Internet-Draft               WebDAV SEARCH                  October 2003


Appendix B. Change Log (to be
   evaluated. 7.1 Implications of XML External Entities

   XML supports a facility known removed by RFC Editor before publication)

B.1 From draft-davis-dasl-protocol-xxx

   Feb 14, 1998 Initial Draft

   Feb 28, 1998 Referring to DASL as "external entities", defined in an extension to HTTP/1.1 rather
      than DAV.
      Added new sections "Notational Conventions", "Protocol Model",
      "Security Considerations".
      Changed section 4.2.2 of [XML], which instruct an XML processor 3 to retrieve
   and perform an inline include "Elements of XML located at a particular URI. An
   external XML entity can be used Protocol".
      Added some stuff to append or modify the document type
   declaration (DTD) associated with an XML document. An external XML
   entity can also be used introduction.
      Added "result set" terminology.
      Added "IANA Considerations".

   Mar 9, 1998 Moved sub-headings of "Elements of Protocol" to include XML within the content first
      level and removed "Elements of Protocol" Heading.
      Added an XML
   document. For non-validating XML, such as the XML used sentence in introduction explaining that this
   specification, including an external XML entity is not required by
   [XML]. However, [XML] does state that an XML processor may, at its
   discretion, include the external XML entity.

   External XML entities have no inherent trustworthiness a
      "sketch" of a protocol.

   Mar 11, 1998 Added orderby, data typing, three valued logic, query
      schema property, and are
   subject to all the attacks that are endemic to any HTTP GET request.
   Furthermore, it is possible element definitions for an external XML entity schema for
      basicsearch.

   April 8, 1998 - made changes based on last week's DASL BOF.

   May 8, 1998 Removed most of DAV:searcherror; converted to modify the
   DTD, and hence affect the final form
      DAV:searchredirect
      Altered DAV:basicsearch grammar to use avoid use of an XML document, ANY in DTD

   June 17, 1998 -Added details on Query Schema Discovery
      -Shortened list of data types

   June 23, 1998 moved data types before change history
      rewrote the data types section
      removed the casesensitive element and replace with the worst
   case significantly modifying its semantics, or exposing
      casesensitive attribute
      added the XML
   processor casesensitive attribute to the security risks discussed in [RFC3023]. Therefore,
   implementers must be aware that external XML entities should be
   treated as untrustworthy.

   There is also the scalability risk DTD for all operations
      that would accompany might work on a widely
   deployed application which made use of external XML entities. In this
   situation, it is possible that there would be significant numbers string

   Jul 20, 1998 A series of
   requests for one external XML entity, potentially overloading any
   server which fields requests changes. See Author's meeting minutes for the resource containing the external
   XML entity.








Reschke, et al.           Expires December 2003                [Page 41]

Internet Draft                WebDAV SEARCH                    June 2003


8 Scalability

   Query grammars are identified by URIs. Applications SHOULD
      details.

   July 28, 1998 Changes as per author's meeting. QSD uses SEARCH, not
   attempt to retrieve these URIs even if they appear to be retrievable
   (for example, those that begin with "http://")














































Reschke, et al.           Expires December 2003                [Page 42]

Internet Draft                WebDAV SEARCH                    June 2003


9 Authentication

   Authentication mechanisms defined in WebDAV will also apply
      PROPFIND.
      Moved text around to DASL.
















































Reschke, et al.           Expires December 2003                [Page 43]

Internet Draft                WebDAV SEARCH                    June 2003


10 IANA Considerations

   This document uses the namespace defined by [RFC2518] for XML
   elements. All other IANA considerations mentioned in [RFC2518] keep concepts nearby.
      Boolean literals are
   also applicable to DASL.














































Reschke, et al.           Expires December 2003                [Page 44]

Internet Draft                WebDAV SEARCH                    June 2003


11 Copyright

   To be supplied. 1 and 0, not T and F.
      contains changed to contentspassthrough.



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 45]

Internet Draft 51]

Internet-Draft               WebDAV SEARCH                    June 2003


12 Intellectual Property

   To be supplied.
















































Reschke, et al.           Expires December                  October 2003                [Page 46]

Internet Draft                WebDAV SEARCH


      Renamed rank to score.

   July 28, 1998 Added Dale Lowry as Author

   September 4, 1998 Added 422 as response when query lists
      unimplemented operators.
      DAV:literal declares a default value for xml:space, 'preserve'
      (see XML spec, section 2.10)
      moved to new XML namespace syntax

   September 22, 1998 Changed "simplesearch" to "basicsearch"
      Changed isnull to isdefined
      Defined NULLness as having a 404 or 403 response
      used ENTITY syntax in DTD
      Added redirect

   October 9, 1998 Fixed a series of typographical and formatting
      errors.
      Modified the section of three-valued logic to use a table rather
      than a text description of the role of UNKNOWN in expressions.

   November 2, 1998 Added the DAV:contains operator.
      Removed the DAV:contentpassthrough operator.

   November 18, 1998 Various author comments for submission

   June 2003


13 Acknowledgements

   This draft has benefited from thoughtful discussion 3, 1999 Cosmetic and minor editorial changes only. Fix nits
      reported by Lisa
   Dusseault, Sung Kim, Elias Sinderson, Martin Wallmer Jim Whitehead in email of April 26, 1999. Converted to
      HTML from Word 97, manually.

   April 20, 2000 Removed redirection feature, since 301/302 suffices.
      Removed Query Schema Discovery (former chapter 4). Everyone agrees
      this is a useful feature, but it is apparently too difficult to
      define at this time, and it is not essential for DASL.


B.2 since start of draft-reschke-webdav-search

   October 09, 2001 Added Julian Reschke as author.
      Chapter about QSD re-added.
      Formatted into RFC2629-compliant XML document.
      Added first comments.
      ID version number kicked up to draft-dasl-protocol-03.

   October 17, 2001 Updated address information for Jim
   Whitehead. Davis.
      Added issue of datatype vocabularies.
      Updated issue descriptions for grammar discovery, added issues on
      query schema DTD.



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 47]

Internet Draft 52]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


Normative References


   [ACL]      Clemm, G., Hopkins, A., Sedlar, E. and Whitehead, J.,
              "WebDAV Access Control Protocol", ID draft-ietf-webdav-
              acl-09, July 2002.

   [RFC2119]  Bradner, S., "Key words for use


      Fixed typos in RFCs XML examples.

   December 17, 2001 Re-introduced split between normative and
      non-normative references.

   January 05, 2002 Version bumbed up to Indicate
              Requirement Levels", BCP 04. Started work on resolving
      the issues identified in the previous version.

   January 14, RFC 2119, March 1997.

   [RFC2518]  Goland, Y., Whitehead, E., Faizi, A., Carter, S.R. and
              Jensen, D., "HTTP Extensions for Distributed Authoring --
              WEBDAV", RFC 2518, February 1999.

   [RFC2616]  Fielding, R.T., Gettys, J., Mogul, J.C., Nielsen, H.F.,
              Masinter, L., Leach, P.J. and Berners-Lee, T., "Hypertext
              Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.

   [RFC3023]  Makoto, M., St.Laurent, S. and Kohn, D., "XML Media
              Types", RFC 3023, 2002 Fixed some XML typos.

   January 2001.

   [RFC3253]  Clemm, G., Amsden, J., Ellison, T., Kaler, C. 22, 2002 Closed issues naming-of-elements. Fixed query search
      DTD and
              Whitehead, J., "Versioning Extensions added option to WebDAV", RFC
              3253, March 2002.

   [XML]      Bray, T., Paoli, J., Sperberg-McQueen, C.M. and Maler, E.,
              "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-
              xml, October 2000.

   [XMLNS]    Bray, T., Hollander, D. and Layman, A., "Namespaces in
              XML", W3C REC-xml-names, discover properties of "other"
      (non-listed) properties.

   January 1999.

   [XS1]      Thompson, H. S., Beech, D., Maloney, M., Mendelsohn, N. 25, 2002 Changed into private submission and World Wide Web Consortium, "XML Schema Part 1:
              Structures", W3C XS1, May 2001.

   [XS2]      Biron, P. V., Malhotra, A. added reference
      to historic DASL draft. Marked reference to DASL requirements
      non-normative.
      Updated reference to latest deltav spec.

   January 29, 2002 Added feedback from and World Wide Web Consortium,
              "XML Schema Part 2: Datatypes", W3C XS2, May 2001.


Informative References


   [BIND]     Clemm, G., Crawford, J., Reschke, J. F., Slein, J. updated contact info for
      Alan Babich.
      Included open issues collected in http://www.webdav.org/dasl/
      protocol/issues.html.

   February 8, 2002 Made sure that all artwork fits into 72 characters
      wide text.

   February 18, 2002 Changed Insufficient storage handling
      (multistatus). Moved is-collection to operators and
              Whitehead, J., "Binding Extensions added to WebDAV", ID draft-
              ietf-webdav-bind-00, October 2002.





Reschke, et al.           Expires December 2003                [Page 48]

Internet Draft                WebDAV SEARCH                    June 2003


   [CaseMap]  Davis, M., "Case Mappings", Unicode Techical Reports 21, DTD.
      Made scope/depth mandatory.

   February 2001.

   [DASL]     Reddy, S., Lowry, D., Reddy, S., Henderson, R., Davis, J. 20, 2002 Updated reference to SQL99.

   February 28, 2002 "Non-normative References" -> "Informative
      References". Abstract updated. Consistently specify a charset when
      using text/xml (no change bars). Do not attempt to define
      PROPFIND's entity encoding (take out specific references to text/
      xml). Remove irrelevant headers (Connection:) from examples (no
      change bars). Added issue on querying based on DAV:href. Updated
      introduction to indicate relationship to DASL draft. Updated HTTP
      reference from RFC2068 to RFC2616. Updated XML reference to XML
      1.0 2nd edition.

   March 1, 2002 Removed superfluous namespace decl in 2.4.2. Reopened
      JW14 and Babich, A., "DAV Searching & Locating", ID draft-dasl-
              protocol-00, July suggest to drop xml:space support.






Reschke, et al.          Expires April 9, 2004                 [Page 53]

Internet-Draft               WebDAV SEARCH                  October 2003


   March 3, 2002 Removed "xml:space" feature on DAV:literal. Added issue
      about string comparison vs. collations vs. xml:lang. Updated some
      of the open issues with details from JimW's original mail in April
      1999.

   [DASLREQ]  Davis, J., Reddy, S. Resolved scope vs relative URI references. Resolved issues
      about DAV:ascending (added to index) and Slein, J., "Requirements the BNF for DAV
              Searching DAV:like
      (changed "octets" to "characters").

   March 8, 2002 Updated reference to DeltaV (now RFC3253). Added Martin
      Wallmer's comments, moved JW5 into DAV:basicsearch section.

   March 11, 2002 Closed open issues regaring the type of search
      arbiters (JW3) and Locating", ID draft-dasl-requirements-01,
              February 1999.

   [SQL99]    Milton, J., "Database Language SQL Part 2: Foundation
              (SQL/Foundation)", ISO ISO/IEC 9075-2:1999 (E), July 1999.


Author's Addresses

   Julian F. Reschke (editor)
   greenbytes GmbH
   Salzmannstrasse 152
   Muenster, NW 48159
   Germany

   Phone: +49 251 2807760
   Fax:   +49 251 2807761
   EMail: julian.reschke@greenbytes.de
   URI:   http://greenbytes.de/tech/webdav/

   Surendra Reddy
   Oracle Corporation
   600 Oracle Parkway, M/S 6op3
   Redwoodshores, CA 94065

   Phone: +1 650 506 5441
   EMail: Surendra.Reddy@oracle.com

   Jim Davis
   Intelligent Markets
   410 Jessie Street 6th floor
   San Francisco, CA 94103

   EMail: jrd3@alum.mit.edu their discovery (JW9). Rephrased requirements
      on multistatus response bodies (propstat only if properties were
      selected, removed requirement for responsedescription).

   March 23, 2002 RFC2376 -> RFC3023. Added missing first names of
      authors. OPTIONS added to example for DAV:supported-method-set.


B.3 since draft-reschke-webdav-search-00

   March 29, 2002 Abstract doesn't refer to DASL WG anymore.

   April 7, 2002 Fixed section title (wrong property name
      supported-search-grammar-set. Changed DAV:casesensitve to
      "casesensitive" (it wasn't in the DAV: namespace after all).

   May 28, 2002 Updated some issues with Jim Davis's comments.

   June 10, 2002 Added proposal for different method for query schema
      discovery, not using pseudo-properties.

   June 25, 2002 QSD marshalling rewritten. Added issue
      "isdefined-optional".


B.4 since draft-reschke-webdav-search-01

   July 04, 2002 Added issue "scope-collection".

   July 08, 2002 Closed issue "scope-collection".

   August 12, 2002 Added issues "results-vs-binds" and "select-allprop".

   October 22, 2002 Added issue "undefined-expressions".






Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 49]

Internet Draft 54]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   Alan Babich
   FileNET Corp.
   3565 Harbor Blvd.
   Costa Mesa, CA 92626

   Phone: +1 714 327 3403
   EMail: ababich@filenet.com


   November 18, 2002 Changed example host names (no change tracking).

   November 25, 2002 Updated issue "DB2/DB7". Closed issues "undefined
      expressions", "isdefined-optional" and "select-allprop".


B.5 since draft-reschke-webdav-search-02

   November 27, 2002 Added issues "undefined-properties",
      "like-exactlyone" and "like-wildcard-adjacent". Closed issue
      "query-on-href". Added acknowledgments section.

   November 28, 2002 Closed issue "like-exactlyone". Added issue
      "mixed-content-properties".

   December 14, 2002 Closed issues "undefined-properties",
      "results-vs-binds", "mixed-content-properties". Updated issue
      "like-wildcard-adjacent". Added informative reference to BIND
      draft. Updated reference to ACL draft.

   January 9, 2003 Removed duplicate section on invalid scopes. Added
      comments to some open issues. Closed issues JW25/26,
      score-pseudo-property and null-ordering.

   January 10, 2003 Issue limit-vs-ordering plus resolution. Closed
      issue JW17/JW24b.

   January 14, 2003 New issue order-precedence. Started resolution of
      DB2/DB7.

   January 15, 2003 Started spec of DAV:typed-literal.

   January 17, 2003 Fix one DAV:like/DAV:getcontenttype example (add /
      to like expression, make case-insensitive).

   January 28, 2003 Update issue(s) result-truncation, JW24d. Fixed
      response headers in OPTIONS example. Added issue qsd-optional.
      Closed issue(s) order-precedence, case-insensitivity-name.

   February 07, 2003 Added issue scope-vs-versions.
      score-pseudo-property: allow DAV:orderby to explicitly specify
      DAV:score.


B.6 since draft-reschke-webdav-search-03






Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 50]

Internet Draft 55]

Internet-Draft               WebDAV SEARCH                  October 2003


   April 24, 2003 Fixed two "?" vs "_" issues (not updated in last
      draft).

   June 13, 2003


A Three-Valued Logic Improve index.


B.7 since draft-reschke-webdav-search-04

   July 7, 2003 Typo fixed (propstat without status element).

   August 11, 2003 Remove superfluous IP and copyright sections.

   September 09, 2003 Added issues "2.4-multiple-uris" and
      "5.1-name-filtering".

   October 06, 2003 Fix misplaced section end in DAV:basicsearch

   ANSI standard three valued logic is used when evaluating the search
   condition (as defined 5.11, add table
      formatting. Enhance table formatting in the ANSI standard SQL specifications, 5.18.3. Updated ACL and
      BIND references. Added XPATH reference. Closed issue JW24d by
      adding new optional operators. Updated more open issues, added
      issues from January meeting. Add K. Wiggen to Acknowledgements.
      Add Contributors section for
   example the authors of the original draft.
      Close issue "scope-vs-versions" (optional feature added). Close
      (new) issue "1.3-import-DTD-terminology". Add issue
      "1.3-import-requirements-terminology".

   October 07, 2003 Typos fixed. Moved statement about DAV: namespace
      usage into separate (sub-)section. Closed
      "1.3-import-requirements-terminology". Update I18N Considerations
      with new xml:lang support info (see issue JW24d). Close issue
      "DB2/DB7" (remaining typing issues are now summarized in ANSI X3.135-1992, issue
      "typed-literal"). Fix misplaced section 8.12, pp. 188-189, end in section 8.2,
   p. 169, General Rule 1)a), etc.).

   ANSI standard three valued logic is undoubtedly 7. Started
      change to use RFC3253-style method definitions and error
      marshalling.

   October 08, 2003 Remove obsolete language that allowed reporting
      invalid scopes and such inside multistatus. Add new issue
      "5.4.2-scope-vs-redirects".














Reschke, et al.          Expires April 9, 2004                 [Page 56]

Internet-Draft               WebDAV SEARCH                  October 2003


Appendix C. Resolved issues (to be removed by RFC Editor before
            publication)

   Issues that were either rejected or resolved in this version of this
   document.

C.1 1.3-import-condition-code-terminology

   Type: change

   [3]

   julian.reschke@greenbytes.de (2003-10-05): Import RFC3253 pre/
   postcondition code terminology and use it throughout the document to
   identify conditions.

   Resolution: Section 2.5 rewritten.

C.2 1.3-import-requirements-terminology

   Type: change

   julian.reschke@greenbytes.de (2003-10-06): Import terminology from
   DASLREQ.

   Resolution: Done.

C.3 1.3-import-DTD-terminology

   Type: change

   [4]

   julian.reschke@greenbytes.de (2003-09-27): Import DTD usage notes
   from ordering spec.

C.4 invalid-scope

   Type: change

   julian.reschke@greenbytes.de (2003-01-09): Marshalling a BAD REQUEST
   with an (extended) multistatus body seems to be a weird approach.
   Should be resolved by finally adopting the RFC3253 error marshalling.

   julian.reschke@greenbytes.de (2003-01-28): Funny enough, Roy
   Fielding's feedback on a related issue indicates that this may be the most widely
   practiced method of dealing
   absolutely right thing to do. Needs coordination with RFC2518bis
   activity.



Reschke, et al.          Expires April 9, 2004                 [Page 57]

Internet-Draft               WebDAV SEARCH                  October 2003


   Resolution: Document style change to use RFC3253 preconditions.

C.5 JW24d

   Type: edit

   [5]

   ejw@ics.uci.edu (2000-04-20): Where does xml:lang go in a query?

   julian.reschke@greenbytes.de (2002-02-28): What would be the issues
   *purpose* of properties in putting xml:lang into a query?

   jrd3@alum.mit.edu (2002-05-28): The purpose is to allow one to
   express queries more precisely, e.g. to distinguish between the
   search condition not having
   English word "hoop" (a circular object) and Dutch "hoop" (hope).
   Imagine a value (e.g., being null or not defined) property that holds keywords for the resource under scan, a resource.   See 4.4 in
   http://www.ietf.org/rfc/rfc2518.txt, and with undefined expressions 2.12 in http://www.w3.org/
   TR/REC-xml

   julian.reschke@greenbytes.de (2002-05-28): I think this would be an
   interesting feature, but it seems to be extremely hard to implement.
   So assuming a query that - the
   search condition (e.g., division by zero, etc.). Three valued logic
   works as follows.

   Undefined expressions are expressions for which query specifies a language and - be
   the value text content of the
   expression is not defined. Undefined expressions are a completely
   separate concept from property matches The result will be: 1) true
   (match), if the truth value UNKNOWN, which is, in fact,
   well defined. Property names and literal constants are considered
   expressions for purposes of this section. If property was stored with a matching xml:lang property in
   (where the
   current resource under scan has not been set language tag matching rules would have to a value, then apply) 2)
   undefined if the
   value of that property is undefined for was stored without xml:lang 3) false
   otherwise On the resource under scan. DASL
   1.0 has no arithmetic division operator, but other hand if it did, division by
   zero would be an - the query doesn't specify a language
   the result will be: 4) undefined arithmetic expression.

   If any subpart of an arithmetic, string, or datetime subexpression is
   undefined, (at least according to the current
   wording). So, 1) requires that the whole arithmetic, string, or datetime subexpression is
   undefined.

   There are no manifest constants query engine actually knows how to explicitly represent undefined
   number, string, or datetime values.

   Since a Boolean value
   match language tags -- I'm not sure that everybody is ultimately returned by the search condition,
   arithmetic, string, and datetime expressions are always arguments willing to
   other operators. Examples of operators
   implement that. 2) is this desirable? 3) ok. 4) that convert arithmetic,
   string, and datetime expressions seems to Boolean values are the six
   relational operators ("greater than", "less than", "equals", etc.). be
   wrong. If either or both operands the query doesn't care, it should match, right? Other
   problems: - what is the language of a relational operator have undefined
   values, then date-typed property? - (sic!)
   where should xml:lang go into the relational operator evaluates query? There's no XML feature to UNKNOWN. Otherwise,
   undefine an xml:lang which is in scope, but there may be cases where
   this is needed. On the relational operator evaluates to TRUE or FALSE, depending upon other hand, if we drop this requirement, a
   client can still do a query and then process the outcome of result set -- the comparison.

   The Boolean operators DAV:and, DAV:or and DAV:not are evaluated
   according
   property elements in the response body will be reported with xml:lang
   (when persisted with language) anyway. So I'd recommend to drop the following rules:

   UNKNOWN and UNKNOWN = UNKNOWN

   UNKNOWN or UNKNOWN = UNKNOWN




Reschke, et al.           Expires December 2003                [Page 51]

Internet Draft                WebDAV SEARCH                    June 2003


   not UNKNOWN = UNKNOWN

   UNKNOWN and TRUE = UNKNOWN

   UNKNOWN and FALSE = FALSE

   UNKNOWN and UNKNOWN = UNKNOWN

   UNKNOWN or TRUE = TRUE

   UNKNOWN or FALSE = UNKNOWN

   UNKNOWN or UNKNOWN = UNKNOWN
   feature. Defining string comparisons vs. collation sequences is hard
   enough.

   julian.reschke@greenbytes.de (2003-01-09): (Proposal to reject)

   julian.reschke@greenbytes.de (2003-01-28): WG meeting feedback:
   should be moved into explicit operators (see proposal on mailing
   list). Open: is this optional or required?



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 52]

Internet Draft 58]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


B Change Log


B.1 From draft-davis-dasl-protocol-xxx



   Feb 14, 1998       Initial Draft
   Feb 28, 1998       Referring to DASL as an extension to HTTP/1.1
                      rather than DAV.
                      Added


   Resolution: Add new sections "Notational Conventions",
                      "Protocol Model", "Security Considerations".
                      Changed section 3 to "Elements of Protocol".
                      Added some stuff optional operators.

C.6 scope-vs-versions

   Type: change

   [6]

   julian.reschke@greenbytes.de (2003-02-05): A relatively frequent use
   case for servers that both support versioning and DASL seems to introduction.
                      Added "result set" terminology.
                      Added "IANA Considerations".
   Mar 9, 1998        Moved sub-headings have
   searches that include all versions of "Elements the resources in scope. In
   general, the version URIs may not be in the scope of Protocol" the query.
   Therefore, I'd like to
                      first level and removed "Elements extend the DAV:scope to specify inclusion of Protocol"
                      Heading.
                      Added
   versions. This would be an sentence in introduction explaining optional extension -- however, a server
   that
                      this is does not support his feature should reject the request (so that
   the client would know that the request could not be satisfied).
   Example: <d:from xmlns:d="DAV:"> <d:scope> <d:href>/container1/</
   d:href> <d:depth>infinity</d:depth> <d:include-versions /> </d:scope>
   </d:from>

   Martin.Wallmer@softwareag.com (2003-02-06): just to clarify: 1. If a "sketch"
   resource in scope has versions, the server SHOULD take care of a protocol.
   Mar 11, 1998       Added orderby, data typing, three valued logic,
                      query schema property, and element definitions for
                      schema for basicsearch.
   April 8, 1998      - made changes based on last week's DASL BOF.
   May 8, 1998        Removed most
   versions as well. 2. If the client specifies <d:include-versions />,
   the server MUST take care of DAV:searcherror; converted to
                      DAV:searchredirect
                      Altered DAV:basicsearch grammar versions or MUST reject the request. 3.
   If the user does not want to use avoid use
                      of ANY get versions, he must specify <not
   xmlns="DAV:"><is-defined><version-name /></is-defined></not> ... Is
   my understanding correct? However, a defined "switch" (include -
   exclude) could be a good hint for the server in DTD
   June 17, 1998      -Added details on Query Schema Discovery
                      -Shortened list terms of data types
   June 23, 1998      moved data types before change history
                      rewrote the data types section
                      removed performance,
   so I'd prefer a <d:exclude-versions/> as well. Alternatively the casesensitive element and replace with
   server should only include the casesensitive attribute
                      added versions, if <d:include-versions /> is
   specified. Does this make sense?

   julian.reschke@greenbytes.de (2003-02-06): I don't like that, because
   I'd prefer to keep the casesensitive attribute definition of "scope" intact. If versions
   happen to be in the DTD for
                      all operations that might work on a string
   Jul 20, 1998       A series namespace scope, they should be in scope of changes. See Author's meeting minutes
                      for details.
   July 28, 1998      Changes the
   search as per author's meeting. QSD uses SEARCH,
                      not PROPFIND.
                      Moved text around well. Thus the proposal to keep concepts nearby.
                      Boolean literals are 1 and 0, not T and F.
                      contains changed add a specific element that
   *extends* the scope of the query.

C.7 DB2/DB7

   Type: change

   [7]

   ejw@ics.uci.edu (2000-04-20): Dates (HTTPDate in getlastmodified).

   ejw@ics.uci.edu (2000-04-20): Agreement that it is OK to contentspassthrough.
                      Renamed rank submit
   isodate to score.
   July 28, 1998      Added Dale Lowry as Author
   September 4, 1998  Added 422 as response when query lists
                      unimplemented operators. search HTTPDate (i.e., it's a marshalling issue only).



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 53]

Internet Draft 59]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


                      DAV:literal declares


   ejw@ics.uci.edu (2000-04-20): Booleans appear to be underspecified in
   the specification. How is a default value for
                      xml:space, 'preserve' (see XML spec, section 2.10)
                      moved boolean tested, and what are the behavior
   of operators like less than, greater than, etc.

   julian.reschke@greenbytes.de (2002-01-28): I think similar questions
   apply to new booleans. Proposal: allow specification of the literal's
   type using XML namespace syntax
   September 22, 1998 Changed "simplesearch" Schema simple types, and declare that "both" WebDAV
   date types are compatible.

   ABabich@filenet.com (2002-01-29): The current DASL draft doesn't
   really have Booleans or any other data type. It's trying to skate on
   data types. Booleans could be tested using the "eq" and the
   combination "not eq", if you had well defined literals for TRUE and
   FALSE. With the current syntax, that is the way you would have to "basicsearch"
                      Changed isnull
   test a Boolean. Generally, Boolean values are not considered to isdefined
                      Defined NULLness as having be
   ordered, so "gt" etc. wouldn't apply. However, if the literal values
   of a 404 or 403 response Boolean were 1 and 0 for TRUE and FALSE (using the most commonly
   used ENTITY syntax in DTD
                      Added redirect
   October 9, 1998    Fixed a series convention of typographical positive logic), then you would have an obvious
   ordering. 1 and formatting
                      errors.
                      Modified 0 have the section advantage of three-valued logic to use
                      a table rather than being language independent.
   You now see a text description lot of electronic and electro-mechanical devices (air
   conditioners, computers, etc.) with a "1/0" label on the role power
   switch, "1" meaning "on", and "0" meaning "off". SQL databases don't
   have Booleans. SQL doesn't control DASL, of UNKNOWN course, but SQL databases
   are so widely used that they are important. The closest thing in expressions.
   November 2, 1998   Added the DAV:contains operator.
                      Removed SQL
   is a bit field. Each bit in a bit field is zero or 1. So, why not
   close the DAV:contentpassthrough operator.
   November 18, 1998  Various author comments issue by saying: DASL doesn't have data types. You can
   simulate Booleans by an integer data type, using 1 for submission
   June 3, 1999       Cosmetic "TRUE" and minor editorial changes only. Fix
                      nits reported by Jim Whitehead in email of April
                      26, 1999. Converted 0
   for "FALSE".

   julian.reschke@greenbytes.de (2002-10-22): let's consider a dead
   property "foo", and some resources a, b and c on which this dead
   property is defined and has the values "1", "3" and "10". Consider a
   DAV:basicsearch with the where clause: <gte xmlns="DAV:"> <prop><foo
   xmlns=""/></prop> <literal>3</literal> </gte> Which resource will
   match? As DAV:basicsearch currently isn't type-aware, the server will
   have to HTML from Word 97,
                      manually.
   April 20, 2000     Removed redirection feature, since 301/302
                      suffices. Removed Query Schema Discovery (former
                      chapter 4). Everyone agrees do a string comparison, and only the b (with value "3") will
   match. Is this is really sufficient? It basically means that dead
   property comparisons are restricted to strings. Proposals: a) If the
   server happens to have type information for a useful
                      feature, but dead property, it is apparently too difficult
   should try to
                      define at do a comparison according to the known property type,
   if the literal can be parsed into this time, and type. This basically
   replicates the behaviour that a client would expect when querying on
   live properties such as DAV:getcontentlength, so it is not essential for
                      DASL.




B.2 since start of draft-reschke-webdav-search



   October 09, 2001  Added Julian Reschke could be taken as author.
                     Chapter about QSD re-added.
                     Formatted into RFC2629-compliant XML document.
                     Added first comments.
                     ID version number kicked up to draft-dasl-
                     protocol-03.
   October 17, 2001  Updated address information for Jim Davis.
                     Added issue of datatype vocabularies.
                     Updated issue descriptions for grammar discovery,
                     added issues on query schema DTD.
                     Fixed typos
   a simple clarification. Extended proposal: b) A client can enforce
   comparison using a specific data type by specifying the type in XML examples.
   December 17, 2001 Re-introduced split between normative and non-
                     normative references. the
   query, for instance using: <gte xmlns="DAV:"> <prop><foo xmlns=""/></
   prop> <literal xsi:type="xs:long">3</literal> </gte>




Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 54]

Internet Draft 60]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   January 05, 2002  Version bumbed up to 04. Started work on resolving
                     the issues identified in the previous version.
   January 14, 2002  Fixed some XML typos.
   January 22, 2002  Closed issues naming-of-elements. Fixed query
                     search DTD and added option to discover properties
                     of "other" (non-listed) properties.
   January 25, 2002  Changed into private submission and added reference
                     to historic DASL draft. Marked reference to DASL
                     requirements non-normative.
                     Updated reference


   Martin.Wallmer@softwareag.com (2002-11-25): What about existing
   implementations? Currently a server might react with "xsi:type
   unknown entity" or just ignore it (which would mean: String
   comparison)

   julian.reschke@greenbytes.de (2002-11-25): OK, how about *adding* an
   alternative to latest deltav spec.
   January 29, 2002  Added feedback from and updated contact info for
                     Alan Babich.
                     Included open issues collected in
                     http://www.webdav.org/dasl/protocol/issues.html.
   February 8, 2002  Made sure that all artwork fits into 72 characters
                     wide text.
   February 18, 2002 Changed Insufficient storage handling
                     (multistatus). Moved is-collection DAV:literal? Therefore: DAV:literal: untyped, server
   can compare according to operators and
                     added it's internal knowledge of types (with the
   clarification above) DAV:typed-literal: typed according to DTD. Made scope/depth mandatory.
   February 20, 2002 Updated reference the
   xsi:type attribute -- "new" servers can implement this without
   affecting any existing code. We'll need to SQL99.
   February 28, 2002 "Non-normative References" -> "Informative
                     References". Abstract updated. Consistently specify
                     a charset when using text/xml (no change bars). Do
                     not attempt think about discovery of
   this feature, though. It might be possible to do this with QSD (in
   the meantime, are there any QSD implementations except ours?)

   Resolution: WG meeting feedback: define PROPFIND's entity encoding
                     (take out specific references DAV:typed-literal. Also allow
   DAV:literal to text/xml). Remove
                     irrelevant headers (Connection:) from examples (no be evaluated by the server according "internal" type
   knowledge. Require timestamps to be ISO, even for
   DAV:getlastmodified.

































Reschke, et al.          Expires April 9, 2004                 [Page 61]

Internet-Draft               WebDAV SEARCH                  October 2003


Appendix D. Open issues (to be removed by RFC Editor before publication)

D.1 1.3-apply-condition-code-terminology

   Type: change bars). Added

   julian.reschke@greenbytes.de (2003-10-07): (Umbrella issue on querying based on
                     DAV:href. Updated introduction to indicate
                     relationship to DASL draft. Updated HTTP reference
                     from RFC2068 that will
   be left open until RFC3253 condition terminlogy is used throughout
   the document)

D.2 2.4-multiple-uris

   Type: change

   julian.reschke@greenbytes.de (2003-09-09): However, the set of URIs
   for a given resource may be unlimited due to RFC2616. Updated XML reference possible bind loops.
   Therefore consider to
                     XML 1.0 2nd edition.
   March 1, 2002     Removed superfluous namespace decl in 2.4.2.
                     Reopened JW14 report just one URI per resource.

D.3 result-truncation

   Type: change

   [8]

   ldusseault@xythos.com (2002-03-29): I believe the same response body
   that contains the first N <DAV:response> elements should also contain
   a *different* element stating that the results were incomplete and suggest
   the result set was truncated by the server. There may also be a need
   to drop xml:space
                     support.
   March 3, 2002     Removed "xml:space" feature on DAV:literal. Added
                     issue about string comparison vs. collations vs.
                     xml:lang. Updated some report that the results were incomplete and the result set was
   truncated at the choice of the open issues client (isn't there a limit set in the
   client request?)  That's important so the client knows the difference
   between receiving 10 results because there were >10 but only 10 were
   asked for, and receiving 10 results because there were only exactly
   10 results and it just happens that 10 were asked for.

   jrd3@alum.mit.edu (2002-05-28): I agree that this could be useful,
   but I think this issue should be consolidated with
                     details from JimW's original mail issue JW5 (see
   below), which proposes that DASL basicsearch ought to have a way for
   client to request additional result sets.  It should be moved because
   there is little or no value in April 1999.
                     Resolved scope vs relative URI references. Resolved
                     issues about DAV:ascending (added allowing a client to index) and distinguish
   between the
                     BNF case where "N results were requested, and there are
   exactly N available" and "N results were requested, and there are
   more than N available" if there is no way for DAV:like (changed "octets" to
                     "characters").
   March 8, 2002     Updated reference client to DeltaV (now RFC3253). Added
                     Martin Wallmer's comments, moved JW5 into
                     DAV:basicsearch section.
   March 11, 2002    Closed open issues regaring get the type next
   batch of search
                     arbiters (JW3) results.

   julian.reschke@greenbytes.de (2003-01-28): Feedback from interim WG
   meeting: agreement that marshalling should be rewritten and their discovery (JW9). Rephrased
                     requirements on multistatus response bodies backwards
   compatibility is not important. Proposal: extend DAV:multistatus by a



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 55]

Internet Draft 62]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


                     (propstat only if properties were selected, removed
                     requirement


   new child element that indicates (1) the range that was returned, (2)
   the total number of results and (3) a URI identifying the result (for
   resubmission when getting the "next" results). Such as <multistatus
   xmlns='DAV:'> <search-result> <href>...identifier for responsedescription).
   March 23, 2002    RFC2376 -> RFC3023. Added missing first names result set...</
   href> <total><-- number of
                     authors. OPTIONS added to example results --></total> <start><-- 1-based
   index of 1st result --></start> <length><-- size of result set
   returned --></length> <partial-result/><-- indicates that this is a
   partial result --> </search-result> ...response elements for
                     DAV:supported-method-set.




B.3 since draft-reschke-webdav-search-00



   March 29, 2002 Abstract doesn't refer search
   results... </multistatus> The example below would then translate to:
   HTTP/1.1 207 Multistatus Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx <?xml version="1.0" encoding="utf-8"?>
   <D:multistatus xmlns:D="DAV:"> <D:search-result> <D:partial-result/>
   </D:search-result> <D:response> <D:href>http://www.example.net/
   sounds/unbrokenchain.au</D:href> <D:propstat> <D:prop/>
   <D:status>HTTP/1.1 200 OK</D:status> </D:propstat> </D:response>
   <D:response> <D:href>http://tech.mit.test/archive96/photos/
   Lesh1.jpg</D:href> <D:propstat> <D:prop/> <D:status>HTTP/1.1 200 OK</
   D:status> </D:propstat> </D:response> </D:multistatus> Q: do we need
   all elements, in particular start and length?

   julian.reschke@greenbytes.de (2003-10-07): Related: if this is
   supposed to DASL WG anymore.
   April 7, 2002  Fixed section title (wrong property name supported-
                  search-grammar-set. Changed DAV:casesensitve be normative to
                  "casesensitive" (it wasn't DAV:basicsearch, it can't stay in the DAV: namespace after
                  all).
   May 28, 2002   Updated some issues with Jim Davis's comments.
   June 10, 2002  Added proposal for different method for query schema
                  discovery, not using pseudo-properties.
   June 25, 2002 an
   "example" sub-section.

D.4 qsd-optional

   Type: change

   julian.reschke@greenbytes.de (2003-01-28): WG January meeting
   feedback: QSD marshalling rewritten. Added issue "isdefined-
                  optional".




B.4 since draft-reschke-webdav-search-01



   July 04, 2002     Added issue "scope-collection".
   July 08, 2002     Closed issue "scope-collection".
   August 12, 2002   Added issues "results-vs-binds" and "select-
                     allprop".
   October 22, 2002  Added issue "undefined-expressions".
   November 18, 2002 Changed example host names (no should be made required.

   kwiggen@xythos.com (2003-10-03): (significant pushback, see mailing
   list thread at http://lists.w3.org/Archives/Public/www-webdav-dasl/
   2003OctDec/0003.html).

D.5 5.1-name-filtering

   Type: change tracking).
   November 25, 2002 Updated issue "DB2/DB7". Closed issues "undefined
                     expressions", "isdefined-optional"

   [9]

   julian.reschke@greenbytes.de (2003-09-08): This query grammar
   supports properties and "select-
                     allprop".




B.5 since draft-reschke-webdav-search-02 content, but not conditions on URL elements
   (such as the last segment that many WebDAV implementations treat as
   "file name"). Discuss possible extension such as adding name filters
   to the scope, or adding a specific operator.





Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 56]

Internet Draft 63]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   November 27, 2002 Added issues "undefined-properties", "like-
                     exactlyone" and "like-wildcard-adjacent". Closed
                     issue "query-on-href". Added acknowledgments
                     section.
   November 28, 2002 Closed issue "like-exactlyone". Added issue "mixed-
                     content-properties".
   December 14, 2002 Closed issues "undefined-properties", "results-vs-
                     binds", "mixed-content-properties". Updated issue
                     "like-wildcard-adjacent". Added informative
                     reference to BIND draft. Updated reference


D.6 5.4.2-multiple-scope

   Type: change

   [10]

   prakash.yamuna@covigna.com (2003-09-27): (asks for the ability to ACL
                     draft.
   January 9, 2003   Removed duplicate section
   specify multiple scopes in a single query)

   julian.reschke@greenbytes.de (2003-10-03): Consider making this an
   optional extension iff we can come up with a simple enough definition
   of it's impact on invalid scopes. Added
                     comments to some open issues. Closed issues
                     JW25/26, score-pseudo-property sorting/ranking and null-ordering.
   January 10, 2003  Issue limit-vs-ordering plus resolution. Closed
                     issue JW17/JW24b.
   January 14, 2003  New issue order-precedence. Started resolution so on. Otherwise propose to
   reject.

D.7 5.4.2-scope-vs-redirects

   Type: change

   [11]

   julian.reschke@greenbytes.de (2003-10-08): Clarify the relation of
                     DB2/DB7.
   January 15, 2003  Started spec
   scope and redirect (3xx) resources.

D.8 language-comparison

   Type: change

   [12]

   julian.reschke@greenbytes.de (2002-03-03): XPath/XQuery (see draft,
   and open issue) specify string comparisons based on collations, not
   languages. I think we should adopt this. This would mean that
   "xml:lang" would be removed, and an optional attribute specifying the
   name of DAV:typed-literal.
   January 17, 2003  Fix one DAV:like/DAV:getcontenttype example (add /
                     to like expression, make case-insensitive).
   January 28, 2003  Update issue(s) result-truncation, JW24d. Fixed
                     response headers the collation is added.

   julian.reschke@greenbytes.de (2003-01-09): Proposal: adopt "lang" and
   "collation" attribute from XSLT 2.0's xsl:sort.

D.9 JW16b/JW24a

   Type: change

   [13]

   ejw@ics.uci.edu (2000-04-20): Define how comparisons on strings work,
   esp for i18n. Need policy statement about sort order in OPTIONS example. Added issue
                     qsd-optional. Closed issue(s) order-precedence,
                     case-insensitivity-name.
   February 07, 2003 Added various
   national languages. (JW said "non-Latin" but it's an issue scope-vs-versions. score-pseudo-
                     property: allow DAV:orderby to explicitly specify
                     DAV:score.




B.6 since draft-reschke-webdav-search-03



   April 24, 2003 Fixed two "?" vs "_" issues (not updated even in last
                  draft).
   June 13,
   languages that use the latin char set.)



Reschke, et al.          Expires April 9, 2004                 [Page 64]

Internet-Draft               WebDAV SEARCH                  October 2003  Improve index.


   julian.reschke@greenbytes.de (2003-01-28): This issue not only
   applies to the comparison operators, but also to ordering!

D.10 typed-literal

   Type: change

   julian.reschke@greenbytes.de (2003-01-15): 1. (insert language
   defining the comparison following the rules defined in http://
   www.w3.org/TR/xpath20/#id-comparisons). 2. Extend Basicsearch QSD
   grammar to support discovery of typed-literal 3. Update DTD. 4.
   Discuss behaviour of DAV:literal when the property's type is known
   for the complete search scope (is the server allowed to be "smart"?)






































Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 57]

Internet Draft 65]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


Index

C
   caseless attribute
      5.8, 5.18  27, 33
   Criteria  5

D
   DAV:and
      5.7  27
   DAV:ascending
      5.6  26
   DAV:contains
      5.16  31
   DAV:depth
      5.4  23
   DAV:descending
      5.6  26
   DAV:eq
      5.8caseless  27
      caseless attribute   5.8  27
   DAV:from
      5.4  23
   DAV:gt
      5.9  27
   DAV:gte
      5.9  27
   DAV:include-versions
      5.4  23
   DAV:is-collection
      5.13  30
   DAV:is-defined
      5.14  30
   DAV:language-defined  29
   DAV:language-matches  29
   DAV:like
      5.15  30
   DAV:limit
      5.17  33
   DAV:literal



Reschke, et al.           Expires December 2003                [Page 58]

Internet Draft                WebDAV SEARCH                    June 2003


      5.10  27
   DAV:lt
      5.9  27
   DAV:lte
      5.9  27
   DAV:not
      5.7  27
   DAV:nresults
      5.17  33
   DAV:or
      5.7  27
   DAV:orderby
      5.6  26
   DAV:scope
      5.4  23
   DAV:score
      5.16.1relationship  32
      relationship to DAV:orderby   5.17.1

   DAV:searchrequest
      2.3  33
   DAV:search-grammar-discovery-supported precondition  10
   DAV:search-grammar-supported precondition  10
   DAV:search-scope-valid precondition  10
   DAV:select
      5.3  23
   DAV:supported-query-grammar-set
      property   3.3  15
   DAV:typed-literal
      5.11  28
   DAV:where
      5.5  24

O
   OPTIONS method
      3.1DASL  14
      DASL response header   3.2




   Q


   Query Grammar Discovery
      3using OPTIONS   3.1
      using live property   3.3  14

P



Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 59]

Internet Draft 66]

Internet-Draft               WebDAV SEARCH                    June                  October 2003


   Preconditions
      DAV:search-grammar-discovery-supported  10
      DAV:search-grammar-supported  10
      DAV:search-scope-valid  10

Q
   Query Grammar Discovery  14
      using live property  15
      using OPTIONS  14
   Query Grammar  6
   Query Schema  6
   Query  5

R
   Result Record Definition  6
   Result Record  6
   Result Set Truncation
      Example   2.4.3  11
   Result Set  6
   Result  6

S
   Scope
      Invalid   2.6  6
   SEARCH method
      2  9
   Search Modifier  6
   Sort Specification  6

























Reschke, et al.          Expires April 9, 2004                 [Page 67]

Internet-Draft               WebDAV SEARCH                  October 2003


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights. Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11. Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard. Please address the information to the IETF Executive
   Director.


Full Copyright Statement

   Copyright (C) The Internet Society (2003). All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise



Reschke, et al.           Expires December 2003                [Page 60]

Internet Draft                WebDAV SEARCH                    June 2003 explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works. However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assignees.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION



Reschke, et al.          Expires April 9, 2004                 [Page 68]

Internet-Draft               WebDAV SEARCH                  October 2003


   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


   Acknowledgement


Acknowledgment

   Funding for the RFC editor Editor function is currently provided by the
   Internet Society.











































Reschke, et al.          Expires December 2003 April 9, 2004                 [Page 61] 69]


----