- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 10 Jun 2002 09:02:04 +0200
- To: "Julian Reschke" <julian.reschke@gmx.de>, "Jim Davis" <jrd3@alum.mit.edu>, <www-webdav-dasl@w3.org>
Here's an attempt to avoid the usage of pseudo-properties (feedback appreciated): 1) Query: Instead of: SEARCH / HTTP/1.1 Host: recipes.com Content-Type: application/xml Content-Length: xxx <?xml version="1.0"?> <searchrequest xmlns="DAV:"> <basicsearch> <select> <prop> <queryschema/> </prop> </select> <from> <scope> <href>http://recipes.com</href> </scope> </from> </basicsearch> </searchrequest> use SEARCH / HTTP/1.1 Host: recipes.com Content-Type: application/xml Content-Length: xxx <?xml version="1.0"?> <grammar-discovery xmlns="DAV:"> <grammar> <basicsearch/> </grammar> <scope> <href>http://recipes.com</href> </scope> </grammar-discovery> Note: we change the name of the document element to distinguish from a search request. An alternative approach would be to use a REPORT, but that would introduce a dependancy on other RFCs I'm sure many won't like. 2) Result: Instead of: HTTP/1.1 207 Multistatus Content-Type: application/xml Content-Length: xxx <?xml version="1.0"?> <multistatus xmlns="DAV:"> <response> <href>http://recipes.com</href> <propstat> <prop> <queryschema> <basicsearchschema> (See section "Query schema for DAV:basicsearch" for the actual contents) </basicsearchschema> </queryschema> </prop> <status>HTTP/1.1 200 OK</status> </propstat> </response> </multistatus> Use: HTTP/1.1 207 Multistatus Content-Type: application/xml Content-Length: xxx <?xml version="1.0"?> <multistatus xmlns="DAV:"> <response> <href>http://recipes.com</href> <queryschema> <basicsearchschema> (See section "Query schema for DAV:basicsearch" for the actual contents) </basicsearchschema> </queryschema> <status>HTTP/1.1 200 OK</status> </response> </multistatus> So we need to extend the response element, but that's still better than introducing pseudo-properties.
Received on Monday, 10 June 2002 03:02:39 UTC