|WEBDAV DASL Working Group||J. Reschke|
|Intended status: Informational||S. Reddy|
|Expires: September 2002||Oracle|
Note: a later version of this document has been published as RFC5323.
This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress”.
The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.
This Internet-Draft will expire in September 2002.
Copyright © The Internet Society (2002). All Rights Reserved.
1 This document specifies a set of methods, headers, and content-types composing DASL, an application of the HTTP/1.1 protocol to efficiently search for DAV resources based upon a set of client-supplied criteria.
2 Distribution of this document is unlimited. Please send comments to the Distributed Authoring and Versioning (WebDAV) working group at firstname.lastname@example.org, which may be joined by sending a message with subject "subscribe" to email@example.com.
3 Discussions of the WEBDAV working group are archived at URL: http://lists.w3.org/Archives/Public/w3c-dist-auth/.
|I introduction (type: change, status: closed)|
|firstname.lastname@example.org||2002-01-25||Need to rewrite introduction stating that is based on the expired WebDAV DASL internet draft.|
8 This document defines DAV Searching & Locating (DASL), an application of HTTP/1.1 forming a lightweight search protocol to transport queries and result sets and allows clients to make use of server-side search facilities. [DASLREQ] describes the motivation for DASL.
9 DASL will minimize the complexity of clients so as to facilitate widespread deployment of applications capable of utilizing the DASL search mechanisms.
10 DASL consists of:
18 DASL relies on the resource and property model defined by [RFC2518]. DASL does not alter this model. Instead, DASL allows clients to access DAV-modeled resources through server-side search.
20 The augmented BNF used by this document to describe protocol elements is exactly the same as the one described in Section 2.1 of [RFC2616]. Because this augmented BNF uses the basic production rules provided in Section 2.2 of [RFC2616], those rules apply to this document as well.
21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT" "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
|I namespace (type: change, status: closed)|
|email@example.com||2002-01-25||As this is an individual (non working group) submission, it should not use the DAV: namespace for any new elements. Need to collect feedback.|
25 One can express the basic usage of DASL in the following steps:
30 The client invokes the SEARCH method to initiate a server-side search. The body of the request defines the query. The server MUST emit
text/xml entity matching the [RFC2518] PROPFIND response.
31 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.
32 The client invokes the SEARCH method on the resource named by the Request-URI.
33 The Request-URI identifies the search arbiter.
|I JW3 (type: change, status: closed)|
|firstname.lastname@example.org||1999-04-26||This specification essentially defines a new type of Web resource, of type "search arbiter". This raises a number of questions regarding how this kind of resource interacts with existing HTTP methods. I would expect to see a section which goes through and details the interactions between HTTP and WebDAV methods and search arbiters. For example, it seems reasonable to me to allow a search arbiter to potentially reply to GET (perhaps with a human-meaningful description of the capabilities of the arbiter), and for this GET response to potentially be authorable using PUT, and locked using LOCK. However, I wouldn't expect COPY, MOVE, or DELETE to work, although I would expect PROPPATCH and PROPFIND to work OK. Another issue is what kind of resource type a search arbiter returns in the resourcetype property (I'd expect a <searcharbiter/> element).|
|email@example.com||1999-04-26||How does a search arbiter respond to searches, if the search arbiter URI is within a search scope? The answer to this is related to the answer to whether a search arbiter has its own properties, body, etc.|
|firstname.lastname@example.org||2002-03-03||A SEARCH arbiter is no special kind of resource and thus this spec doesn't define any particular behaviour.|
|Martin.Wallmer@softwareag.com||2002-03-08||for my understanding the term "search arbiter" is an abstract term for a piece of software, that suplies the SEARCH funcionality. As DASL is an extension of WEBDAV, this piece of software will always be a complete WebDAV server with the well defined behavior of GET, PROPFIND and so on. So no additional definition is necessesary IMHO.|
34 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, the FOO query grammar may force the request-URI to correspond exactly to the search scope.
|I JW9 (type: change, status: closed)|
|email@example.com||1999-04-26||How does a DAV client discover which search arbiter can be used to search a portion of the DAV namespace? At present, the specification seems to imply two things (a) that "/" might be a typical arbiter, and (b) that other arbiters can exist and you can get redirected to them. If this issue isn't addressed in the specification, it might lead to clients having hard-coded search arbiter locations, thus forcing servers to put an arbiter at those locations or be non-interoperable. Or, it will require clients to be configured with the search arbiter location, which also seems bad. It seems far better to have a predefined mechanism which clients can use to discover the location of the search arbiter. One simple mechanism would be to define a property on each collection (but not each resource) which gives the location(s) of appropriate arbiters.|
|julian.reschke||2002-03-10||If a WebDAV-enabled collection is smart enough to know about search arbiters in scope, couldn't it be just forward SEARCH requests to those (making itself a kind of proxy arbiter?). Issue closed as this doesn't seem to solve the *general* discovery problem.|
35 The server MUST process a text/xml or application/xml request body, and MAY process request bodies in other formats. See [RFC3023] for guidance on packaging XML in requests.
36 If the client sends a text/xml or application/xml body, it MUST include the DAV:searchrequest XML element. The DAV:searchrequest XML element identifies the query grammar, defines the criteria, the result record, and any other details needed to perform the search.
<!ELEMENT searchrequest ANY >
37 The DAV:searchrequest XML element contains a single XML element that defines the query. The name of the query element defines the type of the query. The value of that element defines the query itself.
|I JW8 (type: change, status: closed)|
|firstname.lastname@example.org||2000-04-20||Is the response from SEARCH cacheable? (No).|
38 If the server returns 207 (Multistatus), then the search proceeded successfully and the response MUST match that of a PROPFIND.
39 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.
40 In addition, the server MAY include DAV:response items in the reply where the DAV:href element contains a URI that is not a matching resource, e.g. that of a scope or the query arbiter. Each such response item MUST NOT contain a DAV:propstat element, and MUST contain a DAV:status .
It SHOULD contain a DAV:responsedescription.
41 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.
42 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 FOO:natural-language-query, thus the type of the query is FOO:natural-language-query. 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.
|I encoding (type: edit, status: closed)|
|email@example.com||2002-02-18||Make sure that all examples specify an encoding when content type text/xml is used.|
43 >> Request:
SEARCH / HTTP/1.1 Host: ryu.com Content-Type: application/xml Content-Length: xxx <?xml version="1.0" encoding="UTF-8"?> <D:searchrequest xmlns:D="DAV:" xmlns:F="http://example.com/foo"> <F:natural-language-query> Find the locations of good Thai restaurants in Los Angeles </F:natural-language-query> </D:searchrequest>
44 >> Response:
HTTP/1.1 207 Multi-Status Content-Type: text/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="UTF-8"?> <D:multistatus xmlns:D="DAV:" xmlns:F="http://example.com/foo" xmlns:R="http://ryu.com/propschema"> <D:response> <D:href>http://siamiam.com/</D:href> <D:propstat> <D:prop> <R:location>259 W. Hollywood</R:location> <R:rating><R:stars>4</R:stars></R:rating> </D:prop> </D:propstat> </D:response> </D:multistatus>
52 If an error occurred that prevented execution of the query, the server MUST indicate the failure with the appropriate status code and SHOULD include a DAV:multistatus element to point out errors associated with scopes.
53 400 Bad Request. The query could not be executed. The request may be malformed (not valid XML for example). Additionally, this can be used for invalid scopes and search redirections.
54 422 Unprocessable entity. The query could not be executed. If a text/xml request entity was provided, then it may have been
valid (well-formed ) but may have contained an unsupported or unimplemented query operator.
|I JW4/DB4/DB5 (type: change, status: closed)|
|firstname.lastname@example.org||1999-04-26||Section 2.5 states that the 507 (Insufficient Storage) status code should be returned when SEARCH produces more responses that the server is willing to immediately return. A 5xx status code isn't appropriate for this case, since the response does have valid search results, indicating that the client correctly submitted a search, and this search was successfully performed by the server, even if it isn't returning all search results. I recommend defining a new status code for this case, 208 (Partial Results).|
|email@example.com||2000-04-20||When results are truncated, server replies with a 507 and also returns an XML element.|
|firstname.lastname@example.org||2000-04-20||507 is currently in conflict with other specs. Need to avoid collisions.|
|email@example.com||2002-02-18||Use 207 (Multistatus) instead.|
55 507 (Insufficient Storage). The query produced more results than the server was willing to transmit. Partial results have been transmitted. The server MUST send a body that matches that for 207, except that there MAY exist resources that matched the search criteria for which no corresponding DAV:response exists in the reply.
56 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 507. It SHOULD include the partial results.
57 When a result set is truncated, there may be many more resources that satisfy the search criteria but that were not examined.
58 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.
59 Note that the partial results returned MAY be any subset of the result set that would have satisfied the original query.
60 >> Request:
SEARCH / HTTP/1.1 Host: gdr.com Content-Type: application/xml Content-Length: xxxxx <?xml version="1.0" encoding="UTF-8"?> <D:searchrequest xmlns:D="DAV:"> <D:basicsearch> ... the query goes here ... </D:basicsearch> </D:searchrequest>
61 >> Response:
HTTP/1.1 507 Insufficient Storage Content-Type: text/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="UTF-8"?> <D:multistatus xmlns:D="DAV:"> <D:response> <D:href>http://www.gdr.com/sounds/unbrokenchain.au</D:href> <D:propstat> <D:prop/> <D:status>HTTP/1.1 200 OK</D:status> </D:propstat> </D:response> <D:response> <D:href>http://tech.mit.edu/archive96/photos/Lesh1.jpg</D:href> <D:propstat> <D:prop/> <D:status>HTTP/1.1 200 OK</D:status> </D:propstat> </D:response> <D:response> <D:href>http://gdr.com</D:href> <D:status>HTTP/1.1 507 Insufficient Storage</D:status> <D:responsedescription> Only first two matching records were returned </D:responsedescription> </D:response> </D:multistatus>
62 A client may submit a scope that the arbiter may be unable to query. The inability to query may be due to network failure, administrative policy, security, etc. This raises the condition described as an "invalid scope".
63 To indicate an invalid scope, the server MUST respond with a 400 (Bad Request).
64 The response includes a
text/xml body with a DAV:multistatus element. Each DAV:response in the DAV:multistatus identifies a scope. To indicate that this scope is the source of the error, the server MUST include the DAV:scopeerror element.
65 >> Response:
HTTP/1.1 400 Bad-Request Content-Type: text/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="UTF-8"?> <d:multistatus xmlns:d="DAV:"> <d:response> <d:href>http://www.foo.com/X</d:href> <d:status>HTTP/1.1 404 Object Not Found</d:status> <d:scopeerror/> </d:response> </d:multistatus>
66 Servers MUST support discovery of the query grammars supported by a search arbiter resource.
67 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.
71 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.
72 The client issues the OPTIONS method against a resource named by the Request-URI. This is a normal invocation of OPTIONS defined in [RFC2616].
73 If a resource supports the SEARCH method, then the server MUST list SEARCH in the OPTIONS response as defined by [RFC2616].
74 DASL servers MUST include the DASL header in the OPTIONS response. This header identifies the search grammars supported by that resource.
75 >> Response:
DASLHeader = "DASL" ":" Coded-URL-List Coded-URL-List : Coded-URL [ "," Coded-URL-List ] Coded-URL ; defined in section 9.4 of [RFC2518]
|I URI-vs-QNAME (type: change, status: closed)|
|firstname.lastname@example.org||2001-10-17||Here, a grammar is represented as an URI. Later, a grammar is identified by a Qualified XML name (URI reference + local name). This means that the client needs to be aware of a mapping from a URI (that's reported here) to an XML element name (that it can use in a query). Proposal: report XML-based grammars through a different mechanism in SEARCH (details to be done).|
77 This header MAY be repeated.
78 For example:
DASL: <http://foo.bar.com/syntax1> DASL: <http://akuma.com/syntax2> DASL: <DAV:basicsearch> DASL: <http://example.com/foo/natural-language-query>
81 This example shows that the server supports search on the /somefolder resource with the query grammars: DAV:basicsearch, http://foo.bar.com/syntax1 and http://akuma.com/syntax2. Note that every server MUST support DAV:basicsearch.
82 >> Request:
OPTIONS /somefolder HTTP/1.1 Host: ryu.com
83 >> Response:
HTTP/1.1 200 OK Date: Tue, 20 Jan 1998 20:52:29 GMT Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE, MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, SEARCH DASL: <DAV:basicsearch> DASL: <http://foo.bar.com/syntax1> DASL: <http://akuma.com/syntax2>
88 Servers MAY support the discovery of the schema for a query grammar.
89 The DASL response header provides 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 a optional operator that can be used to express content-based queries in a proprietary syntax. QSD allows a client to discover these operators and their syntax. The set of discoverable quantities will differ from grammar to grammar, but each grammar can define a means for a client to discover what can be discovered.
90 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 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.
|I qsd-pseudo-property (type: , status: open)|
|email@example.com||2002-01-25||It would be nice to avoid the definition of a "pseudo" property just for this special use case.|
92 The query schema for DAV:basicsearch is defined in Section 5.19.
<!ELEMENT queryschema ANY >
93 In this example, the arbiter is recipes.com, the grammar is DAV:basicsearch, the scope is also recipes.com.
94 >> Request:
|I queryschema-prop (type: change, status: closed)|
|firstname.lastname@example.org||2001-10-09||DAV:queryschema does not appear in a DAV:prop. Intentional?|
SEARCH / HTTP/1.1 Host: recipes.com Content-Type: application/xml Content-Length: xxx <?xml version="1.0"?> <D:searchrequest xmlns:D="DAV:" > <D:basicsearch> <D:select> <D:queryschema/> </D:select> <D:from> <D:scope> <D:href>http://recipes.com</D:href> </D:scope> </D:from> </D:basicsearch> </D:searchrequest>
96 >> Request:
|I querygrammar-prop (type: change, status: closed)|
|email@example.com||2001-10-09||DAV:queryschema was selected, but DAV:querygrammar was returned.|
HTTP/1.1 207 Multistatus Content-Type: application/xml Content-Length: xxx <?xml version="1.0"?> <D:multistatus xmlns:D="DAV:"> <D:response> <D:href>http://recipes.com</D:href> <D:propstat> <D:prop> <D:querygrammar> <D:basicsearchschema> /See section 5.19.9 for actual contents) </D:basicsearchschema> </D:querygrammar> </D:prop> <D:status>HTTP/1.1 200 Okay</D:status> </D:propstat> </D:response> </D:multistatus>
98 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 others grammars.
99 DAV:basicsearch has several components:
|I JW24d (type: , status: open)|
|firstname.lastname@example.org||2000-04-20||Where does xml:lang go in a query?|
|email@example.com||2002-02-28||What would be the *purpose* of putting xml:lang into a query?|
|I DB7 (type: change, status: closed)|
|firstname.lastname@example.org||2000-04-20||Searches on XML chunks that include namespaces. Need to expand out the XML namespace when doing the search (i.e., do search on DAV:foo, not X:foo xmlns:X="DAV:") Also an issue for expressing searches on XML sub-elements of properties.|
|email@example.com||2002-01-28||I think this is out-of-scope for now.|
<!ELEMENT basicsearch (select, from, where?, orderby?, limit?) > <!ELEMENT select (allprop | prop) > <!ELEMENT from (scope) > <!ELEMENT scope (href, depth?) > <!ENTITY %comp_ops "eq | lt | gt| lte | gte"> <!ENTITY %log_ops "and | or | not"> <!ENTITY %special_ops "isdefined"> <!ENTITY %string_ops "like"> <!ENTITY %content_ops "contains"> <!ENTITY %all_ops "%comp_ops; | %log_ops; | %special_ops; | %string_ops; | %content_ops;"> <!ELEMENT where ( %all_ops; ) > <!ELEMENT and ( ( %all_ops; ) +) > <!ELEMENT or ( ( %all_ops; ) +) > <!ELEMENT not ( %all_ops; ) > <!ELEMENT lt ( prop , literal ) > <!ATTLIST lt casesensitive (1|0) "1" > <!ELEMENT lte ( prop , literal ) > <!ATTLIST lte casesensitive (1|0) "1" > <!ELEMENT gt ( prop , literal) > <!ATTLIST gt casesensitive (1|0) "1" > <!ELEMENT gte ( prop , literal ) > <!ATTLIST gte casesensitive (1|0) "1" > <!ELEMENT eq ( prop , literal ) > <!ATTLIST eq casesensitive (1|0) "1" > <!ELEMENT literal (#PCDATA)> <!ATTLIST literal xml:space (default|preserve) preserve > <!ELEMENT isdefined (prop) > <!ELEMENT like (prop, literal) > <!ATTLIST like casesensitive (1|0) "1" > <!ELEMENT contains (#PCDATA)> <!ELEMENT orderby (order+) > <!ELEMENT order (prop, (ascending | descending)?) <!ATTLIST order casesensitive (1|0) "1" > <!ELEMENT ascending EMPTY> <!ELEMENT descending EMPTY> <!ELEMENT limit (nresults) > <!ELEMENT nresults (#PCDATA) >
106 This query retrieves the content length values for all resources located under the server's "/container1/" URI namespace whose length exceeds 10000.
<d:searchrequest xmlns:d="DAV:"> <d:basicsearch> <d:select> <d:prop><d:getcontentlength/></d:prop> </d:select> <d:from> <d:scope> <d:href>/container1/</d:href> <d:depth>infinity</d:depth> </d:scope> </d:from> <d:where> <d:gt> <d:prop><d:getcontentlength/></d:prop> <d:literal>10000</d:literal> </d:gt> </d:where> <d:orderby> <d:order> <d:prop><d:getcontentlength/></d:prop> <d:ascending/> </d:order> </d:orderby> </d:basicsearch> </d:searchrequest>
107 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 [RFC2518].
108 If the value is DAV:allprop, the result record for a given resource includes all the properties for that resource.
109 If the value is DAV:prop, then the result record for a given resource includes only those properties named by the DAV:prop element. Each property named by the DAV:prop element must be referenced in the Multistatus response.
110 The rules governing the status codes for each property match those of the PROPFIND method defined in [RFC2518].
111 DAV:from defines the query scope. This contains exactly one DAV:scope element.
The scope element contains a mandatory DAV:href element and an optional DAV:depth element.
|I DB3 (type: change, status: closed)|
|firstname.lastname@example.org||2000-04-20||What should the default Depth value be for SEARCH?|
|email@example.com||2000-04-20||Agreement that Depth must be sent with SEARCH.|
112 DAV:href indicates the URI for a collection to use as a scope.
113 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 (toplevel) members of the collection. When it is "infinity", the search includes all recursive members of the collection.
114 If the DAV:scope element is an absolute URI, the scope is exactly that URI.
|I JW12 (type: change, status: closed)|
|firstname.lastname@example.org||2000-04-20||Allowing relative URIs isn't very useful.|
|email@example.com||2000-04-24||Accepted 24 April 2000.|
|firstname.lastname@example.org||2002-02-18||Need agreement on either forbidding relate URIs or leaving them in (which doesn't seem to be hard to implement).|
|email@example.com||2002-03-03||Relative URI reference resolving code is required in WebDAV anyway, so the issue is closed.|
115 If the DAV:scope element is
a relative URI, the scope is taken to be relative to the request-URI.
116 A Scope can be an arbitrary URI.
|I URIs (type: change, status: closed)|
|firstname.lastname@example.org||2002-03-03||Need to cleanup draft to use correct terms for URIs and URI references.|
117 Servers, of course, may support only particular scopes. This may include limitations for particular schemes such as "http:" or "ftp:" or certain URI namespaces.
118 If a scope is given that is not supported the server MUST respond with a 400 status code that includes a Multistatus error. A scope in the query appears as a resource in the response and must include an appropriate status code indicating its validity with respect to the search arbiter.
HTTP/1.1 400 Bad Request Content-Type: text/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="UTF-8"?> <d:multistatus xmlns:d="DAV:"> <d:response> <d:href>http://www.foo.com/scope1</d:href> <d:status>HTTP/1.1 502 Bad Gateway</d:status> </d:response> </d:multistatus>
120 This example shows the response if there is a scope error. The response provides a Multistatus with a status for the scope. In this case, the scope cannot be reached because the server cannot search another server (502).
121 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.
|I query-on-href (type: , status: open)|
|email@example.com||2002-02-28||DAV:href isn't a property, so it can't be used in queries. Is this a problem? Examples where DAV:displayname is queried instead seem to indicate that. A possible solution would be to allow DAV:href whereever DAV:prop is allowed in the where clause.|
122 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.
123 Consult Appendix A for details on the application of three-valued logic in query expressions.
124 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.
125 If a PROPFIND for a property value would yield a 404 or 403 response for that property, then that property is considered NULL.
126 NULL values are "less than" all other values in comparisons.
127 Empty strings (zero length strings) are not NULL values. An empty string is "less than" a string with length greater than zero.
128 The DAV:isdefined operator is defined to test if the value of a property is NULL.
130 The example shows a single operator (DAV:eq) applied in the criteria.
<d:where> <d:eq> <d:prop> <d:getcontentlength/> </d:prop> <d:literal> 100 </d:literal> </d:eq> </d:where>
131 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 that are "image/gifs" over 4K in size.
<D:where> <D:and> <D:eq> <D:prop> <D:getcontenttype/> </D:prop> <D:literal> image/gif </D:literal> </D:eq> <D:gt> <D:prop> <D:getcontentlength/> </D:prop> <D:literal> 4096 </D:literal> </D:gt> </D:and> </D:where>
132 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.
|I JW13 (type: edit, status: closed)|
|firstname.lastname@example.org||1999-04-26||Section 5.6 should have a separate section, with a separate heading, for the description of ascending and descending. I had a hard time finding these descriptions without this section heading.|
|email@example.com||2002-03-03||Added to index.|
133 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.
|I null-ordering (type: , status: open)|
|firstname.lastname@example.org||2002-02-20||In the WebDAV SEARCH spec (5.6, DAV:orderby), it says that nulls sort low, to match SQL92. However, SQL92 and SQL99 both say "Whether a sort key value that is null is considered greater or less than a non-null value is implementation-defined, but all sort key values that are null shall either be considered greater than all non-null values or be considered less than all non-null values." (words taken from SQL99, 14.1 <declare cursor> General Rule 2)c), in reference to null handling for the <order by clause>. ) I would note that in 5.5.3 WebDAV SEARCH says nulls are less than all other values in a comparison, so the DAV:orderby matches that statement, it just gives an inaccurate reason.|
134 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 (
as in ANSI standard SQL, [ANSISQL]).
|I language-comparison (type: , status: open)|
|email@example.com||2002-03-03||XPath/XQuery (see draft, and open issue) specify string comparisons based on collations, not languages. I think we should adopt this. This would mean that "xml:lang" would be removed, and an optional attribute specifying the name of the collation is added.|
135 Comparisons on strings take into account the language defined for that property. Clients MAY specify the language using the xml:lang attribute. If no language is specified either by the client or defined for that property by the server or if a comparison is performed on strings of two different languages, the results are undefined.
|I case-insensitivity (type: change, status: closed)|
|firstname.lastname@example.org||2001-10-17||I think case-insensitive comparison is underspecified here (what does it mean for generic Unicode strings?)|
137 This sort orders first by last name of the author, and then by size, in descending order, so that the largest works appear first.
<d:orderby> <d:order> <d:prop><r:lastname/></d:prop> <d:ascending/> </d:order> <d:order> <d:prop><d:getcontentlength/></d:prop> <d:descending/> </d:order> </d:orderby>
138 The DAV:and operator performs a logical AND operation on the expressions it contains.
139 The DAV:or operator performs a logical OR operation on the values it contains.
140 The DAV:not operator performs a logical NOT operation on the values it contains.
|I JW24c (type: , status: open)|
|email@example.com||2000-04-20||How do string equality and language tag interact. Cross-language comparison should work at least when the two languages are dialects, e.g. en-us vs en-uk.|
|firstname.lastname@example.org||2002-01-28||Proposal: strings match if and only if they match character by character.|
141 The DAV:eq operator provides simple equality matching on property values.
142 The DAV:casesensitive attribute may be used with this element.
|I JW16b/JW24a (type: , status: open)|
|email@example.com||2000-04-20||Define how comparisons on strings work, esp for i18n.|
Need policy statement about sort order in various national languages. (JW said "non-Latin" but it's an issue even in languages that use the latin char set.)
143 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 DAV:casesensitive attribute may be used with these elements.
|I DB2/DB7 (type: , status: open)|
|firstname.lastname@example.org||2000-04-20||Dates (HTTPDate in getlastmodified).|
|email@example.com||2000-04-20||Agreement that it is OK to submit isodate to search HTTPDate (i.e., it's a marshalling issue only).|
|firstname.lastname@example.org||2000-04-20||Booleans appear to be underspecified in the specification. How is a boolean tested, and what are the behavior of operators like less than, greater than, etc.|
|email@example.com||2002-01-28||I think similar questions apply to booleans. Proposal: allow specification of the literal's type using XML Schema simple types, and declare that "both" WebDAV date types are compatible.|
The current DASL draft doesn't really have Booleans or any other data type.
It's trying to skate on data types. Booleans could be tested using the "eq"
and the combination "not eq", if you had well defined literals for TRUE and
FALSE. With the current syntax, that is the way you would have to test a
Boolean. Generally, Boolean values are not considered to be ordered, so "gt"
etc. wouldn't apply. However, if the literal values of a Boolean were 1 and
0 for TRUE and FALSE (using the most commonly used convention of positive
logic), then you would have an obvious ordering. 1 and 0 have the advantage
of being language independent. You now see a lot of electronic and
electro-mechanical devices (air conditioners, computers, etc.) with a "1/0"
label on the power switch, "1" meaning "on", and "0" meaning "off".
SQL databases don't have Booleans. SQL doesn't control DASL, of course, but SQL databases are so widely used that they are important. The closest thing in SQL is a bit field. Each bit in a bit field is zero or 1.
So, why not close the issue by saying: DASL doesn't have data types. You can simulate Booleans by an integer data type, using 1 for "TRUE" and 0 for "FALSE".
144 DAV:literal allows literal values to be placed in an expression.
|I JW14 (type: change, status: closed)|
|firstname.lastname@example.org||2000-04-20||How does xml:space affect DAV:literal.|
|email@example.com||2002-01-28||Do we just need an example here?|
|firstname.lastname@example.org||2002-03-01||Re-opened: see discussion in DASL mailing list: using xml:space would be inconsistent with WebDAV.|
Because white space in literal values is significant in comparisons, DAV:literal makes use of the xml:space attribute to identify this significance. The default value of this attribute for DAV:literal is "preserve". Consult section 2.10 of [XML] for more information on the use of this attribute.
149 The DAV:isdefined operator allows clients to determine whether a property is defined on a resource. The meaning of "defined on a resource" is found in Section 5.5.3.
<d:isdefined> <d:prop><x:someprop/></d:prop> </d:isdefined>
151 The DAV:isdefined operator is optional.
152 The DAV:like is an optional operator intended to give simple wildcard-based pattern matching ability to clients.
153 The operator takes two arguments.
154 The first argument is a DAV:prop element identifying a single property to evaluate.
|I JW14b (type: change, status: closed)|
|email@example.com||2000-04-20||The semantics of DAV:literal should not change inside a DAV:like.|
|firstname.lastname@example.org||2002-01-28||Does it? Need details.|
|email@example.com||2002-03-03||Closed; I think this is clear from the spec.|
155 The second argument is a DAV:literal element that gives the pattern matching string.
Pattern := [wildcard] 0*( text [wildcard] ) wildcard := exactlyone | zeroormore text := 1*( <octet> | escapesequence ) exactlyone : = "?" zeroormore := "%" escapechar := "\" escapesequence := "\" ( exactlyone | zeroormore | escapechar )
|I JW15 (type: change, status: closed)|
|firstname.lastname@example.org||1999-04-26||The BNF for a wildcard permits the entry of "</d:literal>" which would confuse parsers. Also, the BNF sequence for text should use characters instead of octets, to better handle multi-octet character set representations (like UTF-16).|
|email@example.com||2002-03-03||Non-issue: the contents of the DAV:literal element is subject to normal XML escaping. Grammar changed to use chars rather than octets.|
156 The value for the literal is composed of wildcards separated by segments of text. Wildcards may begin or end the literal. Wildcards may not be adjacent.
157 The "?" wildcard matches exactly one character.
158 The "%" wildcard matches zero or more characters
159 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..
160 This example shows how a client might use DAV:like to identify those resources whose content type was a subtype of image.
<D:where> <D:like> <D:prop><D:getcontenttype/></D:prop> <D:literal>image%</D:literal> </D:like> </D:where>
|I JW17/JW24b (type: , status: open)|
|firstname.lastname@example.org||2000-04-20||5.13 should discuss handling of queries when character set differs.
Some text on handling character sets would be helpful.
161 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 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.
162 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.
163 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 left to the server.
164 The following things 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.
165 The DAV:score property is intended to be useful to rank documents satisfying the DAV:contains operator.
166 The example below shows a search for the phrase "Peter Forsberg".
167 Depending on its support for content-based searching, a server MAY treat this as a search for documents that contain the words "Peter" and "Forsberg".
<D:where> <D:contains>Peter Forsberg</D:contains> </D:where>
168 The example below shows a search for resources that contain "Peter" and "Forsberg".
<D:where> <D:and> <D:contains>Peter</D:contains> <D:contains>Forsberg</D:contains> </D:and> </D:where>
<!ELEMENT limit (nresults) >
169 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.
<!ELEMENT nresults (#PCDATA)> ;only digits
|I JW5 (type: , status: open)|
|email@example.com||1999-04-26||On the topic of partial search results, DASL currently has no way for a client to request the next chunk of a set of search results. Since *every* search service I've interacted with on the Internet has a feature for returning the next set of search results, I really would expect this feature to be in DASL. An explanation for why this feature isn't present should be in the protocol specification if it is not going to be supported.|
|Martin.Wallmer@softwareag.com||2002-03-08||of course this issue is legitim. However, as basicsearch should be as simple as possible, I tend to say out of scope as well. But perhaps this could be an optional feature (is it that, what you mean by extension to DAV:basicsearch)?|
|firstname.lastname@example.org||2002-03-08||Moved into DAV:basicsearch section, because this is a request for a specific query grammar feature.|
170 The DAV:nresults XML element contains a requested maximum number of records to be returned in a reply. The server MAY disregard this limit. The value of this element is an integer.
|I case-insensitivity-name (type: , status: open)|
|email@example.com||2002-01-09||The attribute probably should be renamed to "caseless".|
172 The possible values for DAV:casesensitive are "1" or "0". The "1" value indicates case-sensitivity. The "0" value indicates case-insensitivity. The default value is server-specified.
173 Support for the DAV:casesensitive is optional. A server should respond with an error 422 if the DAV:casesensitive attribute is used but cannot be supported.
<!ELEMENT score (#PCDATA)>
174 The DAV:score XML element is a synthetic property whose value is defined only in the context of a query result where the server computes a score, e.g. based on relevance. It may be used in DAV:select or DAV:orderby elements. Servers SHOULD support this property. 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).
175 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.
|I score-pseudo-property (type: , status: open)|
|firstname.lastname@example.org||2002-02-28||Shouldn't be done using a pseudo-property. Report it as child of DAV:propstat instead?|
<!ELEMENT iscollection (#PCDATA)>
176 The DAV:iscollection XML element is a synthetic property whose value is defined only in the context of a query.
177 The property is TRUE (the literal string "1") of a resource if and only if a PROPFIND of the DAV:resourcetype property for that resource would contain the DAV:collection XML element. The property is FALSE (the literal string "0") otherwise.
178 Rationale: This property 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.
|I iscollection-operator (type: change, status: closed)|
|email@example.com||2001-10-09||DAV:iscollection should be an operator rather than a pseudo-property. This both reduces special cases in implementations and avoids confusion with real properties.|
179 This example shows a search criterion that picks out all and only the resources in the scope that are collections.
<D:where> <D:eq> <D:prop><D:iscollection></D:prop> <D:literal>1<D:literal> </D:eq> </D:where>
|I bsschema-DTD (type: change, status: closed)|
|firstname.lastname@example.org||2001-10-17||(1) DTD needs to be cleaned up, (2) there should be a way to advertise propdescs for all properties not mentioned otherwise.|
<!ELEMENT basicsearchschema (properties, operators)> <!ELEMENT properties (propdesc*)> <!ELEMENT propdesc (prop, ANY)> <!ELEMENT operators (opdesc*)> <!ELEMENT opdesc ANY> <!ELEMENT operand_property EMPTY> <!ELEMENT operand_literal EMPTY>
|I naming-of-elements (type: change, status: closed)|
|email@example.com||2001-10-17||To stay consistent with other WebDav specs, I'd prefer to use "-" instead of "_" as separator.|
185 The DAV:operators element describes the optional operators that may be used in a DAV:where element.
186 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.
187 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:casesensitive) 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.
|I datatypes (type: change, status: closed)|
|firstname.lastname@example.org||2001-10-17||Should use standard datatypes from XML Schema Part 2 and also allow for user-defined types.|
<!ELEMENT datatype ANY >
191 DASL defines the following data type elements:
Name Example boolean 1, 0 string Foobar dateTime.iso8601tz 1994-11-05T08:15:5Z float .314159265358979E+1 int -259, 23
192 If the data type of a property is not given, then the data type defaults to string.
<!ELEMENT searchable EMPTY>
193 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.
<!ELEMENT selectable EMPTY>
194 This element indicates that the property may appear in the DAV:select element.
195 This element indicates that the property may appear in the DAV:orderby element.
<!ELEMENT sortable EMPTY>
196 This element only applies to properties whose data type is "string" as per the DAV:datatype property description. Its presence indicates that compares performed for searches, and the comparisons for ordering results on the string property will be case sensitive. (The default is case insensitive.)
<!ELEMENT casesensitive EMPTY>
197 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 consists of the operator (as an empty element), followed by one element for each operand. The operand MUST be either
DAV:operand_property or DAV:operand_literal, which indicate that the operand in the corresponding position is a property or a literal value, respectively. If an operator is polymorphic (allows more than one operand syntax) then each permitted syntax MUST be listed separately.
<D:propdesc> <D:like/><D:operand_property/><D:operand_literal/> </D:propdesc>
<D:basicsearchschema xmlns:D="DAV:" xmlns:t="urn:uuid:C2F41010-65B3-11d1-A29F-00AA00C14882/" xmlns:J="http://jennicam.org"> <D:properties> <D:propdesc> <D:prop><D:getcontentlength/></D:prop> <D:datatype><t:int/></D:datatype> <D:searchable/><D:selectable/><D:sortable/> </D:propdesc> <D:propdesc> <D:prop><D:getcontenttype/><D:displayname/></D:prop> <D:searchable/><D:selectable/> <D:sortable/> </D:propdesc> <D:propdesc> <D:prop><J:fstop/></D:prop> <D:selectable/> </D:propdesc> </D:properties> <D:operators> <D:opdesc> <D:isdefined/><D:operand_property/> </D:opdesc> <D:opdesc> <D:like/><D:operand_property/><D:operand_literal/> </D:opdesc> </D:operators> </D:basicsearchschema>
198 This response lists four properties. The datatype of the last three properties is not given, so it defaults to 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:isdefined and DAV:like are supported.
199 Note: The schema discovery defined here does not provide for discovery of supported values of the DAV:casesensitive attribute. This may require that the reply also list the mandatory operators.
200 Clients have the opportunity to tag properties when they are stored in a language. The server SHOULD read this language-tagging by examining the xml:lang attribute on any properties stored on a resource.
201 The xml:lang attribute specifies a nationalized collation sequence when properties are compared.
202 Comparisons when this attribute differs have undefined order.
|I JW25/JW26 (type: , status: open)|
|email@example.com||2000-04-20||In Security Considerations, copy XML considerations from webDAV spec.|
|firstname.lastname@example.org||2000-04-20||Wouldn't it be better to just cite the XML document, so that if that document is updated, we won't have stale information?|
|email@example.com||2000-04-20||In Security Considerations, mention privacy risks of queries.|
|firstname.lastname@example.org||2002-01-28||Is this resolved?|
203 This section is provided to detail issues concerning security implications of which DASL applications need to be aware. All of the security considerations of HTTP/1.1 also apply to DASL. In addition, this section will include security risks inherent in searching and retrieval of resource properties and content.
204 A query must not allow one to retrieve information about values or existence of properties that one could not obtain via PROPFIND. (e.g. by use in DAV:orderby, or in expressions on properties.)
205 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. 7.1 Implications of XML External Entities
206 XML supports a facility known as "external entities", defined in section 4.2.2 of [XML], which instruct an XML processor to retrieve and perform an inline include of XML located at a particular URI. An external XML entity can be 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 [XML]. However, [XML] does state that an XML processor may, at its discretion, include the external XML entity.
207 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 [RFC3023]. Therefore, implementers must be aware that external XML entities should be treated as untrustworthy.
208 There is also the scalability risk that would accompany a widely deployed application which 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 which fields requests for the resource containing the external XML entity.
209 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://")
210 Authentication mechanisms defined in WebDAV will also apply to DASL.
212 To be supplied.
213 To be supplied.
|[ACL]||Clemm, G., Hopkins, A., Sedlar, E., and J. Whitehead, “WebDAV Access Control Protocol”, ID draft-ietf-webdav-acl-07, November 2001, <http://www.webdav.org/acl/protocol/draft-ietf-webdav-acl-07.htm>.|
|[RFC2119]||Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels”, BCP 14, RFC 2119, March 1997.|
|[RFC2518]||Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. Jensen, “HTTP Extensions for Distributed Authoring -- WEBDAV”, RFC 2518, February 1999.|
|[RFC2616]||Fielding, R., Gettys, J., Mogul, J., Nielsen, H., Masinter, L., Leach, P., and T. Berners-Lee, “Hypertext Transfer Protocol -- HTTP/1.1”, RFC 2616, June 1999.|
|[RFC3023]||Makoto, M., St.Laurent, S., and D. Kohn, “XML Media Types”, RFC 3023, January 2001.|
|[RFC3253]||Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. Whitehead, “Versioning Extensions to WebDAV”, RFC 3253, March 2002.|
|[XML]||Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler, “Extensible Markup Language (XML) 1.0 (2nd ed)”, W3C REC-xml, October 2000, <http://www.w3.org/TR/2000/REC-xml-20001006>.|
|[XMLNS]||Bray, T., Hollander, D., and A. Layman, “Namespaces in XML”, W3C REC-xml-names, January 1999, <http://www.w3.org/TR/REC-xml-names>.|
|[XS2]||Biron, P., Malhotra, A., and World Wide Web Consortium, “XML Schema Part 2: Datatypes”, W3C XS2, May 2001, <http://www.w3.org/TR/xmlschema-2/>.|
|[CaseMap]||Davis, M., “Case Mappings”, Unicode Techical Reports 21, February 2001, <http://www.unicode.org/unicode/reports/tr21>.|
|[DASL]||Reddy, S., Lowry, D., Reddy, S., Henderson, R., Davis, J., and A. Babich, “DAV Searching & Locating”, ID draft-dasl-protocol-00, July 1999, <http://www.webdav.org/dasl/protocol/draft-dasl-protocol-00.html>.|
|[DASLREQ]||Davis, J., Reddy, S., and J. Slein, “Requirements for DAV Searching and Locating”, ID draft-dasl-requirements-01, February 1999, <http://www.webdav.org/dasl/requirements/draft-dasl-requirements-01.html>.|
|[SQL99]||Milton, J., “Database Language SQL Part 2: Foundation (SQL/Foundation)”, ISO ISO/IEC 9075-2:1999 (E), July 1999.|
410 Jessie Street 6th floor
San Francisco, CA 94103
219 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.).
220 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.
221 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 (either because the property is not defined for the current resource, or because it is null for the current resource), 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.
222 If any subpart of an arithmetic, string, or datetime subexpression is undefined, the whole arithmetic, string, or datetime subexpression is undefined.
223 There are no manifest constants to explicitly represent undefined number, string, or datetime values.
224 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.
225 The Boolean operators DAV:and, DAV:or and DAV:not are evaluated according to the following rules:
226 UNKNOWN and UNKNOWN = UNKNOWN
227 UNKNOWN or UNKKNOWN = UNKNOWN
228 not UNKNOWN = UNKNOWN
229 UNKNOWN and TRUE = UNKNOWN
230 UNKNOWN and FALSE = FALSE
231 UNKNOWN and UNKNOWN = UNKNOWN
232 UNKNOWN or TRUE = TRUE
233 UNKNOWN or FALSE = UNKNOWN
234 UNKNOWN or UNKNOWN = UNKNOWN
Copyright © The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an “AS IS” basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.