W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > October to December 2003

RE: SEARCH by last path segment, Was: SEARCH for displayname

From: Lisa Dusseault <lisa@xythos.com>
Date: Tue, 18 Nov 2003 12:18:22 -0800
To: "'Julian Reschke'" <julian.reschke@gmx.de>
Cc: "'Wallmer, Martin'" <Martin.Wallmer@softwareag.com>, "'Kevin Wiggen'" <kwiggen@xythos.com>, <www-webdav-dasl@w3.org>
Message-ID: <01f901c3ae11$1d264430$75c990c6@lisalap>

> > property.  But it's no less feasible than other properties 
> which the 
> > server may calculate based on location/URL, possibly 
> > 'supported-live-property-set' or 'supported-method-set'.  
> E.g. I might 
> > not allow VERSION-CONTROL in some hierarchies of my server 
> and calculate 
> > whether to include it in 'supported-method-set' based on the 
> > first-path-segment.
> In which case I'd claim that your server is broken. It's the 
> *resource* 
> that is version controlled or not, not it's identifier. If 
> you think I'm 
> wrong, please raise this on the DeltaV mailing list.

Julian, please read my message.  I didn't say that the identifier
is resource controlled.  I only said that some property values, 
with the example of 'supported-method-set', may be calculated by 
the server based on the request-URI.  

My argument isn't based on an implementation working one way or
another, at any rate.  It's that if we say that properties have
nothing to do with URLs, then we cut ourselves off from a useful
set of features.  Not only the 'last-path-segment' property 
proposed, but others, such as 'parent-url'.  We could have a 
property listing 'other-bindings' (other than the requested 
binding) with this model.  Properties like 'is-default-document' 
might depend on whether the document's last path segment is
'default.html' or a similar value, again calculated by the
server based on the URL.  Properties like 'is-hidden' might
apply to bindings, not to the underlying resource.

I propose that we do not rule out properties that vary based
on URL, when these are useful and the simplest way to specify
a feature.  

You propose that we rule out properties based on URLs but that
will make some features harder to implement and specify.  I 
do not see sufficient reason for that.

Received on Tuesday, 18 November 2003 15:19:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:22:43 UTC