W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > April to June 2002

RE: comment on DASL draft issue: qsd pseudo property

From: Wallmer, Martin <Martin.Wallmer@softwareag.com>
Date: Mon, 10 Jun 2002 09:05:25 +0200
Message-ID: <DFF2AC9E3583D511A21F0008C7E6210602D9027A@daemsg02.software-ag.de>
To: "'Julian Reschke'" <julian.reschke@gmx.de>, Jim Davis <jrd3@alum.mit.edu>, www-webdav-dasl@w3.org

Sounds good :-)

Martin

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Montag, 10. Juni 2002 09:02
To: Julian Reschke; Jim Davis; www-webdav-dasl@w3.org
Subject: RE: comment on DASL draft issue: qsd pseudo property



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:05:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:08 GMT