Re: bind draft issues

Am Freitag, 07.03.03, um 10:45 Uhr (Europe/Berlin) schrieb Julian 
Reschke:

>> From: w3c-dist-auth-request@w3.org
>> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Stefan Eissing
>> Sent: Friday, March 07, 2003 10:34 AM
>> To: Julian Reschke
>> Cc: Clemm, Geoff; WebDAV
>> Subject: Re: bind draft issues
>>
>> ...
>>
>>>> Hmm, I think I know what you mean, however there are cases
>>>> where you might want this to break:
>>>>
>>>> 1) variants. /news/english/ and /news/german/ might be the same
>>>>    resource with different content based on the "access" URL. All
>>>>    get* properties will probably vary. (They can already vary on
>>>>    a resource with a single binding)
>>>
>>> That would mean that entities may vary based on the request URI. Is
>>> this the
>>> case?
>>
>> I thought that's what I wrote.
>
> OK, I rephrase it: that would mean that a resource is *allowed* to vary
> based on the request URL. I don't think we all agree on that.

Uhh, it can vary based on "Accept-Language" request header. Why should
it not vary on the request URI of the GET?

[...]
>>>> What exactly is it, you want to prevent to happen?
>>>
>>> People falling into the trap of believing in "URL properties", I 
>>> guess.
>>
>> Probably a good guess of Geoff's intentions. Why not give a guess
>> what an "URL property" exactly is? That would be most welcome.
>
> Our (Geoff's any my) understanding is that there *are* no URL 
> properties. A
> URL property would be something that varies with the request URL 
> (under the
> relaxed "sameness" definition stated above).

So: properties can vary based on HTTP request headers, but not based on
the HTTP request URI? Or do you think they should not vary based on
HTTP request headers either? Or that only the get* properties are 
allowed
to do that?

//Stefan

Received on Friday, 7 March 2003 05:01:11 UTC