W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2002


From: Elias Sinderson <elias@cse.ucsc.edu>
Date: Mon, 13 May 2002 15:59:29 -0700
Message-ID: <3CE04551.1F79D581@cse.ucsc.edu>
To: "Webdav WG (E-mail)" <w3c-dist-auth@w3c.org>
I should think that what you have is machine readable as well, or am I missing
some critical bit here? If the specification says to provide a
RFC XXXX compliant URI for the source link, as below, I will bet that my machine
(read client software) can read it with little extra effort.


Joe Orton wrote:

> I just dropped the xlink: from the href attribute, and got rid of the
> xlink:role attribute entirely, giving e.g.:
> <D:prop>
>  <D:source-set>
>   <D:source href="http://example.com/dav/source.xml">Source</D:source>
>   <D:source href="http://example.com/dav/render.xsl">Stylesheet</D:source>
>   <D:source href="http://example.com/dav/etc.etc"/>
>  </D:source-set>
> </D:prop>
> which should satisfy your first and third requirements; I'm not sure
> about "machine-readable" link descriptions being mandatory. My client
> doesn't need to understand anything about the link, I just want it to be
> able to display a menu of "URI: description" choices when there is >1
> source available, so that the user can decide.
> (Similarly, the minimum amount of server configuration I'd like to
> require is saying e.g. "/dav/render.xsl is a source of /dav/*.xml")
> Regards,
> joe
Received on Monday, 13 May 2002 18:59:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:25 UTC