- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 14 May 2002 00:15:24 +0200
- To: "Joe Orton" <joe@manyfish.co.uk>, "Webdav WG \(E-mail\)" <w3c-dist-auth@w3c.org>
> From: w3c-dist-auth-request@w3.org > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Joe Orton > Sent: Monday, May 13, 2002 9:51 PM > To: Webdav WG (E-mail) > Subject: Re: Issue: SOURCE_PROPERTY_UNDERSPECIFIED > > > On Mon, May 13, 2002 at 06:46:49PM +0200, Julian Reschke wrote: > > The main issues are that > > > > - the text and examples in the RFC just do not make sense to me > (see [1]) > > > > - the source property doesn't offer enough information to display > > information about the *types* of link relations > > > > [1] > <http://lists.w3.org/Archives/Public/w3c-dist-auth/2001OctDec/0119.html> > > If you drop the XLink stuff I support the "source-set" property > described in that message as a replacement for the source property; I > implemented it a while ago for mod_dav and cadaver and it very works > nicely. (I started off implementing {DAV:}source but it suffers greatly > because of the two issues given above) > > An alternative would be to retain the "source" property but drop the > redundant "src" element and replace it with a "description" element > giving a human-readable description of the link as the cdata content. Joe, I'm happy to have a different format (I've got enough flak promoting XLink-compatible syntax :-). My requirements are - must support multiple links - there must be a machine-readable description for the link type - the should be a human-readable description for the link type Please post what you're using right now -- we'll probably able to extend if necessary. Julian
Received on Monday, 13 May 2002 18:15:56 UTC