RFC5323 日本語訳

5323 Web Distributed Authoring and Versioning (WebDAV) SEARCH. J.Reschke, Ed., S. Reddy, J. Davis, A. Babich. November 2008. (Format: TXT=91077 bytes) (Status: PROPOSED STANDARD)
プログラムでの自動翻訳です。
RFC一覧
英語原文

Network Working Group                                    J. Reschke, Ed.
Request for Comments: 5323                                    greenbytes
Category: Standards Track                                       S. Reddy
                                                                  Mitrix
                                                                J. Davis

ワーキンググループJ.Reschke、エドをネットワークでつないでください。コメントのために以下を要求してください。 5323greenbytes Category: 標準化過程S.レディ・Mitrix J.デイヴィス

                                                               A. Babich
                                                                     IBM
                                                           November 2008

A.Babich IBM2008年11月

        Web Distributed Authoring and Versioning (WebDAV) SEARCH

ウェブの分配されたオーサリングとVersioning(WebDAV)検索

Status of This Memo

このメモの状態

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

このドキュメントは、インターネットコミュニティにインターネット標準化過程プロトコルを指定して、改良のために議論と提案を要求します。 このプロトコルの標準化状態と状態への「インターネット公式プロトコル標準」(STD1)の現行版を参照してください。 このメモの分配は無制限です。

Copyright Notice

