- From: Al Gilman <asgilman@access.digex.net>
- Date: Mon, 23 Nov 1998 10:47:05 -0500 (EST)
- To: w3c-wai-er-ig@w3.org
- Cc: w3c-wai-pf@w3.org, alexhop@microsoft.com
There are strong parallels between distributed authoring and versioning and second- or third- party construction of adaptive forms of web documents. This relates to work in the WAI ER area concerning finding descriptions for images to use in repair. This relates to requirements for the XML Fragments WG. Al ----- Forwarded message from The IESG ----- To: IETF-Announce: ; Subject: WG ACTION: DAV Searching and Locating (dasl) From: The IESG <iesg-secretary@ietf.org> Date: Mon, 23 Nov 1998 10:15:05 -0500 A new working group has been formed in the Applications Area of the IETF. Please contact the Chair for additional information. DAV Searching and Locating (dasl) --------------------------------- Current Status: Active Working Group Chair(s): Alex Hopmann <alexhop@microsoft.com> Applications Area Director(s): Keith Moore <moore@cs.utk.edu> Patrik Faltstrom <paf@swip.net> Applications Area Advisor: Keith Moore <moore@cs.utk.edu> Mailing Lists: General Discussion:www-webdav-dasl@w3.org To Subscribe: www-webdav-dasl-request@w3.org In Body: subscribe in body of message Archive: http://lists.w3.org/Archives/Public/www-webdav-dasl/ Description of Working Group: The goal of this working group is to define and develop an extensible DAV Searching and Locating protocol as an application of HTTP. The working group will define protocol elements that enable server-executed queries to locate resources based upon their property values and text content as expressed by the DAV data model. Problem Definition WEBDAV and HTTP enable client-side searching by defining a simple set of mechanisms (the PROPFIND and GET methods) to locate those resources meeting client-defined criteria. These mechanisms can be inefficient, do not adequately deal with some simple content-based queries, and do not take advantage of the advanced querying and caching capabilities of modern storage systems. The DASL Protocol will enable a HTTP/1.1 compliant scheme for server-side searching to address these limitations. The working group will define the following for a server-side searching mechanism: - How to express the search: the syntax and semantics of a query - How to focus the query by identifying its scope - How to discover the search capability of a resource. - The syntax for the search results Working Group Scope A generalized search mechanism is a broad problem space. It encompasses a variety of object models, typing schemes, and media. By focusing on a subset of this space, the problem of locating resources based on property values and text content, the working group will leverage much of the existing work that has been done on querying under simple property and resource models. In-Scope items include: - typing - comparisons (>, >=, <, <=, !=, ==) - internationalized content - text content matching - dealing with arbitrary XML values Out-of-scope items include: - definitions of well-known properties - server-to-server communication protocols - cross-language comparisons - searching for non-text content (images, video, audio, etc.) - client control of server administration (e.g. indexing) Deliverables The final output of this working group is expected to be two documents: (1) A requirements document, that describes the high-level functional requirements for DASL, including rationale. This will be an Informational document. (2) A protocol specification describing the additions to HTTP (new methods, headers, request bodies, and response bodies) needed to implement the DASL requirements. This will be a Standards Track document. Goals and Milestones: Dec 98 Complete Scenarios document. Jan 99 Create final version of DASL requirements document. Submit to IESG for consideration as an Informational RFC. Mar 99 Complete revisions to DASL protocol. Submit to IESG for consideration as a Proposed Standard. ----- End of forwarded message from The IESG -----
Received on Monday, 23 November 1998 10:45:49 UTC