idnits 2.17.1 draft-reschke-webdav-search-08.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 on line 20. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2571. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2548. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2555. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2561. ** 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. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == 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 1020 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://") -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 5, 2005) is 6903 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-11 -- No information found for draft-dasl-requirements - is the name correct? Summary: 6 errors (**), 0 flaws (~~), 6 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: November 6, 2005 S. Reddy 5 Oracle 6 J. Davis 7 Intelligent Markets 8 A. Babich 9 Filenet 10 May 5, 2005 12 WebDAV SEARCH 13 draft-reschke-webdav-search-08 15 Status of this Memo 17 By submitting this Internet-Draft, each author represents that any 18 applicable patent or other IPR claims of which he or she is aware 19 have been or will be disclosed, and any of which he or she becomes 20 aware will be disclosed, in accordance with Section 6 of BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire on November 6, 2005. 40 Copyright Notice 42 Copyright (C) The Internet Society (2005). 44 Abstract 46 This document specifies a set of methods, headers, properties and 47 content-types composing WebDAV SEARCH, an application of the HTTP/1.1 48 protocol to efficiently search for DAV resources based upon a set of 49 client-supplied criteria. 51 Editorial Note (To be removed by RFC Editor before publication) 53 Please send comments to the Distributed Authoring and Versioning 54 (WebDAV) DASL mailing list at , which 55 may be joined by sending a message with subject "subscribe" to 56 . Discussions of the WebDAV 57 DASL mailing list are archived at 58 . 60 An issues list and XML and HTML versions of this draft are available 61 from . 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 66 1.1 DASL . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 67 1.2 Relationship to DAV . . . . . . . . . . . . . . . . . . . 5 68 1.3 Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 69 1.4 Notational Conventions . . . . . . . . . . . . . . . . . . 7 70 1.5 Editorial note on usage of 'DAV:' namespace . . . . . . . 7 71 1.6 An Overview of DASL at Work . . . . . . . . . . . . . . . 8 72 2. The SEARCH Method . . . . . . . . . . . . . . . . . . . . . 8 73 2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 8 74 2.2 The Request . . . . . . . . . . . . . . . . . . . . . . . 8 75 2.2.1 The Request-URI . . . . . . . . . . . . . . . . . . . 8 76 2.2.2 The Request Body . . . . . . . . . . . . . . . . . . . 9 77 2.3 The Successful 207 (Multistatus) Response . . . . . . . . 9 78 2.3.1 Extending the PROPFIND Response . . . . . . . . . . . 10 79 2.3.2 Example: A Simple Request and Response . . . . . . . . 10 80 2.3.3 Example: Result Set Truncation . . . . . . . . . . . . 11 81 2.4 Unsuccessful Responses . . . . . . . . . . . . . . . . . . 12 82 2.4.1 Example of an Invalid Scope . . . . . . . . . . . . . 12 83 3. Discovery of Supported Query Grammars . . . . . . . . . . . 13 84 3.1 The OPTIONS Method . . . . . . . . . . . . . . . . . . . . 13 85 3.2 The DASL Response Header . . . . . . . . . . . . . . . . . 14 86 3.3 DAV:supported-query-grammar-set (protected) . . . . . . . 14 87 3.4 Example: Grammar Discovery . . . . . . . . . . . . . . . . 15 88 4. Query Schema Discovery: QSD . . . . . . . . . . . . . . . . 17 89 4.1 Additional SEARCH semantics . . . . . . . . . . . . . . . 17 90 4.1.1 Example of query schema discovery . . . . . . . . . . 18 91 5. The DAV:basicsearch Grammar . . . . . . . . . . . . . . . . 19 92 5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 19 93 5.2 The DAV:basicsearch DTD . . . . . . . . . . . . . . . . . 20 94 5.2.1 Example Query . . . . . . . . . . . . . . . . . . . . 22 95 5.3 DAV:select . . . . . . . . . . . . . . . . . . . . . . . . 23 96 5.4 DAV:from . . . . . . . . . . . . . . . . . . . . . . . . . 23 97 5.4.1 Relationship to the Request-URI . . . . . . . . . . . 23 98 5.4.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . 23 99 5.5 DAV:where . . . . . . . . . . . . . . . . . . . . . . . . 24 100 5.5.1 Use of Three-Valued Logic in Queries . . . . . . . . . 24 101 5.5.2 Handling Optional operators . . . . . . . . . . . . . 24 102 5.5.3 Treatment of NULL Values . . . . . . . . . . . . . . . 24 103 5.5.4 Treatment of properties with mixed/element content . . 24 104 5.5.5 Example: Testing for Equality . . . . . . . . . . . . 25 105 5.5.6 Example: Relative Comparisons . . . . . . . . . . . . 25 106 5.6 DAV:orderby . . . . . . . . . . . . . . . . . . . . . . . 25 107 5.6.1 Comparing Natural Language Strings . . . . . . . . . . 26 108 5.6.2 Example of Sorting . . . . . . . . . . . . . . . . . . 26 109 5.7 Boolean Operators: DAV:and, DAV:or, and DAV:not . . . . . 26 110 5.8 DAV:eq . . . . . . . . . . . . . . . . . . . . . . . . . . 27 111 5.9 DAV:lt, DAV:lte, DAV:gt, DAV:gte . . . . . . . . . . . . . 27 112 5.10 DAV:literal . . . . . . . . . . . . . . . . . . . . . . 27 113 5.11 DAV:typed-literal (optional) . . . . . . . . . . . . . . 27 114 5.11.1 Example for typed numerical comparison . . . . . . . 28 115 5.12 Support for matching xml:lang attributes on properties . 28 116 5.12.1 DAV:language-defined (optional) . . . . . . . . . . 28 117 5.12.2 DAV:language-matches (optional) . . . . . . . . . . 29 118 5.12.3 Example of language-aware matching . . . . . . . . . 29 119 5.13 DAV:is-collection . . . . . . . . . . . . . . . . . . . 29 120 5.13.1 Example of DAV:is-collection . . . . . . . . . . . . 30 121 5.14 DAV:is-defined . . . . . . . . . . . . . . . . . . . . . 30 122 5.15 DAV:like . . . . . . . . . . . . . . . . . . . . . . . . 30 123 5.15.1 Syntax for the Literal Pattern . . . . . . . . . . . 31 124 5.15.2 Example of DAV:like . . . . . . . . . . . . . . . . 31 125 5.16 DAV:contains . . . . . . . . . . . . . . . . . . . . . . 31 126 5.16.1 Result scoring (DAV:score element) . . . . . . . . . 32 127 5.16.2 Ordering by score . . . . . . . . . . . . . . . . . 32 128 5.16.3 Examples . . . . . . . . . . . . . . . . . . . . . . 33 129 5.17 Limiting the result set . . . . . . . . . . . . . . . . 33 130 5.17.1 Relationship to result ordering . . . . . . . . . . 33 131 5.18 The 'caseless' XML attribute . . . . . . . . . . . . . . 33 132 5.19 Query schema for DAV:basicsearch . . . . . . . . . . . . 34 133 5.19.1 DTD for DAV:basicsearch QSD . . . . . . . . . . . . 34 134 5.19.2 DAV:propdesc Element . . . . . . . . . . . . . . . . 34 135 5.19.3 The DAV:datatype Property Description . . . . . . . 35 136 5.19.4 The DAV:searchable Property Description . . . . . . 35 137 5.19.5 The DAV:selectable Property Description . . . . . . 36 138 5.19.6 The DAV:sortable Property Description . . . . . . . 36 139 5.19.7 The DAV:caseless Property Description . . . . . . . 36 140 5.19.8 The DAV:operators XML Element . . . . . . . . . . . 36 141 5.19.9 Example of Query Schema for DAV:basicsearch . . . . 37 142 6. Internationalization Considerations . . . . . . . . . . . . 37 143 7. Security Considerations . . . . . . . . . . . . . . . . . . 38 144 7.1 Implications of XML External Entities . . . . . . . . . . 38 146 8. Scalability . . . . . . . . . . . . . . . . . . . . . . . . 39 147 9. Authentication . . . . . . . . . . . . . . . . . . . . . . . 39 148 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . 39 149 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 39 150 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39 151 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 39 152 13.1 Normative References . . . . . . . . . . . . . . . . . . 39 153 13.2 Informative References . . . . . . . . . . . . . . . . . 40 154 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 41 155 A. Three-Valued Logic in DAV:basicsearch . . . . . . . . . . . 42 156 B. Change Log (to be removed by RFC Editor before 157 publication) . . . . . . . . . . . . . . . . . . . . . . . . 43 158 B.1 From draft-davis-dasl-protocol-xxx . . . . . . . . . . . . 43 159 B.2 since start of draft-reschke-webdav-search . . . . . . . . 45 160 B.3 since draft-reschke-webdav-search-00 . . . . . . . . . . . 46 161 B.4 since draft-reschke-webdav-search-01 . . . . . . . . . . . 47 162 B.5 since draft-reschke-webdav-search-02 . . . . . . . . . . . 47 163 B.6 since draft-reschke-webdav-search-03 . . . . . . . . . . . 48 164 B.7 since draft-reschke-webdav-search-04 . . . . . . . . . . . 48 165 B.8 since draft-reschke-webdav-search-05 . . . . . . . . . . . 49 166 B.9 since draft-reschke-webdav-search-06 . . . . . . . . . . . 49 167 B.10 since draft-reschke-webdav-search-07 . . . . . . . . . . 49 168 C. Resolved issues (to be removed by RFC Editor before 169 publication) . . . . . . . . . . . . . . . . . . . . . . . . 50 170 C.1 abnf . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 171 D. Open issues (to be removed by RFC Editor prior to 172 publication) . . . . . . . . . . . . . . . . . . . . . . . . 50 173 D.1 edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 174 D.2 1.3-apply-condition-code-terminology . . . . . . . . . . . 51 175 D.3 2.4-multiple-uris . . . . . . . . . . . . . . . . . . . . 51 176 D.4 result-truncation . . . . . . . . . . . . . . . . . . . . 51 177 D.5 qsd-optional . . . . . . . . . . . . . . . . . . . . . . . 52 178 D.6 5.1-name-filtering . . . . . . . . . . . . . . . . . . . . 52 179 D.7 5_media_type_match . . . . . . . . . . . . . . . . . . . . 53 180 D.8 5.4.2-scope-vs-redirects . . . . . . . . . . . . . . . . . 53 181 D.9 language-comparison . . . . . . . . . . . . . . . . . . . 53 182 D.10 JW16b/JW24a . . . . . . . . . . . . . . . . . . . . . . 53 183 D.11 typed-literal . . . . . . . . . . . . . . . . . . . . . 54 184 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 185 Intellectual Property and Copyright Statements . . . . . . . 57 187 1. Introduction 189 1.1 DASL 191 This document defines WebDAV SEARCH, an application of HTTP/1.1 192 forming a lightweight search protocol to transport queries and result 193 sets and allows clients to make use of server-side search facilities. 194 It is based on the expired draft for WebDAV DASL [DASL]. [DASLREQ] 195 describes the motivation for DASL. 197 DASL will minimize the complexity of clients so as to facilitate 198 widespread deployment of applications capable of utilizing the DASL 199 search mechanisms. 201 DASL consists of: 203 o the SEARCH method, 205 o the DASL response header, 207 o the DAV:searchrequest XML element, 209 o the DAV:query-schema-discovery XML element, 211 o the DAV:basicsearch XML element and query grammar, and 213 o the DAV:basicsearchschema XML element. 215 For WebDAV-compliant servers, it also defines a new live property 216 DAV:supported-query-grammar-set. 218 1.2 Relationship to DAV 220 DASL relies on the resource and property model defined by [RFC2518]. 221 DASL does not alter this model. Instead, DASL allows clients to 222 access DAV-modeled resources through server-side search. 224 1.3 Terms 226 This document uses the terms defined in [RFC2616], in [RFC2518], in 227 [RFC3253] and in this section. 229 Criteria 231 An expression against which each resource in the search scope is 232 evaluated. 234 Query 235 A query is a combination of a search scope, search criteria, 236 result record definition, sort specification, and a search 237 modifier. 239 Query Grammar 241 A set of definitions of XML elements, attributes, and constraints 242 on their relations and values that defines a set of queries and 243 the intended semantics. 245 Query Schema 247 A listing, for any given grammar and scope, of the properties and 248 operators that may be used in a query with that grammar and scope. 250 Result 252 A result is a result set, optionally augmented with other 253 information describing the search as a whole. 255 Result Record 257 A description of a resource. A result record is a set of 258 properties, and possibly other descriptive information. 260 Result Record Definition 262 A specification of the set of properties to be returned in the 263 result record. 265 Result Set 267 A set of records, one for each resource for which the search 268 criteria evaluated to True. 270 Scope 272 A set of resources to be searched. 274 Search Modifier 276 An instruction that governs the execution of the query but is not 277 part of the search scope, result record definition, the search 278 criteria, or the sort specification. An example of a search 279 modifier is one that controls how much time the server can spend 280 on the query before giving a response. 282 Sort Specification 283 A specification of an ordering on the result records in the result 284 set. 286 1.4 Notational Conventions 288 This specification uses the Augmented Backus-Naur Form (ABNF) 289 notation of [draft-crocker-abnf-rfc2234bis], unless explicitly stated 290 otherwise. 292 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT" 293 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 294 document are to be interpreted as described in [RFC2119]. 296 This document uses XML DTD fragments as a purely notational 297 convention. WebDAV request and response bodies can not be validated 298 due to the specific extensibility rules defined in section 23 of 299 [RFC2518] and due to the fact that all XML elements defined by this 300 specification use the XML namespace name "DAV:". In particular: 302 1. element names use the "DAV:" namespace, 304 2. element ordering is irrelevant unless explicitly stated, 306 3. extension elements (elements not already defined as valid child 307 elements) may be added anywhere, except when explicitly stated 308 otherwise, 310 4. extension attributes (attributes not already defined as valid for 311 this element) may be added anywhere, except when explicitly 312 stated otherwise. 314 When an XML element type in the "DAV:" namespace is referenced in 315 this document outside of the context of an XML fragment, the string 316 "DAV:" will be prefixed to the element type. 318 Similarily, when an XML element type in the namespace 319 "http://www.w3.org/2001/XMLSchema" is referenced in this document 320 outside of the context of an XML fragment, the string "xs:" will be 321 prefixed to the element type. 323 1.5 Editorial note on usage of 'DAV:' namespace 325 _Note that this draft currently defines elements and properties in 326 the WebDAV namespace "DAV:" which it shouldn't do as it isn't a work 327 item of the WebDAV working group. The reason for this is the desire 328 for some kind of backward compatibility to the expired DASL drafts 329 and the assumption that the draft may become an official RFC 330 submission of the WebDAV working group at a later point of time._ 332 1.6 An Overview of DASL at Work 334 One can express the basic usage of DASL in the following steps: 336 o The client constructs a query using the DAV:basicsearch grammar. 338 o The client invokes the SEARCH method on a resource that will 339 perform the search (the search arbiter) and includes a text/xml or 340 application/xml request entity that contains the query. 342 o The search arbiter performs the query. 344 o The search arbiter sends the results of the query back to the 345 client in the response. The server MUST send an entity that 346 matches the [RFC2518] PROPFIND response. 348 2. The SEARCH Method 350 2.1 Overview 352 The client invokes the SEARCH method to initiate a server-side 353 search. The body of the request defines the query. The server MUST 354 emit an entity matching the [RFC2518] PROPFIND response. 356 The SEARCH method plays the role of transport mechanism for the query 357 and the result set. It does not define the semantics of the query. 358 The type of the query defines the semantics. 360 2.2 The Request 362 The client invokes the SEARCH method on the resource named by the 363 Request-URI. 365 2.2.1 The Request-URI 367 The Request-URI identifies the search arbiter. Any HTTP resource may 368 function as search arbiter. It is not a new type of resource (in the 369 sense of DAV:resourcetype as defined in [RFC2518]), nor does it have 370 to be a WebDAV-compliant resource. 372 The SEARCH method defines no relationship between the arbiter and the 373 scope of the search, rather the particular query grammar used in the 374 query defines the relationship. For example, a query grammar may 375 force the request-URI to correspond exactly to the search scope. 377 2.2.2 The Request Body 379 The server MUST process a text/xml or application/xml request body, 380 and MAY process request bodies in other formats. See [RFC3023] for 381 guidance on packaging XML in requests. 383 Marshalling: 385 If a request body with content type text/xml or application/xml is 386 included, it MUST be either a DAV:searchrequest or a DAV:query- 387 schema-discovery XML element. It's single child element 388 identifies the query grammar. 390 For DAV:searchrequest, the definition of search criteria, the 391 result record, and any other details needed to perform the search 392 depend on the individual search grammar. 394 For DAV:query-schema-discovery, the semantics is defined in 395 Section 4. 397 Preconditions: 399 (DAV:search-grammar-discovery-supported): when an XML request body 400 is present and has a DAV:query-schema-discovery document element, 401 the server MUST support the query schema discovery mechanism 402 described in Section 4. 404 (DAV:search-grammar-supported): when an XML request body is 405 present, the search grammar identified by the document element's 406 child element must be a supported search grammar. 408 (DAV:search-multiple-scope-supported): if the SEARCH request 409 specified multiple scopes, the server MUST support this optional 410 feature. 412 (DAV:search-scope-valid): the supplied search scope must be valid. 413 There can be various reasons for a search scope to be invalid, 414 including unsupported URI schemes and communication problems. 415 Servers MAY add [RFC2518] compliant DAV:response elements as 416 content to the condition element indicating the precise reason for 417 the failure. 419 2.3 The Successful 207 (Multistatus) Response 421 If the server returns 207 (Multistatus), then the search proceeded 422 successfully and the response MUST match that of a PROPFIND. The 423 results of this method SHOULD NOT be cached. 425 There MUST be one DAV:response for each resource that matched the 426 search criteria. For each such response, the DAV:href element 427 contains the URI of the resource, and the response MUST include a 428 DAV:propstat element. 430 Note that for each matching resource found there may be multiple URIs 431 within the search scope mapped to it. In this case, a server SHOULD 432 report all of these URIs. Clients can use the live property DAV: 433 resource-id defined in [BIND] to identify possible duplicates. 435 2.3.1 Extending the PROPFIND Response 437 A response MAY include more information than PROPFIND defines so long 438 as the extra information does not invalidate the PROPFIND response. 439 Query grammars SHOULD define how the response matches the PROPFIND 440 response. 442 2.3.2 Example: A Simple Request and Response 444 This example demonstrates the request and response framework. The 445 following XML document shows a simple (hypothetical) natural language 446 query. The name of the query element is natural-language-query in 447 the XML namespace "http://example.com/foo". The actual query is 448 "Find the locations of good Thai restaurants in Los Angeles". For 449 this hypothetical query, the arbiter returns two properties for each 450 selected resource. 452 >> Request: 454 SEARCH / HTTP/1.1 455 Host: example.org 456 Content-Type: application/xml 457 Content-Length: xxx 459 460 461 462 Find the locations of good Thai restaurants in Los Angeles 463 464 465 >> Response: 467 HTTP/1.1 207 Multi-Status 468 Content-Type: text/xml; charset="utf-8" 469 Content-Length: xxx 471 472 474 475 http://siamiam.test/ 476 477 478 259 W. Hollywood 479 4 480 481 HTTP/1.1 200 OK 482 483 484 486 2.3.3 Example: Result Set Truncation 488 A server MAY limit the number of resources in a reply, for example to 489 limit the amount of resources expended in processing a query. If it 490 does so, the reply MUST use status code 207, return a DAV:multistatus 491 response body and indicate a status of 507 (Insufficient Storage) for 492 the search arbiter URI. It SHOULD include the partial results. 494 When a result set is truncated, there may be many more resources that 495 satisfy the search criteria but that were not examined. 497 If partial results are included and the client requested an ordered 498 result set in the original request, then any partial results that are 499 returned MUST be ordered as the client directed. 501 Note that the partial results returned MAY be any subset of the 502 result set that would have satisfied the original query. 504 >> Request: 506 SEARCH / HTTP/1.1 507 Host: example.net 508 Content-Type: text/xml; charset="utf-8" 509 Content-Length: xxx 511 ... the query goes here ... 513 >> Response: 515 HTTP/1.1 207 Multistatus 516 Content-Type: text/xml; charset="utf-8" 517 Content-Length: xxx 519 520 521 522 http://www.example.net/sounds/unbrokenchain.au 523 524 525 HTTP/1.1 200 OK 526 527 528 529 http://tech.mit.test/archive96/photos/Lesh1.jpg 530 531 532 HTTP/1.1 200 OK 533 534 535 536 http://example.net 537 HTTP/1.1 507 Insufficient Storage 538 539 Only first two matching records were returned 540 541 542 544 2.4 Unsuccessful Responses 546 If a SEARCH request could not be executed or the attempt to execute 547 it resulted in an error, the server MUST indicate the failure with an 548 appropriate status code and SHOULD add a response body as defined in 549 [RFC3253], section 1.6. Unless otherwise stated, condition elements 550 are empty, however specific conditions element MAY include additional 551 child elements that describe the error condition in more detail. 553 2.4.1 Example of an Invalid Scope 555 In the example below, a request failed because the scope identifies a 556 HTTP resource that was not found. 558 >> Response: 560 HTTP/1.1 409 Conflict 561 Content-Type: text/xml; charset="utf-8" 562 Content-Length: xxx 564 565 566 567 568 http://www.example.com/X 569 HTTP/1.1 404 Object Not Found 570 571 572 574 3. Discovery of Supported Query Grammars 576 Servers MUST support discovery of the query grammars supported by a 577 search arbiter resource. 579 Clients can determine which query grammars are supported by an 580 arbiter by invoking OPTIONS on the search arbiter. If the resource 581 supports SEARCH, then the DASL response header will appear in the 582 response. The DASL response header lists the supported grammars. 584 Servers supporting the WebDAV extensions [RFC3253] and/or [RFC3744] 585 MUST also 587 o report SEARCH in the live property DAV:supported-method-set for 588 all search arbiter resources and 590 o support the live property DAV:supported-query-grammar-set as 591 defined in Section 3.3. 593 3.1 The OPTIONS Method 595 The OPTIONS method allows the client to discover if a resource 596 supports the SEARCH method and to determine the list of search 597 grammars supported for that resource. 599 The client issues the OPTIONS method against a resource named by the 600 Request-URI. This is a normal invocation of OPTIONS defined in 601 [RFC2616]. 603 If a resource supports the SEARCH method, then the server MUST list 604 SEARCH in the OPTIONS response as defined by [RFC2616]. 606 DASL servers MUST include the DASL header in the OPTIONS response. 607 This header identifies the search grammars supported by that 608 resource. 610 3.2 The DASL Response Header 612 DASLHeader = "DASL" ":" Coded-URL-List 613 Coded-URL-List : Coded-URL [ "," Coded-URL-List ] 614 Coded-URL ; defined in section 9.4 of [RFC2518] 616 (This grammar uses the augmented BNF format defined in Section 2.1 of 617 [RFC2616]) 619 The DASL response header indicates server support for a query grammar 620 in the OPTIONS method. The value is a URI that indicates the type of 621 grammar. Note that although the URI can be used to identify each 622 supported search grammar, there is not necessarily a direct 623 relationship between the URI and the XML element name that can be 624 used in XML based SEARCH requests (the element name itself is 625 identified by it's namespace name (a URI reference) and the element's 626 local name). 628 This header MAY be repeated. 630 For example: 632 DASL: 633 DASL: 634 DASL: 635 DASL: 637 3.3 DAV:supported-query-grammar-set (protected) 639 This WebDAV property is required for any server supporting either 640 [RFC3253] and/or [RFC3744] and identifies the XML based query 641 grammars that are supported by the search arbiter resource. 643 644 645 647 ANY value: a query grammar element type 649 3.4 Example: Grammar Discovery 651 This example shows that the server supports search on the /somefolder 652 resource with the query grammars: DAV:basicsearch, 653 http://foobar.test/syntax1 and http://akuma.test/syntax2. Note that 654 every server MUST support DAV:basicsearch. 656 >> Request: 658 OPTIONS /somefolder HTTP/1.1 659 Host: example.org 661 >> Response: 663 HTTP/1.1 200 OK 664 Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE 665 Allow: MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, SEARCH 666 DASL: 667 DASL: 668 DASL: 670 This example shows the equivalent taking advantage of a server's 671 support for DAV:supported-method-set and DAV:supported-query-grammar- 672 set. 674 >> Request: 676 PROPFIND /somefolder HTTP/1.1 677 Host: example.org 678 Depth: 0 679 Content-Type: text/xml; charset="utf-8" 680 Content-Length: xxx 682 683 684 685 686 687 688 689 >> Response: 691 HTTP/1.1 207 Multi-Status 692 Content-Type: text/xml; charset="utf-8" 693 Content-Length: xxx 695 696 697 698 http://example.org/somefolder 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 728 729 730 HTTP/1.1 200 OK 731 732 733 735 Note that the query grammar element names marshalled as part of the 736 DAV:supported-query-grammar-set can be directly used as element names 737 in an XML based query. 739 4. Query Schema Discovery: QSD 741 Servers MAY support the discovery of the schema for a query grammar. 743 The DASL response header and the DAV:supported-query-grammar-set 744 property provide means for clients to discover the set of query 745 grammars supported by a resource. This alone is not sufficient 746 information for a client to generate a query. For example, the DAV: 747 basicsearch grammar defines a set of queries consisting of a set of 748 operators applied to a set of properties and values, but the grammar 749 itself does not specify which properties may be used in the query. 750 QSD for the DAV:basicsearch grammar allows a client to discover the 751 set of properties that are searchable, selectable, and sortable. 752 Moreover, although the DAV:basicsearch grammar defines a minimal set 753 of operators, it is possible that a resource might support additional 754 operators in a query. For example, a resource might support a 755 optional operator that can be used to express content-based queries 756 in a proprietary syntax. QSD allows a client to discover these 757 operators and their syntax. The set of discoverable quantities will 758 differ from grammar to grammar, but each grammar can define a means 759 for a client to discover what can be discovered. 761 In general, the schema for a given query grammar depends on both the 762 resource (the arbiter) and the scope. A given resource might have 763 access to one set of properties for one potential scope, and another 764 set for a different scope. For example, consider a server able to 765 search two distinct collections, one holding cooking recipes, the 766 other design documents for nuclear weapons. While both collections 767 might support properties such as author, title, and date, the first 768 might also define properties such as calories and preparation time, 769 while the second defined properties such as yield and applicable 770 patents. Two distinct arbiters indexing the same collection might 771 also have access to different properties. For example, the recipe 772 collection mentioned above might also indexed by a value-added server 773 that also stored the names of chefs who had tested the recipe. Note 774 also that the available query schema might also depend on other 775 factors, such as the identity of the principal conducting the search, 776 but these factors are not exposed in this protocol. 778 4.1 Additional SEARCH semantics 780 Each query grammar supported by DASL defines its own syntax for 781 expressing the possible query schema. A client retrieves the schema 782 for a given query grammar on an arbiter resource with a given scope 783 by invoking the SEARCH method on that arbiter with that grammar and 784 scope and with a root element of DAV:query-schema-discovery rather 785 than DAV:searchrequest. 787 Marshalling: 789 The request body MUST be DAV:query-schema-discovery element. 791 792 794 The response body takes the form of a RFC2518 DAV:multistatus 795 element, where DAV:response is extended to hold the returned query 796 grammar inside a DAV:query-schema container element. 798 800 802 The content of this container is an XML element whose name and syntax 803 depend upon the grammar, and whose value may (and likely will) vary 804 depending upon the grammar, arbiter, and scope. 806 4.1.1 Example of query schema discovery 808 In this example, the arbiter is recipes.test, the grammar is DAV: 809 basicsearch, the scope is also recipes.test. 811 >> Request: 813 SEARCH / HTTP/1.1 814 Host: recipes.test 815 Content-Type: application/xml 816 Content-Length: xxx 818 819 820 821 822 823 http://recipes.test 824 infinity 825 826 827 828 829 >> Response: 831 HTTP/1.1 207 Multistatus 832 Content-Type: application/xml 833 Content-Length: xxx 835 836 837 838 http://recipes.test 839 HTTP/1.1 200 OK 840 841 842 844 845 846 847 849 The query schema for DAV:basicsearch is defined in Section 5.19. 851 5. The DAV:basicsearch Grammar 853 5.1 Introduction 855 DAV:basicsearch uses an extensible XML syntax that allows clients to 856 express search requests that are generally useful for WebDAV 857 scenarios. DASL-extended servers MUST accept this grammar, and MAY 858 accept other grammars. 860 DAV:basicsearch has several components: 862 o DAV:select provides the result record definition. 864 o DAV:from defines the scope. 866 o DAV:where defines the criteria. 868 o DAV:orderby defines the sort order of the result set. 870 o DAV:limit provides constraints on the query as a whole. 872 5.2 The DAV:basicsearch DTD 874 876 878 880 882 884 885 886 888 889 890 891 893 894 896 899 901 903 905 907 908 910 911 913 914 916 917 919 920 922 923 924 926 927 929 930 932 933 935 936 938 939 941 942 944 946 947 949 5.2.1 Example Query 951 This query retrieves the content length values for all resources 952 located under the server's "/container1/" URI namespace whose length 953 exceeds 10000. 955 956 957 958 959 960 961 962 /container1/ 963 infinity 964 965 966 967 968 969 10000 970 971 972 973 974 975 976 977 978 979 981 5.3 DAV:select 983 DAV:select defines the result record, which is a set of properties 984 and values. This document defines two possible values: DAV:allprop 985 and DAV:prop, both defined in [RFC2518] and revised in [RFC3253]. 987 5.4 DAV:from 989 990 992 DAV:from defines the query scope. This contains one or more DAV: 993 scope elements. Support for multiple scope elements is optional, 994 however servers MUST fail a request specifying multiple DAV:scope 995 elements if they can't support it (see Section 2.2.2, precondition 996 DAV:search-multiple-scope-supported). The scope element contains 997 mandatory DAV:href and DAV:depth elements. 999 DAV:href indicates the URI to use as a scope. 1001 When the scope is a collection, if DAV:depth is "0", the search 1002 includes only the collection. When it is "1", the search includes 1003 the (toplevel) members of the collection. When it is "infinity", the 1004 search includes all recursive members of the collection. 1006 When the scope is not a collection, the depth is ignored and the 1007 search applies just to the resource itself. 1009 When the child element DAV:include-versions is present, the search 1010 scope will include all versions (see [RFC3253], section 2.2.1) of all 1011 version-controlled resources in scope. Servers that do support 1012 versioning but do not support the DAV:include-versions feature MUST 1013 signal an error if it is used in a query. 1015 5.4.1 Relationship to the Request-URI 1017 If the DAV:scope element is an absolute URI, the scope is exactly 1018 that URI. 1020 If the DAV:scope element is is an absolute URI reference, the scope 1021 is taken to be relative to the request-URI. 1023 5.4.2 Scope 1025 A Scope can be an arbitrary URI. 1027 Servers, of course, may support only particular scopes. This may 1028 include limitations for particular schemes such as "http:" or "ftp:" 1029 or certain URI namespaces. 1031 5.5 DAV:where 1033 The DAV:where element defines the search condition for inclusion of 1034 resources in the result set. The value of this element is an XML 1035 element that defines a search operator that evaluates to one of the 1036 Boolean truth values TRUE, FALSE, or UNKNOWN. The search operator 1037 contained by DAV:where may itself contain and evaluate additional 1038 search operators as operands, which in turn may contain and evaluate 1039 additional search operators as operands, etc. recursively. 1041 5.5.1 Use of Three-Valued Logic in Queries 1043 Each operator defined for use in the where clause that returns a 1044 Boolean value MUST evaluate to TRUE, FALSE, or UNKNOWN. The resource 1045 under scan is included as a member of the result set if and only if 1046 the search condition evaluates to TRUE. 1048 Consult Appendix A for details on the application of three-valued 1049 logic in query expressions. 1051 5.5.2 Handling Optional operators 1053 If a query contains an operator that is not supported by the server, 1054 then the server MUST respond with a 422 (Unprocessable Entity) status 1055 code. 1057 5.5.3 Treatment of NULL Values 1059 If a PROPFIND for a property value would yield a non-2xx (see 1060 [RFC2616], section 10.2) response for that property, then that 1061 property is considered NULL. 1063 NULL values are "less than" all other values in comparisons. 1065 Empty strings (zero length strings) are not NULL values. An empty 1066 string is "less than" a string with length greater than zero. 1068 The DAV:is-defined operator is defined to test if the value of a 1069 property is NULL. 1071 5.5.4 Treatment of properties with mixed/element content 1073 Comparisons of properties that do not have simple types (text-only 1074 content) is out-of-scope for the standard operators defined for DAV: 1075 basicsearch and therefore is defined to be UNKNOWN (as per 1076 Appendix A). For querying the DAV:resourcetype property, see 1077 Section 5.13. 1079 5.5.5 Example: Testing for Equality 1081 The example shows a single operator (DAV:eq) applied in the criteria. 1083 1084 1085 1086 1087 1088 100 1089 1090 1092 5.5.6 Example: Relative Comparisons 1094 The example shows a more complex operation involving several 1095 operators (DAV:and, DAV:eq, DAV:gt) applied in the criteria. This 1096 DAV:where expression matches those resources that are "image/gifs" 1097 over 4K in size. 1099 1100 1101 1102 1103 1104 1105 image/gif 1106 1107 1108 1109 1110 1111 4096 1112 1113 1114 1116 5.6 DAV:orderby 1118 The DAV:orderby element specifies the ordering of the result set. It 1119 contains one or more DAV:order elements, each of which specifies a 1120 comparison between two items in the result set. Informally, a 1121 comparison specifies a test that determines whether one resource 1122 appears before another in the result set. Comparisons are applied in 1123 the order they occur in the DAV:orderby element, earlier comparisons 1124 being more significant. 1126 The comparisons defined here use only a single property from each 1127 resource, compared using the same ordering as the DAV:lt operator 1128 (ascending) or DAV:gt operator (descending). If neither direction is 1129 specified, the default is DAV:ascending. 1131 In the context of the DAV:orderby element, null values are considered 1132 to collate before any actual (i.e., non null) value, including 1133 strings of zero length (this is compatible with [SQL99]). 1135 5.6.1 Comparing Natural Language Strings 1137 Comparisons on strings take into account the language defined for 1138 that property. Clients MAY specify the language using the xml:lang 1139 attribute. If no language is specified either by the client or 1140 defined for that property by the server or if a comparison is 1141 performed on strings of two different languages, the results are 1142 undefined. 1144 The "caseless" attribute may be used to indicate case-sensitivity for 1145 comparisons. 1147 5.6.2 Example of Sorting 1149 This sort orders first by last name of the author, and then by size, 1150 in descending order, so that for each author, the largest works 1151 appear first. 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1164 5.7 Boolean Operators: DAV:and, DAV:or, and DAV:not 1166 The DAV:and operator performs a logical AND operation on the 1167 expressions it contains. 1169 The DAV:or operator performs a logical OR operation on the values it 1170 contains. 1172 The DAV:not operator performs a logical NOT operation on the values 1173 it contains. 1175 5.8 DAV:eq 1177 The DAV:eq operator provides simple equality matching on property 1178 values. 1180 The "caseless" attribute may be used with this element. 1182 5.9 DAV:lt, DAV:lte, DAV:gt, DAV:gte 1184 The DAV:lt, DAV:lte, DAV:gt, and DAV:gte operators provide 1185 comparisons on property values, using less-than, less-than or equal, 1186 greater-than, and greater-than or equal respectively. The "caseless" 1187 attribute may be used with these elements. 1189 5.10 DAV:literal 1191 DAV:literal allows literal values to be placed in an expression. 1193 White space in literal values is significant in comparisons. For 1194 consistency with [RFC2518], clients SHOULD NOT specify the attribute 1195 "xml:space" (section 2.10 of [XML]) to override this behaviour. 1197 In comparisons, the contents of DAV:literal SHOULD be treated as 1198 string, with the following exceptions: 1200 o when operand for a comparison with a DAV:getcontentlength 1201 property, it SHOULD be treated as an integer value (the behaviour 1202 for non-integer values is undefined), 1204 o when operand for a comparison with a DAV:creationdate or DAV: 1205 getlastmodified property, it SHOULD be treated as a date value in 1206 the ISO-8601 subset defined for the DAV:creationdate property 1207 ([RFC2518], section 13.1). 1209 o when operand for a comparison with a property for which the type 1210 is known, it MAY be treated according to this type. 1212 5.11 DAV:typed-literal (optional) 1214 There are situations in which a client may want to force a comparison 1215 not to be string-based (as defined for DAV:literal). In these cases, 1216 a typed comparison can be enforced by using DAV:typed-literal 1217 instead. 1219 1221 The data type is specified using the xsi:type attribute defined in 1223 [XS1], section 2.6.1. If the type is not specified, it defaults to 1224 "xs:string". 1226 A server MUST reject a request with an unknown type. 1228 5.11.1 Example for typed numerical comparison 1230 Consider a set of resources with the dead property "edits" in the 1231 namespace "http://ns.example.org": 1233 +-----+----------------+ 1234 | URI | property value | 1235 +-----+----------------+ 1236 | /a | "-1" | 1237 | /b | "01" | 1238 | /c | "3" | 1239 | /d | "test" | 1240 | /e | (undefined) | 1241 +-----+----------------+ 1243 The expression 1245 1248 1249 3 1250 1252 will evaluate to TRUE for the resources "/a" and "/b" (their property 1253 values can be parsed as type xs:number, and the numerical comparison 1254 evaluates to true), to FALSE for "/c" (property value is compatible, 1255 but numerical comparison evaluates to false) and UNKNOWN for "/d" and 1256 "/e" (the property either is undefined, or its value can not be 1257 parsed as xs:number). 1259 5.12 Support for matching xml:lang attributes on properties 1261 The following two optional operators can be used to express 1262 conditions on the language of a property value (as expressed using 1263 the xml:lang attribute). 1265 5.12.1 DAV:language-defined (optional) 1267 1269 This operator evaluates to TRUE if the language for the value of the 1270 given property is known, FALSE if it isn't and UNKNOWN if the 1271 property itself is not defined. 1273 5.12.2 DAV:language-matches (optional) 1275 1277 This operator evaluates to TRUE if the language for the value of the 1278 given property is known and matches the language name given in the 1279 element, FALSE if it doesn't match and UNKNOWN if the 1280 property itself is not defined. 1282 Languages are considered to match if they are the same, or if the 1283 language of the property value is a sublanguage of the language 1284 specified in the element (see [XPATH], section 4.3, "lang 1285 function"). 1287 5.12.3 Example of language-aware matching 1289 The expression below will evaluate to TRUE if the property "foobar" 1290 exists and it's language is either unknown, English or a sublanguage 1291 of English. 1293 1294 1295 1296 1297 1298 1299 1300 1301 en 1302 1303 1305 5.13 DAV:is-collection 1307 The DAV:is-collection operator allows clients to determine whether a 1308 resource is a collection (that is, whether it's DAV:resourcetype 1309 element contains the element DAV:collection). 1311 Rationale: This operator is provided in lieu of defining generic 1312 structure queries, which would suffice for this and for many more 1313 powerful queries, but seems inappropriate to standardize at this 1314 time. 1316 5.13.1 Example of DAV:is-collection 1318 This example shows a search criterion that picks out all and only the 1319 resources in the scope that are collections. 1321 1322 1323 1325 5.14 DAV:is-defined 1327 The DAV:is-defined operator allows clients to determine whether a 1328 property is defined on a resource. The meaning of "defined on a 1329 resource" is found in Section 5.5.3. 1331 Example: 1333 1334 1335 1337 5.15 DAV:like 1339 The DAV:like is an optional operator intended to give simple 1340 wildcard-based pattern matching ability to clients. 1342 The operator takes two arguments. 1344 The first argument is a DAV:prop element identifying a single 1345 property to evaluate. 1347 The second argument is a DAV:literal element that gives the pattern 1348 matching string. 1350 5.15.1 Syntax for the Literal Pattern 1352 pattern = [wildcard] 0*( text [wildcard] ) 1354 wildcard = exactlyone / zeroormore 1355 text = 1*( character / escapeseq ) 1357 exactlyone = "_" 1358 zeroormore = "%" 1359 escapechar = "\" 1360 escapeseq = "\" ( exactlyone / zeroormore / escapechar ) 1362 ; character: see [XML], section 2.2, minus wildcard / escapechar 1363 character = HTAB / LF / CR ; whitespace 1364 character =/ %x20-24 / %x26-5B / %x5D-5E / %x60-D7FF 1365 character =/ %xE000-FFFD / %x10000-10FFFF 1367 The value for the literal is composed of wildcards separated by 1368 segments of text. Wildcards may begin or end the literal. 1370 The "_" wildcard matches exactly one character. 1372 The "%" wildcard matches zero or more characters 1374 The "\" character is an escape sequence so that the literal can 1375 include "_" and "%". To include the "\" character in the pattern, 1376 the escape sequence "\\" is used. 1378 5.15.2 Example of DAV:like 1380 This example shows how a client might use DAV:like to identify those 1381 resources whose content type was a subtype of image. 1383 1384 1385 1386 image/% 1387 1388 1390 5.16 DAV:contains 1392 The DAV:contains operator is an optional operator that provides 1393 content-based search capability. This operator implicitly searches 1394 against the text content of a resource, not against content of 1395 properties. The DAV:contains operator is intentionally not overly 1396 constrained, in order to allow the server to do the best job it can 1397 in performing the search. 1399 The DAV:contains operator evaluates to a Boolean value. It evaluates 1400 to TRUE if the content of the resource satisfies the search. 1401 Otherwise, It evaluates to FALSE. 1403 Within the DAV:contains XML element, the client provides a phrase: a 1404 single word or whitespace delimited sequence of words. Servers MAY 1405 ignore punctuation in a phrase. Case-sensitivity is left to the 1406 server. 1408 The following things may or may not be done as part of the search: 1409 Phonetic methods such as "soundex" may or may not be used. Word 1410 stemming may or may not be performed. Thesaurus expansion of words 1411 may or may not be done. Right or left truncation may or may not be 1412 performed. The search may be case insensitive or case sensitive. 1413 The word or words may or may not be interpreted as names. Multiple 1414 words may or may not be required to be adjacent or "near" each other. 1415 Multiple words may or may not be required to occur in the same order. 1416 Multiple words may or may not be treated as a phrase. The search may 1417 or may not be interpreted as a request to find documents "similar" to 1418 the string operand. 1420 5.16.1 Result scoring (DAV:score element) 1422 Servers SHOULD indicate scores for the DAV:contains condition by 1423 adding a DAV:score XML element to the DAV:response element. It's 1424 value is defined only in the context of a particular query result. 1425 The value is a string representing the score, an integer from zero to 1426 10000 inclusive, where a higher value indicates a higher score (e.g. 1427 more relevant). 1429 Modified DTD fragment for DAV:propstat: 1431 1433 1435 Clients should note that, in general, it is not meaningful to compare 1436 the numeric values of scores from two different query results unless 1437 both were executed by the same underlying search system on the same 1438 collection of resources. 1440 5.16.2 Ordering by score 1442 To order search results by their score, the DAV:score element may be 1443 added as child to the DAV:orderby element (in place of a DAV:prop 1444 element). 1446 5.16.3 Examples 1448 The example below shows a search for the phrase "Peter Forsberg". 1450 Depending on its support for content-based searching, a server MAY 1451 treat this as a search for documents that contain the words "Peter" 1452 and "Forsberg". 1454 1455 Peter Forsberg 1456 1458 The example below shows a search for resources that contain "Peter" 1459 and "Forsberg". 1461 1462 1463 Peter 1464 Forsberg 1465 1466 1468 5.17 Limiting the result set 1470 1471 ;only digits 1473 The DAV:limit XML element contains requested limits from the client 1474 to limit the size of the reply or amount of effort expended by the 1475 server. The DAV:nresults XML element contains a requested maximum 1476 number of DAV:response elements to be returned in the response body. 1477 The server MAY disregard this limit. The value of this element is an 1478 integer. 1480 5.17.1 Relationship to result ordering 1482 If the result set is both limited by DAV:limit and ordered according 1483 to DAV:orderby, the results that are included in the response 1484 document must be those that order highest. 1486 5.18 The 'caseless' XML attribute 1488 The "caseless" attribute allows clients to specify caseless matching 1489 behaviour instead of character-by-character matching for DAV: 1490 basicsearch operators. 1492 The possible values for "caseless" are "yes" or "no". The default 1493 value is server-specified. Caseless matching SHOULD be implemented 1494 as defined in section 5.18 of the Unicode Standard ([UNICODE4]). 1496 Support for the "caseless" attribute is optional. A server should 1497 respond with a status of 422 if it is used but cannot be supported. 1499 5.19 Query schema for DAV:basicsearch 1501 The DAV:basicsearch grammar defines a search criteria that is a 1502 Boolean-valued expression, and allows for an arbitrary set of 1503 properties to be included in the result record. The result set may 1504 be sorted on a set of property values. Accordingly the DTD for 1505 schema discovery for this grammar allows the server to express: 1507 1. the set of properties that may be either searched, returned, or 1508 used to sort, and a hint about the data type of such properties 1510 2. the set of optional operators defined by the resource. 1512 5.19.1 DTD for DAV:basicsearch QSD 1514 1515 1516 1517 1520 1521 1522 1523 1525 The DAV:properties element holds a list of descriptions of 1526 properties. 1528 The DAV:operators element describes the optional operators that may 1529 be used in a DAV:where element. 1531 5.19.2 DAV:propdesc Element 1533 Each instance of a DAV:propdesc element describes the property or 1534 properties in the DAV:prop element it contains. All subsequent 1535 elements are descriptions that apply to those properties. All 1536 descriptions are optional and may appear in any order. Servers 1537 SHOULD support all the descriptions defined here, and MAY define 1538 others. 1540 DASL defines five descriptions. The first, DAV:datatype, provides a 1541 hint about the type of the property value, and may be useful to a 1542 user interface prompting for a value. The remaining four (DAV: 1543 searchable, DAV:selectable, DAV:sortable, and DAV:caseless) identify 1544 portions of the query (DAV:where, DAV:select, and DAV:orderby, 1545 respectively). If a property has a description for a section, then 1546 the server MUST allow the property to be used in that section. These 1547 descriptions are optional. If a property does not have such a 1548 description, or is not described at all, then the server MAY still 1549 allow the property to be used in the corresponding section. 1551 5.19.2.1 DAV:any-other-property 1553 This element can be used in place of DAV:prop to describe properties 1554 of WebDAV properties not mentioned in any other DAV:prop element. 1555 For instance, this can be used to indicate that all other properties 1556 are searchable and selectable without giving details about their 1557 types (a typical scenario for dead properties). 1559 5.19.3 The DAV:datatype Property Description 1561 The DAV:datatype element contains a single XML element that provides 1562 a hint about the domain of the property, which may be useful to a 1563 user interface prompting for a value to be used in a query. 1564 Datatypes are identified by an element name. Where appropriate, a 1565 server SHOULD use the simple datatypes defined in [XS2]. 1567 1569 Examples from [XS2], section 3: 1571 +----------------+---------------------+ 1572 | Qualified name | Example | 1573 +----------------+---------------------+ 1574 | xs:boolean | true, false, 1, 0 | 1575 | xs:string | Foobar | 1576 | xs:dateTime | 1994-11-05T08:15:5Z | 1577 | xs:float | .314159265358979E+1 | 1578 | xs:integer | -259, 23 | 1579 +----------------+---------------------+ 1581 If the data type of a property is not given, then the data type 1582 defaults to xs:string. 1584 5.19.4 The DAV:searchable Property Description 1586 1588 If this element is present, then the server MUST allow this property 1589 to appear within a DAV:where element where an operator allows a 1590 property. Allowing a search does not mean that the property is 1591 guaranteed to be defined on every resource in the scope, it only 1592 indicates the server's willingness to check. 1594 5.19.5 The DAV:selectable Property Description 1596 1598 This element indicates that the property may appear in the DAV:select 1599 element. 1601 5.19.6 The DAV:sortable Property Description 1603 This element indicates that the property may appear in the DAV: 1604 orderby element. 1606 1608 5.19.7 The DAV:caseless Property Description 1610 This element only applies to properties whose data type is "xs: 1611 string" and derived data types as per the DAV:datatype property 1612 description. Its presence indicates that compares performed for 1613 searches, and the comparisons for ordering results on the string 1614 property will be caseless (the default is character-by-character). 1616 1618 5.19.8 The DAV:operators XML Element 1620 The DAV:operators element describes every optional operator supported 1621 in a query. (Mandatory operators are not listed since they are 1622 mandatory and permit no variation in syntax.). All optional 1623 operators that are supported MUST be listed in the DAV:operators 1624 element. The listing for an operator consists of the operator (as an 1625 empty element), followed by one element for each operand. The 1626 operand MUST be either DAV:operand-property or DAV:operand-literal, 1627 which indicate that the operand in the corresponding position is a 1628 property or a literal value, respectively. If an operator is 1629 polymorphic (allows more than one operand syntax) then each permitted 1630 syntax MUST be listed separately. 1632 1633 1634 1635 1636 1638 5.19.9 Example of Query Schema for DAV:basicsearch 1640 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1668 This response lists four properties. The datatype of the last three 1669 properties is not given, so it defaults to xs:string. All are 1670 selectable, and the first three may be searched. All but the last 1671 may be used in a sort. Of the optional DAV operators, DAV:is-defined 1672 and DAV:like are supported. 1674 Note: The schema discovery defined here does not provide for 1675 discovery of supported values of the "caseless" attribute. This may 1676 require that the reply also list the mandatory operators. 1678 6. Internationalization Considerations 1680 Properties may be language-tagged using the xml:lang attribute (see 1681 [RFC2518], section 4.4). The optional operators DAV:language-defined 1682 (Section 5.12.1) and DAV:language-matches (Section 5.12.2) allow to 1683 express conditions on the language tagging information. 1685 7. Security Considerations 1687 This section is provided to detail issues concerning security 1688 implications of which DASL applications need to be aware. All of the 1689 security considerations of HTTP/1.1 also apply to DASL. In addition, 1690 this section will include security risks inherent in searching and 1691 retrieval of resource properties and content. 1693 A query must not allow one to retrieve information about values or 1694 existence of properties that one could not obtain via PROPFIND. (e.g. 1695 by use in DAV:orderby, or in expressions on properties.) 1697 A server should prepare for denial of service attacks. For example a 1698 client may issue a query for which the result set is expensive to 1699 calculate or transmit because many resources match or must be 1700 evaluated. 1702 7.1 Implications of XML External Entities 1704 XML supports a facility known as "external entities", defined in 1705 section 4.2.2 of [XML], which instruct an XML processor to retrieve 1706 and perform an inline include of XML located at a particular URI. An 1707 external XML entity can be used to append or modify the document type 1708 declaration (DTD) associated with an XML document. An external XML 1709 entity can also be used to include XML within the content of an XML 1710 document. For non-validating XML, such as the XML used in this 1711 specification, including an external XML entity is not required by 1712 [XML]. However, [XML] does state that an XML processor may, at its 1713 discretion, include the external XML entity. 1715 External XML entities have no inherent trustworthiness and are 1716 subject to all the attacks that are endemic to any HTTP GET request. 1717 Furthermore, it is possible for an external XML entity to modify the 1718 DTD, and hence affect the final form of an XML document, in the worst 1719 case significantly modifying its semantics, or exposing the XML 1720 processor to the security risks discussed in [RFC3023]. Therefore, 1721 implementers must be aware that external XML entities should be 1722 treated as untrustworthy. 1724 There is also the scalability risk that would accompany a widely 1725 deployed application which made use of external XML entities. In 1726 this situation, it is possible that there would be significant 1727 numbers of requests for one external XML entity, potentially 1728 overloading any server which fields requests for the resource 1729 containing the external XML entity. 1731 8. Scalability 1733 Query grammars are identified by URIs. Applications SHOULD not 1734 attempt to retrieve these URIs even if they appear to be retrievable 1735 (for example, those that begin with "http://") 1737 9. Authentication 1739 Authentication mechanisms defined in WebDAV will also apply to DASL. 1741 10. IANA Considerations 1743 This document uses the namespace defined by [RFC2518] for XML 1744 elements. All other IANA considerations mentioned in [RFC2518] are 1745 also applicable to DASL. 1747 11. Contributors 1749 This document is based on prior work on the DASL protocol done by the 1750 WebDAV DASL working group until the year 2000 -- namely by Alan 1751 Babich, Jim Davis, Rick Henderson, Dale Lowry, Saveen Reddy and 1752 Surendra Reddy. 1754 12. Acknowledgements 1756 This document has benefited from thoughtful discussion by Lisa 1757 Dusseault, Sung Kim, Elias Sinderson, Martin Wallmer, Keith 1758 Wannamaker, Jim Whitehead and Kevin Wiggen. 1760 13. References 1762 13.1 Normative References 1764 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1765 Requirement Levels", BCP 14, RFC 2119, March 1997. 1767 [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. 1768 Jensen, "HTTP Extensions for Distributed Authoring -- 1769 WEBDAV", RFC 2518, February 1999. 1771 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., 1772 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 1773 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 1775 [RFC3023] Makoto, M., St.Laurent, S., and D. Kohn, "XML Media 1776 Types", RFC 3023, January 2001. 1778 [RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. 1780 Whitehead, "Versioning Extensions to WebDAV", RFC 3253, 1781 March 2002. 1783 [RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web 1784 Distributed Authoring and Versioning (WebDAV) Access 1785 Control Protocol", RFC 3744, May 2004. 1787 [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 1788 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third 1789 Edition)", W3C REC-xml-20040204, February 2004, 1790 . 1792 [XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath) 1793 Version 1.0", W3C REC-xpath-19991116, November 1999, 1794 . 1796 [XS1] Thompson, H., Beech, D., Maloney, M., Mendelsohn, N., and 1797 World Wide Web Consortium, "XML Schema Part 1: 1798 Structures", W3C REC-xmlschema-1-20041028, October 2004, 1799 . 1801 [XS2] Biron, P., Malhotra, A., and World Wide Web Consortium, 1802 "XML Schema Part 2: Datatypes Second Edition", W3C REC- 1803 xmlschema-2-20041028, October 2004, 1804 . 1806 [draft-crocker-abnf-rfc2234bis] 1807 Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 1808 Specifications: ABNF", draft-crocker-abnf-rfc2234bis-00 1809 (work in progress), March 2005. 1811 Work in progress. 1813 13.2 Informative References 1815 [BIND] Clemm, G., Crawford, J., Reschke, J., Slein, J., and J. 1816 Whitehead, "Binding Extensions to WebDAV", 1817 draft-ietf-webdav-bind-11 (work in progress), 1818 February 2005, . 1821 Work in progress. 1823 [DASL] Reddy, S., Lowry, D., Reddy, S., Henderson, R., Davis, J., 1824 and A. Babich, "DAV Searching & Locating", 1825 draft-ietf-dasl-protocol-00 (work in progress), July 1999, 1826 . 1829 [DASLREQ] Davis, J., Reddy, S., and J. Slein, "Requirements for DAV 1830 Searching and Locating", February 1999, . 1834 This is an updated version of the Internet Draft 1835 "draft-ietf-dasl-requirements-00", but obviously never was 1836 submitted to the IETF. 1838 [SQL99] Milton, J., "Database Language SQL Part 2: Foundation 1839 (SQL/Foundation)", ISO ISO/IEC 9075-2:1999 (E), July 1999. 1841 [UNICODE4] 1842 The Unicode Consortium, "The Unicode Standard - Version 1843 4.0", Addison-Wesley , August 2003, 1844 . 1846 ISBN 0321185781 [4] 1848 URIs 1850 [4] 1852 Authors' Addresses 1854 Julian F. Reschke (editor) 1855 greenbytes GmbH 1856 Salzmannstrasse 152 1857 Muenster, NW 48159 1858 Germany 1860 Phone: +49 251 2807760 1861 Fax: +49 251 2807761 1862 Email: julian.reschke@greenbytes.de 1863 URI: http://greenbytes.de/tech/webdav/ 1865 Surendra Reddy 1866 Oracle Corporation 1867 600 Oracle Parkway, M/S 6op3 1868 Redwoodshores, CA 94065 1870 Phone: +1 650 506 5441 1871 Email: Surendra.Reddy@oracle.com 1872 Jim Davis 1873 Intelligent Markets 1874 410 Jessie Street 6th floor 1875 San Francisco, CA 94103 1877 Email: jrd3@alum.mit.edu 1879 Alan Babich 1880 FileNET Corp. 1881 3565 Harbor Blvd. 1882 Costa Mesa, CA 92626 1884 Phone: +1 714 327 3403 1885 Email: ababich@filenet.com 1887 Appendix A. Three-Valued Logic in DAV:basicsearch 1889 ANSI standard three valued logic is used when evaluating the search 1890 condition (as defined in the ANSI standard SQL specifications, for 1891 example in ANSI X3.135-1992, section 8.12, pp. 188-189, section 8.2, 1892 p. 169, General Rule 1)a), etc.). 1894 ANSI standard three valued logic is undoubtedly the most widely 1895 practiced method of dealing with the issues of properties in the 1896 search condition not having a value (e.g., being null or not defined) 1897 for the resource under scan, and with undefined expressions in the 1898 search condition (e.g., division by zero, etc.). Three valued logic 1899 works as follows. 1901 Undefined expressions are expressions for which the value of the 1902 expression is not defined. Undefined expressions are a completely 1903 separate concept from the truth value UNKNOWN, which is, in fact, 1904 well defined. Property names and literal constants are considered 1905 expressions for purposes of this section. If a property in the 1906 current resource under scan has not been set to a value, then the 1907 value of that property is undefined for the resource under scan. 1908 DASL 1.0 has no arithmetic division operator, but if it did, division 1909 by zero would be an undefined arithmetic expression. 1911 If any subpart of an arithmetic, string, or datetime subexpression is 1912 undefined, the whole arithmetic, string, or datetime subexpression is 1913 undefined. 1915 There are no manifest constants to explicitly represent undefined 1916 number, string, or datetime values. 1918 Since a Boolean value is ultimately returned by the search condition, 1919 arithmetic, string, and datetime expressions are always arguments to 1920 other operators. Examples of operators that convert arithmetic, 1921 string, and datetime expressions to Boolean values are the six 1922 relational operators ("greater than", "less than", "equals", etc.). 1923 If either or both operands of a relational operator have undefined 1924 values, then the relational operator evaluates to UNKNOWN. 1925 Otherwise, the relational operator evaluates to TRUE or FALSE, 1926 depending upon the outcome of the comparison. 1928 The Boolean operators DAV:and, DAV:or and DAV:not are evaluated 1929 according to the following rules: 1931 not UNKNOWN = UNKNOWN 1933 UNKNOWN and TRUE = UNKNOWN 1935 UNKNOWN and FALSE = FALSE 1937 UNKNOWN and UNKNOWN = UNKNOWN 1939 UNKNOWN or TRUE = TRUE 1941 UNKNOWN or FALSE = UNKNOWN 1943 UNKNOWN or UNKNOWN = UNKNOWN 1945 Appendix B. Change Log (to be removed by RFC Editor before publication) 1947 B.1 From draft-davis-dasl-protocol-xxx 1949 Feb 14, 1998 Initial Draft 1951 Feb 28, 1998 Referring to DASL as an extension to HTTP/1.1 rather 1952 than DAV. 1953 Added new sections "Notational Conventions", "Protocol Model", 1954 "Security Considerations". 1955 Changed section 3 to "Elements of Protocol". 1956 Added some stuff to introduction. 1957 Added "result set" terminology. 1958 Added "IANA Considerations". 1960 Mar 9, 1998 Moved sub-headings of "Elements of Protocol" to first 1961 level and removed "Elements of Protocol" Heading. 1962 Added an sentence in introduction explaining that this is a 1963 "sketch" of a protocol. 1965 Mar 11, 1998 Added orderby, data typing, three valued logic, query 1966 schema property, and element definitions for schema for 1967 basicsearch. 1969 April 8, 1998 - made changes based on last week's DASL BOF. 1971 May 8, 1998 Removed most of DAV:searcherror; converted to DAV: 1972 searchredirect 1973 Altered DAV:basicsearch grammar to use avoid use of ANY in DTD 1975 June 17, 1998 -Added details on Query Schema Discovery 1976 -Shortened list of data types 1978 June 23, 1998 moved data types before change history 1979 rewrote the data types section 1980 removed the casesensitive element and replace with the 1981 casesensitive attribute 1982 added the casesensitive attribute to the DTD for all operations 1983 that might work on a string 1985 Jul 20, 1998 A series of changes. See Author's meeting minutes for 1986 details. 1988 July 28, 1998 Changes as per author's meeting. QSD uses SEARCH, not 1989 PROPFIND. 1990 Moved text around to keep concepts nearby. 1991 Boolean literals are 1 and 0, not T and F. 1992 contains changed to contentspassthrough. 1993 Renamed rank to score. 1995 July 28, 1998 Added Dale Lowry as Author 1997 September 4, 1998 Added 422 as response when query lists 1998 unimplemented operators. 1999 DAV:literal declares a default value for xml:space, 'preserve' 2000 (see XML spec, section 2.10) 2001 moved to new XML namespace syntax 2003 September 22, 1998 Changed "simplesearch" to "basicsearch" 2004 Changed isnull to isdefined 2005 Defined NULLness as having a 404 or 403 response 2006 used ENTITY syntax in DTD 2007 Added redirect 2009 October 9, 1998 Fixed a series of typographical and formatting 2010 errors. 2011 Modified the section of three-valued logic to use a table rather 2012 than a text description of the role of UNKNOWN in expressions. 2014 November 2, 1998 Added the DAV:contains operator. 2015 Removed the DAV:contentpassthrough operator. 2017 November 18, 1998 Various author comments for submission 2019 June 3, 1999 Cosmetic and minor editorial changes only. Fix nits 2020 reported by Jim Whitehead in email of April 26, 1999. Converted 2021 to HTML from Word 97, manually. 2023 April 20, 2000 Removed redirection feature, since 301/302 suffices. 2024 Removed Query Schema Discovery (former chapter 4). Everyone 2025 agrees this is a useful feature, but it is apparently too 2026 difficult to define at this time, and it is not essential for 2027 DASL. 2029 B.2 since start of draft-reschke-webdav-search 2031 October 09, 2001 Added Julian Reschke as author. 2032 Chapter about QSD re-added. 2033 Formatted into RFC2629-compliant XML document. 2034 Added first comments. 2035 ID version number kicked up to draft-dasl-protocol-03. 2037 October 17, 2001 Updated address information for Jim Davis. 2038 Added issue of datatype vocabularies. 2039 Updated issue descriptions for grammar discovery, added issues on 2040 query schema DTD. 2041 Fixed typos in XML examples. 2043 December 17, 2001 Re-introduced split between normative and non- 2044 normative references. 2046 January 05, 2002 Version bumbed up to 04. Started work on resolving 2047 the issues identified in the previous version. 2049 January 14, 2002 Fixed some XML typos. 2051 January 22, 2002 Closed issues naming-of-elements. Fixed query 2052 search DTD and added option to discover properties of "other" 2053 (non-listed) properties. 2055 January 25, 2002 Changed into private submission and added reference 2056 to historic DASL draft. Marked reference to DASL requirements 2057 non-normative. 2058 Updated reference to latest deltav spec. 2060 January 29, 2002 Added feedback from and updated contact info for 2061 Alan Babich. 2062 Included open issues collected in 2063 http://www.webdav.org/dasl/protocol/issues.html. 2065 February 8, 2002 Made sure that all artwork fits into 72 characters 2066 wide text. 2068 February 18, 2002 Changed Insufficient storage handling 2069 (multistatus). Moved is-collection to operators and added to DTD. 2070 Made scope/depth mandatory. 2072 February 20, 2002 Updated reference to SQL99. 2074 February 28, 2002 "Non-normative References" -> "Informative 2075 References". Abstract updated. Consistently specify a charset 2076 when using text/xml (no change bars). Do not attempt to define 2077 PROPFIND's entity encoding (take out specific references to text/ 2078 xml). Remove irrelevant headers (Connection:) from examples (no 2079 change bars). Added issue on querying based on DAV:href. Updated 2080 introduction to indicate relationship to DASL draft. Updated HTTP 2081 reference from RFC2068 to RFC2616. Updated XML reference to XML 2082 1.0 2nd edition. 2084 March 1, 2002 Removed superfluous namespace decl in 2.4.2. Reopened 2085 JW14 and suggest to drop xml:space support. 2087 March 3, 2002 Removed "xml:space" feature on DAV:literal. Added 2088 issue about string comparison vs. collations vs. xml:lang. 2089 Updated some of the open issues with details from JimW's original 2090 mail in April 1999. Resolved scope vs relative URI references. 2091 Resolved issues about DAV:ascending (added to index) and the BNF 2092 for DAV:like (changed "octets" to "characters"). 2094 March 8, 2002 Updated reference to DeltaV (now RFC3253). Added 2095 Martin Wallmer's comments, moved JW5 into DAV:basicsearch section. 2097 March 11, 2002 Closed open issues regaring the type of search 2098 arbiters (JW3) and their discovery (JW9). Rephrased requirements 2099 on multistatus response bodies (propstat only if properties were 2100 selected, removed requirement for responsedescription). 2102 March 23, 2002 RFC2376 -> RFC3023. Added missing first names of 2103 authors. OPTIONS added to example for DAV:supported-method-set. 2105 B.3 since draft-reschke-webdav-search-00 2107 March 29, 2002 Abstract doesn't refer to DASL WG anymore. 2109 April 7, 2002 Fixed section title (wrong property name supported- 2110 search-grammar-set. Changed DAV:casesensitve to "casesensitive" 2111 (it wasn't in the DAV: namespace after all). 2113 May 28, 2002 Updated some issues with Jim Davis's comments. 2115 June 10, 2002 Added proposal for different method for query schema 2116 discovery, not using pseudo-properties. 2118 June 25, 2002 QSD marshalling rewritten. Added issue "isdefined- 2119 optional". 2121 B.4 since draft-reschke-webdav-search-01 2123 July 04, 2002 Added issue "scope-collection". 2125 July 08, 2002 Closed issue "scope-collection". 2127 August 12, 2002 Added issues "results-vs-binds" and "select-allprop". 2129 October 22, 2002 Added issue "undefined-expressions". 2131 November 18, 2002 Changed example host names (no change tracking). 2133 November 25, 2002 Updated issue "DB2/DB7". Closed issues "undefined 2134 expressions", "isdefined-optional" and "select-allprop". 2136 B.5 since draft-reschke-webdav-search-02 2138 November 27, 2002 Added issues "undefined-properties", "like- 2139 exactlyone" and "like-wildcard-adjacent". Closed issue "query-on- 2140 href". Added acknowledgments section. 2142 November 28, 2002 Closed issue "like-exactlyone". Added issue 2143 "mixed-content-properties". 2145 December 14, 2002 Closed issues "undefined-properties", "results-vs- 2146 binds", "mixed-content-properties". Updated issue "like-wildcard- 2147 adjacent". Added informative reference to BIND draft. Updated 2148 reference to ACL draft. 2150 January 9, 2003 Removed duplicate section on invalid scopes. Added 2151 comments to some open issues. Closed issues JW25/26, score- 2152 pseudo-property and null-ordering. 2154 January 10, 2003 Issue limit-vs-ordering plus resolution. Closed 2155 issue JW17/JW24b. 2157 January 14, 2003 New issue order-precedence. Started resolution of 2158 DB2/DB7. 2160 January 15, 2003 Started spec of DAV:typed-literal. 2162 January 17, 2003 Fix one DAV:like/DAV:getcontenttype example (add / 2163 to like expression, make case-insensitive). 2165 January 28, 2003 Update issue(s) result-truncation, JW24d. Fixed 2166 response headers in OPTIONS example. Added issue qsd-optional. 2167 Closed issue(s) order-precedence, case-insensitivity-name. 2169 February 07, 2003 Added issue scope-vs-versions. score-pseudo- 2170 property: allow DAV:orderby to explicitly specify DAV:score. 2172 B.6 since draft-reschke-webdav-search-03 2174 April 24, 2003 Fixed two "?" vs "_" issues (not updated in last 2175 draft). 2177 June 13, 2003 Improve index. 2179 B.7 since draft-reschke-webdav-search-04 2181 July 7, 2003 Typo fixed (propstat without status element). 2183 August 11, 2003 Remove superfluous IP and copyright sections. 2185 September 09, 2003 Added issues "2.4-multiple-uris" and "5.1-name- 2186 filtering". 2188 October 06, 2003 Fix misplaced section end in 5.11, add table 2189 formatting. Enhance table formatting in 5.18.3. Updated ACL and 2190 BIND references. Added XPATH reference. Closed issue JW24d by 2191 adding new optional operators. Updated more open issues, added 2192 issues from January meeting. Add K. Wiggen to Acknowledgements. 2193 Add Contributors section for the authors of the original draft. 2194 Close issue "scope-vs-versions" (optional feature added). Close 2195 (new) issue "1.3-import-DTD-terminology". Add issue "1.3-import- 2196 requirements-terminology". 2198 October 07, 2003 Typos fixed. Moved statement about DAV: namespace 2199 usage into separate (sub-)section. Closed "1.3-import- 2200 requirements-terminology". Update I18N Considerations with new 2201 xml:lang support info (see issue JW24d). Close issue "DB2/DB7" 2202 (remaining typing issues are now summarized in issue "typed- 2203 literal"). Fix misplaced section end in section 7. Started 2204 change to use RFC3253-style method definitions and error 2205 marshalling. 2207 October 08, 2003 Remove obsolete language that allowed reporting 2208 invalid scopes and such inside multistatus. Add new issue "5.4.2- 2209 scope-vs-redirects". 2211 B.8 since draft-reschke-webdav-search-05 2213 October 11, 2003 Separate DAV:basicsearch DTD into separate figures 2214 for better maintainability. Update DTD with language-* operators 2215 and typed-literal element (optional). 2217 October 14, 2003 Close issue "5.4.2-multiple-scope". 2219 November 04, 2003 Update reference from CaseMap to UNICODE4, section 2220 5.18. 2222 November 16, 2003 Updated issue "5.1-name-filtering". 2224 November 24, 2003 Reformatted scope description (collection vs. non- 2225 collection). 2227 November 30, 2003 Add issue "5_media_type_match". 2229 February 6, 2004 Updated all references. 2231 B.9 since draft-reschke-webdav-search-06 2233 July 05, 2004 Fix table in Appendix "Three-Valued Logic in DAV: 2234 basicsearch". 2236 September 14, 2004 Fix inconsistent DTD in section 5.2 and 5.4 for 2237 scope element. 2239 September 30, 2004 Rewrite editorial note and abstract. Update 2240 references (remove unneeded XMLNS, update ref to ACL and BIND 2241 specs). 2243 B.10 since draft-reschke-webdav-search-07 2245 October 01, 2004 Fix previous section heading (no change tracking). 2247 October 13, 2004 Fix DTD entry for is-collection. 2249 November 1, 2004 Fix DTD fragment query-schema-discovery. 2251 December 11, 2004 Update BIND reference. 2253 January 01, 2005 Fix DASL and DASLREQ references. 2255 February 06, 2005 Update XS2 reference. 2257 February 11, 2005 Rewrite "like" and "DASL" (response header) grammar 2258 in ABNF. 2260 May 5, 2005 Update references. Close issue "abnf" (only use ABNF 2261 when applicable). 2263 Appendix C. Resolved issues (to be removed by RFC Editor before 2264 publication) 2266 Issues that were either rejected or resolved in this version of this 2267 document. 2269 C.1 abnf 2271 Type: change 2273 julian.reschke@greenbytes.de (2005-02-11): Use ABNF syntax from 2274 RFC2234. 2276 julian.reschke@greenbytes.de (2005-05-05): ...where applicable. That 2277 is, stick with RFC2616 grammar for HTTP definitions. 2279 Resolution (2005-05-05): Done. 2281 Appendix D. Open issues (to be removed by RFC Editor prior to 2282 publication) 2284 D.1 edit 2286 Type: edit 2288 julian.reschke@greenbytes.de (2004-07-05): Umbrella issue for 2289 editorial fixes/enhancements. 2291 D.2 1.3-apply-condition-code-terminology 2293 Type: change 2295 julian.reschke@greenbytes.de (2003-10-07): (Umbrella issue that will 2296 be left open until RFC3253 condition terminlogy is used throughout 2297 the document) 2299 D.3 2.4-multiple-uris 2301 Type: change 2303 julian.reschke@greenbytes.de (2003-09-09): However, the set of URIs 2304 for a given resource may be unlimited due to possible bind loops. 2305 Therefore consider to report just one URI per resource. 2307 D.4 result-truncation 2309 Type: change 2311 2314 ldusseault@xythos.com (2002-03-29): I believe the same response body 2315 that contains the first N elements should also contain 2316 a *different* element stating that the results were incomplete and 2317 the result set was truncated by the server. There may also be a need 2318 to report that the results were incomplete and the result set was 2319 truncated at the choice of the client (isn't there a limit set in the 2320 client request?) That's important so the client knows the difference 2321 between receiving 10 results because there were >10 but only 10 were 2322 asked for, and receiving 10 results because there were only exactly 2323 10 results and it just happens that 10 were asked for. 2325 jrd3@alum.mit.edu (2002-05-28): I agree that this could be useful, 2326 but I think this issue should be consolidated with issue JW5 (see 2327 below), which proposes that DASL basicsearch ought to have a way for 2328 client to request additional result sets. It should be moved because 2329 there is little or no value in allowing a client to distinguish 2330 between the case where "N results were requested, and there are 2331 exactly N available" and "N results were requested, and there are 2332 more than N available" if there is no way for client to get the next 2333 batch of results. 2335 julian.reschke@greenbytes.de (2003-01-28): Feedback from interim WG 2336 meeting: agreement that marshalling should be rewritten and backwards 2337 compatibility is not important. Proposal: extend DAV:multistatus by 2338 a new child element that indicates (1) the range that was returned, 2339 (2) the total number of results and (3) a URI identifying the result 2340 (for resubmission when getting the "next" results). Such as 2341 ...identifier for 2342 result set... <-- number of results --> 2343 <-- 1-based index of 1st result --> <-- size 2344 of result set returned --> <-- indicates 2345 that this is a partial result --> ...response 2346 elements for search results... The example below would 2347 then translate to: HTTP/1.1 207 Multistatus Content-Type: text/xml; 2348 charset="utf-8" Content-Length: xxx 2350 2351 http://www.example.net/sounds/unbrokenchain.au 2352 HTTP/1.1 200 OK 2353 2354 http://tech.mit.test/archive96/photos/Lesh1.jpg 2355 HTTP/1.1 200 OK 2356 Q: do we need all 2357 elements, in particular start and length? 2359 julian.reschke@greenbytes.de (2003-10-07): Related: if this is 2360 supposed to be normative to DAV:basicsearch, it can't stay in an 2361 "example" sub-section. 2363 D.5 qsd-optional 2365 Type: change 2367 julian.reschke@greenbytes.de (2003-01-28): WG January meeting 2368 feedback: QSD should be made required. 2370 kwiggen@xythos.com (2003-10-03): (significant pushback, see mailing 2371 list thread at http://lists.w3.org/Archives/Public/www-webdav-dasl/ 2372 2003OctDec/0003.html). 2374 D.6 5.1-name-filtering 2376 Type: change 2378 2380 julian.reschke@greenbytes.de (2003-09-08): This query grammar 2381 supports properties and content, but not conditions on URL elements 2382 (such as the last segment that many WebDAV implementations treat as 2383 "file name"). Discuss possible extension such as adding name filters 2384 to the scope, or adding a specific operator. 2386 Martin.Wallmer@softwareag.com (2003-11-11): Specific proposal to add 2387 this feature as scope restriction, see . 2390 Martin.Wallmer@softwareag.com (2003-11-25): Updated proposal: . 2393 D.7 5_media_type_match 2395 Type: change 2397 julian.reschke@greenbytes.de (2003-11-30): Putting conditions on DAV: 2398 getcontenttype is hard (see is (too?) hard. Proposal for a 2400 specific operator for expressing conditions on the media type: . 2403 D.8 5.4.2-scope-vs-redirects 2405 Type: change 2407 2410 julian.reschke@greenbytes.de (2003-10-08): Clarify the relation of 2411 scope and redirect (3xx) resources. 2413 D.9 language-comparison 2415 Type: change 2417 2420 julian.reschke@greenbytes.de (2002-03-03): XPath/XQuery (see draft, 2421 and open issue) specify string comparisons based on collations, not 2422 languages. I think we should adopt this. This would mean that "xml: 2423 lang" would be removed, and an optional attribute specifying the name 2424 of the collation is added. 2426 julian.reschke@greenbytes.de (2003-01-09): Proposal: adopt "lang" and 2427 "collation" attribute from XSLT 2.0's xsl:sort. 2429 D.10 JW16b/JW24a 2431 Type: change 2433 2436 ejw@ics.uci.edu (2000-04-20): Define how comparisons on strings work, 2437 esp for i18n. Need policy statement about sort order in various 2438 national languages. (JW said "non-Latin" but it's an issue even in 2439 languages that use the latin char set.) 2441 julian.reschke@greenbytes.de (2003-01-28): This issue not only 2442 applies to the comparison operators, but also to ordering! 2444 D.11 typed-literal 2446 Type: change 2448 julian.reschke@greenbytes.de (2003-01-15): 1. (insert language 2449 defining the comparison following the rules defined in 2450 http://www.w3.org/TR/xpath20/#id-comparisons). 2. Extend Basicsearch 2451 QSD grammar to support discovery of typed-literal 3. Update DTD. 4. 2452 Discuss behaviour of DAV:literal when the property's type is known 2453 for the complete search scope (is the server allowed to be "smart"?) 2455 julian.reschke@greenbytes.de (2003-10-11): 3.: done 2457 Index 2459 C 2460 caseless attribute 27, 33 2461 Condition Names 2462 DAV:search-grammar-discovery-supported (pre) 9 2463 DAV:search-grammar-supported (pre) 9 2464 DAV:search-multiple-scope-supported (pre) 9 2465 DAV:search-scope-valid (pre) 9 2466 Criteria 5 2468 D 2469 DAV:and 26 2470 DAV:ascending 26 2471 DAV:contains 31 2472 DAV:depth 23 2473 DAV:descending 26 2474 DAV:eq 27 2475 caseless attribute 27 2476 DAV:from 23 2477 DAV:gt 27 2478 DAV:gte 27 2479 DAV:include-versions 23 2480 DAV:is-collection 29 2481 DAV:is-defined 30 2482 DAV:language-defined 28 2483 DAV:language-matches 29 2484 DAV:like 30 2485 DAV:limit 33 2486 DAV:literal 27 2487 DAV:lt 27 2488 DAV:lte 27 2489 DAV:not 26 2490 DAV:nresults 33 2491 DAV:or 26 2492 DAV:orderby 25 2493 DAV:scope 23 2494 DAV:score 32 2495 relationship to DAV:orderby 33 2496 DAV:search-grammar-discovery-supported precondition 9 2497 DAV:search-grammar-supported precondition 9 2498 DAV:search-multiple-scope-supported precondition 9 2499 DAV:search-scope-valid precondition 9 2500 DAV:select 23 2501 DAV:supported-query-grammar-set property 14 2502 DAV:typed-literal 27 2503 DAV:where 24 2505 M 2506 Methods 2507 SEARCH 8 2509 O 2510 OPTIONS method 13 2511 DASL response header 14 2513 P 2514 Properties 2515 DAV:supported-query-grammar-set 14 2517 Q 2518 Query Grammar Discovery 13 2519 using live property 14 2520 using OPTIONS 13 2521 Query Grammar 6 2522 Query Schema 6 2523 Query 5 2525 R 2526 Result Record Definition 6 2527 Result Record 6 2528 Result Set Truncation 2529 Example 11 2530 Result Set 6 2531 Result 6 2533 S 2534 Scope 6 2535 SEARCH method 8 2536 Search Modifier 6 2537 Sort Specification 6 2539 Intellectual Property Statement 2541 The IETF takes no position regarding the validity or scope of any 2542 Intellectual Property Rights or other rights that might be claimed to 2543 pertain to the implementation or use of the technology described in 2544 this document or the extent to which any license under such rights 2545 might or might not be available; nor does it represent that it has 2546 made any independent effort to identify any such rights. Information 2547 on the procedures with respect to rights in RFC documents can be 2548 found in BCP 78 and BCP 79. 2550 Copies of IPR disclosures made to the IETF Secretariat and any 2551 assurances of licenses to be made available, or the result of an 2552 attempt made to obtain a general license or permission for the use of 2553 such proprietary rights by implementers or users of this 2554 specification can be obtained from the IETF on-line IPR repository at 2555 http://www.ietf.org/ipr. 2557 The IETF invites any interested party to bring to its attention any 2558 copyrights, patents or patent applications, or other proprietary 2559 rights that may cover technology that may be required to implement 2560 this standard. Please address the information to the IETF at 2561 ietf-ipr@ietf.org. 2563 Disclaimer of Validity 2565 This document and the information contained herein are provided on an 2566 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2567 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2568 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2569 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2570 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2571 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2573 Copyright Statement 2575 Copyright (C) The Internet Society (2005). This document is subject 2576 to the rights, licenses and restrictions contained in BCP 78, and 2577 except as set forth therein, the authors retain all their rights. 2579 Acknowledgment 2581 Funding for the RFC Editor function is currently provided by the 2582 Internet Society.