版権情報

   Copyright (c) 2008 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Copyright(c)2008IETF Trustと人々はドキュメントとして作者を特定しました。 All rights reserved。

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (http://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

事実上、このドキュメントはこのドキュメントの公表の日付にIETF Documents( http://trustee.ietf.org/ ライセンスインフォメーション)へのBCP78とIETF TrustのLegal Provisions Relatingを受けることがあります。 このドキュメントに関して権利と制限について説明するとき、慎重にこれらのドキュメントを再検討してください。

Abstract

要約

   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.

このドキュメントはウェブDistributed AuthoringとVersioning(WebDAV)検索(効率的にクライアントによって供給された評価基準のセットに基づくDAVリソースを検索するHTTP/1.1プロトコルの応用)を構成する1セットの方法、ヘッダー、および特性を指定します。

Reschke, et al.             Standards Track                     [Page 1]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[1ページ]。

Table of Contents

目次

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  DASL . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.2.  Relationship to DAV  . . . . . . . . . . . . . . . . . . .  4
     1.3.  Terms  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.4.  Notational Conventions . . . . . . . . . . . . . . . . . .  6
     1.5.  Note on Usage of 'DAV:' XML Namespace  . . . . . . . . . .  7
     1.6.  An Overview of DASL at Work  . . . . . . . . . . . . . . .  7
   2.  The SEARCH Method  . . . . . . . . . . . . . . . . . . . . . .  7
     2.1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . .  7
     2.2.  The Request  . . . . . . . . . . . . . . . . . . . . . . .  8
       2.2.1.  The Request-URI  . . . . . . . . . . . . . . . . . . .  8
       2.2.2.  The Request Body . . . . . . . . . . . . . . . . . . .  8
     2.3.  The Successful 207 (Multistatus) Response  . . . . . . . .  9
       2.3.1.  Result Set Truncation  . . . . . . . . . . . . . . . .  9
       2.3.2.  Extending the PROPFIND Response  . . . . . . . . . . . 10
       2.3.3.  Example: A Simple Request and Response . . . . . . . . 10
       2.3.4.  Example: Result Set Truncation . . . . . . . . . . . . 11
     2.4.  Unsuccessful Responses . . . . . . . . . . . . . . . . . . 12
       2.4.1.  Example of an Invalid Scope  . . . . . . . . . . . . . 12
   3.  Discovery of Supported Query Grammars  . . . . . . . . . . . . 13
     3.1.  The OPTIONS Method . . . . . . . . . . . . . . . . . . . . 13
     3.2.  The DASL Response Header . . . . . . . . . . . . . . . . . 14
     3.3.  DAV:supported-query-grammar-set (Protected)  . . . . . . . 14
     3.4.  Example: Grammar Discovery . . . . . . . . . . . . . . . . 15
   4.  Query Schema Discovery: QSD  . . . . . . . . . . . . . . . . . 17
     4.1.  Additional SEARCH Semantics  . . . . . . . . . . . . . . . 17
       4.1.1.  Example of Query Schema Discovery  . . . . . . . . . . 18
   5.  The DAV:basicsearch Grammar  . . . . . . . . . . . . . . . . . 19
     5.1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . 19
     5.2.  The DAV:basicsearch DTD  . . . . . . . . . . . . . . . . . 20
       5.2.1.  Example Query  . . . . . . . . . . . . . . . . . . . . 22
     5.3.  DAV:select . . . . . . . . . . . . . . . . . . . . . . . . 23
     5.4.  DAV:from . . . . . . . . . . . . . . . . . . . . . . . . . 23
       5.4.1.  Relationship to the Request-URI  . . . . . . . . . . . 23
       5.4.2.  Scope  . . . . . . . . . . . . . . . . . . . . . . . . 24
     5.5.  DAV:where  . . . . . . . . . . . . . . . . . . . . . . . . 24
       5.5.1.  Use of Three-Valued Logic in Queries . . . . . . . . . 24
       5.5.2.  Handling Optional Operators  . . . . . . . . . . . . . 24
       5.5.3.  Treatment of NULL Values . . . . . . . . . . . . . . . 24
       5.5.4.  Treatment of Properties with Mixed/Element Content . . 25
       5.5.5.  Example: Testing for Equality  . . . . . . . . . . . . 25
       5.5.6.  Example: Relative Comparisons  . . . . . . . . . . . . 25
     5.6.  DAV:orderby  . . . . . . . . . . . . . . . . . . . . . . . 26
       5.6.1.  Example of Sorting . . . . . . . . . . . . . . . . . . 26
     5.7.  Boolean Operators: DAV:and, DAV:or, and DAV:not  . . . . . 26
     5.8.  DAV:eq . . . . . . . . . . . . . . . . . . . . . . . . . . 27

1. 序論. . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1。 DASL. . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2。 DAV. . . . . . . . . . . . . . . . . . . 4 1.3との関係。 用語. . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.4。 記号法のコンベンション. . . . . . . . . . . . . . . . . . 6 1.5。 'DAV:'XML名前空間. . . . . . . . . . 7 1.6の用法では、注意します。 仕事. . . . . . . . . . . . . . . 7 2におけるDASLの概観。 検索方法. . . . . . . . . . . . . . . . . . . . . . 7 2.1。 概観. . . . . . . . . . . . . . . . . . . . . . . . . 7 2.2。 要求. . . . . . . . . . . . . . . . . . . . . . . 8 2.2.1。 要求URI.82.2、.2 要求本体. . . . . . . . . . . . . . . . . . . 8 2.3。 うまくいっている207(Multistatus)応答. . . . . . . . 9 2.3.1。 結果はトランケーション. . . . . . . . . . . . . . . . 9 2.3.2を設定しました。 PROPFIND応答. . . . . . . . . . . 10 2.3.3を広げています。 例: 簡単な要求と応答. . . . . . . . 10 2.3.4。 例: 結果はトランケーション. . . . . . . . . . . . 11 2.4を設定しました。 失敗の応答. . . . . . . . . . . . . . . . . . 12 2.4.1。 無効の範囲. . . . . . . . . . . . . 12 3に関する例。 支持された質問文法. . . . . . . . . . . . 13 3.1の発見。 オプション方法. . . . . . . . . . . . . . . . . . . . 13 3.2 DASL応答ヘッダ. . . . . . . . . . . . . . . . . 14 3.3。 DAV: 支持された質問文法セット(保護される).143.4。 例: 文法発見. . . . . . . . . . . . . . . . 15 4。 図式発見について質問してください: QSD. . . . . . . . . . . . . . . . . 17 4.1。 追加検索意味論. . . . . . . . . . . . . . . 17 4.1.1。 質問図式発見. . . . . . . . . . 18 5に関する例。 DAV: basicsearch文法. . . . . . . . . . . . . . . . . 19 5.1。 序論. . . . . . . . . . . . . . . . . . . . . . . 19 5.2。 DAV: basicsearch DTD. . . . . . . . . . . . . . . . . 20 5.2.1。 例の質問. . . . . . . . . . . . . . . . . . . . 22 5.3。 DAV: .235.4を選択してください。 DAV:、.235.4 .1。 要求URI.235.4との関係、.2 範囲. . . . . . . . . . . . . . . . . . . . . . . . 24 5.5。 DAV: どこ、.245.5 .1。 質問. . . . . . . . . 24 5.5.2における3で評価された論理の使用。 任意のオペレータ. . . . . . . . . . . . . 24 5.5.3を扱います。 ヌルの処理は.4に.245.5を評価します。 Mixed/要素含有量. . 25 5.5.5がある特性の処理。 例: 平等. . . . . . . . . . . . 25 5.5.6のために、テストします。 例: 相対比較. . . . . . . . . . . . 25 5.6。 DAV: orderby. . . . . . . . . . . . . . . . . . . . . . . 26 5.6.1。 ソーティング. . . . . . . . . . . . . . . . . . 26 5.7に関する例。 論理演算子: DAV、:、DAV、:、DAV: .265.8でない DAV: eq. . . . . . . . . . . . . . . . . . . . . . . . . . 27

Reschke, et al.             Standards Track                     [Page 2]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[2ページ]。

     5.9.  DAV:lt, DAV:lte, DAV:gt, DAV:gte . . . . . . . . . . . . . 27
     5.10. DAV:literal  . . . . . . . . . . . . . . . . . . . . . . . 27
     5.11. DAV:typed-literal (Optional) . . . . . . . . . . . . . . . 28
       5.11.1. Example for Typed Numerical Comparison . . . . . . . . 28
     5.12. Support for Matching xml:lang Attributes on Properties . . 29
       5.12.1. DAV:language-defined (Optional)  . . . . . . . . . . . 29
       5.12.2. DAV:language-matches (Optional)  . . . . . . . . . . . 29
       5.12.3. Example of Language-Aware Matching . . . . . . . . . . 29
     5.13. DAV:is-collection  . . . . . . . . . . . . . . . . . . . . 30
       5.13.1. Example of DAV:is-collection . . . . . . . . . . . . . 30
     5.14. DAV:is-defined . . . . . . . . . . . . . . . . . . . . . . 30
     5.15. DAV:like . . . . . . . . . . . . . . . . . . . . . . . . . 30
       5.15.1. Syntax for the Literal Pattern . . . . . . . . . . . . 31
       5.15.2. Example of DAV:like  . . . . . . . . . . . . . . . . . 31
     5.16. DAV:contains . . . . . . . . . . . . . . . . . . . . . . . 31
       5.16.1. Result Scoring (DAV:score Element) . . . . . . . . . . 32
       5.16.2. Ordering by Score  . . . . . . . . . . . . . . . . . . 33
       5.16.3. Examples . . . . . . . . . . . . . . . . . . . . . . . 33
     5.17. Limiting the Result Set  . . . . . . . . . . . . . . . . . 33
       5.17.1. Relationship to Result Ordering  . . . . . . . . . . . 33
     5.18. The 'caseless' XML Attribute . . . . . . . . . . . . . . . 34
     5.19. Query Schema for DAV:basicsearch . . . . . . . . . . . . . 34
       5.19.1. DTD for DAV:basicsearch QSD  . . . . . . . . . . . . . 34
       5.19.2. DAV:propdesc Element . . . . . . . . . . . . . . . . . 35
       5.19.3. The DAV:datatype Property Description  . . . . . . . . 35
       5.19.4. The DAV:searchable Property Description  . . . . . . . 36
       5.19.5. The DAV:selectable Property Description  . . . . . . . 36
       5.19.6. The DAV:sortable Property Description  . . . . . . . . 36
       5.19.7. The DAV:caseless Property Description  . . . . . . . . 36
       5.19.8. The DAV:operators XML Element  . . . . . . . . . . . . 37
       5.19.9. Example of Query Schema for DAV:basicsearch  . . . . . 38
   6.  Internationalization Considerations  . . . . . . . . . . . . . 39
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 39
     7.1.  Implications of XML External Entities  . . . . . . . . . . 39
   8.  Scalability  . . . . . . . . . . . . . . . . . . . . . . . . . 40
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 40
     9.1.  HTTP Headers . . . . . . . . . . . . . . . . . . . . . . . 40
       9.1.1.  DASL . . . . . . . . . . . . . . . . . . . . . . . . . 40
   10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 41
   11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 41
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 41
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 41
     12.2. Informative References . . . . . . . . . . . . . . . . . . 42
   Appendix A.  Three-Valued Logic in DAV:basicsearch . . . . . . . . 44
   Appendix B.  Candidates for Future Protocol Extensions . . . . . . 45
     B.1.  Collation Support  . . . . . . . . . . . . . . . . . . . . 45
     B.2.  Count  . . . . . . . . . . . . . . . . . . . . . . . . . . 46
     B.3.  Diagnostics for Unsupported Queries  . . . . . . . . . . . 46

5.9. DAV: lt、DAV: lte、DAV: gt、DAV: gte. . . . . . . . . . . . . 27 5.10。 DAV: 文字通りの.27 5.11。 DAV: タイプされて文字通りの(任意の).28 5.11.1。 タイプされた数字の比較. . . . . . . . 28 5.12のための例。 Matching xmlのサポート: Properties. . 29 5.12.1のlang Attributes。 DAV: (任意の).29 5.12.2を言語で定義しました。 DAV: 言語マッチ(任意の).29 5.12.3。 言語意識しているマッチング. . . . . . . . . . 29 5.13に関する例。 DAV:、-、収集、.30 5.13 .1。 DAVに関する例:、-、収集、.30 5.14 DAV:、-、定義、.30 5.15 DAV:、.30 5.15は.1に好きです。 文字通りのパターン. . . . . . . . . . . . 31 5.15.2のための構文。 DAVに関する例: .31 5.16のように。 DAV: .31 5.16に、.1を含んでいます。 (DAV: スコア要素).32 5.16.2を得点して、なってください。 スコア. . . . . . . . . . . . . . . . . . 33 5.16.3注文します。 例. . . . . . . . . . . . . . . . . . . . . . . 33 5.17。 結果セット. . . . . . . . . . . . . . . . . 33 5.17.1を制限します。 結果注文. . . . . . . . . . . 33 5.18との関係。 'caseless'XMLは.34 5.19を結果と考えます。 DAVのために図式について質問してください: basicsearch. . . . . . . . . . . . . 34 5.19.1。 DAVのためのDTD: basicsearch QSD. . . . . . . . . . . . . 34 5.19.2。 DAV: propdesc要素. . . . . . . . . . . . . . . . . 35 5.19.3。 DAV: データ型式不動産の表示. . . . . . . . 35 5.19.4。 DAV: 探せる不動産の表示. . . . . . . 36 5.19.5。 DAV: 選択可能な不動産の表示. . . . . . . 36 5.19.6。 DAV: 分類可能不動産の表示. . . . . . . . 36 5.19.7。 DAV: caseless不動産の表示. . . . . . . . 36 5.19.8。 DAV: オペレータXML要素. . . . . . . . . . . . 37 5.19.9。 DAVのための質問図式に関する例: basicsearch. . . . . 38 6。 国際化問題. . . . . . . . . . . . . 39 7。 セキュリティ問題. . . . . . . . . . . . . . . . . . . 39 7.1。 XML外部実体. . . . . . . . . . 39 8の含意。 スケーラビリティ. . . . . . . . . . . . . . . . . . . . . . . . . 40 9。 IANA問題. . . . . . . . . . . . . . . . . . . . . 40 9.1。 HTTPヘッダ. . . . . . . . . . . . . . . . . . . . . . . 40 9.1.1。 DASL. . . . . . . . . . . . . . . . . . . . . . . . . 40 10。 貢献者. . . . . . . . . . . . . . . . . . . . . . . . . 41 11。 承認. . . . . . . . . . . . . . . . . . . . . . . 41 12。 参照. . . . . . . . . . . . . . . . . . . . . . . . . . 41 12.1。 引用規格. . . . . . . . . . . . . . . . . . . 41 12.2。 DAVの有益な参照. . . . . . . . . . . . . . . . . . 42の付録のA.の3で評価された論理: basicsearch.44に、未来の付録B.候補は拡大について議定書の中で述べます。.45B.1。 照合サポート. . . . . . . . . . . . . . . . . . . . 45B.2。 .46B.3を数えてください。 サポートされない質問. . . . . . . . . . . 46のための病気の特徴

Reschke, et al.             Standards Track                     [Page 3]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[3ページ]。

     B.4.  Language Matching  . . . . . . . . . . . . . . . . . . . . 46
     B.5.  Matching Media Types . . . . . . . . . . . . . . . . . . . 46
     B.6.  Query by Name  . . . . . . . . . . . . . . . . . . . . . . 46
     B.7.  Result Paging  . . . . . . . . . . . . . . . . . . . . . . 46
     B.8.  Search Scope Discovery . . . . . . . . . . . . . . . . . . 47
   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

B.4。 言語マッチング. . . . . . . . . . . . . . . . . . . . 46B.5。 メディアを合わせると、.46B.6はタイプされます。 名前. . . . . . . . . . . . . . . . . . . . . . 46で、B.7について質問してください。 .46B.8を呼び出して、なってください。 検索範囲発見. . . . . . . . . . . . . . . . . . 47インデックス. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

1.  Introduction

1. 序論

1.1.  DASL

1.1. DASL

   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
   earlier work done in the IETF DASL Working Group (see Section 10).
   In this specification, the terms "WebDAV SEARCH" and "DASL" are used
   interchangeably.

このドキュメントはウェブDistributed AuthoringとVersioning(WebDAV)検索(クライアントがサーバサイド検索施設を利用できる軽量の検索プロトコルを輸送に形成するのが質問して、結果が設定するHTTP/1.1のアプリケーション)を定義します。 それはIETF DASL作業部会で行われた以前の仕事に基づいています(セクション10を見てください)。 この仕様では、用語の「WebDAVは探し」て"DASL"は互換性を持って使用されます。

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

DASLは、DASL検索メカニズムを利用できるアプリケーションの広範囲の展開を容易にするためにクライアントの複雑さを最小にします。

   DASL consists of:

DASLは以下から成ります。

   o  the SEARCH method and the request/response formats defined for it
      (Section 2),

o 検索方法と要求/応答形式はそれのために(セクション2)を定義しました。

   o  feature discovery through the "DASL" response header and the
      optional DAV:supported-grammar-set property (Section 3),

o "DASL"応答ヘッダと任意のDAV: 支持された文法セット所有地(セクション3)を通した発見を特徴としてください。

   o  optional grammar schema discovery (Section 4), and

o そして任意の文法図式発見(セクション4)。

   o  one mandatory grammar: DAV:basicsearch (Section 5).

o 1つの義務的な文法: DAV: basicsearch(セクション5)。

1.2.  Relationship to DAV

1.2. DAVとの関係

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

DASLは[RFC4918]によって定義されたリソースと特性のモデルを当てにします。 DASLはこのモデルを変更しません。 代わりに、サーバサイド検索でDASLはクライアントをDAVによってモデル化されたリソースにアクセスさせます。

Reschke, et al.             Standards Track                     [Page 4]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[4ページ]。

1.3.  Terms

1.3. 用語

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

このドキュメントは[RFC2616]、[RFC4918][RFC3253]とこのセクションで定義された用語を使用します。

   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.

それらの関係と値における1セットの質問と意図している意味論を定義する1セットのXML要素の定義、属性、および規制。

   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.

リソースの記述。 結果レコードは、1セットの特性と、ことによると他の記述的な情報です。

   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.

Aは検索評価基準がTrueに評価したもののために記録、各リソースあたり1つをセットしました。

Reschke, et al.             Standards Track                     [Page 5]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[5ページ]。

   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.

結果における結果記録での注文の仕様はセットしました。

1.4.  Notational Conventions

1.4. 記号法のコンベンション

   This specification uses the Augmented Backus-Naur Form (ABNF)
   notation of [RFC5234], unless explicitly stated otherwise.

別の方法で明らかに述べられない場合、この仕様は[RFC5234]のAugmented BN記法(ABNF)記法を使用します。

   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].

キーワード“MUST"、「必須NOT」が「必要です」、“SHALL"、「」、“SHOULD"、「「推薦され」て、「5月」の、そして、「任意」のNOTは[RFC2119]で説明されるように本書では解釈されることであるべきですか?

   This document uses XML DTD fragments ([XML], 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 [RFC4918] and due to the fact that all XML elements
   defined by this specification use the XML namespace name "DAV:".  In
   particular:

このドキュメントは純粋に記号法のコンベンションとしてXML DTD断片([XML]、セクション3.2)を使用します。 [RFC4918]のセクション17で定義された特定の伸展性規則のためとこの仕様で定義されたすべてのXML要素がXML名前空間名を使用するという事実のためDTDでWebDAV要求と応答本体を有効にすることができない、「DAV:」 特に:

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

1. 要素が使用を命名する、「DAV:」 名前空間

   2.  element ordering is irrelevant unless explicitly stated,

2. 明らかに述べられない場合、要素注文は無関係です。

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

3. 別の方法で明らかに述べられている時を除いて、拡大要素(既に有効な子供要素と定義されなかった要素)はどこでも加えられるかもしれません。

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

4. 拡大属性(既にこの要素に有効であると定義されなかった属性)はどこでも加えられるかもしれません、別の方法で明らかに述べられている時を除いて。

Reschke, et al.             Standards Track                     [Page 6]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[6ページ]。

   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.

中のXML要素型である、「DAV:」 名前空間が本書ではXML断片、ストリングの文脈の外で参照をつけられる、「DAV:」 要素型へ前に置かれるでしょう。

   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.

名前空間" http://www.w3.org/2001/XMLSchema "のXML要素型が本書ではXML断片の文脈の外で参照をつけられるとき、同様に、ストリングは「以下をxsします」。 要素型へ前に置かれるでしょう。

   This document inherits, and sometimes extends, DTD productions from
   Section 14 of [RFC4918].

このドキュメントは、[RFC4918]のセクション14からDTD創作を引き継いで、時々広げています。

1.5.  Note on Usage of 'DAV:' XML Namespace

1.5. 'DAV:'XML名前空間の用法に関する注

   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 (<http://www.webdav.org/dasl/>, and at
   the time the working group closed down there was already significant
   deployment of this specification.

この仕様がXML名前空間で要素、特性、および状態名を定義する、「DAV:」 一般に、IETFワーキンググループによって書かれた仕様だけがこれをするべきです。 この場合例外は作られました、WebDAV検索がIETF DASLワーキンググループの人生を始めたので。(<は://www.webdav.org/dasl/>をhttpして、ワーキンググループが閉鎖されたとき、この仕様の重要な展開が既にありました。

1.6.  An Overview of DASL at Work

1.6. 仕事におけるDASLの概観

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

人は以下のステップでDASLの基本的な使用を言い表すことができます:

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

o クライアントはDAVを使用することで質問を構成します: basicsearch文法。

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

o クライアントは、検索(検索仲裁者)を実行するリソースに検索方法を呼び出して、質問を含むテキスト/xmlかアプリケーション/xml要求実体を入れます。

   o  The search arbiter performs the query.

o 検索仲裁者は質問を実行します。

   o  The search arbiter sends the results of the query back to the
      client in the response.  The server MUST send an entity that
      matches the WebDAV multistatus format ([RFC4918], Section 13).

o 検索仲裁者は応答で質問の結果をクライアントに送り返します。 サーバはWebDAV multistatus形式([RFC4918]、セクション13)に合っている実体を送らなければなりません。

2.  The SEARCH Method

2. 検索方法

2.1.  Overview

2.1. 概観

   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 ([RFC4918],
   Section 13).

クライアントはサーバサイド検索を開始する検索方法を呼び出します。 要求のボディーは質問を定義します。 サーバはWebDAV multistatus形式([RFC4918]、セクション13)に合っている実体を放たなければなりません。

Reschke, et al.             Standards Track                     [Page 7]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[7ページ]。

   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 [RFC2616],
   Section 9.1.1).

検索は確実な方法です。 それには、質問を実行して、質問結果を返す以外の少しの意味もありません([RFC2616]、セクション9.1.1を見てください)。

2.2.  The Request

2.2. 要求

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

クライアントはRequest-URIによって指定されたリソースに検索方法を呼び出します。

2.2.1.  The Request-URI

2.2.1. 要求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 [RFC4918], Section 15.9), nor
   does it have to be a WebDAV-compliant resource.

Request-URIは検索仲裁者を特定します。 どんなHTTPリソースも検索仲裁者として機能するかもしれません。 それは新しいタイプに関するリソース(DAVの感覚: [RFC4918]で定義されるresourcetypeのセクション15.9)ではありません、そして、WebDAV対応することのリソースである必要はありません。

   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.

検索方法は検索の仲裁者と範囲との関係を全く定義しません。 むしろ、質問に使用される特定の質問文法は関係を定義します。 例えば、質問文法によって、Request-URIはやむを得ずちょうど検索範囲に相当するかもしれません。

2.2.2.  The Request Body

2.2.2. 要求本体

   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.

サーバは、テキスト/xmlかアプリケーション/xml要求ボディーを処理しなければならなくて、他の形式で要求本体を処理するかもしれません。 要求でパッケージXMLで指導に関して[RFC3023]を見てください。

   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.

内容のタイプテキスト/xmlかアプリケーション/xmlがある要求本体が含まれているなら、それはDAVであるに違いありません: 最もsearchrequestであるかa DAV: 図式発見XML要素について質問してください。 ただ一つの子供要素は質問文法を特定します。

      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.

DAVのために: 最もsearchrequestに、検索評価基準の定義、結果記録、および検索を実行するのに必要であるいかなる他の詳細も個々の検索文法によります。

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

DAV: 質問図式発見において、意味論はセクション4で定義されます。

Reschke, et al.             Standards Track                     [Page 8]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[8ページ]。

   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 Section 4.

(DAV: 発見がサポートした検索文法): XML要求ボディーが存在していて、DAV: 質問図式発見ドキュメント要素を持っているとき、サーバはセクション4で説明された質問図式発見メカニズムをサポートしなければなりません。

      (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: 文法が支持した検索): XML要求ボディーが存在しているとき、ドキュメント要素の子供要素によって特定された検索文法は支持された検索文法であるに違いありません。

      (DAV:search-multiple-scope-supported): if the SEARCH request
      specified multiple scopes, the server MUST support this optional
      feature.

(DAV: 複数の範囲が支持した検索): 検索要求が複数の範囲を指定したなら、サーバはこのオプション機能を支持しなければなりません。

      (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 [RFC4918] compliant DAV:response elements as
      content to the condition element indicating the precise reason for
      the failure.

(有効な状態で範囲を捜しているDAV): 供給された検索範囲は有効であるに違いありません。 検索範囲が無効になる様々な理由があることができます、サポートされないURI計画と意思疎通の問題を含んでいて。サーバは[RFC4918]対応することのDAV: 失敗の正確な理由を示す状態要素に同じくらい満足している応答要素を加えるかもしれません。

2.3.  The Successful 207 (Multistatus) Response

2.3. うまくいっている207(Multistatus)応答

   If the server returns 207 (Multistatus), then the search proceeded
   successfully, and the response MUST use the WebDAV multistatus format
   ([RFC4918], Section 13).  The results of this method SHOULD NOT be
   cached.

サーバが207(Multistatus)を返すなら、検索は首尾よく続きました、そして、応答はWebDAV multistatus形式([RFC4918]、セクション13)を使用しなければなりません。 結果、この方法SHOULD NOTでは、キャッシュされてください。

   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.

1DAV: 検索評価基準に合っていた各リソースのための応答があるに違いありません。 そのような各応答、DAVのために: 応答はDAVを含まなければなりません: href要素はリソースのURIを含んでいます、そして、propstat要素

      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.

以下に注意してください。 WebDAV multistatus形式は少なくとも1DAVを必要とします: 応答子供要素。 この仕様は、空の結果を表すことができるようにその規制を緩和します。

   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 [WEBDAV-BIND] to
   identify possible duplicates.

見つけられたそれぞれの合っているリソースのためにそれに写像された検索範囲の中に複数のURIがあるかもしれないことに注意してください。 この場合サーバSHOULDレポートこれらの唯一の1つURI。 クライアントは精力の特性のDAVを使用できます: 可能な写しを特定するために[WEBDAV-BIND]のセクション3.1で定義されたリソースイド。

2.3.1.  Result Set Truncation

2.3.1. 結果セットトランケーション

   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

例えば、サーバは、質問を処理する際に費やされたリソースの量を制限するために回答における、リソースの数を制限するかもしれません。 if

Reschke, et al.             Standards Track                     [Page 9]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[9ページ]。

   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.

それはそうして、回答はステータスコード207を使用しなければならなくて、リターンはDAVです: 「マルチ-状態」応答は、検索仲裁者URIのために507(不十分なStorage)の状態を具体化して、示します。 それ、SHOULDは部分的な結果を含んでいます。

   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.

部分的な結果が戻ったというメモはオリジナルの質問を満たした結果セットのどんな部分集合であるかもしれません。

2.3.2.  Extending the PROPFIND Response

2.3.2. PROPFIND応答を広げています。

   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.

応答はPROPFINDが定義するより多くの情報を含むかもしれません、その他の情報がPROPFIND応答を無効にしない限り。 質問文法SHOULDは応答がどうPROPFIND応答に合っているかを定義します。

2.3.3.  Example: A Simple Request and Response

2.3.3. 例: 簡単な要求と応答

   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.

この例は要求と応答枠組みを示します。 以下のXMLドキュメントは簡単な(仮定している)自然言語クエリーを示しています。 質問要素の名前はXML名前空間" http://example.com/foo "で自然言語クエリーです。 実際の質問は「ロサンゼルスの良いタイ料理のレストランの位置を見つける」ことです。 この仮定している質問のために、仲裁者はそれぞれの選択されたリソースあたり2つの資産を返します。

   >> Request:

>>要求:

   SEARCH / HTTP/1.1
   Host: example.org
   Content-Type: application/xml; charset="utf-8"
   Content-Length: 252

/ HTTP/1.1ホストを身体検査してください: example.orgコンテントタイプ: アプリケーション/xml。 charsetが等しい、「utf-8インチのContent-長さ:」 252

   <?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>

<?xmlバージョン=、「=「UTF-8インチ?」をコード化する1インチ><D:searchrequest xmlns:Dが等しい、「DAV:」 xmlns: Fが等しい、「 http://example.com/foo 、「><F: 自然言語クエリー>Find、ロサンゼルス</Fの良いタイ料理のレストランの位置: 自然言語クエリー></D: 最もsearchrequestな>、」

Reschke, et al.             Standards Track                    [Page 10]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[10ページ]。

   >> Response:

>>応答:

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

HTTP/1.1 207マルチ状態コンテントタイプ: テキスト/xml。 charsetが等しい、「utf-8インチのContent-長さ:」 429

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

<?xmlバージョン=、「=「UTF-8インチ?」をコード化する1インチ><D:multistatus xmlns:Dが等しい、「DAV:」 xmlns: Rが等しい、「 http://example.org/propschema 、「><D: 応答><D: href>http://siamiam.example/</D: href><D: propstat><D: ><R: 位置の>を支えてください、259、W、」; ハリウッド</R: 位置の><R: ></R: D: ></D: 支柱><が状態>HTTP/1.1 200OK</Dであると評定します: 状態></D: propstat></D: 応答></D: ><R: 星の>4</R: 星の「マルチ-状態」が>であると評定すること。

2.3.4.  Example: Result Set Truncation

2.3.4. 例: 結果セットトランケーション

   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.

以下の例では、サーバは、ちょうど2つの結果を返して、次に、結果がDAVを加えることによって先端を切られるのを示します: 507(不十分なStorage)状態がある検索仲裁者リソースのための応答要素。

   >> Request:

>>要求:

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

/ HTTP/1.1ホストを身体検査してください: example.netコンテントタイプ: テキスト/xml。 charsetが等しい、「utf-8インチのContent-長さ:」 xxx

    ... the query goes here ...

… 質問はここに行きます…

Reschke, et al.             Standards Track                    [Page 11]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[11ページ]。

   >> Response:

>>応答:

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

HTTP/1.1 207Multistatusコンテントタイプ: テキスト/xml。 charsetが等しい、「utf-8インチのContent-長さ:」 640

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

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

2.4.  Unsuccessful Responses

2.4. Unsuccessful Responses

   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 [RFC3253].  Unless otherwise stated, condition
   elements are empty; however, specific condition elements MAY include
   additional child elements that describe the error condition in more
   detail.

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 [RFC3253]. Unless otherwise stated, condition elements are empty; however, specific condition elements MAY include additional child elements that describe the error condition in more detail.

2.4.1.  Example of an Invalid Scope

2.4.1. Example of an Invalid Scope

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

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

Reschke, et al.             Standards Track                    [Page 12]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 12] RFC 5323 WebDAV SEARCH November 2008

   >> Response:

>> Response:

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

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

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

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

3.  Discovery of Supported Query Grammars

3. Discovery of Supported Query Grammars

   Servers MUST support discovery of the query grammars supported by a
   search arbiter resource.

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.

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 [RFC3253] and/or [RFC3744]
   MUST also:

Servers supporting the WebDAV extensions [RFC3253] and/or [RFC3744] MUST also:

   o  report SEARCH in the live property DAV:supported-method-set for
      all search arbiter resources, and

o report SEARCH in the live property DAV:supported-method-set for all search arbiter resources, and

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

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

3.1.  The OPTIONS Method

3.1. The OPTIONS Method

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

The 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 [RFC2616].

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 [RFC2616].

Reschke, et al.             Standards Track                    [Page 13]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 13] RFC 5323 WebDAV SEARCH November 2008

   If a resource supports the SEARCH method, then the server MUST list
   SEARCH in the Allow header defined in Section 14.7 of [RFC2616].

If a resource supports the SEARCH method, then the server MUST list SEARCH in the Allow header defined in Section 14.7 of [RFC2616].

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

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

3.2.  The DASL Response Header

3.2. The DASL Response Header

   DASLHeader = "DASL" ":" 1#Coded-URL
   Coded-URL  = <defined in Section 10.1 of [RFC4918]>

DASLHeader = "DASL" ":" 1#Coded-URL Coded-URL = <defined in Section 10.1 of [RFC4918]>

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

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

   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).

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
      ([RFC2616], Section 4.2); thus, grammar URIs can appear in
      multiple header instances, separated by commas, or both.

