- From: Werner Donné <werner.donne@re.be>
- Date: Mon, 29 May 2006 18:10:41 +0200
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: ietf-dav-versioning@w3.org
An activity has no contents, so the HTTP headers wouldn't apply and hence the corresponding properties have no meaning either. Werner. Julian Reschke wrote: > Werner Donné schrieb: >> Hi, >> >> Section A.13 of RFC 3253 says that an activity supports all DeltaV- >> compliant properties, which include the DAV properties. What would >> be the meaning, for an activity, of the properties getcontentlanguage >> and getcontenttype? Section 3.1.4 seems to allow to leave them out >> of the supported-live-property-set if they have no semantics for an >> activity, but shouldn't the semantics be explained for the common >> live properties if there are any? > > Well, the semantics are the ones defined in RFC2518. That is, if an > activity responds to a GET request, then those properties should behave > just as the HTTP response headers Content-Language and Content-Type. > > What am I missing? > > Best regards, Julian > > -- Werner Donné -- Re Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: werner.donne@re.be
Received on Monday, 29 May 2006 16:09:42 UTC