greenbytes GmbH

Hafenweg 16 MuensterNW48155 Germany +49 251 2807760 julian.reschke@greenbytes.de http://greenbytes.de/tech/webdav/

Mitrix, Inc.

303 Twin Dolphin Drive, Suite 600-37 Redwood CityCA94065 U.S.A. +1 408 500 1135 Surendra.Reddy@mitrix.com

27 Borden Street TorontoOntarioM5S 2M8 Canada +1 416 929 5854 jrd3@alum.mit.edu http://www.econetwork.net/~jdavis

IBM Corporation

3565 Harbor Blvd. Costa MesaCA92626 U.S.A. +1 714 327 3403 ababich@us.ibm.com

HTTP Query Properties This document specifies a set of methods, headers, and properties composing Web Distributed Authoring and Versioning (WebDAV) SEARCH, an application of the HTTP/1.1 protocol to efficiently search for DAV resources based upon a set of client-supplied criteria.

This document defines Web Distributed Authoring and Versioning (WebDAV) SEARCH, an application of HTTP/1.1 forming a lightweight search protocol to transport queries and result sets that allows clients to make use of server-side search facilities. It is based on the earlier document "DAV Searching & Locating" . describes the motivation for DASL. In this specification, the terms "WebDAV SEARCH" and "DASL" are used interchangeably. DASL minimizes the complexity of clients so as to facilitate widespread deployment of applications capable of utilizing the DASL search mechanisms. DASL consists of: the SEARCH method and the request/response formats defined for it (), feature discovery through the "DASL" response header and the optional DAV:supported-grammar-set property (), optional grammar schema discovery (), and one mandatory grammar: DAV:basicsearch ().

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

This document uses the terms defined in , , , and in this section. Criteria An expression against which each resource in the search scope is evaluated. Query A query is a combination of a search scope, search criteria, result record definition, sort specification, and a search modifier. Query Grammar A set of definitions of XML elements, attributes, and constraints on their relations and values that defines a set of queries and the intended semantics. Query Schema A listing, for any given grammar and scope, of the properties and operators that may be used in a query with that grammar and scope. Result A result is a result set, optionally augmented with other information describing the search as a whole. Result Record A description of a resource. A result record is a set of properties, and possibly other descriptive information. Result Record Definition A specification of the set of properties to be returned in the result record. Result Set A set of records, one for each resource for which the search criteria evaluated to True. Scope A set of resources to be searched. Search Arbiter A resource that supports the SEARCH method. Search Modifier An instruction that governs the execution of the query but is not part of the search scope, result record definition, the search criteria, or the sort specification. An example of a search modifier is one that controls how much time the server can spend on the query before giving a response. Sort Specification A specification of an ordering on the result records in the result set.

This specification uses the Augmented Backus-Naur Form (ABNF) notation of , unless explicitly stated otherwise. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . This document uses XML DTD fragments (, Section 3.2) as a purely notational convention. WebDAV request and response bodies cannot be validated by a DTD due to the specific extensibility rules defined in Section 17 of and due to the fact that all XML elements defined by this specification use the XML namespace name "DAV:". In particular: element names use the "DAV:" namespace, element ordering is irrelevant unless explicitly stated, extension elements (elements not already defined as valid child elements) may be added anywhere, except when explicitly stated otherwise, extension attributes (attributes not already defined as valid for this element) may be added anywhere, except when explicitly stated otherwise. When an XML element type in the "DAV:" namespace is referenced in this document outside of the context of an XML fragment, the string "DAV:" will be prefixed to the element type. Similarly, when an XML element type in the namespace "http://www.w3.org/2001/XMLSchema" is referenced in this document outside of the context of an XML fragment, the string "xs:" will be prefixed to the element type. This document inherits, and sometimes extends, DTD productions from Section 14 of .