Note: this header field value is defined as a comma-separated list ([RFC2616], Section 4.2); thus, grammar URIs can appear in multiple header instances, separated by commas, or both.

   For example:

For example:

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

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

3.3.  DAV:supported-query-grammar-set (Protected)

3.3. DAV:supported-query-grammar-set (Protected)

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

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

   <!ELEMENT supported-query-grammar-set (supported-query-grammar*)>
   <!ELEMENT supported-query-grammar (grammar)>
   <!ELEMENT grammar ANY>
   <!-- ANY value: a query grammar element type -->

<!ELEMENT supported-query-grammar-set (supported-query-grammar*)> <!ELEMENT supported-query-grammar (grammar)> <!ELEMENT grammar ANY> <!-- ANY value: a query grammar element type -->

Reschke, et al.             Standards Track                    [Page 14]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 14] RFC 5323 WebDAV SEARCH November 2008

3.4.  Example: Grammar Discovery

3.4. Example: Grammar Discovery

   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.

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:

>> Request:

   OPTIONS /somefolder HTTP/1.1
   Host: example.org

OPTIONS /somefolder HTTP/1.1 Host: example.org

   >> Response:

>> Response:

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

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

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

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

   >> Request:

>> Request:

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

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

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

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

Reschke, et al.             Standards Track                    [Page 15]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 15] RFC 5323 WebDAV SEARCH November 2008

   >> Response:

