From: jamsden@us.ibm.com To: ietf-dav-versioning@w3.org Message-ID: <852568C0.00767213.00@d54mta03.raleigh.ibm.com> Date: Thu, 13 Apr 2000 17:33:43 -0400 Subject: Re: OPTIONS method We're working on it. The OPTIONS methods is the last thing we'll do because we have to know all the versioning semantics and protocol in order to know what the options are. |------------------------+------------------------> | | Ron Jacobs | | | <rjacobs@gforce.com> | | | (by way of "Ralph R. | | | Swick" <swick | | | Sent by: | | | ietf-dav-versioning-r| | | equest@w3.org | | | | | | 04/13/2000 03:02 PM | | | | |------------------------+------------------------> >------------------------| | | | To: | | ietf-dav-versioning@w| | 3.org | | cc: | | Subject: | | OPTIONS method | >------------------------| Date: Thu, 13 Apr 2000 13:26:32 -0400 (EDT) Message-ID: <4927C2E1CD80D311A2C500A0CC516497060F6F@MAIL> From: Ron Jacobs <rjacobs@gforce.com> To: ietf-dav-versioning@w3.org Shouldn't the DeltaV specification better specify capability discovery? I am suggesting the inclusion of a section along the lines of section 17 of draft-ieft-webdav-binding-protocol-01. I do not see anything in 04.2 that specifies the response to an OPTIONS request. Thanks, Ron