Lisa Dusseault wrote: > A new property with the value of the last path segment is useful in more > than just WHERE and SELECT. It's also useful in ORDERBY and in some > REPORT types, and in general PROPFIND results. If the server is capable > of using this information in the proposed exclude/include syntax, then > it should be equally capable of using the information in a property syntax. > > I've heard the argument that this isn't a "real" resource property in > that different URLs to the same resource have different values for this > 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. Regards, Julian -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760Received on Tuesday, 18 November 2003 14:20:07 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:10 GMT