>> Response:

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

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

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

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

Reschke, et al.             Standards Track                    [Page 16]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 16] RFC 5323 WebDAV SEARCH November 2008

   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.

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.

4.  Query Schema Discovery: QSD

4. Query Schema Discovery: QSD

   Servers MAY support the discovery of the schema for a query grammar.

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.

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.

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.

4.1.  Additional SEARCH Semantics

4.1. Additional SEARCH Semantics

   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

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

Reschke, et al.             Standards Track                    [Page 17]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 17] RFC 5323 WebDAV SEARCH November 2008

   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.

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:

Marshalling:

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

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

      <!ELEMENT query-schema-discovery ANY>
      <!-- ANY value: XML element specifying the query grammar
                      and the scope -->

<!ELEMENT query-schema-discovery ANY> <!-- ANY value: XML element specifying the query grammar and the scope -->

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

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

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

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

   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.

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.

4.1.1.  Example of Query Schema Discovery

4.1.1. Example of Query Schema Discovery

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

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

   >> Request:

>> Request:

   SEARCH / HTTP/1.1
   Host: recipes.example
   Content-Type: application/xml; charset="utf-8"
   Content-Length: 258

SEARCH / HTTP/1.1 Host: recipes.example Content-Type: application/xml; charset="utf-8" Content-Length: 258

   <?xml version="1.0"?>
   <query-schema-discovery xmlns="DAV:">
     <basicsearch>
       <from>
         <scope>
           <href>http://recipes.example</href>
           <depth>infinity</depth>
         </scope>
       </from>
     </basicsearch>
   </query-schema-discovery>

<?xml version="1.0"?> <query-schema-discovery xmlns="DAV:"> <basicsearch> <from> <scope> <href>http://recipes.example</href> <depth>infinity</depth> </scope> </from> </basicsearch> </query-schema-discovery>

Reschke, et al.             Standards Track                    [Page 18]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 18] RFC 5323 WebDAV SEARCH November 2008

   >> Response:

>> Response:

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

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

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

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

   The query schema for DAV:basicsearch is defined in Section 5.19.

The query schema for DAV:basicsearch is defined in Section 5.19.

5.  The DAV:basicsearch Grammar

5. The DAV:basicsearch Grammar

5.1.  Introduction

5.1. Introduction

   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 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:basicsearch has several components:

   o  DAV:select provides the result record definition.

o DAV:select provides the result record definition.

   o  DAV:from defines the scope.

o DAV:from defines the scope.

   o  DAV:where defines the criteria.

o DAV:where defines the criteria.

   o  DAV:orderby defines the sort order of the result set.

o DAV:orderby defines the sort order of the result set.

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

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

Reschke, et al.             Standards Track                    [Page 19]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 19] RFC 5323 WebDAV SEARCH November 2008

5.2.  The DAV:basicsearch DTD

5.2. The DAV:basicsearch DTD

   <!-- "basicsearch" element -->

<!-- "basicsearch" element -->

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

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

   <!-- "select" element -->

<!-- "select" element -->

   <!ELEMENT select        (allprop | prop) >

<!ELEMENT select (allprop | prop) >

   <!-- "from" element -->

<!-- "from" element -->

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

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

   <!-- "where" element -->

<!-- "where" element -->

Reschke, et al.             Standards Track                    [Page 20]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 20] RFC 5323 WebDAV SEARCH November 2008

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

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

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

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

   <!ELEMENT where         ( %all_ops; ) >

<!ELEMENT where ( %all_ops; ) >

   <!ELEMENT and           ( %all_ops; )+ >

<!ELEMENT and ( %all_ops; )+ >

   <!ELEMENT or            ( %all_ops; )+ >

<!ELEMENT or ( %all_ops; )+ >

   <!ELEMENT not           ( %all_ops; ) >

<!ELEMENT not ( %all_ops; ) >

   <!ELEMENT lt            (prop, (literal|typed-literal)) >
   <!ATTLIST lt            caseless   (yes|no) #IMPLIED>

<!ELEMENT lt (prop, (literal|typed-literal)) > <!ATTLIST lt caseless (yes|no) #IMPLIED>

   <!ELEMENT lte           (prop, (literal|typed-literal)) >
   <!ATTLIST lte           caseless   (yes|no) #IMPLIED>

<!ELEMENT lte (prop, (literal|typed-literal)) > <!ATTLIST lte caseless (yes|no) #IMPLIED>

   <!ELEMENT gt            (prop, (literal|typed-literal)) >
   <!ATTLIST gt            caseless   (yes|no) #IMPLIED>

<!ELEMENT gt (prop, (literal|typed-literal)) > <!ATTLIST gt caseless (yes|no) #IMPLIED>

   <!ELEMENT gte           (prop, (literal|typed-literal)) >
   <!ATTLIST gte           caseless   (yes|no) #IMPLIED>

<!ELEMENT gte (prop, (literal|typed-literal)) > <!ATTLIST gte caseless (yes|no) #IMPLIED>

   <!ELEMENT eq            (prop, (literal|typed-literal)) >
   <!ATTLIST eq            caseless   (yes|no) #IMPLIED>

<!ELEMENT eq (prop, (literal|typed-literal)) > <!ATTLIST eq caseless (yes|no) #IMPLIED>

   <!ELEMENT literal       (#PCDATA)>
   <!ELEMENT typed-literal (#PCDATA)>
   <!ATTLIST typed-literal xsi:type CDATA #IMPLIED>

<!ELEMENT literal (#PCDATA)> <!ELEMENT typed-literal (#PCDATA)> <!ATTLIST typed-literal xsi:type CDATA #IMPLIED>

   <!ELEMENT is-collection EMPTY >
   <!ELEMENT is-defined    (prop) >

<!ELEMENT is-collection EMPTY > <!ELEMENT is-defined (prop) >

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

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

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

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

   <!ELEMENT contains      (#PCDATA)>

<!ELEMENT contains (#PCDATA)>

Reschke, et al.             Standards Track                    [Page 21]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 21] RFC 5323 WebDAV SEARCH November 2008

   <!-- "orderby" element -->

<!-- "orderby" element -->

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

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

   <!-- "limit" element -->

<!-- "limit" element -->

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

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

5.2.1.  Example Query

5.2.1. Example Query

   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.

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.

   <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>

<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>

Reschke, et al.             Standards Track                    [Page 22]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 22] RFC 5323 WebDAV SEARCH November 2008

5.3.  DAV:select

5.3. DAV:select

   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 [RFC4918].

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 [RFC4918].

5.4.  DAV:from

5.4. DAV:from

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

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

   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 Section 2.2.2, precondition
   DAV:search-multiple-scope-supported).  The scope element contains
   mandatory DAV:href and DAV:depth elements.

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 Section 2.2.2, precondition DAV:search-multiple-scope-supported). The scope element contains mandatory DAV:href and DAV:depth elements.

   DAV:href indicates the URI reference ([RFC3986], Section 4.1) to use
   as a scope.

DAV:href indicates the URI reference ([RFC3986], 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 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.

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
   ([RFC4437]) and the search scope contains a redirect reference
   resource, then it applies only to that resource, not to its target.

If the server supports WebDAV Redirect Reference Resources ([RFC4437]) 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 [RFC3253], 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 Section 2.2.2,
   precondition DAV:search-scope-valid).

When the child element DAV:include-versions is present, the search scope will include all versions (see [RFC3253], 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 Section 2.2.2, precondition DAV:search-scope-valid).

5.4.1.  Relationship to the Request-URI

5.4.1. Relationship to the Request-URI

   If the DAV:scope element is a URI ([RFC3986], Section 3), the scope
   is exactly that URI.

If the DAV:scope element is a URI ([RFC3986], Section 3), the scope is exactly that URI.

   If the DAV:scope element is a relative reference ([RFC3986], Section
   4.2), the scope is taken to be relative to the Request-URI.

If the DAV:scope element is a relative reference ([RFC3986], Section 4.2), the scope is taken to be relative to the Request-URI.

Reschke, et al.             Standards Track                    [Page 23]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 23] RFC 5323 WebDAV SEARCH November 2008

5.4.2.  Scope