This specification defines elements, properties, and condition names in the XML namespace "DAV:". In general, only specifications authored by IETF working groups are supposed to do this. In this case an exception was made, because WebDAV SEARCH started its life in the IETF DASL working group (, and at the time the working group closed down there was already significant deployment of this specification.

One can express the basic usage of DASL in the following steps: The client constructs a query using the DAV:basicsearch grammar. The client invokes the SEARCH method on a resource that will perform the search (the search arbiter) and includes a text/xml or application/xml request entity that contains the query. The search arbiter performs the query. The search arbiter sends the results of the query back to the client in the response. The server MUST send an entity that matches the WebDAV multistatus format (, Section 13).

The client invokes the SEARCH method to initiate a server-side search. The body of the request defines the query. The server MUST emit an entity matching the WebDAV multistatus format (, Section 13). The SEARCH method plays the role of transport mechanism for the query and the result set. It does not define the semantics of the query. The type of the query defines the semantics. SEARCH is a safe method; it does not have any significance other than executing a query and returning a query result (see , Section 9.1.1).

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

The Request-URI identifies the search arbiter. Any HTTP resource may function as search arbiter. It is not a new type of resource (in the sense of DAV:resourcetype as defined in , Section 15.9), nor does it have to be a WebDAV-compliant resource. The SEARCH method defines no relationship between the arbiter and the scope of the search; rather, the particular query grammar used in the query defines the relationship. For example, a query grammar may force the Request-URI to correspond exactly to the search scope.

The server MUST process a text/xml or application/xml request body, and MAY process request bodies in other formats. See for guidance on packaging XML in requests. Marshalling: If a request body with content type text/xml or application/xml is included, it MUST be either a DAV:searchrequest or a DAV:query-schema-discovery XML element. Its single child element identifies the query grammar. For DAV:searchrequest, the definition of search criteria, the result record, and any other details needed to perform the search depend on the individual search grammar. For DAV:query-schema-discovery, the semantics is defined in . Preconditions: (DAV:search-grammar-discovery-supported): when an XML request body is present and has a DAV:query-schema-discovery document element, the server MUST support the query schema discovery mechanism described in . (DAV:search-grammar-supported): when an XML request body is present, the search grammar identified by the document element's child element must be a supported search grammar. (DAV:search-multiple-scope-supported): if the SEARCH request specified multiple scopes, the server MUST support this optional feature. (DAV:search-scope-valid): the supplied search scope must be valid. There can be various reasons for a search scope to be invalid, including unsupported URI schemes and communication problems. Servers MAY add compliant DAV:response elements as content to the condition element indicating the precise reason for the failure.

If the server returns 207 (Multistatus), then the search proceeded successfully, and the response MUST use the WebDAV multistatus format (, Section 13). The results of this method SHOULD NOT be cached. There MUST be one DAV:response for each resource that matched the search criteria. For each such response, the DAV:href element contains the URI of the resource, and the response MUST include a DAV:propstat element. Note: the WebDAV multistatus format requires at least one DAV:response child element. This specification relaxes that restriction so that empty results can be represented. Note that for each matching resource found, there may be multiple URIs within the search scope mapped to it. In this case, a server SHOULD report only one of these URIs. Clients can use the live property DAV:resource-id, defined in Section 3.1 of to identify possible duplicates.

A server MAY limit the number of resources in a reply, for example, to limit the amount of resources expended in processing a query. If it does so, the reply MUST use status code 207, return a DAV:multistatus response body, and indicate a status of 507 (Insufficient Storage) for the search arbiter URI. It SHOULD include the partial results. When a result set is truncated, there may be many more resources that satisfy the search criteria but that were not examined. If partial results are included and the client requested an ordered result set in the original request, then any partial results that are returned MUST be ordered as the client directed. Note that the partial results returned MAY be any subset of the result set that would have satisfied the original query.

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

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

>> Request: Find the locations of good Thai restaurants in Los Angeles ]]>

>> Response: http://siamiam.example/ 259 W. Hollywood 4 HTTP/1.1 200 OK ]]>

In the example below, the server returns just two results, and then indicates that the result is truncated by adding a DAV:response element for the search arbiter resource with 507 (Insufficient Storage) status.

>> Request:

>> Response: http://www.example.net/sounds/unbrokenchain.au HTTP/1.1 200 OK http://tech.mit.example/arch96/photos/Lesh1.jpg HTTP/1.1 200 OK http://example.net HTTP/1.1 507 Insufficient Storage Only first two matching records were returned ]]>

If a SEARCH request could not be executed or the attempt to execute it resulted in an error, the server MUST indicate the failure with an appropriate status code and SHOULD add a response body as defined in Section 1.6 of . Unless otherwise stated, condition elements are empty; however, specific condition elements MAY include additional child elements that describe the error condition in more detail.

In the example below, a request failed because the scope identifies a HTTP resource that was not found.

>> Response: http://www.example.com/X HTTP/1.1 404 Object Not Found ]]>

Servers MUST support discovery of the query grammars supported by a search arbiter resource. Clients can determine which query grammars are supported by an arbiter by invoking OPTIONS on the search arbiter. If the resource supports SEARCH, then the DASL response header will appear in the response. The DASL response header lists the supported grammars. Servers supporting the WebDAV extensions and/or MUST also: report SEARCH in the live property DAV:supported-method-set for all search arbiter resources, and support the live property DAV:supported-query-grammar-set as defined in .

The OPTIONS method allows the client to discover if a resource supports the SEARCH method and to determine the list of search grammars supported for that resource. The client issues the OPTIONS method against a resource named by the Request-URI. This is a normal invocation of OPTIONS as defined in Section 9.2 of . If a resource supports the SEARCH method, then the server MUST list SEARCH in the Allow header defined in Section 14.7 of . DASL servers MUST include the DASL header in the OPTIONS response. This header identifies the search grammars supported by that resource.

]]> (This grammar uses the augmented BNF format defined in Section 2.1 of .)

The DASL response header indicates server support for query grammars in the OPTIONS method. The value is a list of URIs that indicate the types of supported grammars. Note that although the URIs can be used to identify each supported search grammar, there is not necessarily a direct relationship between the URI and the XML element name that can be used in XML based SEARCH requests (the element name itself is identified by its namespace name (a URI reference) and the element's local name). Note: this header field value is defined as a comma-separated list (, Section 4.2); thus, grammar URIs can appear in multiple header instances, separated by commas, or both.

For example: , , DASL: ]]>

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

]]>

This example shows that the server supports search on the /somefolder resource with the query grammars: DAV:basicsearch, http://foobar.example/syntax1 and http://akuma.example/syntax2. Note that servers supporting WebDAV SEARCH MUST support DAV:basicsearch.

>> Request:

>> Response: DASL: , ]]>

This example shows the equivalent taking advantage of a server's support for DAV:supported-method-set and DAV:supported-query-grammar-set.

>> Request: ]]>

>> Response: http://example.org/somefolder HTTP/1.1 200 OK ]]>

