- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 8 Jul 2002 19:05:00 +0200
- To: "Jim Davis" <jrd3@alum.mit.edu>, <www-webdav-dasl@w3.org>
> From: www-webdav-dasl-request@w3.org > [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Jim Davis > Sent: Monday, July 08, 2002 6:51 PM > To: www-webdav-dasl@w3.org > Subject: RE: QSD: DAV:opdesc > > > > At 03:54 PM 7/8/2002 +0200, Julian Reschke wrote: > > consider...in addition to operators and parameters, the opdesc > element also > >carries a human-readable description of the operator? > > > >On the other hand, it's certainly possible that the "new" > operator resides > >in a namespace for which additional human-readable documention can be > >accessed (for instance a namespace document that can be > retrieved using GET > >>from a HTTP based namespace...) > > I don't object to this, if you want to add it, as long as it is optional. > > Are we talking about a natural language string? If so, perhaps > the element > should be repeatable, to allow for multiple languages? As in other WebDAV specs (ACL), this can be done (and labelled) according the Accept-Language header... > Or maybe there should be a way to express a URI that leads to > documentation? OK, we now have three options :-) 1) return description with the Query Schema 2) return *pointer* to description with the Query Schema 3) use namespace name of query operator as pointer to description
Received on Monday, 8 July 2002 13:05:32 UTC