5.4.2. Scope

   A Scope can be an arbitrary URI reference.

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.

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.

5.5.  DAV:where

5.5. DAV:where

   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.

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.

5.5.1.  Use of Three-Valued Logic in Queries

5.5.1. Use of Three-Valued Logic in Queries

   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.

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 Appendix A for details on the application of three-valued
   logic in query expressions.

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

5.5.2.  Handling Optional Operators

5.5.2. Handling Optional Operators

   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 query contains an operator that is not supported by the server, then the server MUST respond with a 422 (Unprocessable Entity) status code.

5.5.3.  Treatment of NULL Values

5.5.3. Treatment of NULL Values

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

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

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

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.

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.

The DAV:is-defined operator is defined to test if the value of a property is not NULL.

Reschke, et al.             Standards Track                    [Page 24]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 24] RFC 5323 WebDAV SEARCH November 2008

5.5.4.  Treatment of Properties with Mixed/Element Content

5.5.4. Treatment of Properties with Mixed/Element Content

   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
   Appendix A).  For querying the DAV:resourcetype property, see
   Section 5.13.

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 Appendix A). For querying the DAV:resourcetype property, see Section 5.13.

5.5.5.  Example: Testing for Equality

5.5.5. Example: Testing for Equality

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

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

   <d:where xmlns:d='DAV:'>
     <d:eq>
       <d:prop>
         <d:getcontentlength/>
       </d:prop>
       <d:literal>100</d:literal>
     </d:eq>
   </d:where>

<d:where xmlns:d='DAV:'> <d:eq> <d:prop> <d:getcontentlength/> </d:prop> <d:literal>100</d:literal> </d:eq> </d:where>

5.5.6.  Example: Relative Comparisons

5.5.6. Example: Relative Comparisons

   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.

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.

   <D:where xmlns:D='DAV:'>
     <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>

<D:where xmlns:D='DAV:'> <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>

Reschke, et al.             Standards Track                    [Page 25]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 25] RFC 5323 WebDAV SEARCH November 2008

5.6.  DAV:orderby

5.6. DAV:orderby

   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 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.

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 [SQL99]).

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 [SQL99]).

   The "caseless" attribute may be used to indicate case-sensitivity for
   comparisons (Section 5.18).

The "caseless" attribute may be used to indicate case-sensitivity for comparisons (Section 5.18).

5.6.1.  Example of Sorting

5.6.1. Example of Sorting

   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.

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.

   <d:orderby xmlns:d='DAV:' xmlns:r='http://example.com/ns'>
     <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>

<d:orderby xmlns:d='DAV:' xmlns:r='http://example.com/ns'> <d:order> <d:prop><r:lastname/></d:prop> <d:ascending/> </d:order> <d:order> <d:prop><d:getcontentlength/></d:prop> <d:descending/> </d:order> </d:orderby>

5.7.  Boolean Operators: DAV:and, DAV:or, and DAV:not

5.7. Boolean Operators: DAV:and, DAV:or, and DAV:not

   The DAV:and operator performs a logical AND operation on the
   expressions it contains.

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:or operator performs a logical OR operation on the values it contains.

Reschke, et al.             Standards Track                    [Page 26]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 26] RFC 5323 WebDAV SEARCH November 2008

   The DAV:not operator performs a logical NOT operation on the values
   it contains.

The DAV:not operator performs a logical NOT operation on the values it contains.

5.8.  DAV:eq

5.8. DAV:eq

   The DAV:eq operator provides simple equality matching on property
   values.

The DAV:eq operator provides simple equality matching on property values.

   The "caseless" attribute may be used with this element
   (Section 5.18).

The "caseless" attribute may be used with this element (Section 5.18).

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

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

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

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 (Section 5.18).

5.10.  DAV:literal

5.10. DAV:literal

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

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

   White space in literal values is significant in comparisons.  For
   consistency with [RFC4918], clients SHOULD NOT specify the attribute
   "xml:space" (Section 2.10 of [XML]) to override this behavior.

White space in literal values is significant in comparisons. For consistency with [RFC4918], clients SHOULD NOT specify the attribute "xml:space" (Section 2.10 of [XML]) to override this behavior.

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

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

   o  when operand for a comparison with a DAV:getcontentlength
      property, it SHOULD be treated as an unsigned integer value (the
      behavior for values not in this format is undefined),

o 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),

   o  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 [RFC4918]; the behavior of values not in this
      format is undefined),

o 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 [RFC4918]; the behavior of values not in this format is undefined),

   o  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.

o 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.

Reschke, et al.             Standards Track                    [Page 27]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 27] RFC 5323 WebDAV SEARCH November 2008

5.11.  DAV:typed-literal (Optional)

5.11. DAV:typed-literal (Optional)

   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.

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.

   <!ELEMENT typed-literal (#PCDATA)>

<!ELEMENT typed-literal (#PCDATA)>

   The data type is specified using the xsi:type attribute defined in
   Section 2.6.1 of [XS1].  If the type is not specified, it defaults to
   "xs:string".

The data type is specified using the xsi:type attribute defined in Section 2.6.1 of [XS1]. 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.

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 [XPATHFUNC], Section 17).

The comparison evaluates to UNKNOWN if the property value cannot be cast to the specified datatype (see [XPATHFUNC], Section 17).

5.11.1.  Example for Typed Numerical Comparison

5.11.1. Example for Typed Numerical Comparison

   Consider a set of resources with the dead property "edits" in the
   namespace "http://ns.example.org":

Consider a set of resources with the dead property "edits" in the namespace "http://ns.example.org":

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

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

   The expression

The expression

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

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

   will evaluate 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"

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"

Reschke, et al.             Standards Track                    [Page 28]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 28] RFC 5323 WebDAV SEARCH November 2008

   and "/e" (the property either is undefined, or its value cannot be
   parsed as xs:integer).

and "/e" (the property either is undefined, or its value cannot be parsed as xs:integer).

5.12.  Support for Matching xml:lang Attributes on Properties

5.12. Support for Matching xml:lang Attributes on Properties

   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).

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).

5.12.1.  DAV:language-defined (Optional)

5.12.1. DAV:language-defined (Optional)

   <!ELEMENT language-defined (prop)>

<!ELEMENT language-defined (prop)>

   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, FALSE if it isn't, and UNKNOWN if the property itself is not defined.

5.12.2.  DAV:language-matches (Optional)

5.12.2. DAV:language-matches (Optional)

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

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

   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.

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 [XPATH], "lang
   function").

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 [XPATH], "lang function").

5.12.3.  Example of Language-Aware Matching

5.12.3. Example of Language-Aware Matching

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

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

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

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

Reschke, et al.             Standards Track                    [Page 29]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 29] RFC 5323 WebDAV SEARCH November 2008

5.13.  DAV:is-collection

5.13. DAV:is-collection

   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).

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.

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

5.13.1.  Example of DAV:is-collection

5.13.1. Example of DAV:is-collection

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

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

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

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

5.14.  DAV:is-defined

5.14. DAV:is-defined

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

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

   Example:

Example:

   <d:is-defined xmlns:d='DAV:' xmlns:x='http://example.com/ns'>
     <d:prop><x:someprop/></d:prop>
   </d:is-defined>

<d:is-defined xmlns:d='DAV:' xmlns:x='http://example.com/ns'> <d:prop><x:someprop/></d:prop> </d:is-defined>

5.15.  DAV:like

5.15. DAV:like

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

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

   The operator takes two arguments.

The operator takes two arguments.

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

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.

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

Reschke, et al.             Standards Track                    [Page 30]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 30] RFC 5323 WebDAV SEARCH November 2008

5.15.1.  Syntax for the Literal Pattern

5.15.1. Syntax for the Literal Pattern

   pattern       = [wildcard] 0*( text [wildcard] )

pattern = [wildcard] 0*( text [wildcard] )

   wildcard      = exactlyone / zeroormore
   text          = 1*( character / escapeseq )

wildcard = exactlyone / zeroormore text = 1*( character / escapeseq )

   exactlyone    = "_"
   zeroormore    = "%"
   escapechar    = "\"
   escapeseq     = escapechar ( exactlyone / zeroormore / escapechar )

exactlyone = "_" zeroormore = "%" escapechar = "\" escapeseq = escapechar ( exactlyone / zeroormore / escapechar )

   ; character: see [XML], Section 2.2, minus wildcard / escapechar
   character     = HTAB / LF / CR ; whitespace
   character     =/ %x20-24 / %x26-5B / %x5D-5E / %x60-D7FF
   character     =/ %xE000-FFFD / %x10000-10FFFF

; character: see [XML], Section 2.2, minus wildcard / escapechar character = HTAB / LF / CR ; whitespace character =/ %x20-24 / %x26-5B / %x5D-5E / %x60-D7FF character =/ %xE000-FFFD / %x10000-10FFFF

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

(Note that the ABNF above is defined in terms of Unicode code points ([UNICODE5]); 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 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 exactly one character.

   The "%" wildcard matches zero or more characters.

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.

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.

5.15.2.  Example of DAV:like

5.15.2. Example of DAV:like

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

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

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

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

5.16.  DAV:contains

5.16. DAV:contains

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

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

Reschke, et al.             Standards Track                    [Page 31]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 31] RFC 5323 WebDAV SEARCH November 2008

   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.

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.

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.

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.

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.

5.16.1.  Result Scoring (DAV:score Element)

5.16.1. Result Scoring (DAV:score Element)

   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).

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:

Modified DTD fragment for DAV:propstat:

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

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

   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.

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.

Reschke, et al.             Standards Track                    [Page 32]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 32] RFC 5323 WebDAV SEARCH November 2008

5.16.2.  Ordering by Score

5.16.2. Ordering by Score

   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).

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).

5.16.3.  Examples

5.16.3. Examples

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

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".

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 xmlns:D='DAV:'>
     <D:contains>Peter Forsberg</D:contains>
   </D:where>

<D:where xmlns:D='DAV:'> <D:contains>Peter Forsberg</D:contains> </D:where>

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

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

   <D:where xmlns:D='DAV:'>
     <D:and>
       <D:contains>Peter</D:contains>
       <D:contains>Forsberg</D:contains>
     </D:and>
   </D:where>

<D:where xmlns:D='DAV:'> <D:and> <D:contains>Peter</D:contains> <D:contains>Forsberg</D:contains> </D:and> </D:where>

5.17.  Limiting the Result Set

5.17. Limiting the Result Set

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

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

   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.

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.

5.17.1.  Relationship to Result Ordering

5.17.1. Relationship to Result Ordering

   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.

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.

Reschke, et al.             Standards Track                    [Page 33]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 33] RFC 5323 WebDAV SEARCH November 2008

5.18.  The 'caseless' XML Attribute

5.18. The 'caseless' XML Attribute

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

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 ([UNICODE5]).

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 ([UNICODE5]).

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

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

5.19.  Query Schema for DAV:basicsearch

5.19. Query Schema for DAV:basicsearch

   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 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:

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

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

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

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

5.19.1.  DTD for DAV:basicsearch QSD