Note that the query grammar element names marshalled as part of the DAV:supported-query-grammar-set can be directly used as element names in an XML-based query.

Servers MAY support the discovery of the schema for a query grammar. The DASL response header and the DAV:supported-query-grammar-set property provide means for clients to discover the set of query grammars supported by a resource. This alone is not sufficient information for a client to generate a query. For example, the DAV:basicsearch grammar defines a set of queries consisting of a set of operators applied to a set of properties and values, but the grammar itself does not specify which properties may be used in the query. QSD for the DAV:basicsearch grammar allows a client to discover the set of properties that are searchable, selectable, and sortable. Moreover, although the DAV:basicsearch grammar defines a minimal set of operators, it is possible that a resource might support additional operators in a query. For example, a resource might support an optional operator that can be used to express content-based queries in a proprietary syntax. QSD allows a client to discover these operators and their syntax. The set of discoverable quantities will differ from grammar to grammar, but each grammar can define a means for a client to discover what can be discovered. In general, the schema for a given query grammar depends on both the resource (the arbiter) and the scope. A given resource might have access to one set of properties for one potential scope, and another set for a different scope. For example, consider a server able to search two distinct collections: one holding cooking recipes, the other design documents for nuclear weapons. While both collections might support properties such as author, title, and date, the first might also define properties such as calories and preparation time, while the second defined properties such as yield and applicable patents. Two distinct arbiters indexing the same collection might also have access to different properties. For example, the recipe collection mentioned above might also be indexed by a value-added server that also stored the names of chefs who had tested the recipe. Note also that the available query schema might also depend on other factors, such as the identity of the principal conducting the search, but these factors are not exposed in this protocol.

Each query grammar supported by DASL defines its own syntax for expressing the possible query schema. A client retrieves the schema for a given query grammar on an arbiter resource with a given scope by invoking the SEARCH method on that arbiter with that grammar and scope and with a root element of DAV:query-schema-discovery rather than DAV:searchrequest. Marshalling: The request body MUST be a DAV:query-schema-discovery element.

]]>

The response body takes the form of a DAV:multistatus element (, Section 13), where DAV:response is extended to hold the returned query grammar inside a DAV:query-schema container element.

]]>

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

In this example, the arbiter is recipes.example, the grammar is DAV:basicsearch, the scope is also recipes.example.

>> Request: http://recipes.example infinity ]]>

>> Response: http://recipes.example HTTP/1.1 200 OK ]]>

The query schema for DAV:basicsearch is defined in .

DAV:basicsearch uses an extensible XML syntax that allows clients to express search requests that are generally useful for WebDAV scenarios. DASL-extended servers MUST accept this grammar, and MAY accept other grammars. DAV:basicsearch has several components: DAV:select provides the result record definition. DAV:from defines the scope. DAV:where defines the criteria. DAV:orderby defines the sort order of the result set. DAV:limit provides constraints on the query as a whole.

<!-- "basicsearch" element --> ]]>

<!-- "select" element --> ]]>

<!-- "from" element --> ]]>

<!-- "where" element --> ]]>

<!-- "orderby" element --> ]]>

<!-- "limit" element --> ]]>

This query retrieves the content length values for all resources located under the server's "/container1/" URI namespace whose length exceeds 10000 sorted ascending by size.

/container1/ infinity 10000 ]]>

DAV:select defines the result record, which is a set of properties and values. This document defines two possible values: DAV:allprop and DAV:prop, both defined in Section 14 of .

]]>

DAV:from defines the query scope. This contains one or more DAV:scope elements. Support for multiple scope elements is optional, however servers MUST fail a request specifying multiple DAV:scope elements if they can't support it (see , precondition DAV:search-multiple-scope-supported). The scope element contains mandatory DAV:href and DAV:depth elements. DAV:href indicates the URI reference (, Section 4.1) to use as a scope. When the scope is a collection, if DAV:depth is "0", the search includes only the collection. When it is "1", the search includes the collection and its immediate children. When it is "infinity", it includes the collection and all its progeny. When the scope is not a collection, the depth is ignored and the search applies just to the resource itself. If the server supports WebDAV Redirect Reference Resources () and the search scope contains a redirect reference resource, then it applies only to that resource, not to its target. When the child element DAV:include-versions is present, the search scope will include all versions (see , Section 2.2.1) of all version-controlled resources in scope. Servers that do support versioning but do not support the DAV:include-versions feature MUST signal an error if it is used in a query (see , precondition DAV:search-scope-valid).

If the DAV:scope element is a URI (, Section 3), the scope is exactly that URI. If the DAV:scope element is a relative reference (, Section 4.2), the scope is taken to be relative to the Request-URI.

A Scope can be an arbitrary URI reference. Servers, of course, may support only particular scopes. This may include limitations for particular schemes such as "http:" or "ftp:" or certain URI namespaces. However, WebDAV-compliant search arbiters minimally SHOULD support scopes that match their own URI.

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

Each operator defined for use in the where clause that returns a Boolean value MUST evaluate to TRUE, FALSE, or UNKNOWN. The resource under scan is included as a member of the result set if and only if the search condition evaluates to TRUE. Consult for details on the application of three-valued logic in query expressions.

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

If a PROPFIND for a property value would yield a non-2xx (see Section 2.10 of ) response for that property, then that property is considered NULL. NULL values are "less than" all other values in comparisons. Empty strings (zero length strings) are not NULL values. An empty string is "less than" a string with length greater than zero. The DAV:is-defined operator is defined to test if the value of a property is not NULL.

