W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > January to March 2003

RE: quick summary of DASL discussion during WebDAV working group meeting

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 28 Jan 2003 16:55:17 +0100
To: <www-webdav-dasl@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCIEGGGFAA.julian.reschke@gmx.de>

Hi,

I've tried to update all open issues with the results of the WG meeting
discussion (I've also resolved a few minor issues and did some of the
renaming that was discussed):

	http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-latest.html

Feedback appreciated.

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Julian Reschke
> Sent: Wednesday, January 22, 2003 4:58 PM
> To: www-webdav-dasl@w3.org
> Subject: quick summary of DASL discussion during WebDAV working group
> meeting
>
>
>
> Hi,
>
> here are my notes of the dicussions around DASL that we had on
> Monday. They
> give a short summary of what has been discussed and how we intend
> to resolve
> these issues. There may be some details I left out (maybe Jim or Elias can
> add them?).
>
> Regards, Julian
>
> --
>
>
> Summary of consensus regarding DASL spec changes
> (WebDAG WG meeting January, Monday session)
>
> 1) Naming / error marshalling
>
> Backwards compatibility to older drafts doesn't seem to be required. It is
> therefore acceptable to
>
> - update error marshalling to use RFC3253 semantics
> - change element/attribute names for enhanced consistency or precision
>
> (may want to rename DASL header to make detection of "new" server easier)
>
>
> 2) getting "next" results
>
> Feedback is that this is needed. Implementation plan:
>
> - add DAV:skip to DAV:limit
> - optionally return identifier for search result that can be
> submitted with
> next request
> - consider using HTTP Range header to retrieve part of
> multistatus response
> body
>
>
> 3) language handling (xml:lang)
>
> xml:lang in a search request is ignored. Proposal to add specific
> operators
> comparing the xml:lang of a property value. To do: flesh out syntax and
> decide whether optional or not.
>
>
> 4) collation sequences (ordering)
>
> - primarily server defined
> - allow "lang" (not xml:lang) attribute to help server in selecting a
> default collation
> - possibley reserve "collation" attribute for compatibility with XPath
> 2.0/Query
>
> (summary: make it compatible to XSLT/XPath 2.0 / XQuery)
>
>
> 5) type handling in queries (clarification DAV:literal)
>
> - for DAV:getlastmodified and DAV:creationdate, require DAV:literal to be
> an ISO date (otherwise undefined), and make a date comparison a MUST
> - for DAV:getcontentlength, require DAV:literal to be a numerical
> value, and
> make a numerical comparison a MUST
> - for other live properties which are typed but not defined in RFC2518,
> allow
> the server to cast the DAV:literal and do a type-aware comparison
>
>
> 6) type handling in queries (new operand DAV:typed-literal)
>
> (dicussion to be added separately)
>
>
> --
> <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
>
Received on Tuesday, 28 January 2003 10:55:55 GMT

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