5.19.1. DTD for DAV:basicsearch QSD

   <!ELEMENT basicsearchschema  (properties, operators)>
   <!ELEMENT any-other-property EMPTY>
   <!ELEMENT properties         (propdesc*)>
   <!ELEMENT propdesc           ((prop|any-other-property), datatype?,
                                 searchable?, selectable?, sortable?,
                                 caseless?)>
   <!ELEMENT operators          (opdesc*)>
   <!ELEMENT opdesc             ANY>
   <!ATTLIST opdesc             allow-pcdata (yes|no) #IMPLIED>
   <!ELEMENT operand-literal    EMPTY>
   <!ELEMENT operand-typed-literal EMPTY>
   <!ELEMENT operand-property   EMPTY>

<!ELEMENT basicsearchschema (properties, operators)> <!ELEMENT any-other-property EMPTY> <!ELEMENT properties (propdesc*)> <!ELEMENT propdesc ((prop|any-other-property), datatype?, searchable?, selectable?, sortable?, caseless?)> <!ELEMENT operators (opdesc*)> <!ELEMENT opdesc ANY> <!ATTLIST opdesc allow-pcdata (yes|no) #IMPLIED> <!ELEMENT operand-literal EMPTY> <!ELEMENT operand-typed-literal EMPTY> <!ELEMENT operand-property EMPTY>

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

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.

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

Reschke, et al.             Standards Track                    [Page 34]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 34] RFC 5323 WebDAV SEARCH November 2008

5.19.2.  DAV:propdesc Element

5.19.2. DAV:propdesc Element

   Each instance of a DAV:propdesc element describes the property or
   properties in the DAV:prop element it contains.  All subsequent
   elements are descriptions that apply to those properties.  All
   descriptions are optional and may appear in any order.  Servers
   SHOULD support all the descriptions defined here, and MAY define
   others.

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.

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.

5.19.2.1.  DAV:any-other-property

5.19.2.1. DAV:any-other-property

   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).

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).

5.19.3.  The DAV:datatype Property Description

5.19.3. The DAV:datatype Property Description

   The DAV:datatype element contains a single XML element that provides
   a hint about the domain of the property, which may be useful 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 [XS2].

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 [XS2].

   <!ELEMENT datatype ANY >

<!ELEMENT datatype ANY >

Reschke, et al.             Standards Track                    [Page 35]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 35] RFC 5323 WebDAV SEARCH November 2008

   Examples from [XS2], Section 3:

Examples from [XS2], Section 3:

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

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

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

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

5.19.4.  The DAV:searchable Property Description

5.19.4. The DAV:searchable Property Description

   <!ELEMENT searchable EMPTY>

<!ELEMENT searchable EMPTY>

   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.

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.

5.19.5.  The DAV:selectable Property Description

5.19.5. The DAV:selectable Property Description

   <!ELEMENT selectable EMPTY>

<!ELEMENT selectable EMPTY>

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

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

5.19.6.  The DAV:sortable Property Description

5.19.6. The DAV:sortable Property Description

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

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

   <!ELEMENT sortable EMPTY>

<!ELEMENT sortable EMPTY>

5.19.7.  The DAV:caseless Property Description

5.19.7. The DAV:caseless Property Description

   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).

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).

   <!ELEMENT caseless EMPTY>

<!ELEMENT caseless EMPTY>

Reschke, et al.             Standards Track                    [Page 36]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 36] RFC 5323 WebDAV SEARCH November 2008

5.19.8.  The DAV:operators XML Element

5.19.8. The DAV:operators XML Element

   The DAV:operators element describes every optional operator supported
   in a query.  (Mandatory operators are not listed since they are
   mandatory and permit no variation in syntax.)  All optional operators
   that are supported MUST be listed in the DAV:operators element.

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 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
   Section 5.16).  Definition of additional operators using this format
   is NOT RECOMMENDED.

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 Section 5.16). Definition of additional operators using this format is NOT RECOMMENDED.

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

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

Reschke, et al.             Standards Track                    [Page 37]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke, et al. Standards Track [Page 37] RFC 5323 WebDAV SEARCH November 2008

5.19.9.  Example of Query Schema for DAV:basicsearch

5.19.9. Example of Query Schema for DAV:basicsearch

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

<D:basicsearchschema xmlns:Dが等しい、「DAV:」 xmlns: xsが等しい、「 http://www.w3.org/2001/XMLSchema 、「><D: 特性の><D: propdesc><D: ><D: getcontentlength/></Dを支えてください: ><D: データ型式><xs: nonNegativeInteger/></D: データ型式><D: 探せる/><D: 選択可能な/><Dを支えてください」; 分類可能/></D: propdesc><D: propdesc><D: 支柱><D: getcontenttype/><D: displayname/></D: ><D: 探せる/><D: 選択可能な/><D: 分類可能/></D: propdesc><D: propdesc><Dを支えてください:; 支柱><fstop xmlnsは" http://ns.example.org "/></Dと等しいです: ><D: 選択可能な/></D: propdesc><D: propdesc><D: 他のどんな特性も/><D: 探せる/><D: 選択可能な/></D: propdesc></D: 特性の><Dを支えてください:; オペレータ><D: opdesc><D: 同類/><D: オペランド特性/><D: オペランドリテラル/></D: opdesc><D: opdescに-pcdataに=を許容してください、「はい、「><D: /></D: opdesc></D: オペレータ></Dを含んでいます:、basicsearchschema>、」

   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.

この応答は4つの特性を記載します。 したがって、xsをデフォルトとします: 最後の3つの特性に関するデータ型は与えられていなくて、ストリング。 すべてが選択可能です、そして、最初の3は捜されるかもしれません。 最終以外のすべてが種類で使用されるかもしれません。 任意のDAVオペレータ、DAVについて:、含有、そして、: 同類がサポートされるDAV。

      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.

以下に注意してください。 ここで定義された図式発見は"caseless"属性のサポートしている値の発見に備えません。 これは、また、回答が義務的なオペレータを記載するのを必要とするかもしれません。

Reschke, et al.             Standards Track                    [Page 38]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[38ページ]。

6.  Internationalization Considerations

6. 国際化問題

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

特性は言語によってxmlを使用することでタグ付けをされているかもしれません: lang属性([RFC4918]、セクション4.3を見ます)。 DAV: 言語における定義(セクション5.12.1)にされるのであるオペレータDAVと(セクション5.12.2)が言語に関する状態の式を許容する言語マッチの任意のタグ付け情報。

7.  Security Considerations

7. セキュリティ問題

   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 ([RFC2616] and WebDAV ([RFC4918])
   also apply to DASL.  In addition, this section will include security
   risks inherent in the search and retrieval of resource properties and
   content.

DASLアプリケーションが意識している必要があるセキュリティ含意に関してこのセクションを詳細問題に提供します。 また、HTTP/1.1の[RFC2616]とWebDAV([RFC4918])のセキュリティ問題のすべてがDASLに当てはまります。さらに、このセクションはリソースの特性と内容の検索と検索に固有のセキュリティ危険を含むでしょう。

   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:

クライアントは第一に、質問でGETを通して利用可能でない情報かPROPFINDメソッドを検索できてはいけません。 特に:

   o  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 Section 5.5.3).

o クライアントがそうしないWebDAV所有地における質問規制はまるで特性が存在していないかのように(セクション5.5.3を見てください)評価されるべきアクセスの必要性を読みました。

   o  Query constraints on content (as with DAV:contains, defined in
      Section 5.16) for which the client does not have read access need
      to be evaluated as if a GET would return a 4xx status code.

o 内容で規制について質問してください、(DAVのような以下のこと、中で定義されて、含んでいる、セクション5.16) クライアントが読書アクセスがまるでGETが4xxステータスコードを返すかのように評価される必要がさせない。

   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

7.1. XML外部実体の含意

   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.

XMLは、特定のURIで位置するXMLのインラインインクルードを検索して、実行するためにXMLプロセッサを命令する.2セクション4.2[XML]で定義された「外部実体」として知られている施設をサポートします。 XMLドキュメントに関連しているドキュメント型の宣言(DTD)を追加するか、または変更するのに外部のXML実体を使用できます。 また、XMLドキュメントの中身の中にXMLを含むのに外部のXML実体を使用できます。 この仕様で使用されるXMLなどの非の有効にするXMLに関しては、外部のXML実体を含んでいるのは[XML]によって必要とされません。 しかしながら、[XML]は、XMLプロセッサが自己判断で外部のXML実体を含むかもしれないと述べます。

   External XML entities have no inherent trustworthiness and are
   subject to all the attacks that are endemic to any HTTP GET request.

外部のXML実体は、どんな固有の信頼できることも持たないで、どんなHTTP GET要求に風土病であるすべての攻撃も受けることがあります。

Reschke, et al.             Standards Track                    [Page 39]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[39ページ]。

   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.

その上、外部のXML実体がDTDを変更して、したがって、XMLドキュメントの最終形態に影響するのは、可能です、最悪の場合には意味論をかなり変更するか、または[RFC3023]で議論したセキュリティ危険にXMLプロセッサを暴露して。 したがって、implementersは外部のXML実体が信頼できないとして扱われるべきであるのを意識しているに違いありません。

   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.

また、外部のXML実体を利用した広く配布しているアプリケーションに伴うスケーラビリティリスクがあります。 この状況で、1つの外部のXML実体を求める重要な数の要求があるのは、可能です、潜在的に外部のXML実体を含むリソースに関する要求をさばくどんなサーバも積みすぎて。

8.  Scalability

8. スケーラビリティ

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

質問文法はURIによって特定されます。 回収可能であるように(例えば「http://」で始まるもの)見えても、アプリケーションSHOULD NOTは、これらのURIを検索するのを試みます。

9.  IANA Considerations

9. IANA問題

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

このドキュメントはXML要素のために[RFC4918]のセクション21で定義された名前空間を使用します。

9.1.  HTTP Headers

9.1. HTTPヘッダ

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

このドキュメントは以下に記載されたHTTPヘッダを指定します。(それは、[RFC3864]で定義された永久的なHTTPヘッダ登録に加えられます)。

9.1.1.  DASL

9.1.1. DASL

   Header field name:  DASL

ヘッダーフィールド名: DASL

   Applicable protocol:  http

適切なプロトコル: http

   Status:  standard

状態: 規格

   Author/Change controller:  IETF

コントローラを書くか、または変えてください: IETF

   Specification document:  this specification (Section 3.2)

仕様ドキュメント: この仕様(セクション3.2)

Reschke, et al.             Standards Track                    [Page 40]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[40ページ]。

10.  Contributors

10. 貢献者

   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, Surendra
   Reddy, and Judith Slein (see <http://www.webdav.org/dasl/> for the
   working group's web site,
   <http://purl.org/NET/webdav/dasl-references/reqs> for a requirements
   document, and
   <http://purl.org/NET/webdav/dasl-references/dasl-protocol-00> for an
   early version of the specification).

このドキュメントは2000年までWebDAV DASLワーキンググループによって行われたDASLプロトコルに対する先の仕事に基づいています; すなわち、アランBabich、ジム・デイヴィス、リック・ヘンダーソン、デール・ロウリー、Saveenレディ、Surendraレディ、およびジュディスSlein(<http://www.webdav.org/dasl/>をワーキンググループのウェブサイトに見てください、仕様の早めのバージョンのための要件ドキュメント、および<dasl http://purl.org/NET/webdav/参照/daslプロトコル-00>のための<dasl http://purl.org/NET/webdav/参照/reqs>)。

11.  Acknowledgements

11. 承認

   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.

このドキュメントはリサDusseault、ハビエル・ゴドイ、Sungキム、クリス・ニューマン、エリアスSinderson、マーチンWallmer、キースWannamaker、ジム・ホワイトヘッド、およびケビンWiggenによる思慮に富む議論の利益を得ました。

12.  References

12. 参照

12.1.  Normative References

12.1. 引用規格

   [RFC2119]      Bradner, S., "Key words for use in RFCs to Indicate
                  Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC2119] ブラドナー、S.、「Indicate Requirement LevelsへのRFCsにおける使用のためのキーワード」、BCP14、RFC2119、1997年3月。

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

[RFC2616] フィールディング、R.、Gettys、J.、ムガール人、J.、Frystyk、H.、Masinter、L.、リーチ、P.、およびT.バーナーズ・リー、「HTTP/1.1インチ、RFC2616、1999年ハイパーテキスト転送プロトコル--6月。」

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

[RFC3023] ムラタとM.と聖ローラン、S.とD.コーン、「XMLメディアタイプ」、RFC3023、2001年1月。

   [RFC3253]      Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J.
                  Whitehead, "Versioning Extensions to WebDAV (Web
                  Distributed Authoring and Versioning)", RFC 3253,
                  March 2002.