Comparisons of properties that do not have simple types (text-only content) is out of scope for the standard operators defined for DAV:basicsearch and therefore is defined to be UNKNOWN (as per ). For querying the DAV:resourcetype property, see .

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

100 ]]>

The example shows a more complex operation involving several operators (DAV:and, DAV:eq, DAV:gt) applied in the criteria. This DAV:where expression matches those resources of type "image/gif" over 4K in size.

image/gif 4096 ]]>

The DAV:orderby element specifies the ordering of the result set. It contains one or more DAV:order elements, each of which specifies a comparison between two items in the result set. Informally, a comparison specifies a test that determines whether one resource appears before another in the result set. Comparisons are applied in the order they occur in the DAV:orderby element, earlier comparisons being more significant. The comparisons defined here use only a single property from each resource, compared using the same ordering as the DAV:lt operator (ascending) or DAV:gt operator (descending). If neither direction is specified, the default is DAV:ascending. In the context of the DAV:orderby element, null values are considered to collate before any actual (i.e., non-null) value, including strings of zero length (this is compatible with ). The "caseless" attribute may be used to indicate case-sensitivity for comparisons ().

This sort orders first by last name of the author and then by size, in descending order, so that for each author, the largest works appear first.

]]>

The DAV:and operator performs a logical AND operation on the expressions it contains. The DAV:or operator performs a logical OR operation on the values it contains. The DAV:not operator performs a logical NOT operation on the values it contains.

The DAV:eq operator provides simple equality matching on property values. The "caseless" attribute may be used with this element ().

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

DAV:literal allows literal values to be placed in an expression. White space in literal values is significant in comparisons. For consistency with , clients SHOULD NOT specify the attribute "xml:space" (, Section 10.2) to override this behavior. In comparisons, the contents of DAV:literal SHOULD be treated as string, with the following exceptions: when operand for a comparison with a DAV:getcontentlength property, it SHOULD be treated as an unsigned integer value (the behavior for values not in this format is undefined), when operand for a comparison with a DAV:creationdate or DAV:getlastmodified property, it SHOULD be treated as a date value in the ISO-8601 subset defined for the DAV:creationdate property (see Section 15.1 of ; the behavior of values not in this format is undefined), when operand for a comparison with a property for which the type is known and when compatible with that type, it MAY be treated according to this type.

There are situations in which a client may want to force a comparison not to be string-based (as defined for DAV:literal). In these cases, a typed comparison can be enforced by using DAV:typed-literal instead.

]]>

The data type is specified using the xsi:type attribute defined in Section 2.6.1 of . If the type is not specified, it defaults to "xs:string". A server MUST reject a request using an unknown type with a status of 422 (Unprocessable Entity). It SHOULD reject a request if the value provided in DAV:typed-literal cannot be cast to the specified type. The comparison evaluates to UNKNOWN if the property value cannot be cast to the specified datatype (see , Section 17).

Consider a set of resources with the dead property "edits" in the namespace "http://ns.example.org": URIproperty value /a"-1" /b"01" /c"3" /d"test" /e(undefined) The expression

3 ]]>

will evaluate to TRUE for the resources "/a" and "/b" (their property values can be parsed as type xs:integer, and the numerical comparison evaluates to true), to FALSE for "/c" (property value is compatible, but numerical comparison evaluates to false), and UNKNOWN for "/d" and "/e" (the property either is undefined, or its value cannot be parsed as xs:integer).

The following two optional operators can be used to express conditions on the language of a property value (as expressed using the xml:lang attribute).

]]>

This operator evaluates to TRUE if the language for the value of the given property is known, FALSE if it isn't, and UNKNOWN if the property itself is not defined.

]]>

This operator evaluates to TRUE if the language for the value of the given property is known and matches the language name given in the <literal> element, FALSE if it doesn't match, and UNKNOWN if the property itself is not defined. Languages are considered to match if they are the same, or if the language of the property value is a sublanguage of the language specified in the <literal> element (see Section 4.3 of , "lang function").

The expression below will evaluate to TRUE if the property "foobar" exists and its language is either unknown, English, or a sublanguage of English.

en ]]>

The DAV:is-collection operator allows clients to determine whether a resource is a collection (that is, whether its DAV:resourcetype element contains the element DAV:collection). Rationale: This operator is provided in lieu of defining generic structure queries, which would suffice for this and for many more powerful queries, but seems inappropriate to standardize at this time.

This example shows a search criterion that picks out all, and only, the resources in the scope that are collections.

]]>

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

Example: ]]>

The DAV:like is an optional operator intended to give simple wildcard-based pattern matching ability to clients. The operator takes two arguments. The first argument is a DAV:prop element identifying a single property to evaluate. The second argument is a DAV:literal element that gives the pattern matching string.

(Note that the ABNF above is defined in terms of Unicode code points (); when a query is transmitted as an XML document over WebDAV, these characters are typically encoded in UTF-8 or UTF-16.)

The value for the literal is composed of wildcards separated by segments of text. Wildcards may begin or end the literal. The "_" wildcard matches exactly one character. The "%" wildcard matches zero or more characters. The "\" character is an escape sequence so that the literal can include "_" and "%". To include the "\" character in the pattern, the escape sequence "\\" is used.

This example shows how a client might use DAV:like to identify those resources whose content type was a subtype of image.

image/% ]]>

