idnits 2.17.1 draft-reschke-webdav-search-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 22. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2521. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2498. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2505. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2511. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == Mismatching filename: the document gives the document name as 'draft-reschke-webdav-search-latest-07', but the file name used is 'draft-reschke-webdav-search-07' == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1019 has weird spacing: '...ment is is an...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: Query grammars are identified by URIs. Applications SHOULD not attempt to retrieve these URIs even if they appear to be retrievable (for example, those that begin with "http://") == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (September 30, 2004) is 7147 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2518 (Obsoleted by RFC 4918) ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' -- Possible downref: Non-RFC (?) normative reference: ref. 'XPATH' -- Possible downref: Non-RFC (?) normative reference: ref. 'XS1' -- Possible downref: Non-RFC (?) normative reference: ref. 'XS2' == Outdated reference: A later version (-27) exists of draft-ietf-webdav-bind-07 -- No information found for draft-dasl-protocol - is the name correct? -- No information found for draft-dasl-requirements - is the name correct? Summary: 8 errors (**), 0 flaws (~~), 8 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Reschke, Ed. 3 Internet-Draft greenbytes 4 Expires: March 31, 2005 S. Reddy 5 Oracle 6 J. Davis 7 Intelligent Markets 8 A. Babich 9 Filenet 10 September 30, 2004 12 WebDAV SEARCH 13 draft-reschke-webdav-search-latest-07 15 Status of this Memo 17 This document is an Internet-Draft and is subject to all provisions 18 of section 3 of RFC 3667. By submitting this Internet-Draft, each 19 author represents that any applicable patent or other IPR claims of 20 which he or she is aware have been or will be disclosed, and any of 21 which he or she become aware will be disclosed, in accordance with 22 RFC 3668. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as 27 Internet-Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt. 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 This Internet-Draft will expire on March 31, 2005. 42 Copyright Notice 44 Copyright (C) The Internet Society (2004). 46 Abstract 48 This document specifies a set of methods, headers, properties and 49 content-types composing WebDAV SEARCH, an application of the HTTP/1.1 50 protocol to efficiently search for DAV resources based upon a set of 51 client-supplied criteria. 53 Editorial Note (To be removed by RFC Editor before publication) 55 Please send comments to the Distributed Authoring and Versioning 56 (WebDAV) DASL mailing list at , which 57 may be joined by sending a message with subject "subscribe" to 58 . Discussions of the WebDAV 59 DASL mailing list are archived at 60 . 62 An issues list and XML and HTML versions of this draft are available 63 from . 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 68 1.1 DASL . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 69 1.2 Relationship to DAV . . . . . . . . . . . . . . . . . . . 5 70 1.3 Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 71 1.4 Notational Conventions . . . . . . . . . . . . . . . . . . 7 72 1.5 Editorial note on usage of 'DAV:' namespace . . . . . . . 7 73 1.6 An Overview of DASL at Work . . . . . . . . . . . . . . . 8 74 2. The SEARCH Method . . . . . . . . . . . . . . . . . . . . . 8 75 2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 8 76 2.2 The Request . . . . . . . . . . . . . . . . . . . . . . . 8 77 2.2.1 The Request-URI . . . . . . . . . . . . . . . . . . . 8 78 2.2.2 The Request Body . . . . . . . . . . . . . . . . . . . 9 79 2.3 The Successful 207 (Multistatus) Response . . . . . . . . 9 80 2.3.1 Extending the PROPFIND Response . . . . . . . . . . . 10 81 2.3.2 Example: A Simple Request and Response . . . . . . . . 10 82 2.3.3 Example: Result Set Truncation . . . . . . . . . . . . 11 83 2.4 Unsuccessful Responses . . . . . . . . . . . . . . . . . . 12 84 2.4.1 Example of an Invalid Scope . . . . . . . . . . . . . 12 85 3. Discovery of Supported Query Grammars . . . . . . . . . . . 13 86 3.1 The OPTIONS Method . . . . . . . . . . . . . . . . . . . . 13 87 3.2 The DASL Response Header . . . . . . . . . . . . . . . . . 14 88 3.3 DAV:supported-query-grammar-set (protected) . . . . . . . 14 89 3.4 Example: Grammar Discovery . . . . . . . . . . . . . . . . 14 90 4. Query Schema Discovery: QSD . . . . . . . . . . . . . . . . 16 91 4.1 Additional SEARCH semantics . . . . . . . . . . . . . . . 17 92 4.1.1 Example of query schema discovery . . . . . . . . . . 18 93 5. The DAV:basicsearch Grammar . . . . . . . . . . . . . . . . 19 94 5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 19 95 5.2 The DAV:basicsearch DTD . . . . . . . . . . . . . . . . . 20 96 5.2.1 Example Query . . . . . . . . . . . . . . . . . . . . 21 97 5.3 DAV:select . . . . . . . . . . . . . . . . . . . . . . . . 22 98 5.4 DAV:from . . . . . . . . . . . . . . . . . . . . . . . . . 22 99 5.4.1 Relationship to the Request-URI . . . . . . . . . . . 23 100 5.4.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . 23 101 5.5 DAV:where . . . . . . . . . . . . . . . . . . . . . . . . 23 102 5.5.1 Use of Three-Valued Logic in Queries . . . . . . . . . 23 103 5.5.2 Handling Optional operators . . . . . . . . . . . . . 24 104 5.5.3 Treatment of NULL Values . . . . . . . . . . . . . . . 24 105 5.5.4 Treatment of properties with mixed/element content . . 24 106 5.5.5 Example: Testing for Equality . . . . . . . . . . . . 24 107 5.5.6 Example: Relative Comparisons . . . . . . . . . . . . 24 108 5.6 DAV:orderby . . . . . . . . . . . . . . . . . . . . . . . 25 109 5.6.1 Comparing Natural Language Strings . . . . . . . . . . 25 110 5.6.2 Example of Sorting . . . . . . . . . . . . . . . . . . 26 111 5.7 Boolean Operators: DAV:and, DAV:or, and DAV:not . . . . . 26 112 5.8 DAV:eq . . . . . . . . . . . . . . . . . . . . . . . . . . 26 113 5.9 DAV:lt, DAV:lte, DAV:gt, DAV:gte . . . . . . . . . . . . . 26 114 5.10 DAV:literal . . . . . . . . . . . . . . . . . . . . . . 26 115 5.11 DAV:typed-literal (optional) . . . . . . . . . . . . . . 27 116 5.11.1 Example for typed numerical comparison . . . . . . . 27 117 5.12 Support for matching xml:lang attributes on properties . 28 118 5.12.1 DAV:language-defined (optional) . . . . . . . . . . 28 119 5.12.2 DAV:language-matches (optional) . . . . . . . . . . 28 120 5.12.3 Example of language-aware matching . . . . . . . . . 28 121 5.13 DAV:is-collection . . . . . . . . . . . . . . . . . . . 29 122 5.13.1 Example of DAV:is-collection . . . . . . . . . . . . 29 123 5.14 DAV:is-defined . . . . . . . . . . . . . . . . . . . . . 29 124 5.15 DAV:like . . . . . . . . . . . . . . . . . . . . . . . . 30 125 5.15.1 Syntax for the Literal Pattern . . . . . . . . . . . 30 126 5.15.2 Example of DAV:like . . . . . . . . . . . . . . . . 30 127 5.16 DAV:contains . . . . . . . . . . . . . . . . . . . . . . 31 128 5.16.1 Result scoring (DAV:score element) . . . . . . . . . 31 129 5.16.2 Ordering by score . . . . . . . . . . . . . . . . . 32 130 5.16.3 Examples . . . . . . . . . . . . . . . . . . . . . . 32 131 5.17 Limiting the result set . . . . . . . . . . . . . . . . 32 132 5.17.1 Relationship to result ordering . . . . . . . . . . 32 133 5.18 The 'caseless' XML attribute . . . . . . . . . . . . . . 33 134 5.19 Query schema for DAV:basicsearch . . . . . . . . . . . . 33 135 5.19.1 DTD for DAV:basicsearch QSD . . . . . . . . . . . . 33 136 5.19.2 DAV:propdesc Element . . . . . . . . . . . . . . . . 34 137 5.19.3 The DAV:datatype Property Description . . . . . . . 34 138 5.19.4 The DAV:searchable Property Description . . . . . . 35 139 5.19.5 The DAV:selectable Property Description . . . . . . 35 140 5.19.6 The DAV:sortable Property Description . . . . . . . 35 141 5.19.7 The DAV:caseless Property Description . . . . . . . 35 142 5.19.8 The DAV:operators XML Element . . . . . . . . . . . 35 143 5.19.9 Example of Query Schema for DAV:basicsearch . . . . 36 144 6. Internationalization Considerations . . . . . . . . . . . . 37 145 7. Security Considerations . . . . . . . . . . . . . . . . . . 37 146 7.1 Implications of XML External Entities . . . . . . . . . . 37 147 8. Scalability . . . . . . . . . . . . . . . . . . . . . . . . 38 148 9. Authentication . . . . . . . . . . . . . . . . . . . . . . . 38 149 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . 38 150 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 38 151 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38 152 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 38 153 13.1 Normative References . . . . . . . . . . . . . . . . . . . 38 154 13.2 Informative References . . . . . . . . . . . . . . . . . . 39 155 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 40 156 A. Three-Valued Logic in DAV:basicsearch . . . . . . . . . . . 41 157 B. Change Log (to be removed by RFC Editor before 158 publication) . . . . . . . . . . . . . . . . . . . . . . . . 42 159 B.1 From draft-davis-dasl-protocol-xxx . . . . . . . . . . . . 42 160 B.2 since start of draft-reschke-webdav-search . . . . . . . . 44 161 B.3 since draft-reschke-webdav-search-00 . . . . . . . . . . . 45 162 B.4 since draft-reschke-webdav-search-01 . . . . . . . . . . . 46 163 B.5 since draft-reschke-webdav-search-02 . . . . . . . . . . . 46 164 B.6 since draft-reschke-webdav-search-03 . . . . . . . . . . . 47 165 B.7 since draft-reschke-webdav-search-04 . . . . . . . . . . . 47 166 B.8 since draft-reschke-webdav-search-05 . . . . . . . . . . . 48 167 B.9 since draft-reschke-webdav-search-05 . . . . . . . . . . . 48 168 C. Open issues (to be removed by RFC Editor prior to 169 publication) . . . . . . . . . . . . . . . . . . . . . . . . 48 170 C.1 edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 171 C.2 1.3-apply-condition-code-terminology . . . . . . . . . . . 49 172 C.3 2.4-multiple-uris . . . . . . . . . . . . . . . . . . . . 49 173 C.4 result-truncation . . . . . . . . . . . . . . . . . . . . 49 174 C.5 qsd-optional . . . . . . . . . . . . . . . . . . . . . . . 50 175 C.6 5.1-name-filtering . . . . . . . . . . . . . . . . . . . . 50 176 C.7 5_media_type_match . . . . . . . . . . . . . . . . . . . . 51 177 C.8 5.4.2-scope-vs-redirects . . . . . . . . . . . . . . . . . 51 178 C.9 language-comparison . . . . . . . . . . . . . . . . . . . 51 179 C.10 JW16b/JW24a . . . . . . . . . . . . . . . . . . . . . . 52 180 C.11 typed-literal . . . . . . . . . . . . . . . . . . . . . 52 181 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 182 Intellectual Property and Copyright Statements . . . . . . . 55 184 1. Introduction 186 1.1 DASL 188 This document defines WebDAV SEARCH, an application of HTTP/1.1 189 forming a lightweight search protocol to transport queries and result 190 sets and allows clients to make use of server-side search facilities. 191 It is based on the expired draft for WebDAV DASL [DASL]. [DASLREQ] 192 describes the motivation for DASL. 194 DASL will minimize the complexity of clients so as to facilitate 195 widespread deployment of applications capable of utilizing the DASL 196 search mechanisms. 198 DASL consists of: 200 o the SEARCH method, 202 o the DASL response header, 204 o the DAV:searchrequest XML element, 206 o the DAV:query-schema-discovery XML element, 208 o the DAV:basicsearch XML element and query grammar, and 210 o the DAV:basicsearchschema XML element. 212 For WebDAV-compliant servers, it also defines a new live property 213 DAV:supported-query-grammar-set. 215 1.2 Relationship to DAV 217 DASL relies on the resource and property model defined by [RFC2518]. 218 DASL does not alter this model. Instead, DASL allows clients to 219 access DAV-modeled resources through server-side search. 221 1.3 Terms 223 This document uses the terms defined in [RFC2616], in [RFC2518], in 224 [RFC3253] and in this section. 226 Criteria 228 An expression against which each resource in the search scope is 229 evaluated. 231 Query 232 A query is a combination of a search scope, search criteria, 233 result record definition, sort specification, and a search 234 modifier. 236 Query Grammar 238 A set of definitions of XML elements, attributes, and constraints 239 on their relations and values that defines a set of queries and 240 the intended semantics. 242 Query Schema 244 A listing, for any given grammar and scope, of the properties and 245 operators that may be used in a query with that grammar and scope. 247 Result 249 A result is a result set, optionally augmented with other 250 information describing the search as a whole. 252 Result Record 254 A description of a resource. A result record is a set of 255 properties, and possibly other descriptive information. 257 Result Record Definition 259 A specification of the set of properties to be returned in the 260 result record. 262 Result Set 264 A set of records, one for each resource for which the search 265 criteria evaluated to True. 267 Scope 269 A set of resources to be searched. 271 Search Modifier 273 An instruction that governs the execution of the query but is not 274 part of the search scope, result record definition, the search 275 criteria, or the sort specification. An example of a search 276 modifier is one that controls how much time the server can spend 277 on the query before giving a response. 279 Sort Specification 280 A specification of an ordering on the result records in the result 281 set. 283 1.4 Notational Conventions 285 The augmented BNF used by this document to describe protocol elements 286 is exactly the same as the one described in Section 2.1 of [RFC2616]. 287 Because this augmented BNF uses the basic production rules provided 288 in Section 2.2 of [RFC2616], those rules apply to this document as 289 well. 291 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT" 292 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 293 document are to be interpreted as described in [RFC2119]. 295 This document uses XML DTD fragments as a purely notational 296 convention. WebDAV request and response bodies can not be validated 297 due to the specific extensibility rules defined in section 23 of 298 [RFC2518] and due to the fact that all XML elements defined by this 299 specification use the XML namespace name "DAV:". In particular: 301 1. element names use the "DAV:" namespace, 303 2. element ordering is irrelevant unless explicitly stated, 305 3. extension elements (elements not already defined as valid child 306 elements) may be added anywhere, except when explicitly stated 307 otherwise, 309 4. extension attributes (attributes not already defined as valid for 310 this element) may be added anywhere, except when explicitly 311 stated otherwise. 313 When an XML element type in the "DAV:" namespace is referenced in 314 this document outside of the context of an XML fragment, the string 315 "DAV:" will be prefixed to the element type. 317 Similarily, when an XML element type in the namespace 318 "http://www.w3.org/2001/XMLSchema" is referenced in this document 319 outside of the context of an XML fragment, the string "xs:" will be 320 prefixed to the element type. 322 1.5 Editorial note on usage of 'DAV:' namespace 324 *Note that this draft currently defines elements and properties in 325 the WebDAV namespace "DAV:" which it shouldn't do as it isn't a work 326 item of the WebDAV working group. The reason for this is the desire 327 for some kind of backward compatibility to the expired DASL drafts 328 and the assumption that the draft may become an official RFC 329 submission of the WebDAV working group at a later point of time.* 331 1.6 An Overview of DASL at Work 333 One can express the basic usage of DASL in the following steps: 335 o The client constructs a query using the DAV:basicsearch grammar. 337 o The client invokes the SEARCH method on a resource that will 338 perform the search (the search arbiter) and includes a text/xml or 339 application/xml request entity that contains the query. 341 o The search arbiter performs the query. 343 o The search arbiter sends the results of the query back to the 344 client in the response. The server MUST send an entity that 345 matches the [RFC2518] PROPFIND response. 347 2. The SEARCH Method 349 2.1 Overview 351 The client invokes the SEARCH method to initiate a server-side 352 search. The body of the request defines the query. The server MUST 353 emit an entity matching the [RFC2518] PROPFIND response. 355 The SEARCH method plays the role of transport mechanism for the query 356 and the result set. It does not define the semantics of the query. 357 The type of the query defines the semantics. 359 2.2 The Request 361 The client invokes the SEARCH method on the resource named by the 362 Request-URI. 364 2.2.1 The Request-URI 366 The Request-URI identifies the search arbiter. Any HTTP resource may 367 function as search arbiter. It is not a new type of resource (in the 368 sense of DAV:resourcetype as defined in [RFC2518]), nor does it have 369 to be a WebDAV-compliant resource. 371 The SEARCH method defines no relationship between the arbiter and the 372 scope of the search, rather the particular query grammar used in the 373 query defines the relationship. For example, a query grammar may 374 force the request-URI to correspond exactly to the search scope. 376 2.2.2 The Request Body 378 The server MUST process a text/xml or application/xml request body, 379 and MAY process request bodies in other formats. See [RFC3023] for 380 guidance on packaging XML in requests. 382 Marshalling: 384 If a request body with content type text/xml or application/xml is 385 included, it MUST be either a DAV:searchrequest or a 386 DAV:query-schema-discovery XML element. It's single child element 387 identifies the query grammar. 389 For DAV:searchrequest, the definition of search criteria, the 390 result record, and any other details needed to perform the search 391 depend on the individual search grammar. 393 For DAV:query-schema-discovery, the semantics is defined in 394 Section 4. 396 Preconditions: 398 (DAV:search-grammar-discovery-supported): when an XML request body 399 is present and has a DAV:query-schema-discovery document element, 400 the server MUST support the query schema discovery mechanism 401 described in Section 4. 403 (DAV:search-grammar-supported): when an XML request body is 404 present, the search grammar identified by the document element's 405 child element must be a supported search grammar. 407 (DAV:search-multiple-scope-supported): if the SEARCH request 408 specified multiple scopes, the server MUST support this optional 409 feature. 411 (DAV:search-scope-valid): the supplied search scope must be valid. 412 There can be various reasons for a search scope to be invalid, 413 including unsupported URI schemes and communication problems. 414 Servers MAY add [RFC2518] compliant DAV:response elements as 415 content to the condition element indicating the precise reason for 416 the failure. 418 2.3 The Successful 207 (Multistatus) Response 420 If the server returns 207 (Multistatus), then the search proceeded 421 successfully and the response MUST match that of a PROPFIND. The 422 results of this method SHOULD NOT be cached. 424 There MUST be one DAV:response for each resource that matched the 425 search criteria. For each such response, the DAV:href element 426 contains the URI of the resource, and the response MUST include a 427 DAV:propstat element. 429 Note that for each matching resource found there may be multiple URIs 430 within the search scope mapped to it. In this case, a server SHOULD 431 report all of these URIs. Clients can use the live property 432 DAV:resource-id defined in [BIND] to identify possible duplicates. 434 2.3.1 Extending the PROPFIND Response 436 A response MAY include more information than PROPFIND defines so long 437 as the extra information does not invalidate the PROPFIND response. 438 Query grammars SHOULD define how the response matches the PROPFIND 439 response. 441 2.3.2 Example: A Simple Request and Response 443 This example demonstrates the request and response framework. The 444 following XML document shows a simple (hypothetical) natural language 445 query. The name of the query element is natural-language-query in 446 the XML namespace "http://example.com/foo". The actual query is 447 "Find the locations of good Thai restaurants in Los Angeles". For 448 this hypothetical query, the arbiter returns two properties for each 449 selected resource. 451 >> Request: 453 SEARCH / HTTP/1.1 454 Host: example.org 455 Content-Type: application/xml 456 Content-Length: xxx 458 459 460 461 Find the locations of good Thai restaurants in Los Angeles 462 463 464 >> Response: 466 HTTP/1.1 207 Multi-Status 467 Content-Type: text/xml; charset="utf-8" 468 Content-Length: xxx 470 471 473 474 http://siamiam.test/ 475 476 477 259 W. Hollywood 478 4 479 480 HTTP/1.1 200 OK 481 482 483 485 2.3.3 Example: Result Set Truncation 487 A server MAY limit the number of resources in a reply, for example to 488 limit the amount of resources expended in processing a query. If it 489 does so, the reply MUST use status code 207, return a DAV:multistatus 490 response body and indicate a status of 507 (Insufficient Storage) for 491 the search arbiter URI. It SHOULD include the partial results. 493 When a result set is truncated, there may be many more resources that 494 satisfy the search criteria but that were not examined. 496 If partial results are included and the client requested an ordered 497 result set in the original request, then any partial results that are 498 returned MUST be ordered as the client directed. 500 Note that the partial results returned MAY be any subset of the 501 result set that would have satisfied the original query. 503 >> Request: 505 SEARCH / HTTP/1.1 506 Host: example.net 507 Content-Type: text/xml; charset="utf-8" 508 Content-Length: xxx 510 ... the query goes here ... 512 >> Response: 514 HTTP/1.1 207 Multistatus 515 Content-Type: text/xml; charset="utf-8" 516 Content-Length: xxx 518 519 520 521 http://www.example.net/sounds/unbrokenchain.au 522 523 524 HTTP/1.1 200 OK 525 526 527 528 http://tech.mit.test/archive96/photos/Lesh1.jpg 529 530 531 HTTP/1.1 200 OK 532 533 534 535 http://example.net 536 HTTP/1.1 507 Insufficient Storage 537 538 Only first two matching records were returned 539 540 541 543 2.4 Unsuccessful Responses 545 If a SEARCH request could not be executed or the attempt to execute 546 it resulted in an error, the server MUST indicate the failure with an 547 appropriate status code and SHOULD add a response body as defined in 548 [RFC3253], section 1.6. Unless otherwise stated, condition elements 549 are empty, however specific conditions element MAY include additional 550 child elements that describe the error condition in more detail. 552 2.4.1 Example of an Invalid Scope 554 In the example below, a request failed because the scope identifies a 555 HTTP resource that was not found. 557 >> Response: 559 HTTP/1.1 409 Conflict 560 Content-Type: text/xml; charset="utf-8" 561 Content-Length: xxx 563 564 565 566 567 http://www.example.com/X 568 HTTP/1.1 404 Object Not Found 569 570 571 573 3. Discovery of Supported Query Grammars 575 Servers MUST support discovery of the query grammars supported by a 576 search arbiter resource. 578 Clients can determine which query grammars are supported by an 579 arbiter by invoking OPTIONS on the search arbiter. If the resource 580 supports SEARCH, then the DASL response header will appear in the 581 response. The DASL response header lists the supported grammars. 583 Servers supporting the WebDAV extensions [RFC3253] and/or [RFC3744] 584 MUST also 586 o report SEARCH in the live property DAV:supported-method-set for 587 all search arbiter resources and 589 o support the live property DAV:supported-query-grammar-set as 590 defined in Section 3.3. 592 3.1 The OPTIONS Method 594 The OPTIONS method allows the client to discover if a resource 595 supports the SEARCH method and to determine the list of search 596 grammars supported for that resource. 598 The client issues the OPTIONS method against a resource named by the 599 Request-URI. This is a normal invocation of OPTIONS defined in 600 [RFC2616]. 602 If a resource supports the SEARCH method, then the server MUST list 603 SEARCH in the OPTIONS response as defined by [RFC2616]. 605 DASL servers MUST include the DASL header in the OPTIONS response. 606 This header identifies the search grammars supported by that 607 resource. 609 3.2 The DASL Response Header 611 DASLHeader = "DASL" ":" Coded-URL-List 612 Coded-URL-List : Coded-URL [ "," Coded-URL-List ] 613 Coded-URL ; defined in section 9.4 of [RFC2518] 615 The DASL response header indicates server support for a query grammar 616 in the OPTIONS method. The value is a URI that indicates the type of 617 grammar. Note that although the URI can be used to identify each 618 supported search grammar, there is not necessarily a direct 619 relationship between the URI and the XML element name that can be 620 used in XML based SEARCH requests (the element name itself is 621 identified by it's namespace name (a URI reference) and the element's 622 local name). 624 This header MAY be repeated. 626 For example: 628 DASL: 629 DASL: 630 DASL: 631 DASL: 633 3.3 DAV:supported-query-grammar-set (protected) 635 This WebDAV property is required for any server supporting either 636 [RFC3253] and/or [RFC3744] and identifies the XML based query 637 grammars that are supported by the search arbiter resource. 639 640 641 643 ANY value: a query grammar element type 645 3.4 Example: Grammar Discovery 647 This example shows that the server supports search on the /somefolder 648 resource with the query grammars: DAV:basicsearch, 649 http://foobar.test/syntax1 and http://akuma.test/syntax2. Note that 650 every server MUST support DAV:basicsearch. 652 >> Request: 654 OPTIONS /somefolder HTTP/1.1 655 Host: example.org 657 >> Response: 659 HTTP/1.1 200 OK 660 Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE 661 Allow: MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, SEARCH 662 DASL: 663 DASL: 664 DASL: 666 This example shows the equivalent taking advantage of a server's 667 support for DAV:supported-method-set and 668 DAV:supported-query-grammar-set. 670 >> Request: 672 PROPFIND /somefolder HTTP/1.1 673 Host: example.org 674 Depth: 0 675 Content-Type: text/xml; charset="utf-8" 676 Content-Length: xxx 678 679 680 681 682 683 684 686 >> Response: 688 HTTP/1.1 207 Multi-Status 689 Content-Type: text/xml; charset="utf-8" 690 Content-Length: xxx 692 693 694 695 http://example.org/somefolder 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 HTTP/1.1 200 OK 728 729 730 732 Note that the query grammar element names marshalled as part of the 733 DAV:supported-query-grammar-set can be directly used as element names 734 in an XML based query. 736 4. Query Schema Discovery: QSD 738 Servers MAY support the discovery of the schema for a query grammar. 740 The DASL response header and the DAV:supported-query-grammar-set 741 property provide means for clients to discover the set of query 742 grammars supported by a resource. This alone is not sufficient 743 information for a client to generate a query. For example, the 744 DAV:basicsearch grammar defines a set of queries consisting of a set 745 of operators applied to a set of properties and values, but the 746 grammar itself does not specify which properties may be used in the 747 query. QSD for the DAV:basicsearch grammar allows a client to 748 discover the set of properties that are searchable, selectable, and 749 sortable. Moreover, although the DAV:basicsearch grammar defines a 750 minimal set of operators, it is possible that a resource might 751 support additional operators in a query. For example, a resource 752 might support a optional operator that can be used to express 753 content-based queries in a proprietary syntax. QSD allows a client 754 to discover these operators and their syntax. The set of 755 discoverable quantities will differ from grammar to grammar, but each 756 grammar can define a means for a client to discover what can be 757 discovered. 759 In general, the schema for a given query grammar depends on both the 760 resource (the arbiter) and the scope. A given resource might have 761 access to one set of properties for one potential scope, and another 762 set for a different scope. For example, consider a server able to 763 search two distinct collections, one holding cooking recipes, the 764 other design documents for nuclear weapons. While both collections 765 might support properties such as author, title, and date, the first 766 might also define properties such as calories and preparation time, 767 while the second defined properties such as yield and applicable 768 patents. Two distinct arbiters indexing the same collection might 769 also have access to different properties. For example, the recipe 770 collection mentioned above might also indexed by a value-added server 771 that also stored the names of chefs who had tested the recipe. Note 772 also that the available query schema might also depend on other 773 factors, such as the identity of the principal conducting the search, 774 but these factors are not exposed in this protocol. 776 4.1 Additional SEARCH semantics 778 Each query grammar supported by DASL defines its own syntax for 779 expressing the possible query schema. A client retrieves the schema 780 for a given query grammar on an arbiter resource with a given scope 781 by invoking the SEARCH method on that arbiter with that grammar and 782 scope and with a root element of DAV:query-schema-discovery rather 783 than DAV:searchrequest. 785 Marshalling: 787 The request body MUST be DAV:query-schema-discovery element. 789 790 ANY value: XML element defining a valid query 792 The response body takes the form of a RFC2518 DAV:multistatus 793 element, where DAV:response is extended to hold the returned query 794 grammar inside a DAV:query-schema container element. 796 798 800 The content of this container is an XML element whose name and syntax 801 depend upon the grammar, and whose value may (and likely will) vary 802 depending upon the grammar, arbiter, and scope. 804 4.1.1 Example of query schema discovery 806 In this example, the arbiter is recipes.test, the grammar is 807 DAV:basicsearch, the scope is also recipes.test. 809 >> Request: 811 SEARCH / HTTP/1.1 812 Host: recipes.test 813 Content-Type: application/xml 814 Content-Length: xxx 816 817 818 819 820 821 http://recipes.test 822 infinity 823 824 825 826 827 >> Response: 829 HTTP/1.1 207 Multistatus 830 Content-Type: application/xml 831 Content-Length: xxx 833 834 835 836 http://recipes.test 837 HTTP/1.1 200 OK 838 839 840 842 843 844 845 847 The query schema for DAV:basicsearch is defined in Section 5.19. 849 5. The DAV:basicsearch Grammar 851 5.1 Introduction 853 DAV:basicsearch uses an extensible XML syntax that allows clients to 854 express search requests that are generally useful for WebDAV 855 scenarios. DASL-extended servers MUST accept this grammar, and MAY 856 accept other grammars. 858 DAV:basicsearch has several components: 860 o DAV:select provides the result record definition. 862 o DAV:from defines the scope. 864 o DAV:where defines the criteria. 866 o DAV:orderby defines the sort order of the result set. 868 o DAV:limit provides constraints on the query as a whole. 870 5.2 The DAV:basicsearch DTD 872 874 876 878 880 882 883 884 886 888 889 890 892 893 895 898 900 902 904 906 907 909 910 912 913 915 916 917 918 920 921 922 924 925 927 928 930 931 933 935 937 938 940 941 943 945 946 948 5.2.1 Example Query 950 This query retrieves the content length values for all resources 951 located under the server's "/container1/" URI namespace whose length 952 exceeds 10000. 954 955 956 957 958 959 960 961 /container1/ 962 infinity 963 964 965 966 967 968 10000 969 970 971 972 973 974 975 976 977 978 980 5.3 DAV:select 982 DAV:select defines the result record, which is a set of properties 983 and values. This document defines two possible values: DAV:allprop 984 and DAV:prop, both defined in [RFC2518] and revised in [RFC3253]. 986 5.4 DAV:from 988 989 991 DAV:from defines the query scope. This contains one or more 992 DAV:scope elements. Support for multiple scope elements is optional, 993 however servers MUST fail a request specifying multiple DAV:scope 994 elements if they can't support it (see Section 2.2.2, precondition 995 DAV:search-multiple-scope-supported). The scope element contains 996 mandatory DAV:href and DAV:depth elements. 998 DAV:href indicates the URI to use as a scope. 1000 When the scope is a collection, if DAV:depth is "0", the search 1001 includes only the collection. When it is "1", the search includes 1002 the (toplevel) members of the collection. When it is "infinity", the 1003 search includes all recursive members of the collection. 1005 When the scope is not a collection, the depth is ignored and the 1006 search applies just to the resource itself. 1008 When the child element DAV:include-versions is present, the search 1009 scope will include all versions (see [RFC3253], section 2.2.1) of all 1010 version-controlled resources in scope. Servers that do support 1011 versioning but do not support the DAV:include-versions feature MUST 1012 signal an error if it is used in a query. 1014 5.4.1 Relationship to the Request-URI 1016 If the DAV:scope element is an absolute URI, the scope is exactly 1017 that URI. 1019 If the DAV:scope element is is an absolute URI reference, the scope 1020 is taken to be relative to the request-URI. 1022 5.4.2 Scope 1024 A Scope can be an arbitrary URI. 1026 Servers, of course, may support only particular scopes. This may 1027 include limitations for particular schemes such as "http:" or "ftp:" 1028 or certain URI namespaces. 1030 5.5 DAV:where 1032 The DAV:where element defines the search condition for inclusion of 1033 resources in the result set. The value of this element is an XML 1034 element that defines a search operator that evaluates to one of the 1035 Boolean truth values TRUE, FALSE, or UNKNOWN. The search operator 1036 contained by DAV:where may itself contain and evaluate additional 1037 search operators as operands, which in turn may contain and evaluate 1038 additional search operators as operands, etc. recursively. 1040 5.5.1 Use of Three-Valued Logic in Queries 1042 Each operator defined for use in the where clause that returns a 1043 Boolean value MUST evaluate to TRUE, FALSE, or UNKNOWN. The resource 1044 under scan is included as a member of the result set if and only if 1045 the search condition evaluates to TRUE. 1047 Consult Appendix A for details on the application of three-valued 1048 logic in query expressions. 1050 5.5.2 Handling Optional operators 1052 If a query contains an operator that is not supported by the server, 1053 then the server MUST respond with a 422 (Unprocessable Entity) status 1054 code. 1056 5.5.3 Treatment of NULL Values 1058 If a PROPFIND for a property value would yield a non-2xx (see 1059 [RFC2616], section 10.2) response for that property, then that 1060 property is considered NULL. 1062 NULL values are "less than" all other values in comparisons. 1064 Empty strings (zero length strings) are not NULL values. An empty 1065 string is "less than" a string with length greater than zero. 1067 The DAV:is-defined operator is defined to test if the value of a 1068 property is NULL. 1070 5.5.4 Treatment of properties with mixed/element content 1072 Comparisons of properties that do not have simple types (text-only 1073 content) is out-of-scope for the standard operators defined for 1074 DAV:basicsearch and therefore is defined to be UNKNOWN (as per 1075 Appendix A). For querying the DAV:resourcetype property, see Section 1076 5.13. 1078 5.5.5 Example: Testing for Equality 1080 The example shows a single operator (DAV:eq) applied in the criteria. 1082 1083 1084 1085 1086 1087 100 1088 1089 1091 5.5.6 Example: Relative Comparisons 1093 The example shows a more complex operation involving several 1094 operators (DAV:and, DAV:eq, DAV:gt) applied in the criteria. This 1095 DAV:where expression matches those resources that are "image/gifs" 1096 over 4K in size. 1098 1099 1100 1101 1102 1103 1104 image/gif 1105 1106 1107 1108 1109 1110 4096 1111 1112 1113 1115 5.6 DAV:orderby 1117 The DAV:orderby element specifies the ordering of the result set. It 1118 contains one or more DAV:order elements, each of which specifies a 1119 comparison between two items in the result set. Informally, a 1120 comparison specifies a test that determines whether one resource 1121 appears before another in the result set. Comparisons are applied in 1122 the order they occur in the DAV:orderby element, earlier comparisons 1123 being more significant. 1125 The comparisons defined here use only a single property from each 1126 resource, compared using the same ordering as the DAV:lt operator 1127 (ascending) or DAV:gt operator (descending). If neither direction is 1128 specified, the default is DAV:ascending. 1130 In the context of the DAV:orderby element, null values are considered 1131 to collate before any actual (i.e., non null) value, including 1132 strings of zero length (this is compatible with [SQL99]). 1134 5.6.1 Comparing Natural Language Strings 1136 Comparisons on strings take into account the language defined for 1137 that property. Clients MAY specify the language using the xml:lang 1138 attribute. If no language is specified either by the client or 1139 defined for that property by the server or if a comparison is 1140 performed on strings of two different languages, the results are 1141 undefined. 1143 The "caseless" attribute may be used to indicate case-sensitivity for 1144 comparisons. 1146 5.6.2 Example of Sorting 1148 This sort orders first by last name of the author, and then by size, 1149 in descending order, so that for each author, the largest works 1150 appear first. 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1163 5.7 Boolean Operators: DAV:and, DAV:or, and DAV:not 1165 The DAV:and operator performs a logical AND operation on the 1166 expressions it contains. 1168 The DAV:or operator performs a logical OR operation on the values it 1169 contains. 1171 The DAV:not operator performs a logical NOT operation on the values 1172 it contains. 1174 5.8 DAV:eq 1176 The DAV:eq operator provides simple equality matching on property 1177 values. 1179 The "caseless" attribute may be used with this element. 1181 5.9 DAV:lt, DAV:lte, DAV:gt, DAV:gte 1183 The DAV:lt, DAV:lte, DAV:gt, and DAV:gte operators provide 1184 comparisons on property values, using less-than, less-than or equal, 1185 greater-than, and greater-than or equal respectively. The "caseless" 1186 attribute may be used with these elements. 1188 5.10 DAV:literal 1190 DAV:literal allows literal values to be placed in an expression. 1192 White space in literal values is significant in comparisons. For 1193 consistency with [RFC2518], clients SHOULD NOT specify the attribute 1194 "xml:space" (section 2.10 of [XML]) to override this behaviour. 1196 In comparisons, the contents of DAV:literal SHOULD be treated as 1197 string, with the following exceptions: 1199 o when operand for a comparison with a DAV:getcontentlength 1200 property, it SHOULD be treated as an integer value (the behaviour 1201 for non-integer values is undefined), 1203 o when operand for a comparison with a DAV:creationdate or 1204 DAV:getlastmodified property, it SHOULD be treated as a date value 1205 in the ISO-8601 subset defined for the DAV:creationdate property 1206 ([RFC2518], section 13.1). 1208 o when operand for a comparison with a property for which the type 1209 is known, it MAY be treated according to this type. 1211 5.11 DAV:typed-literal (optional) 1213 There are situations in which a client may want to force a comparison 1214 not to be string-based (as defined for DAV:literal). In these cases, 1215 a typed comparison can be enforced by using DAV:typed-literal 1216 instead. 1218 1220 The data type is specified using the xsi:type attribute defined in 1221 [XS1], section 2.6.1. If the type is not specified, it defaults to 1222 "xs:string". 1224 A server MUST reject a request with an unknown type. 1226 5.11.1 Example for typed numerical comparison 1228 Consider a set of resources with the dead property "edits" in the 1229 namespace "http://ns.example.org": 1231 +-----+----------------+ 1232 | URI | property value | 1233 +-----+----------------+ 1234 | /a | "-1" | 1235 | /b | "01" | 1236 | /c | "3" | 1237 | /d | "test" | 1238 | /e | (undefined) | 1239 +-----+----------------+ 1241 The expression 1243 1246 1247 3 1248 1250 will evaluate to TRUE for the resources "/a" and "/b" (their property 1251 values can be parsed as type xs:number, and the numerical comparison 1252 evaluates to true), to FALSE for "/c" (property value is compatible, 1253 but numerical comparison evaluates to false) and UNKNOWN for "/d" and 1254 "/e" (the property either is undefined, or its value can not be 1255 parsed as xs:number). 1257 5.12 Support for matching xml:lang attributes on properties 1259 The following two optional operators can be used to express 1260 conditions on the language of a property value (as expressed using 1261 the xml:lang attribute). 1263 5.12.1 DAV:language-defined (optional) 1265 1267 This operator evaluates to TRUE if the language for the value of the 1268 given property is known, FALSE if it isn't and UNKNOWN if the 1269 property itself is not defined. 1271 5.12.2 DAV:language-matches (optional) 1273 1275 This operator evaluates to TRUE if the language for the value of the 1276 given property is known and matches the language name given in the 1277 element, FALSE if it doesn't match and UNKNOWN if the 1278 property itself is not defined. 1280 Languages are considered to match if they are the same, or if the 1281 language of the property value is a sublanguage of the language 1282 specified in the element (see [XPATH], section 4.3, "lang 1283 function"). 1285 5.12.3 Example of language-aware matching 1287 The expression below will evaluate to TRUE if the property "foobar" 1288 exists and it's language is either unknown, English or a sublanguage 1289 of English. 1291 1292 1293 1294 1295 1296 1297 1298 1299 en 1300 1301 1303 5.13 DAV:is-collection 1305 The DAV:is-collection operator allows clients to determine whether a 1306 resource is a collection (that is, whether it's DAV:resourcetype 1307 element contains the element DAV:collection). 1309 Rationale: This operator is provided in lieu of defining generic 1310 structure queries, which would suffice for this and for many more 1311 powerful queries, but seems inappropriate to standardize at this 1312 time. 1314 5.13.1 Example of DAV:is-collection 1316 This example shows a search criterion that picks out all and only the 1317 resources in the scope that are collections. 1319 1320 1321 1323 5.14 DAV:is-defined 1325 The DAV:is-defined operator allows clients to determine whether a 1326 property is defined on a resource. The meaning of "defined on a 1327 resource" is found in Section 5.5.3. 1329 Example: 1331 1332 1333 1335 5.15 DAV:like 1337 The DAV:like is an optional operator intended to give simple 1338 wildcard-based pattern matching ability to clients. 1340 The operator takes two arguments. 1342 The first argument is a DAV:prop element identifying a single 1343 property to evaluate. 1345 The second argument is a DAV:literal element that gives the pattern 1346 matching string. 1348 5.15.1 Syntax for the Literal Pattern 1350 Pattern := [wildcard] 0*( text [wildcard] ) 1351 wildcard := exactlyone | zeroormore 1352 text := 1*( | escapesequence ) 1353 exactlyone : = "_" 1354 zeroormore := "%" 1355 escapechar := "\" 1356 escapesequence := "\" ( exactlyone | zeroormore | escapechar ) 1357 character: valid XML characters (see section 2.2 of [XML]), 1358 minus ( exactlyone | zeroormore | escapechar ) 1360 The value for the literal is composed of wildcards separated by 1361 segments of text. Wildcards may begin or end the literal. 1363 The "_" wildcard matches exactly one character. 1365 The "%" wildcard matches zero or more characters 1367 The "\" character is an escape sequence so that the literal can 1368 include "_" and "%". To include the "\" character in the pattern, 1369 the escape sequence "\\" is used. 1371 5.15.2 Example of DAV:like 1373 This example shows how a client might use DAV:like to identify those 1374 resources whose content type was a subtype of image. 1376 1377 1378 1379 image/% 1380 1381 1383 5.16 DAV:contains 1385 The DAV:contains operator is an optional operator that provides 1386 content-based search capability. This operator implicitly searches 1387 against the text content of a resource, not against content of 1388 properties. The DAV:contains operator is intentionally not overly 1389 constrained, in order to allow the server to do the best job it can 1390 in performing the search. 1392 The DAV:contains operator evaluates to a Boolean value. It evaluates 1393 to TRUE if the content of the resource satisfies the search. 1394 Otherwise, It evaluates to FALSE. 1396 Within the DAV:contains XML element, the client provides a phrase: a 1397 single word or whitespace delimited sequence of words. Servers MAY 1398 ignore punctuation in a phrase. Case-sensitivity is left to the 1399 server. 1401 The following things may or may not be done as part of the search: 1402 Phonetic methods such as "soundex" may or may not be used. Word 1403 stemming may or may not be performed. Thesaurus expansion of words 1404 may or may not be done. Right or left truncation may or may not be 1405 performed. The search may be case insensitive or case sensitive. 1406 The word or words may or may not be interpreted as names. Multiple 1407 words may or may not be required to be adjacent or "near" each other. 1408 Multiple words may or may not be required to occur in the same order. 1409 Multiple words may or may not be treated as a phrase. The search may 1410 or may not be interpreted as a request to find documents "similar" to 1411 the string operand. 1413 5.16.1 Result scoring (DAV:score element) 1415 Servers SHOULD indicate scores for the DAV:contains condition by 1416 adding a DAV:score XML element to the DAV:response element. It's 1417 value is defined only in the context of a particular query result. 1418 The value is a string representing the score, an integer from zero to 1419 10000 inclusive, where a higher value indicates a higher score (e.g. 1420 more relevant). 1422 Modified DTD fragment for DAV:propstat: 1424 1426 1428 Clients should note that, in general, it is not meaningful to compare 1429 the numeric values of scores from two different query results unless 1430 both were executed by the same underlying search system on the same 1431 collection of resources. 1433 5.16.2 Ordering by score 1435 To order search results by their score, the DAV:score element may be 1436 added as child to the DAV:orderby element (in place of a DAV:prop 1437 element). 1439 5.16.3 Examples 1441 The example below shows a search for the phrase "Peter Forsberg". 1443 Depending on its support for content-based searching, a server MAY 1444 treat this as a search for documents that contain the words "Peter" 1445 and "Forsberg". 1447 1448 Peter Forsberg 1449 1451 The example below shows a search for resources that contain "Peter" 1452 and "Forsberg". 1454 1455 1456 Peter 1457 Forsberg 1458 1459 1461 5.17 Limiting the result set 1463 1464 ;only digits 1466 The DAV:limit XML element contains requested limits from the client 1467 to limit the size of the reply or amount of effort expended by the 1468 server. The DAV:nresults XML element contains a requested maximum 1469 number of DAV:response elements to be returned in the response body. 1470 The server MAY disregard this limit. The value of this element is an 1471 integer. 1473 5.17.1 Relationship to result ordering 1475 If the result set is both limited by DAV:limit and ordered according 1476 to DAV:orderby, the results that are included in the response 1477 document must be those that order highest. 1479 5.18 The 'caseless' XML attribute 1481 The "caseless" attribute allows clients to specify caseless matching 1482 behaviour instead of character-by-character matching for 1483 DAV:basicsearch operators. 1485 The possible values for "caseless" are "yes" or "no". The default 1486 value is server-specified. Caseless matching SHOULD be implemented 1487 as defined in section 5.18 of the Unicode Standard ([UNICODE4]). 1489 Support for the "caseless" attribute is optional. A server should 1490 respond with a status of 422 if it is used but cannot be supported. 1492 5.19 Query schema for DAV:basicsearch 1494 The DAV:basicsearch grammar defines a search criteria that is a 1495 Boolean-valued expression, and allows for an arbitrary set of 1496 properties to be included in the result record. The result set may 1497 be sorted on a set of property values. Accordingly the DTD for 1498 schema discovery for this grammar allows the server to express: 1500 1. the set of properties that may be either searched, returned, or 1501 used to sort, and a hint about the data type of such properties 1503 2. the set of optional operators defined by the resource. 1505 5.19.1 DTD for DAV:basicsearch QSD 1507 1508 1509 1510 1513 1514 1515 1516 1518 The DAV:properties element holds a list of descriptions of 1519 properties. 1521 The DAV:operators element describes the optional operators that may 1522 be used in a DAV:where element. 1524 5.19.2 DAV:propdesc Element 1526 Each instance of a DAV:propdesc element describes the property or 1527 properties in the DAV:prop element it contains. All subsequent 1528 elements are descriptions that apply to those properties. All 1529 descriptions are optional and may appear in any order. Servers 1530 SHOULD support all the descriptions defined here, and MAY define 1531 others. 1533 DASL defines five descriptions. The first, DAV:datatype, provides a 1534 hint about the type of the property value, and may be useful to a 1535 user interface prompting for a value. The remaining four 1536 (DAV:searchable, DAV:selectable, DAV:sortable, and DAV:caseless) 1537 identify portions of the query (DAV:where, DAV:select, and 1538 DAV:orderby, respectively). If a property has a description for a 1539 section, then the server MUST allow the property to be used in that 1540 section. These descriptions are optional. If a property does not 1541 have such a description, or is not described at all, then the server 1542 MAY still allow the property to be used in the corresponding section. 1544 5.19.2.1 DAV:any-other-property 1546 This element can be used in place of DAV:prop to describe properties 1547 of WebDAV properties not mentioned in any other DAV:prop element. 1548 For instance, this can be used to indicate that all other properties 1549 are searchable and selectable without giving details about their 1550 types (a typical scenario for dead properties). 1552 5.19.3 The DAV:datatype Property Description 1554 The DAV:datatype element contains a single XML element that provides 1555 a hint about the domain of the property, which may be useful to a 1556 user interface prompting for a value to be used in a query. 1557 Datatypes are identified by an element name. Where appropriate, a 1558 server SHOULD use the simple datatypes defined in [XS2]. 1560 1562 Examples from [XS2], section 3: 1564 +----------------+---------------------+ 1565 | Qualified name | Example | 1566 +----------------+---------------------+ 1567 | xs:boolean | true, false, 1, 0 | 1568 | xs:string | Foobar | 1569 | xs:dateTime | 1994-11-05T08:15:5Z | 1570 | xs:float | .314159265358979E+1 | 1571 | xs:integer | -259, 23 | 1572 +----------------+---------------------+ 1574 If the data type of a property is not given, then the data type 1575 defaults to xs:string. 1577 5.19.4 The DAV:searchable Property Description 1579 1581 If this element is present, then the server MUST allow this property 1582 to appear within a DAV:where element where an operator allows a 1583 property. Allowing a search does not mean that the property is 1584 guaranteed to be defined on every resource in the scope, it only 1585 indicates the server's willingness to check. 1587 5.19.5 The DAV:selectable Property Description 1589 1591 This element indicates that the property may appear in the DAV:select 1592 element. 1594 5.19.6 The DAV:sortable Property Description 1596 This element indicates that the property may appear in the 1597 DAV:orderby element. 1599 1601 5.19.7 The DAV:caseless Property Description 1603 This element only applies to properties whose data type is 1604 "xs:string" and derived data types as per the DAV:datatype property 1605 description. Its presence indicates that compares performed for 1606 searches, and the comparisons for ordering results on the string 1607 property will be caseless (the default is character-by-character). 1609 1611 5.19.8 The DAV:operators XML Element 1613 The DAV:operators element describes every optional operator supported 1614 in a query. (Mandatory operators are not listed since they are 1615 mandatory and permit no variation in syntax.). All optional 1616 operators that are supported MUST be listed in the DAV:operators 1617 element. The listing for an operator consists of the operator (as an 1618 empty element), followed by one element for each operand. The 1619 operand MUST be either DAV:operand-property or DAV:operand-literal, 1620 which indicate that the operand in the corresponding position is a 1621 property or a literal value, respectively. If an operator is 1622 polymorphic (allows more than one operand syntax) then each permitted 1623 syntax MUST be listed separately. 1625 1626 1627 1628 1629 1631 5.19.9 Example of Query Schema for DAV:basicsearch 1633 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1661 This response lists four properties. The datatype of the last three 1662 properties is not given, so it defaults to xs:string. All are 1663 selectable, and the first three may be searched. All but the last 1664 may be used in a sort. Of the optional DAV operators, DAV:is-defined 1665 and DAV:like are supported. 1667 Note: The schema discovery defined here does not provide for 1668 discovery of supported values of the "caseless" attribute. This may 1669 require that the reply also list the mandatory operators. 1671 6. Internationalization Considerations 1673 Properties may be language-tagged using the xml:lang attribute (see 1674 [RFC2518], section 4.4). The optional operators DAV:language-defined 1675 (Section 5.12.1) and DAV:language-matches (Section 5.12.2) allow to 1676 express conditions on the language tagging information. 1678 7. Security Considerations 1680 This section is provided to detail issues concerning security 1681 implications of which DASL applications need to be aware. All of the 1682 security considerations of HTTP/1.1 also apply to DASL. In addition, 1683 this section will include security risks inherent in searching and 1684 retrieval of resource properties and content. 1686 A query must not allow one to retrieve information about values or 1687 existence of properties that one could not obtain via PROPFIND. 1688 (e.g. by use in DAV:orderby, or in expressions on properties.) 1690 A server should prepare for denial of service attacks. For example a 1691 client may issue a query for which the result set is expensive to 1692 calculate or transmit because many resources match or must be 1693 evaluated. 1695 7.1 Implications of XML External Entities 1697 XML supports a facility known as "external entities", defined in 1698 section 4.2.2 of [XML], which instruct an XML processor to retrieve 1699 and perform an inline include of XML located at a particular URI. An 1700 external XML entity can be used to append or modify the document type 1701 declaration (DTD) associated with an XML document. An external XML 1702 entity can also be used to include XML within the content of an XML 1703 document. For non-validating XML, such as the XML used in this 1704 specification, including an external XML entity is not required by 1705 [XML]. However, [XML] does state that an XML processor may, at its 1706 discretion, include the external XML entity. 1708 External XML entities have no inherent trustworthiness and are 1709 subject to all the attacks that are endemic to any HTTP GET request. 1710 Furthermore, it is possible for an external XML entity to modify the 1711 DTD, and hence affect the final form of an XML document, in the worst 1712 case significantly modifying its semantics, or exposing the XML 1713 processor to the security risks discussed in [RFC3023]. Therefore, 1714 implementers must be aware that external XML entities should be 1715 treated as untrustworthy. 1717 There is also the scalability risk that would accompany a widely 1718 deployed application which made use of external XML entities. In 1719 this situation, it is possible that there would be significant 1720 numbers of requests for one external XML entity, potentially 1721 overloading any server which fields requests for the resource 1722 containing the external XML entity. 1724 8. Scalability 1726 Query grammars are identified by URIs. Applications SHOULD not 1727 attempt to retrieve these URIs even if they appear to be retrievable 1728 (for example, those that begin with "http://") 1730 9. Authentication 1732 Authentication mechanisms defined in WebDAV will also apply to DASL. 1734 10. IANA Considerations 1736 This document uses the namespace defined by [RFC2518] for XML 1737 elements. All other IANA considerations mentioned in [RFC2518] are 1738 also applicable to DASL. 1740 11. Contributors 1742 This document is based on prior work on the DASL protocol done by the 1743 WebDAV DASL working group until the year 2000 -- namely by Alan 1744 Babich, Jim Davis, Rick Henderson, Dale Lowry, Saveen Reddy and 1745 Surendra Reddy. 1747 12. Acknowledgements 1749 This document has benefited from thoughtful discussion by Lisa 1750 Dusseault, Sung Kim, Elias Sinderson, Martin Wallmer, Jim Whitehead 1751 and Kevin Wiggen. 1753 13. References 1755 13.1 Normative References 1757 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1758 Requirement Levels", BCP 14, RFC 2119, March 1997. 1760 [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D. 1761 Jensen, "HTTP Extensions for Distributed Authoring -- 1762 WEBDAV", RFC 2518, February 1999. 1764 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., 1765 Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext 1766 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 1768 [RFC3023] Makoto, M., St.Laurent, S. and D. Kohn, "XML Media Types", 1769 RFC 3023, January 2001. 1771 [RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C. and J. 1772 Whitehead, "Versioning Extensions to WebDAV", RFC 3253, 1773 March 2002. 1775 [RFC3744] Clemm, G., Reschke, J., Sedlar, E. and J. Whitehead, "Web 1776 Distributed Authoring and Versioning (WebDAV) Access 1777 Control Protocol", May 2004. 1779 [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E. and 1780 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third 1781 Edition)", W3C REC-xml-20040204, February 2004, 1782 . 1784 [XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath) 1785 Version 1.0", W3C REC REC-xpath-19991116, November 1999, 1786 . 1788 [XS1] Thompson, H., Beech, D., Maloney, M., Mendelsohn, N. and 1789 World Wide Web Consortium, "XML Schema Part 1: 1790 Structures", W3C REC-xmlschema-1-20010502, May 2001, 1791 . 1793 [XS2] Biron, P., Malhotra, A. and World Wide Web Consortium, 1794 "XML Schema Part 2: Datatypes", W3C 1795 REC-xmlschema-2-20010502, May 2001, 1796 . 1798 13.2 Informative References 1800 [BIND] Clemm, G., Crawford, J., Reschke, J., Slein, J. and J. 1801 Whitehead, "Binding Extensions to WebDAV", ID 1802 draft-ietf-webdav-bind-07, September 2004, 1803 . 1806 [DASL] Reddy, S., Lowry, D., Reddy, S., Henderson, R., Davis, J. 1807 and A. Babich, "DAV Searching & Locating", ID 1808 draft-dasl-protocol-00, July 1999, 1809 . 1812 [DASLREQ] Davis, J., Reddy, S. and J. Slein, "Requirements for DAV 1813 Searching and Locating", ID draft-dasl-requirements-01, 1814 February 1999, 1815 . 1818 [SQL99] Milton, J., "Database Language SQL Part 2: Foundation 1819 (SQL/Foundation)", ISO ISO/IEC 9075-2:1999 (E), July 1999. 1821 [UNICODE4] 1822 The Unicode Consortium, "The Unicode Standard - Version 1823 4.0", Addison-Wesley , August 2003, 1824 . 1826 ISBN 0321185781 [4] 1828 URIs 1830 [4] 1832 Authors' Addresses 1834 Julian F. Reschke (editor) 1835 greenbytes GmbH 1836 Salzmannstrasse 152 1837 Muenster, NW 48159 1838 Germany 1840 Phone: +49 251 2807760 1841 Fax: +49 251 2807761 1842 EMail: julian.reschke@greenbytes.de 1843 URI: http://greenbytes.de/tech/webdav/ 1845 Surendra Reddy 1846 Oracle Corporation 1847 600 Oracle Parkway, M/S 6op3 1848 Redwoodshores, CA 94065 1850 Phone: +1 650 506 5441 1851 EMail: Surendra.Reddy@oracle.com 1852 Jim Davis 1853 Intelligent Markets 1854 410 Jessie Street 6th floor 1855 San Francisco, CA 94103 1857 EMail: jrd3@alum.mit.edu 1859 Alan Babich 1860 FileNET Corp. 1861 3565 Harbor Blvd. 1862 Costa Mesa, CA 92626 1864 Phone: +1 714 327 3403 1865 EMail: ababich@filenet.com 1867 Appendix A. Three-Valued Logic in DAV:basicsearch 1869 ANSI standard three valued logic is used when evaluating the search 1870 condition (as defined in the ANSI standard SQL specifications, for 1871 example in ANSI X3.135-1992, section 8.12, pp. 188-189, section 8.2, 1872 p. 169, General Rule 1)a), etc.). 1874 ANSI standard three valued logic is undoubtedly the most widely 1875 practiced method of dealing with the issues of properties in the 1876 search condition not having a value (e.g., being null or not defined) 1877 for the resource under scan, and with undefined expressions in the 1878 search condition (e.g., division by zero, etc.). Three valued logic 1879 works as follows. 1881 Undefined expressions are expressions for which the value of the 1882 expression is not defined. Undefined expressions are a completely 1883 separate concept from the truth value UNKNOWN, which is, in fact, 1884 well defined. Property names and literal constants are considered 1885 expressions for purposes of this section. If a property in the 1886 current resource under scan has not been set to a value, then the 1887 value of that property is undefined for the resource under scan. 1888 DASL 1.0 has no arithmetic division operator, but if it did, division 1889 by zero would be an undefined arithmetic expression. 1891 If any subpart of an arithmetic, string, or datetime subexpression is 1892 undefined, the whole arithmetic, string, or datetime subexpression is 1893 undefined. 1895 There are no manifest constants to explicitly represent undefined 1896 number, string, or datetime values. 1898 Since a Boolean value is ultimately returned by the search condition, 1899 arithmetic, string, and datetime expressions are always arguments to 1900 other operators. Examples of operators that convert arithmetic, 1901 string, and datetime expressions to Boolean values are the six 1902 relational operators ("greater than", "less than", "equals", etc.). 1903 If either or both operands of a relational operator have undefined 1904 values, then the relational operator evaluates to UNKNOWN. 1905 Otherwise, the relational operator evaluates to TRUE or FALSE, 1906 depending upon the outcome of the comparison. 1908 The Boolean operators DAV:and, DAV:or and DAV:not are evaluated 1909 according to the following rules: 1911 not UNKNOWN = UNKNOWN 1913 UNKNOWN and TRUE = UNKNOWN 1915 UNKNOWN and FALSE = FALSE 1917 UNKNOWN and UNKNOWN = UNKNOWN 1919 UNKNOWN or TRUE = TRUE 1921 UNKNOWN or FALSE = UNKNOWN 1923 UNKNOWN or UNKNOWN = UNKNOWN 1925 Appendix B. Change Log (to be removed by RFC Editor before publication) 1927 B.1 From draft-davis-dasl-protocol-xxx 1929 Feb 14, 1998 Initial Draft 1931 Feb 28, 1998 Referring to DASL as an extension to HTTP/1.1 rather 1932 than DAV. 1933 Added new sections "Notational Conventions", "Protocol Model", 1934 "Security Considerations". 1935 Changed section 3 to "Elements of Protocol". 1936 Added some stuff to introduction. 1937 Added "result set" terminology. 1938 Added "IANA Considerations". 1940 Mar 9, 1998 Moved sub-headings of "Elements of Protocol" to first 1941 level and removed "Elements of Protocol" Heading. 1942 Added an sentence in introduction explaining that this is a 1943 "sketch" of a protocol. 1945 Mar 11, 1998 Added orderby, data typing, three valued logic, query 1946 schema property, and element definitions for schema for 1947 basicsearch. 1949 April 8, 1998 - made changes based on last week's DASL BOF. 1951 May 8, 1998 Removed most of DAV:searcherror; converted to 1952 DAV:searchredirect 1953 Altered DAV:basicsearch grammar to use avoid use of ANY in DTD 1955 June 17, 1998 -Added details on Query Schema Discovery 1956 -Shortened list of data types 1958 June 23, 1998 moved data types before change history 1959 rewrote the data types section 1960 removed the casesensitive element and replace with the 1961 casesensitive attribute 1962 added the casesensitive attribute to the DTD for all operations 1963 that might work on a string 1965 Jul 20, 1998 A series of changes. See Author's meeting minutes for 1966 details. 1968 July 28, 1998 Changes as per author's meeting. QSD uses SEARCH, not 1969 PROPFIND. 1970 Moved text around to keep concepts nearby. 1971 Boolean literals are 1 and 0, not T and F. 1972 contains changed to contentspassthrough. 1973 Renamed rank to score. 1975 July 28, 1998 Added Dale Lowry as Author 1977 September 4, 1998 Added 422 as response when query lists 1978 unimplemented operators. 1979 DAV:literal declares a default value for xml:space, 'preserve' 1980 (see XML spec, section 2.10) 1981 moved to new XML namespace syntax 1983 September 22, 1998 Changed "simplesearch" to "basicsearch" 1984 Changed isnull to isdefined 1985 Defined NULLness as having a 404 or 403 response 1986 used ENTITY syntax in DTD 1987 Added redirect 1989 October 9, 1998 Fixed a series of typographical and formatting 1990 errors. 1991 Modified the section of three-valued logic to use a table rather 1992 than a text description of the role of UNKNOWN in expressions. 1994 November 2, 1998 Added the DAV:contains operator. 1995 Removed the DAV:contentpassthrough operator. 1997 November 18, 1998 Various author comments for submission 1999 June 3, 1999 Cosmetic and minor editorial changes only. Fix nits 2000 reported by Jim Whitehead in email of April 26, 1999. Converted 2001 to HTML from Word 97, manually. 2003 April 20, 2000 Removed redirection feature, since 301/302 suffices. 2004 Removed Query Schema Discovery (former chapter 4). Everyone 2005 agrees this is a useful feature, but it is apparently too 2006 difficult to define at this time, and it is not essential for 2007 DASL. 2009 B.2 since start of draft-reschke-webdav-search 2011 October 09, 2001 Added Julian Reschke as author. 2012 Chapter about QSD re-added. 2013 Formatted into RFC2629-compliant XML document. 2014 Added first comments. 2015 ID version number kicked up to draft-dasl-protocol-03. 2017 October 17, 2001 Updated address information for Jim Davis. 2018 Added issue of datatype vocabularies. 2019 Updated issue descriptions for grammar discovery, added issues on 2020 query schema DTD. 2021 Fixed typos in XML examples. 2023 December 17, 2001 Re-introduced split between normative and 2024 non-normative references. 2026 January 05, 2002 Version bumbed up to 04. Started work on resolving 2027 the issues identified in the previous version. 2029 January 14, 2002 Fixed some XML typos. 2031 January 22, 2002 Closed issues naming-of-elements. Fixed query 2032 search DTD and added option to discover properties of "other" 2033 (non-listed) properties. 2035 January 25, 2002 Changed into private submission and added reference 2036 to historic DASL draft. Marked reference to DASL requirements 2037 non-normative. 2038 Updated reference to latest deltav spec. 2040 January 29, 2002 Added feedback from and updated contact info for 2041 Alan Babich. 2042 Included open issues collected in 2043 http://www.webdav.org/dasl/protocol/issues.html. 2045 February 8, 2002 Made sure that all artwork fits into 72 characters 2046 wide text. 2048 February 18, 2002 Changed Insufficient storage handling 2049 (multistatus). Moved is-collection to operators and added to DTD. 2050 Made scope/depth mandatory. 2052 February 20, 2002 Updated reference to SQL99. 2054 February 28, 2002 "Non-normative References" -> "Informative 2055 References". Abstract updated. Consistently specify a charset 2056 when using text/xml (no change bars). Do not attempt to define 2057 PROPFIND's entity encoding (take out specific references to 2058 text/xml). Remove irrelevant headers (Connection:) from examples 2059 (no change bars). Added issue on querying based on DAV:href. 2060 Updated introduction to indicate relationship to DASL draft. 2061 Updated HTTP reference from RFC2068 to RFC2616. Updated XML 2062 reference to XML 1.0 2nd edition. 2064 March 1, 2002 Removed superfluous namespace decl in 2.4.2. Reopened 2065 JW14 and suggest to drop xml:space support. 2067 March 3, 2002 Removed "xml:space" feature on DAV:literal. Added 2068 issue about string comparison vs. collations vs. xml:lang. 2069 Updated some of the open issues with details from JimW's original 2070 mail in April 1999. Resolved scope vs relative URI references. 2071 Resolved issues about DAV:ascending (added to index) and the BNF 2072 for DAV:like (changed "octets" to "characters"). 2074 March 8, 2002 Updated reference to DeltaV (now RFC3253). Added 2075 Martin Wallmer's comments, moved JW5 into DAV:basicsearch section. 2077 March 11, 2002 Closed open issues regaring the type of search 2078 arbiters (JW3) and their discovery (JW9). Rephrased requirements 2079 on multistatus response bodies (propstat only if properties were 2080 selected, removed requirement for responsedescription). 2082 March 23, 2002 RFC2376 -> RFC3023. Added missing first names of 2083 authors. OPTIONS added to example for DAV:supported-method-set. 2085 B.3 since draft-reschke-webdav-search-00 2087 March 29, 2002 Abstract doesn't refer to DASL WG anymore. 2089 April 7, 2002 Fixed section title (wrong property name 2090 supported-search-grammar-set. Changed DAV:casesensitve to 2091 "casesensitive" (it wasn't in the DAV: namespace after all). 2093 May 28, 2002 Updated some issues with Jim Davis's comments. 2095 June 10, 2002 Added proposal for different method for query schema 2096 discovery, not using pseudo-properties. 2098 June 25, 2002 QSD marshalling rewritten. Added issue 2099 "isdefined-optional". 2101 B.4 since draft-reschke-webdav-search-01 2103 July 04, 2002 Added issue "scope-collection". 2105 July 08, 2002 Closed issue "scope-collection". 2107 August 12, 2002 Added issues "results-vs-binds" and "select-allprop". 2109 October 22, 2002 Added issue "undefined-expressions". 2111 November 18, 2002 Changed example host names (no change tracking). 2113 November 25, 2002 Updated issue "DB2/DB7". Closed issues "undefined 2114 expressions", "isdefined-optional" and "select-allprop". 2116 B.5 since draft-reschke-webdav-search-02 2118 November 27, 2002 Added issues "undefined-properties", 2119 "like-exactlyone" and "like-wildcard-adjacent". Closed issue 2120 "query-on-href". Added acknowledgments section. 2122 November 28, 2002 Closed issue "like-exactlyone". Added issue 2123 "mixed-content-properties". 2125 December 14, 2002 Closed issues "undefined-properties", 2126 "results-vs-binds", "mixed-content-properties". Updated issue 2127 "like-wildcard-adjacent". Added informative reference to BIND 2128 draft. Updated reference to ACL draft. 2130 January 9, 2003 Removed duplicate section on invalid scopes. Added 2131 comments to some open issues. Closed issues JW25/26, 2132 score-pseudo-property and null-ordering. 2134 January 10, 2003 Issue limit-vs-ordering plus resolution. Closed 2135 issue JW17/JW24b. 2137 January 14, 2003 New issue order-precedence. Started resolution of 2138 DB2/DB7. 2140 January 15, 2003 Started spec of DAV:typed-literal. 2142 January 17, 2003 Fix one DAV:like/DAV:getcontenttype example (add / 2143 to like expression, make case-insensitive). 2145 January 28, 2003 Update issue(s) result-truncation, JW24d. Fixed 2146 response headers in OPTIONS example. Added issue qsd-optional. 2147 Closed issue(s) order-precedence, case-insensitivity-name. 2149 February 07, 2003 Added issue scope-vs-versions. 2150 score-pseudo-property: allow DAV:orderby to explicitly specify 2151 DAV:score. 2153 B.6 since draft-reschke-webdav-search-03 2155 April 24, 2003 Fixed two "?" vs "_" issues (not updated in last 2156 draft). 2158 June 13, 2003 Improve index. 2160 B.7 since draft-reschke-webdav-search-04 2162 July 7, 2003 Typo fixed (propstat without status element). 2164 August 11, 2003 Remove superfluous IP and copyright sections. 2166 September 09, 2003 Added issues "2.4-multiple-uris" and 2167 "5.1-name-filtering". 2169 October 06, 2003 Fix misplaced section end in 5.11, add table 2170 formatting. Enhance table formatting in 5.18.3. Updated ACL and 2171 BIND references. Added XPATH reference. Closed issue JW24d by 2172 adding new optional operators. Updated more open issues, added 2173 issues from January meeting. Add K. Wiggen to Acknowledgements. 2174 Add Contributors section for the authors of the original draft. 2175 Close issue "scope-vs-versions" (optional feature added). Close 2176 (new) issue "1.3-import-DTD-terminology". Add issue 2177 "1.3-import-requirements-terminology". 2179 October 07, 2003 Typos fixed. Moved statement about DAV: namespace 2180 usage into separate (sub-)section. Closed 2181 "1.3-import-requirements-terminology". Update I18N Considerations 2182 with new xml:lang support info (see issue JW24d). Close issue 2183 "DB2/DB7" (remaining typing issues are now summarized in issue 2184 "typed-literal"). Fix misplaced section end in section 7. 2185 Started change to use RFC3253-style method definitions and error 2186 marshalling. 2188 October 08, 2003 Remove obsolete language that allowed reporting 2189 invalid scopes and such inside multistatus. Add new issue 2190 "5.4.2-scope-vs-redirects". 2192 B.8 since draft-reschke-webdav-search-05 2194 October 11, 2003 Separate DAV:basicsearch DTD into separate figures 2195 for better maintainability. Update DTD with language-* operators 2196 and typed-literal element (optional). 2198 October 14, 2003 Close issue "5.4.2-multiple-scope". 2200 November 04, 2003 Update reference from CaseMap to UNICODE4, section 2201 5.18. 2203 November 16, 2003 Updated issue "5.1-name-filtering". 2205 November 24, 2003 Reformatted scope description (collection vs. 2206 non-collection). 2208 November 30, 2003 Add issue "5_media_type_match". 2210 February 6, 2004 Updated all references. 2212 B.9 since draft-reschke-webdav-search-05 2214 July 05, 2004 Fix table in Appendix "Three-Valued Logic in 2215 DAV:basicsearch". 2217 September 14, 2004 Fix inconsistent DTD in section 5.2 and 5.4 for 2218 scope element. 2220 September 30, 2004 Rewrite editorial note and abstract. Update 2221 references (remove unneeded XMLNS, update ref to ACL and BIND 2222 specs). 2224 Appendix C. Open issues (to be removed by RFC Editor prior to 2225 publication) 2227 C.1 edit 2229 Type: edit 2231 julian.reschke@greenbytes.de (2004-07-05): Umbrella issue for 2232 editorial fixes/enhancements. 2234 C.2 1.3-apply-condition-code-terminology 2236 Type: change 2238 julian.reschke@greenbytes.de (2003-10-07): (Umbrella issue that will 2239 be left open until RFC3253 condition terminlogy is used throughout 2240 the document) 2242 C.3 2.4-multiple-uris 2244 Type: change 2246 julian.reschke@greenbytes.de (2003-09-09): However, the set of URIs 2247 for a given resource may be unlimited due to possible bind loops. 2248 Therefore consider to report just one URI per resource. 2250 C.4 result-truncation 2252 Type: change 2254 2257 ldusseault@xythos.com (2002-03-29): I believe the same response body 2258 that contains the first N elements should also contain 2259 a *different* element stating that the results were incomplete and 2260 the result set was truncated by the server. There may also be a need 2261 to report that the results were incomplete and the result set was 2262 truncated at the choice of the client (isn't there a limit set in the 2263 client request?) That's important so the client knows the difference 2264 between receiving 10 results because there were >10 but only 10 were 2265 asked for, and receiving 10 results because there were only exactly 2266 10 results and it just happens that 10 were asked for. 2268 jrd3@alum.mit.edu (2002-05-28): I agree that this could be useful, 2269 but I think this issue should be consolidated with issue JW5 (see 2270 below), which proposes that DASL basicsearch ought to have a way for 2271 client to request additional result sets. It should be moved because 2272 there is little or no value in allowing a client to distinguish 2273 between the case where "N results were requested, and there are 2274 exactly N available" and "N results were requested, and there are 2275 more than N available" if there is no way for client to get the next 2276 batch of results. 2278 julian.reschke@greenbytes.de (2003-01-28): Feedback from interim WG 2279 meeting: agreement that marshalling should be rewritten and backwards 2280 compatibility is not important. Proposal: extend DAV:multistatus by 2281 a new child element that indicates (1) the range that was returned, 2282 (2) the total number of results and (3) a URI identifying the result 2283 (for resubmission when getting the "next" results). Such as 2284 ...identifier for 2285 result set... <-- number of results --> 2286 <-- 1-based index of 1st result --> <-- size 2287 of result set returned --> <-- indicates 2288 that this is a partial result --> ...response 2289 elements for search results... The example below 2290 would then translate to: HTTP/1.1 207 Multistatus Content-Type: 2291 text/xml; charset="utf-8" Content-Length: xxx 2293 2294 http://www.example.net/sounds/unbrokenchain.au 2295 HTTP/1.1 200 OK 2296 2297 http://tech.mit.test/archive96/photos/Lesh1.jpg 2298 HTTP/1.1 200 OK 2299 Q: do we need all 2300 elements, in particular start and length? 2302 julian.reschke@greenbytes.de (2003-10-07): Related: if this is 2303 supposed to be normative to DAV:basicsearch, it can't stay in an 2304 "example" sub-section. 2306 C.5 qsd-optional 2308 Type: change 2310 julian.reschke@greenbytes.de (2003-01-28): WG January meeting 2311 feedback: QSD should be made required. 2313 kwiggen@xythos.com (2003-10-03): (significant pushback, see mailing 2314 list thread at 2315 http://lists.w3.org/Archives/Public/www-webdav-dasl/2003OctDec/0003.h 2316 tml). 2318 C.6 5.1-name-filtering 2320 Type: change 2322 2325 julian.reschke@greenbytes.de (2003-09-08): This query grammar 2326 supports properties and content, but not conditions on URL elements 2327 (such as the last segment that many WebDAV implementations treat as 2328 "file name"). Discuss possible extension such as adding name filters 2329 to the scope, or adding a specific operator. 2331 Martin.Wallmer@softwareag.com (2003-11-11): Specific proposal to add 2332 this feature as scope restriction, see 2333 . 2336 Martin.Wallmer@softwareag.com (2003-11-25): Updated proposal: 2337 . 2340 C.7 5_media_type_match 2342 Type: change 2344 julian.reschke@greenbytes.de (2003-11-30): Putting conditions on 2345 DAV:getcontenttype is hard (see 2346 is (too?) hard. Proposal for a specific operator for 2348 expressing conditions on the media type: 2349 . 2352 C.8 5.4.2-scope-vs-redirects 2354 Type: change 2356 2359 julian.reschke@greenbytes.de (2003-10-08): Clarify the relation of 2360 scope and redirect (3xx) resources. 2362 C.9 language-comparison 2364 Type: change 2366 2369 julian.reschke@greenbytes.de (2002-03-03): XPath/XQuery (see draft, 2370 and open issue) specify string comparisons based on collations, not 2371 languages. I think we should adopt this. This would mean that 2372 "xml:lang" would be removed, and an optional attribute specifying the 2373 name of the collation is added. 2375 julian.reschke@greenbytes.de (2003-01-09): Proposal: adopt "lang" and 2376 "collation" attribute from XSLT 2.0's xsl:sort. 2378 C.10 JW16b/JW24a 2380 Type: change 2382 2385 ejw@ics.uci.edu (2000-04-20): Define how comparisons on strings work, 2386 esp for i18n. Need policy statement about sort order in various 2387 national languages. (JW said "non-Latin" but it's an issue even in 2388 languages that use the latin char set.) 2390 julian.reschke@greenbytes.de (2003-01-28): This issue not only 2391 applies to the comparison operators, but also to ordering! 2393 C.11 typed-literal 2395 Type: change 2397 julian.reschke@greenbytes.de (2003-01-15): 1. (insert language 2398 defining the comparison following the rules defined in 2399 http://www.w3.org/TR/xpath20/#id-comparisons). 2. Extend 2400 Basicsearch QSD grammar to support discovery of typed-literal 3. 2401 Update DTD. 4. Discuss behaviour of DAV:literal when the property's 2402 type is known for the complete search scope (is the server allowed to 2403 be "smart"?) 2405 julian.reschke@greenbytes.de (2003-10-11): 3.: done 2407 Index 2409 C 2410 caseless attribute 26, 33 2411 Condition Names 2412 DAV:search-grammar-discovery-supported (pre) 9 2413 DAV:search-grammar-supported (pre) 9 2414 DAV:search-multiple-scope-supported (pre) 9 2415 DAV:search-scope-valid (pre) 9 2416 Criteria 5 2418 D 2419 DAV:and 26 2420 DAV:ascending 25 2421 DAV:contains 31 2422 DAV:depth 22 2423 DAV:descending 25 2424 DAV:eq 26 2425 caseless attribute 26 2426 DAV:from 22 2427 DAV:gt 26 2428 DAV:gte 26 2429 DAV:include-versions 22 2430 DAV:is-collection 29 2431 DAV:is-defined 29 2432 DAV:language-defined 28 2433 DAV:language-matches 28 2434 DAV:like 30 2435 DAV:limit 32 2436 DAV:literal 26 2437 DAV:lt 26 2438 DAV:lte 26 2439 DAV:not 26 2440 DAV:nresults 32 2441 DAV:or 26 2442 DAV:orderby 25 2443 DAV:scope 22 2444 DAV:score 31 2445 relationship to DAV:orderby 32 2446 DAV:search-grammar-discovery-supported precondition 9 2447 DAV:search-grammar-supported precondition 9 2448 DAV:search-multiple-scope-supported precondition 9 2449 DAV:search-scope-valid precondition 9 2450 DAV:select 22 2451 DAV:supported-query-grammar-set property 14 2452 DAV:typed-literal 27 2453 DAV:where 23 2455 M 2456 Methods 2457 SEARCH 8 2459 O 2460 OPTIONS method 13 2461 DASL response header 14 2463 P 2464 Properties 2465 DAV:supported-query-grammar-set 14 2467 Q 2468 Query Grammar Discovery 13 2469 using live property 14 2470 using OPTIONS 13 2471 Query Grammar 6 2472 Query Schema 6 2473 Query 5 2475 R 2476 Result Record Definition 6 2477 Result Record 6 2478 Result Set Truncation 2479 Example 11 2480 Result Set 6 2481 Result 6 2483 S 2484 Scope 6 2485 SEARCH method 8 2486 Search Modifier 6 2487 Sort Specification 6 2489 Intellectual Property Statement 2491 The IETF takes no position regarding the validity or scope of any 2492 Intellectual Property Rights or other rights that might be claimed to 2493 pertain to the implementation or use of the technology described in 2494 this document or the extent to which any license under such rights 2495 might or might not be available; nor does it represent that it has 2496 made any independent effort to identify any such rights. Information 2497 on the procedures with respect to rights in RFC documents can be 2498 found in BCP 78 and BCP 79. 2500 Copies of IPR disclosures made to the IETF Secretariat and any 2501 assurances of licenses to be made available, or the result of an 2502 attempt made to obtain a general license or permission for the use of 2503 such proprietary rights by implementers or users of this 2504 specification can be obtained from the IETF on-line IPR repository at 2505 http://www.ietf.org/ipr. 2507 The IETF invites any interested party to bring to its attention any 2508 copyrights, patents or patent applications, or other proprietary 2509 rights that may cover technology that may be required to implement 2510 this standard. Please address the information to the IETF at 2511 ietf-ipr@ietf.org. 2513 Disclaimer of Validity 2515 This document and the information contained herein are provided on an 2516 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2517 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2518 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2519 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2520 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2521 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2523 Copyright Statement 2525 Copyright (C) The Internet Society (2004). This document is subject 2526 to the rights, licenses and restrictions contained in BCP 78, and 2527 except as set forth therein, the authors retain all their rights. 2529 Acknowledgment 2531 Funding for the RFC Editor function is currently provided by the 2532 Internet Society.