- From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
- Date: Fri, 21 Jan 2000 13:57:52 -0500
- To: w3c-dist-auth@w3.org
I vote for choice 2, since choice 1 is so egregiously bad. Cheers, Geoff From: Jim Whitehead <ejw@ics.uci.edu> Date: Fri, 21 Jan 2000 09:49:46 -0800 Content-Length: 708 Jason writes: > Note: in the presence of multiple bindings, if the server initializes it > to the URI and treats it as a dead property, that URI might be different > from the URI from which it was accessed. Hmm, since properties are part of the state of the resource, in the presence of bindings it is more than possible for there to be multiple URI names for the same "display name". This removes the value of the displayname property. Some solutions: 1) move displayname to the collection, and have the collection maintain displayname/binding pairs (this solution seems icky to me) 2) deprecate displayname, and only use URIs for display to the user, and concentrate on i18n support for URIs. - Jim
Received on Friday, 21 January 2000 13:58:05 UTC