The DAV:contains operator is an optional operator that provides content-based search capability. This operator implicitly searches against the text content of a resource, not against the content of properties. The DAV:contains operator is intentionally not overly constrained, in order to allow the server to do the best job it can in performing the search. The DAV:contains operator evaluates to a Boolean value. It evaluates to TRUE if the content of the resource satisfies the search. Otherwise, it evaluates to FALSE. Within the DAV:contains XML element, the client provides a phrase: a single word or whitespace delimited sequence of words. Servers MAY ignore punctuation in a phrase. Case-sensitivity is at the discretion of the server implementation. The following non-exhaustive list enumerates things that may or may not be done as part of the search: Phonetic methods such as "soundex" may or may not be used. Word stemming may or may not be performed. Thesaurus expansion of words may or may not be done. Right or left truncation may or may not be performed. The search may be case insensitive or case sensitive. The word or words may or may not be interpreted as names. Multiple words may or may not be required to be adjacent or "near" each other. Multiple words may or may not be required to occur in the same order. Multiple words may or may not be treated as a phrase. The search may or may not be interpreted as a request to find documents "similar" to the string operand. Character canonicalization such as that done by the Unicode collation algorithm may or may not be applied.

Servers SHOULD indicate scores for the DAV:contains condition by adding a DAV:score XML element to the DAV:response element. Its value is defined only in the context of a particular query result. The value is a string representing the score, an integer from zero to 10000 inclusive, where a higher value indicates a higher score (e.g., more relevant).

Modified DTD fragment for DAV:propstat: ]]>

Clients should note that, in general, it is not meaningful to compare the numeric values of scores from two different query results unless both were executed by the same underlying search system on the same collection of resources.

To order search results by their score, the DAV:score element may be added as child to the DAV:orderby element (in place of a DAV:prop element).

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

Peter Forsberg ]]>

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

Peter Forsberg ]]>

]]>

The DAV:limit XML element contains requested limits from the client to limit the size of the reply or amount of effort expended by the server. The DAV:nresults XML element contains a requested maximum number of DAV:response elements to be returned in the response body. The server MAY disregard this limit. The value of this element is an unsigned integer.

If the result set is both limited by DAV:limit and ordered according to DAV:orderby, the results that are included in the response document SHOULD be those that order highest.

The "caseless" attribute allows clients to specify caseless matching behavior instead of character-by-character matching for DAV:basicsearch operators. The possible values for "caseless" are "yes" or "no". The default value is server-specified. Caseless matching SHOULD be implemented as defined in Section 5.18 of the Unicode Standard (). Support for the "caseless" attribute is optional. A server should respond with a status of 422 if it is used but cannot be supported.

The DAV:basicsearch grammar defines a search criteria that is a Boolean-valued expression, and allows for an arbitrary set of properties to be included in the result record. The result set may be sorted on a set of property values. Accordingly, the DTD for schema discovery for this grammar allows the server to express: the set of properties that may be either searched, returned, or used to sort, and a hint about the data type of such properties. the set of optional operators defined by the resource.

]]>

The DAV:properties element holds a list of descriptions of properties. The DAV:operators element describes the optional operators that may be used in a DAV:where element.

Each instance of a DAV:propdesc element describes the property or properties in the DAV:prop element it contains. All subsequent elements are descriptions that apply to those properties. All descriptions are optional and may appear in any order. Servers SHOULD support all the descriptions defined here, and MAY define others. DASL defines five descriptions. The first, DAV:datatype, provides a hint about the type of the property value, and may be useful to a user interface prompting for a value. The remaining four (DAV:searchable, DAV:selectable, DAV:sortable, and DAV:caseless) identify portions of the query (DAV:where, DAV:select, and DAV:orderby, respectively). If a property has a description for a section, then the server MUST allow the property to be used in that section. These descriptions are optional. If a property does not have such a description, or is not described at all, then the server MAY still allow the property to be used in the corresponding section.

This element can be used in place of DAV:prop to describe properties of WebDAV properties not mentioned in any other DAV:prop element. For instance, this can be used to indicate that all other properties are searchable and selectable without giving details about their types (a typical scenario for dead properties).

The DAV:datatype element contains a single XML element that provides a hint about the domain of the property, which may be useful to a user interface prompting for a value to be used in a query. Data types are identified by an element name. Where appropriate, a server SHOULD use the simple data types defined in .

]]>

Examples from , Section 3: Qualified nameExample xs:booleantrue, false, 1, 0 xs:stringFoobar xs:dateTime1994-11-05T08:15:5Z xs:float.314159265358979E+1 xs:integer-259, 23 If the data type of a property is not given, then the data type defaults to xs:string.

]]>

If this element is present, then the server MUST allow this property to appear within a DAV:where element where an operator allows a property. Allowing a search does not mean that the property is guaranteed to be defined on every resource in the scope, it only indicates the server's willingness to check.

]]>

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

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

]]>

This element only applies to properties whose data type is "xs:string" and derived data types as per the DAV:datatype property description. Its presence indicates that comparisons performed for searches, and the comparisons for ordering results on the string property will be caseless (the default is character by character).

]]>