[RFC3253] クレム、G.、Amsden、J.、エリソン、T.、Kaler、C.、およびJ.ホワイトヘッド、「WebDAV(ウェブの分配されたオーサリングとVersioning)へのVersioning拡張子」、RFC3253(2002年3月)。

   [RFC3744]      Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead,
                  "Web Distributed Authoring and Versioning (WebDAV)
                  Access Control Protocol", RFC 3744, May 2004.

[RFC3744] クレム、G.、Reschke、J.、Sedlar、E.、およびJ.ホワイトヘッド、「ウェブの分配されたオーサリングとVersioning(WebDAV)アクセスコントロールは議定書を作ります」、RFC3744、2004年5月。

   [RFC3986]      Berners-Lee, T., Fielding, R., and L. Masinter,
                  "Uniform Resource Identifier (URI): Generic Syntax",
                  STD 66, RFC 3986, January 2005.

[RFC3986] バーナーズ・リー、T.、フィールディング、R.、およびL.Masinter、「Uniform Resource Identifier(URI):」 「ジェネリック構文」、STD66、RFC3986、2005年1月。

Reschke, et al.             Standards Track                    [Page 41]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[41ページ]。

   [RFC4918]      Dusseault, L., Ed., "HTTP Extensions for Web
                  Distributed Authoring and Versioning (WebDAV)",
                  RFC 4918, June 2007.

[RFC4918] Dusseault、L.、エド、「ウェブの分配されたオーサリングとVersioning(WebDAV)のためのHTTP拡大」、RFC4918、6月2007日

   [RFC5234]      Crocker, D., Ed. and P. Overell, "Augmented BNF for
                  Syntax Specifications: ABNF", STD 68, RFC 5234,
                  January 2008.

エド[RFC5234]クロッカー、D.、P.Overell、「構文仕様のための増大しているBNF:」 "ABNF"、STD68、RFC5234、2008年1月。

   [XML]          Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E.,
                  and F. Yergeau, "Extensible Markup Language (XML) 1.0
                  (Fourth Edition)", W3C REC-xml-20060816, August 2006,
                  <http://www.w3.org/TR/2006/REC-xml-20060816>.

T.、パオリ、J.、Sperberg-マックィーン、C.、Maler、E.、およびF.Yergeau、「拡張マークアップ言語(XML)1.0(第4版)」を[XML]は、いななかせます、W3C REC-xml-20060816、2006年8月、<http://www.w3.org/TR/2006/REC-xml-20060816>。

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

[XPATH] クラークとJ.とS.DeRose、「XML経路言語(XPath)バージョン1インチ、W3C REC-xpath-19991116、<http://www.w3.org/TR/1999/REC-xpath-19991116 1999年11月の>。」

   [XPATHFUNC]    Malhotra, A., Melton, J., and N. Walsh, "XQuery 1.0
                  and XPath 2.0 Functions and Operators", W3C REC-xpath-
                  functions-20070123, January 2007, <http://www.w3.org/
                  TR/2007/REC-xpath-functions-20070123/>.

[XPATHFUNC] Malhotra、A.、Melton、J.、N.ウォルシュ、および「XQuery1.0とXPath2.0機能とオペレータ」、W3C REC-xpath機能-20070123、2007年1月、<は://REC-xpath www.w3.org/TR/2007/機能20070123/>をhttpします。

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

[XS1] トンプソン、H.、ぶな、D.、マローニー、M.、メンデルゾーン、N.、およびワールドワイドウェブコンソーシアム、「XML図式第1部:」 「構造」、W3C REC-xmlschema-1-20041028 2004年10月、<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/>。

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

[XS2] ビロン、P.、Malhotra、A.、およびワールドワイドウェブコンソーシアム、「XML図式第2部:」 「データ型式第2版」、W3C REC-xmlschema-2-20041028、2004年10月、<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/>。

12.2.    Informative References

12.2. 有益な参照

   [BCP47]        Phillips, A. and M. Davis, "Matching of Language
                  Tags", BCP 47, RFC 4647, September 2006.

[BCP47]フィリップス、A.とM.デイヴィス、「言語タグのマッチング」BCP47、2006年9月のRFC4647。

   [RFC3864]      Klyne, G., Nottingham, M., and J. Mogul, "Registration
                  Procedures for Message Header Fields", BCP 90,
                  RFC 3864, September 2004.

[RFC3864]KlyneとG.とノッティンガム、M.とJ.ムガール人、「メッセージヘッダーフィールドのための登録手順」BCP90、2004年9月のRFC3864。

   [RFC4437]      Whitehead, J., Clemm, G., and J. Reschke, Ed., "Web
                  Distributed Authoring and Versioning (WebDAV) Redirect
                  Reference Resources", RFC 4437, March 2006.

[RFC4437] ホワイトヘッド、J.、クレム、G.、およびReschke(エド)(「ウェブの分配されたオーサリングとVersioning(WebDAV)の再直接の参照用の情報資源」、RFC4437)が2006に行進させるJ.

Reschke, et al.             Standards Track                    [Page 42]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[42ページ]。

   [RFC4790]      Newman, C., Duerst, M., and A. Gulbrandsen, "Internet
                  Application Protocol Collation Registry", RFC 4790,
                  March 2007.

[RFC4790] ニューマンとC.とDuerst、M.とA.Gulbrandsen、「インターネットアプリケーション・プロトコル照合登録」、RFC4790、2007年3月。

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

[SQL99]ミルトン、J.、「データベース言語SQL第2部:」 「財団(SQL/財団)」、ISO ISO/IEC9075-2: 1999年7月の1999(E)。

   [UNICODE5]     The Unicode Consortium, "The Unicode Standard -
                  Version 5.0", Addison-Wesley , November 2006,
                  <http://www.unicode.org/versions/Unicode5.0.0/>.

[UNICODE5] ユニコード共同体であり、「ユニコード規格--バージョン5インチ、アディソン-ウエスリー、2006年11月、<は://www.unicode.org/バージョン/Unicode5.0.0/>をhttpします」。

                  ISBN 0321480910 [1]

ISBN0321480910[1]

   [WEBDAV-BIND]  Clemm, G., Crawford, J., Reschke, J., Ed., and J.
                  Whitehead, "Binding Extensions to Web Distributed
                  Authoring and Versioning (WebDAV)", October 2008.

[WEBDAV-ひも] クレム、G.、クロフォード、J.、Reschke、J.、エドJ.ホワイトヘッド、「ウェブへの拘束力がある拡大はオーサリングとVersioning(WebDAV)を分配しました」、2008年10月。

URIs

URI

   [1]  <urn:isbn:0321480910>

[1] <つぼ:isbn:0321480910>。

Reschke, et al.             Standards Track                    [Page 43]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[43ページ]。

Appendix A.  Three-Valued Logic in DAV:basicsearch

DAVの付録のA.の3で評価された論理: basicsearch

   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規格の3で評価された論理は使用されています。(例えば、ANSI X3.135-1992、セクション8.12でANSI規格SQL仕様に基づき定義されるように、ページです。 188-189、セクション8.2、p。 169 一般規則1)a)など)

   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.

ANSI規格の3で評価された論理はリソースのためにスキャンで値を持っていない(例えば、ヌルである、または定義されません)検索条件、そして、未定義の式が検索条件(例えば、ゼロ除算など)にある状態で特性の問題に対処する確かに最も広く練習されたメソッドです。 3は以下の通り論理作品を評価しました。

   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.

未定義の式は式の値が定義されない式です。 未定義の式は真理値UNKNOWNからの完全に別々の概念です。(事実上、UNKNOWNはよく定義されます)。 特性の名と直定数はこのセクションの目的のための式であると考えられます。 スキャン中の現在のリソースの特性が値に設定されていないなら、リソースに、その属性の価値はスキャンで未定義です。 そうするなら、DASL1.0には、どんな算数の除算演算子もいませんが、ゼロ除算は未定義の算術式でしょうに。

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

演算、ストリング、またはdatetime subexpressionの何か下位区分が未定義であるなら、全体の演算、ストリング、またはdatetime subexpressionが未定義です。

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

明らかに未定義の数、ストリング、またはdatetime値を表すために、どんな明白な定数もありません。

   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.

結局検索条件でブール値を返すので、いつも演算、ストリング、およびdatetime式は他のオペレータへの議論です。 演算、ストリング、およびdatetime式をブール値に変換するオペレータの例が6つの関係演算子である、(「すばらしさ、」、「より少なさ、」、「同輩」など) 関係演算子のどちらかかオペランドの両方に未定義値があるなら、関係演算子がUNKNOWNに評価するその時です。 さもなければ、比較の結果によって、関係演算子はTRUEかFALSEに評価します。

   The Boolean operators DAV:and, DAV:or, and DAV:not are evaluated
   according to the following rules:

論理演算子、DAV、:、DAV、:、DAV: 以下の規則に従って、評価されません:

   not UNKNOWN = UNKNOWN

未知の=未知でない

   UNKNOWN and TRUE = UNKNOWN

未知の未知の、そして、本当の=

Reschke, et al.             Standards Track                    [Page 44]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[44ページ]。

   UNKNOWN and FALSE = FALSE

未知の、そして、誤った=偽

   UNKNOWN and UNKNOWN = UNKNOWN

未知の、そして、未知の=未知

   UNKNOWN or TRUE = TRUE

未知の、または、本当の=、本当

   UNKNOWN or FALSE = UNKNOWN

未知の未知の、または、誤った=

   UNKNOWN or UNKNOWN = UNKNOWN

未知の、または、未知の=未知

Appendix B.  Candidates for Future Protocol Extensions

今後のプロトコル拡大の付録B.候補

   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.

