W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2004

Re: Properties of bindings (was Re: Issues remaining with Bind draft)

From: Jason Crawford <ccjason@us.ibm.com>
Date: Tue, 30 Mar 2004 02:32:07 -0500
To: nnw3c-dist-auth___at___w3.org@smallcue.com
Cc:
Message-ID: <OF1B9D44F3.05BCF603-ON85256E67.0028D48A-85256E67.002963C3@us.ibm.com>
> > Although I'm not sure if hidden is a good example, I don't have a
> > problem with some hypothetical property returning a different value
> > depending on which URL you use to reference it.  In fact I wouldn't be
> > surprised if we eventually intentionally define a property that does
> > vary by URL.  But we should be clear right now that all properties 
that
> > are resource based (which is basically everything at the time of the
> > writing) should not vary by URL and that future properties should not
> > vary by URL without a documented reason.
> 
> Well, I think that properties SHOULD NOT vary on request URI (nor should
> the content), as this is clearly against the goals of the BIND spec.
I agree.  "SHOULD NOT" seems more than lenient enough.


> RFC2518 says that PROPFIND returns the resource's properties, and BIND
> speaks about having multiple URIs for the same resource. I think this is
> clear enough...

Agreed.
Received on Tuesday, 30 March 2004 02:37:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:17:51 UTC