The DAV:operators element describes every optional operator supported in a query. (Mandatory operators are not listed since they are mandatory and permit no variation in syntax.) All optional operators that are supported MUST be listed in the DAV:operators element. The listing for an operator, contained in an DAV:opdesc element, consists of the operator (as an empty element), followed by one element for each operand. The operand MUST be either DAV:operand-property, DAV:operand-literal, or DAV:operand-typed-literal, which indicate that the operand in the corresponding position is a property, a literal value, or a typed literal value, respectively. If an operator is polymorphic (allows more than one operand syntax) then each permitted syntax MUST be listed separately. The DAV:opdesc element MAY have a "allow-pcdata" attribute (defaulting to "no"). A value of "yes" indicates that the operator can contain character data, as it is the case with DAV:contains (see ). Definition of additional operators using this format is NOT RECOMMENDED.

]]>

]]>

This response lists four properties. The data type of the last three properties is not given, so it defaults to xs:string. All are selectable, and the first three may be searched. All but the last may be used in a sort. Of the optional DAV operators, DAV:contains and DAV:like are supported. Note: The schema discovery defined here does not provide for discovery of supported values of the "caseless" attribute. This may require that the reply also list the mandatory operators.

Properties may be language-tagged using the xml:lang attribute (see , Section 4.3). The optional operators DAV:language-defined () and DAV:language-matches () allow the expression of conditions on the language tagging information.

This section is provided to detail issues concerning security implications of which DASL applications need to be aware. All of the security considerations of HTTP/1.1 ( and WebDAV () also apply to DASL. In addition, this section will include security risks inherent in the search and retrieval of resource properties and content. A query MUST NOT allow clients to retrieve information that wouldn't have been available through the GET or PROPFIND methods in the first place. In particular: Query constraints on WebDAV properties for which the client does not have read access need to be evaluated as if the property did not exist (see ). Query constraints on content (as with DAV:contains, defined in ) for which the client does not have read access need to be evaluated as if a GET would return a 4xx status code. A server should prepare for denial-of-service attacks. For example a client may issue a query for which the result set is expensive to calculate or transmit because many resources match or must be evaluated.

XML supports a facility known as "external entities", defined in Section 4.2.2 of , which instruct an XML processor to retrieve and perform an inline include of XML located at a particular URI. An external XML entity can be used to append or modify the document type declaration (DTD) associated with an XML document. An external XML entity can also be used to include XML within the content of an XML document. For non-validating XML, such as the XML used in this specification, including an external XML entity is not required by . However, does state that an XML processor may, at its discretion, include the external XML entity. External XML entities have no inherent trustworthiness and are subject to all the attacks that are endemic to any HTTP GET request. Furthermore, it is possible for an external XML entity to modify the DTD, and hence affect the final form of an XML document, in the worst case significantly modifying its semantics, or exposing the XML processor to the security risks discussed in . Therefore, implementers must be aware that external XML entities should be treated as untrustworthy. There is also the scalability risk that would accompany a widely deployed application that made use of external XML entities. In this situation, it is possible that there would be significant numbers of requests for one external XML entity, potentially overloading any server that fields requests for the resource containing the external XML entity.

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://").

This document uses the namespace defined in Section 21 of for XML elements.

This document specifies the HTTP header listed below, which has been added to the permanent HTTP header registry defined in .

DASL http standard IETF this specification ()

This document is based on prior work on the DASL protocol done by the WebDAV DASL working group until the year 2000 -- namely by Alan Babich, Jim Davis, Rick Henderson, Dale Lowry, Saveen Reddy, and Surendra Reddy.

This document has benefited from thoughtful discussion by Lisa Dusseault, Javier Godoy, Sung Kim, Chris Newman, Elias Sinderson, Martin Wallmer, Keith Wannamaker, Jim Whitehead, and Kevin Wiggen.

Department of Information and Computer Science

University of California, Irvine Irvine CA 92697-3425 +1(949)824-1715 fielding@ics.uci.edu

World Wide Web Consortium

MIT Laboratory for Computer Science, NE43-356 545 Technology Square Cambridge MA 02139 +1(617)258-8682 jg@w3.org

Compaq Computer Corporation

Western Research Laboratory 250 University Avenue Palo Alto CA 94305 mogul@wrl.dec.com

World Wide Web Consortium

MIT Laboratory for Computer Science, NE43-356 545 Technology Square Cambridge MA 02139 +1(617)258-8682 frystyk@w3.org

Xerox Corporation

MIT Laboratory for Computer Science, NE43-356 3333 Coyote Hill Road Palo Alto CA 94034 masinter@parc.xerox.com

Microsoft Corporation

1 Microsoft Way Redmond WA 98052 paulle@microsoft.com

World Wide Web Consortium

MIT Laboratory for Computer Science, NE43-356 545 Technology Square Cambridge MA 02139 +1(617)258-8682 timbl@w3.org

The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers . A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1", and is an update to RFC 2068 . Harvard University

1350 Mass. Ave. Cambridge MA 02138 - +1 617 495 3864 sob@harvard.edu

General keyword In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. Authors who follow these guidelines should incorporate this phrase near the beginning of their document: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Note that the force of these words is modified by the requirement level of the document in which they are used. Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS TRACK] Textuality and Netscape

tbray@textuality.com

Microsoft

jeanpa@microsoft.com

University of Illinois at Chicago and Text Encoding Initiative

cmsmcq@uic.edu

Sun Microsystems

eve.maler@east.sun.com

francois@yergeau.com

University of Edinburgh

ht@cogsci.ed.ac.uk

Oracle

David.Beech@oracle.com

(for) Commerce One

murray@muzmo.com

Lotus Development Corporation

Noah_Mendelsohn@lotus.com

World Wide Web Consortium