このセクションはこの仕様の開発の間に上げられていましたが、規制が適所にあった状態で解決を全く見つけることができなかった問題をまとめます。 もっとも、この仕様の今後の改正はこれらの問題を再訪させるべきです。

B.1.  Collation Support

B.1。 照合サポート

   Matching and sorting of textual data relies on collations.  With
   respect to WebDAV SEARCH, a combination of various design approaches
   could be used:

原文のデータのマッチングとソーティングは校合に依存します。 WebDAV検索に関して、様々な設計手法の組み合わせを使用できました:

   o  Require server support for specific collations.

o 特定の校合のサーバサポートを必要としてください。

   o  Require that the server can advertise which collations it
      supports.

o サーバがそれがサポートするどの校合の広告を出すことができるかを必要であってください。

   o  Allow a client to select the collation to be used.

o 照合が使用されるのをクライアントを選択させてください。

   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.

実際には、通常、WebDAV検索の現在の実装は制御しないで、また照合情報が利用可能でないかもしれないバックエンドを当てにします。 さらに悪いことには、DAV: basicsearch文法の実装は、頻繁に複数の基本的な店(特性や全文内容などの)からのデータを結合する必要があります、そして、その結果、照合サポートはオペレータか特性に基づいて異なるかもしれません。

   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:

別の未解決の問題はどんな照合形式をサポートするかということです。 この書くこと時点で、以下の2つの仕様が、必要なフレームワークを提供するように思えて、その結果、WebDAV検索における照合サポートへの今後の活動のためのベースであるかもしれません:

   1.  "Internet Application Protocol Collation Registry" ([RFC4790]).

1. 「インターネットアプリケーション・プロトコル照合登録」([RFC4790]。)

   2.  "XQuery 1.0 and XPath 2.0 Functions and Operators" ([XPATHFUNC],
       Section 7.3.1).

2. 「XQuery1.0とXPath2.0機能とオペレータ。」([XPATHFUNC]、セクション7.3.1)

Reschke, et al.             Standards Track                    [Page 45]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[45ページ]。

B.2.  Count

B.2。 カウント

   DAV:basicsearch does not allow a request that returns the count of
   matching resources.

DAV: basicsearchはリソースを合わせるカウントを返す要求を許しません。

   A protocol extension would need to extend DAV:select, and also modify
   the DAV:multistatus response format.

プロトコル拡張子は、DAVを広げる必要があるでしょう: DAVを選択して、また、変更してください: 「マルチ-状態」応答形式。

B.3.  Diagnostics for Unsupported Queries

B.3。 サポートされない質問のための病気の特徴

   There are many reasons why a given query may not be supported by a
   server.  Query Schema Discovery (Section 4) can be used to discover
   some constraints, but not all.

与えられた質問がサーバで後押しされていないかもしれない多くの理由があります。質問Schemaディスカバリー(セクション4)は、いくつかの規制を発見するのに使用されますが、すべて使用できません。

   Future revisions should consider the introduction of specific
   condition codes ([RFC4918], Section 16) to these situations.

今後の改正は特定の条件コード([RFC4918]、セクション16)の導入をこれらの状況と考えるべきです。

B.4.  Language Matching

B.4。 言語マッチング

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

セクション5.12 .2 XPath"lang"機能([XPATH]、セクション4.3)に関して合っている言語を定義します。 今後の改正は、代わりに[BCP47]に建てると考えるべきです。

B.5.  Matching Media Types

B.5。 メディアを合わせるのはタイプされます。

   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 <http
   ://lists.w3.org/Archives/Public/www-webdav-dasl/2003OctDec/0109.html>
   for a specific proposal.

DAVを使用することでメディアタイプを合わせます: getcontenttypeの特性とDAV: オペレータのように、DAV: また、パラメタを許容するgetcontenttypeへの困難な支払われるべきものはそうですか? メディアタイプを合わせる目的のために明確に設計された新しいオペレータはたぶんものを大いに簡素化するでしょう。 明確な提案に関して<http://lists.w3.org/アーカイブ/公衆/www-webdav-dasl/2003OctDec/0109.html>を見てください。

B.6.  Query by Name

B.6。 名前の質問

   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 <http://lists.w3.org/Archives/
   Public/www-webdav-dasl/2003OctDec/0100.html> for a proposed extension
   covering this use case.

DAV: basicsearchが所有地を作動させる、(任意に、コンテンツ)、リソース、その結果、本当に、リソースのURIの部品で合っているのを許容しません。 この使用がケースに入れる提案された拡大覆いのために<http://lists.w3.org/アーカイブ/公衆/www-webdav-dasl/2003OctDec/0100.html>を見てください。

B.7.  Result Paging

B.7。 結果ページング

   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 Section 5.17).

頻繁に議論された特徴は明確に結果の「次」のセットを要求する能力です、サーバが、結果に先端を切らせると決めたか、またはクライアントが明らかに、限られたセット(例えば、DAVを使用します: セクション5.17で定義された限界要素)を求めたとき。

Reschke, et al.             Standards Track                    [Page 46]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[46ページ]。

   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.

この場合、サーバが完全な質問結果を保って、別々の結果リソースを特定する新しいURIを提供できるなら、望ましいでしょうに、クライアントがGET要求で追加データを検索して、DELETE要求で結果を取り除くのを許容して。

B.8.  Search Scope Discovery

B.8。 検索範囲発見

   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
   Section 4.

検索Arbiterリソースを考えて、現在、プログラムに基づいてサポートしているセットの検索範囲を発見する方法が全くありません。 この仕様の今後の改正は範囲発見メカニズムを指定するかもしれません、セクション4で定義されたQuery Schemaディスカバリーと同様です。

Index

インデックス

   C
      caseless attribute  26-27, 34
      Condition Names
         DAV:search-grammar-discovery-supported (pre)  9
         DAV:search-grammar-supported (pre)  9
         DAV:search-multiple-scope-supported (pre)  9
         DAV:search-scope-valid (pre)  9
      Criteria  5

C caselessは26-27を結果と考えます、34Condition Names DAV: 発見がサポートした文法を捜してください、(前、)、9DAV: 文法がサポートした検索、(前、)、9DAV: 複数の範囲がサポートした検索、(前、)、9DAV: 有効な状態で範囲を捜してください、(前、)、9Criteria5

   D
      DAV:and  26
      DAV:ascending  26
      DAV:contains  31
      DAV:depth  23
      DAV:descending  26
      DAV:eq  27
         caseless attribute  27
      DAV:from  23
      DAV:gt  27
      DAV:gte  27
      DAV:include-versions  23
      DAV:is-collection  30
      DAV:is-defined  30
      DAV:language-defined  29
      DAV:language-matches  29
      DAV:like  30
      DAV:limit  33
      DAV:literal  27
      DAV:lt  27
      DAV:lte  27
      DAV:not  26
      DAV:nresults  33
      DAV:or  26

昇る..含む..徹底的..下る..結果と考える..含む..バージョン..収集..定義..言語..定義..言語..マッチ..制限..文字通り

Reschke, et al.             Standards Track                    [Page 47]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[47ページ]。

      DAV:orderby  26
      DAV:scope  23
      DAV:score  32
         relationship to DAV:orderby  33
      DAV:search-grammar-discovery-supported precondition  9
      DAV:search-grammar-supported precondition  9
      DAV:search-multiple-scope-supported precondition  9
      DAV:search-scope-valid precondition  9
      DAV:select  23
      DAV:supported-query-grammar-set property  14
      DAV:typed-literal  28
      DAV:where  24

DAV: orderby26DAV: 23DAVを見てください: DAV: orderby33DAVとの32関係を得点してください: 発見がサポートした検索文法は9DAVをあらかじめ調整します: 文法がサポートした検索は9DAVをあらかじめ調整します: 複数の範囲がサポートした検索は9DAV: 有効な状態で範囲を捜している前提条件をあらかじめ調整します。9DAV: 23DAVを選択してください:、サポートしている質問文法セット所有地、14DAV: タイプされたリテラル28DAV: どこ、24

   M
      Methods
         SEARCH  7

Mメソッドは7を捜します。

   O
      OPTIONS method  13
         DASL response header  14

○ OPTIONSメソッド13DASL応答ヘッダ14

   P
      Properties
         DAV:supported-query-grammar-set  14

P特性のDAV: サポートしている質問文法セット14

   Q
      Query  5
      Query Grammar  5
      Query Grammar Discovery  13
         using live property  13
         using OPTIONS  13
      Query Schema  5

OPTIONS13Query Schema5を使用することで精力の特性13を使用するQ質問5Query Grammar5Query Grammarディスカバリー13

   R
      Result  5
      Result Record  5
      Result Record Definition  5
      Result Set  5
      Result Set Truncation
         Example  10

R結果5結果記録5結果の記録的な定義5結果セット5結果セットトランケーションの例10

   S
      Scope  6
      Search Arbiter  6
      SEARCH method  7
      Search Modifier  6
      Sort Specification  6

S範囲6検索Arbiter6検索メソッド7検索Modifier6Sort Specification6

Reschke, et al.             Standards Track                    [Page 48]

RFC 5323                     WebDAV SEARCH                 November 2008

Reschke、他 規格はWebDAV検索2008年11月にRFC5323を追跡します[48ページ]。

Authors' Addresses

作者のアドレス

   Julian F. Reschke (editor)
   greenbytes GmbH
   Hafenweg 16
   Muenster, NW  48155
   Germany

greenbytes GmbH Hafenweg16Muenster、ジュリアンF.Reschke(エディタ)NW48155ドイツ

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

以下に電話をしてください。 +49 251 2807760 メール: julian.reschke@greenbytes.de ユリ: http://greenbytes.de/tech/webdav/

   Surendra Reddy
   Mitrix, Inc.
   303 Twin Dolphin Drive, Suite 600-37
   Redwood City, CA  94065
   U.S.A.

SurendraレディMitrix Inc.303の双子のイルカドライブ、Suite600-37レッドウッドシティー、カリフォルニア94065米国

   Phone: +1 408 500 1135
   EMail: Surendra.Reddy@mitrix.com

以下に電話をしてください。 +1 1135年の408 500メール: Surendra.Reddy@mitrix.com

   Jim Davis
   27 Borden Street
   Toronto, Ontario  M5S 2M8
   Canada

ジムデイヴィス27Borden通りトロント、オンタリオM5S 2M8カナダ

   Phone: +1 416 929 5854
   EMail: jrd3@alum.mit.edu
   URI:   http://www.econetwork.net/~jdavis

以下に電話をしてください。 +1 5854年の416 929メール: jrd3@alum.mit.edu ユリ: http://www.econetwork.net/~jdavis

   Alan Babich
   IBM Corporation
   3565 Harbor Blvd.
   Costa Mesa, CA  92626
   U.S.A.

アランBabich IBM社3565の港Blvd. コスタメサ、カリフォルニア92626米国

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

以下に電話をしてください。 +1 3403年の714 327メール: ababich@us.ibm.com

Reschke, et al.             Standards Track                    [Page 49]

Reschke、他 標準化過程[49ページ]

一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

DROP FUNCTION ストアードファンクションを削除する

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る