- From: Clemm, Geoff <gclemm@rational.com>
- Date: 2002年5月27日 20:43:56 -0400
- To: "Webdav WG (E-mail)" <w3c-dist-auth@w3c.org>
- Message-ID: <3906C56A7BD1F54593344C05BD1374B106EEC1DD@SUS-MA1IT01>
I agree with the addition of the DAV:sourcelabel element. But I object to the use of the xlink:href attribute, instead of the standard WebDAV DAV:href element. I believe it is significantly more important to maintain consistency within the WebDAV standard than it is to be consistent with some non-WebDAV standard such as xlink. In particular, this breaks functionality such as is provided by the DAV:expand-property report defined in RFC-3253, which is based on the existence of DAV:href nodes in property values. Cheers, Geoff -----Original Message----- From: Jason Crawford [mailto:ccjason@us.ibm.com] Sent: Monday, May 27, 2002 11:32 AM To: Julian Reschke Cc: Jim Whitehead; Roy T. Fielding; Webdav WG (E-mail); w3c-dist-auth-request@w3.org Subject: RE: Issue: SOURCE_PROPERTY_UNDERSPECIFIED It sounds like we're converging on a proposal that looks much like Julian's at the bottom of the following posting... http://lists.w3.org/Archives/Public/w3c-dist-auth/2001OctDec/0119.html I have one other proposal to make. It's based on the above proposal, but adjusts it a bit so that we have room to add other structured data to the source tag later if we want. It just creates a tag (sourcelabel) to envelop the optional? natural language description of the source. <D:prop xmlns:D="DAV:" xmlns:F="http://www.foocorp.com/Project/"> <D:source-set> <D:source xlink:href="http://foo.bar/src/main.c" xlink:role="UriDescribingTheRole"> <D:sourcelabel xml:lang="en">source file</D:sourcelabel> </D:source> <D:source xlink:href="http://foo.bar/src/main.lib" xlink:role="UriDescribingTheRole"> <D:sourcelabel xml:lang="en">library file</D:sourcelabel> </D:source> <D:source xlink:href="http://foo.bar/src/makefile" xlink:role="UriDescribingTheRole"> <D:sourcelabel xml:lang="en">makefile</D:sourcelabel> </D:source> </D:source-set> </D:prop> Also please comment on how you'd express the situation where a single source URL has multiple roles. Thanks :-) J ------------------------------------------ Phone: 914-784-7569, ccjason@us.ibm.com
Received on Monday, 27 May 2002 20:44:39 UTC