MIT Laboratory for Computer Science 545 Technology Square Cambridge MA 02139 US + 1 617 253 2613 + 1 617 258 5999 timbl@w3.org http://www.w3c.org

Kaiser Permanente, for Health Level Seven

Paul.V.Biron@kp.org

Microsoft, formerly of IBM

ashokma@microsoft.com

World Wide Web Consortium

MIT Laboratory for Computer Science 545 Technology Square Cambridge MA 02139 US + 1 617 253 2613 + 1 617 258 5999 timbl@w3.org http://www.w3c.org

Web Distributed Authoring and Versioning (WebDAV) consists of a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, URL namespace manipulation, and resource locking (collision avoidance). RFC 2518 was published in February 1999, and this specification obsoletes RFC 2518 with minor revisions mostly due to interoperability experience. [STANDARDS TRACK] Rational Software

20 Maguire Road Lexington MA 02421 US geoffrey.clemm@rational.com

IBM

3039 Cornwallis Research Triangle Park NC 27709 US jamsden@us.ibm.com

IBM

Hursley Park Winchester S021 2JN UK tim_ellison@uk.ibm.com

Microsoft

One Microsoft Way Redmond WA 90852 US ckaler@microsoft.com

UC Santa Cruz, Dept. of Computer Science

1156 High Street Santa Cruz CA 95064 US ejw@cse.ucsc.edu

This document standardizes five new media types -- text/xml, application/xml, text/xml-external-parsed-entity, application/xml- external-parsed-entity, and application/xml-dtd -- for use in exchanging network entities that are related to the Extensible Markup Language (XML). This document also standardizes a convention (using the suffix '+xml') for naming media types outside of these five types when those media types represent XML MIME (Multipurpose Internet Mail Extensions) entities. [STANDARDS TRACK] IBM

20 Maguire Road Lexington MA 02421 geoffrey.clemm@us.ibm.com

greenbytes GmbH

Salzmannstrasse 152 Muenster NW 48159 Germany julian.reschke@greenbytes.de

Oracle Corporation

500 Oracle Parkway Redwood Shores CA 94065 eric.sedlar@oracle.com

U.C. Santa Cruz, Dept. of Computer Science

1156 High Street Santa Cruz CA 95064 ejw@cse.ucsc.edu

This document specifies a set of methods, headers, message bodies, properties, and reports that define Access Control extensions to the WebDAV Distributed Authoring Protocol. This protocol permits a client to read and modify access control lists that instruct a server whether to allow or deny operations upon a resource (such as HyperText Transfer Protocol (HTTP) method invocations) by a given principal. A lightweight representation of principals as Web resources supports integration of a wide range of user management repositories. Search operations allow discovery and manipulation of principals using human names.

jjc@jclark.com

Inso Corp. and Brown University

Steven_DeRose@Brown.edu

Oracle Corporation

ashok.malhotra@alum.mit.edu

Oracle Corporation

jim.melton@acm.org

Sun Microsystems

Norman.Walsh@Sun.COM

World Wide Web Consortium

Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge MA 02139 USA +1-617-253-5702 +1-617-258-5999 timbl@w3.org http://www.w3.org/People/Berners-Lee/

Day Software

5251 California Ave., Suite 110 Irvine CA 92617 USA +1-949-679-2960 +1-949-679-2972 fielding@gbiv.com http://roy.gbiv.com/

Adobe Systems Incorporated

345 Park Ave San Jose CA 95110 USA +1-408-536-3024 LMM@acm.org http://larry.masinter.net/

Applications uniform resource identifier URI URL URN WWW resource A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. International Organization for Standardization The Unicode Consortium ISBN 0321480910 CourseNet Systems

170 Capp Street San FranciscoCA94110 jrd3@alum.mit.edu

Microsoft

One Microsoft Way RedmondWA9085-6933 saveenr@microsoft.com

Xerox Corporation

800 Phillips Road 128-29E slein@wrc.xerox.com

Work in Progress. Microsoft

One Microsoft Way RedmondWA9085-6933 saveenr@microsoft.com

Novell

1555 N. Technology Way, M/S ORM-M-314 OremUT84097 dlowry@novell.com

Oracle Corporation

600 Oracle Parkway, M/S 6op3 RedwoodshoresCA94065 +1 650 506 5441 skreddy@us.oracle.com

Netscape

rickh@netscape.com

Intelligent Markets

410 Jessie Street 6th floor San FranciscoCA94103 jrd3@alum.mit.edu

Filenet

3565 Harbor Blvd. Costa MesaCA92626 +1 714 966 3403 ababich@filenet.com

This specification defines registration procedures for the message header fields used by Internet mail, HTTP, Netnews and other applications. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Many Internet application protocols include string-based lookup, searching, or sorting operations. However, the problem space for searching and sorting international strings is large, not fully explored, and is outside the area of expertise for the Internet Engineering Task Force (IETF). Rather than attempt to solve such a large problem, this specification creates an abstraction framework so that application protocols can precisely identify a comparison function, and the repertoire of comparison functions can be extended in the future. [STANDARDS TRACK] This document describes a syntax, called a "language-range", for specifying items in a user's list of language preferences. It also describes different mechanisms for comparing and matching these to language tags. Two kinds of matching mechanisms, filtering and lookup, are defined. Filtering produces a (potentially empty) set of language tags, whereas lookup produces a single language tag. Possible applications include language negotiation or content selection. This document, in combination with RFC 4646, replaces RFC 3066, which replaced RFC 1766. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. UC Santa Cruz, Dept. of Computer Science

