RE: Issue: SOURCE_PROPERTY_UNDERSPECIFIED

The point is that is should be possible for the client to display the *type*
of the link without having to look at the human-readable description. It's
fine if this is optional. IMHO it's not ok if there's no standard way to do
this.

> -----Original Message-----
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Elias Sinderson
> Sent: Tuesday, May 14, 2002 12:59 AM
> To: Webdav WG (E-mail)
> Subject: Re: Issue: SOURCE_PROPERTY_UNDERSPECIFIED
>
>
> 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.
>
> Elias
>
>
> 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 19:08:36 UTC