- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 14 May 2002 02:31:15 +0200
- To: "Jim Whitehead" <ejw@cse.ucsc.edu>, "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 Jim Whitehead > Sent: Tuesday, May 14, 2002 1:56 AM > To: Webdav WG (E-mail) > Subject: RE: Issue: SOURCE_PROPERTY_UNDERSPECIFIED > > > > Joe Orton writes: > > 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> > > > > I like this, except for the "Source" and "Stylesheet" not being individual > elements or attributes. The i18n characteristics of the approach above are Why is that a problem? > not great -- I can just see a Kanji UI popping up a pick list of English > words, ugh. What was the perceived problem with using the xlink:role I think Joe's example is just missing the statement that the human-readable text needs to be qualified with xml:lang *somewhere* in scope. > attribute (and Xlink syntax in general?) That I'd like to know as well.
Received on Monday, 13 May 2002 20:31:27 UTC