1156 High Street Santa Cruz CA 95064 US ejw@cse.ucsc.edu

IBM

20 Maguire Road Lexington MA 02421 US geoffrey.clemm@us.ibm.com

greenbytes GmbH

Hafenweg 16 Muenster NW 48155 Germany +49 251 2807760 +49 251 2807761 julian.reschke@greenbytes.de http://greenbytes.de/tech/webdav/

WEBDAV Working Group This specification defines an extension to Web Distributed Authoring and Versioning (WebDAV) to allow clients to author HTTP redirect reference resources whose default response is an HTTP/1.1 3xx (Redirection) status code. A redirect reference makes it possible to access the target resourced indirectly through any URI mapped to the redirect reference resource. This specification does not address remapping of trees of resources or regular expression based redirections. There are no integrity guarantees associated with redirect reference resources. Other mechanisms can also be used to achieve the same functionality as this specification. This specification allows operators to experiment with this mechanism and develop experience on what is the best approach to the problem.

ANSI standard three-valued logic is used when evaluating the search condition (as defined in the ANSI standard SQL specifications, for example, in ANSI X3.135-1992, Section 8.12, pp. 188-189, Section 8.2, p. 169, General Rule 1)a), etc.). ANSI standard three-valued logic is undoubtedly the most widely practiced method of dealing with the issues of properties in the search condition not having a value (e.g., being null or not defined) for the resource under scan, and with undefined expressions in the search condition (e.g., division by zero, etc.). Three valued logic works as follows. Undefined expressions are expressions for which the value of the expression is not defined. Undefined expressions are a completely separate concept from the truth value UNKNOWN, which is, in fact, well defined. Property names and literal constants are considered expressions for purposes of this section. If a property in the current resource under scan has not been set to a value, then the value of that property is undefined for the resource under scan. DASL 1.0 has no arithmetic division operator, but if it did, division by zero would be an undefined arithmetic expression. If any subpart of an arithmetic, string, or datetime subexpression is undefined, the whole arithmetic, string, or datetime subexpression is undefined. There are no manifest constants to explicitly represent undefined number, string, or datetime values. Since a Boolean value is ultimately returned by the search condition, arithmetic, string, and datetime expressions are always arguments to other operators. Examples of operators that convert arithmetic, string, and datetime expressions to Boolean values are the six relational operators ("greater than", "less than", "equals", etc.). If either or both operands of a relational operator have undefined values, then the relational operator evaluates to UNKNOWN. Otherwise, the relational operator evaluates to TRUE or FALSE, depending upon the outcome of the comparison. The Boolean operators DAV:and, DAV:or, and DAV:not are evaluated according to the following rules: not UNKNOWN = UNKNOWN UNKNOWN and TRUE = UNKNOWN UNKNOWN and FALSE = FALSE UNKNOWN and UNKNOWN = UNKNOWN UNKNOWN or TRUE = TRUE UNKNOWN or FALSE = UNKNOWN UNKNOWN or UNKNOWN = UNKNOWN

This section summarizes issues that have been raised during the development of this specification, but for which no resolution could be found with the constraints in place. Future revisions of this specification should revisit these issues, though.

Matching and sorting of textual data relies on collations. With respect to WebDAV SEARCH, a combination of various design approaches could be used: Require server support for specific collations. Require that the server can advertise which collations it supports. Allow a client to select the collation to be used. In practice, the current implementations of WebDAV SEARCH usually rely on backends they do not control, and for which collation information may not be available. To make things worse, implementations of the DAV:basicsearch grammar frequently need to combine data from multiple underlying stores (such as properties and full text content), and thus collation support may vary based on the operator or property. Another open issue is what collation formalism to support. At the time of this writing, the two specifications below seem to provide the necessary framework and thus may be the base for future work on collation support in WebDAV SEARCH: "Internet Application Protocol Collation Registry" (). "XQuery 1.0 and XPath 2.0 Functions and Operators" (, Section 7.3.1).

DAV:basicsearch does not allow a request that returns the count of matching resources. A protocol extension would need to extend DAV:select, and also modify the DAV:multistatus response format.

There are many reasons why a given query may not be supported by a server. Query Schema Discovery () can be used to discover some constraints, but not all. Future revisions should consider the introduction of specific condition codes (, Section 16) to these situations.

defines language matching in terms of the XPath "lang" function (, Section 4.3). Future revisions should consider building on instead.

Matching media types using the DAV:getcontenttype property and the DAV:like operator is hard due to DAV:getcontenttype also allowing parameters. A new operator specifically designed for the purpose of matching media types probably would simplify things a lot. See for a specific proposal.

DAV:basicsearch operates on the properties (and optionally the contents) of resources, and thus doesn't really allow matching on parts of the resource's URI. See for a proposed extension covering this use case.

A frequently discussed feature is the ability to specifically request the "next" set of results, when either the server decided to truncate the result, or the client explicitly asked for a limited set (for instance, using the DAV:limit element defined in ). In this case, it would be desirable if the server could keep the full query result, and provide a new URI identifying a separate result resource, allowing the client to retrieve additional data through GET requests, and remove the result through a DELETE request.

Given a Search Arbiter resource, there's currently no way to discover programmatically the supported sets of search scopes. Future revisions of this specification could specify a scope discovery mechanism, similar to the Query Schema Discovery defined in .