RE: Replacing the Label header with a DAV:labeled-version report
"Julian Reschke" <[email protected]>
| Newsgroups | gmane.ietf.deltav |
|---|---|
| Message-ID | <[email protected]> |
> From: [email protected] > [mailto:[email protected]]On Behalf Of Clemm, Geoff > Sent: Saturday, June 29, 2002 12:23 AM > To: 'Deltav WG' > Subject: RE: Replacing the Label header with a DAV:labeled-version > report > > > > Julian didn't like the marshalling of this report, > because it makes it look like the properties are those of > the VCR, when they actually are properties of the version > (Basically, I was just being lazy and re-using the D:response > element in a bogus fashion). Yes, that's the problem, and I fear the new format doesn't address this. If the multistatus/response format is re-used for a REPORT (basically a good thing), it must not break the existing semantics, in particular: - the properties reported must actually be the properties of the resource identified by the reported URI (DAV:href) and - the properties reported actually must be properties (!). If this is not the case, the response seems to indicate that there's a DAV:labeled-version-report property, which isn't the case. So how about properly extending the response element, for instance: <?xml version="1.0" encoding="utf-8" ?> <D:multistatus xmlns:D="DAV:"> <D:response> <D:href>http://www.webdav.org/folder/</D:href> <D:labeled-version-report> <D:href>http://repo.webdav.org/his/23/ver/V5</D:href> <D:propstat> <D:prop> <D:version-name>V5</D:version-name> </D:prop> <D:status>HTTP/1.1 200 OK</D:status> </Dpropstat> </D:labeled-version-report> <D:status>HTTP/1.1 200 OK</D:status> </D:response> <D:response> <D:href>http://www.webdav.org/folder/foo.html</D:href> <D:labeled-version-report> <D:href>http://repo.webdav.org/his/84/ver/V8</D:href> <D:propstat> <D:prop> <D:version-name>V8</D:version-name> </D:prop> <D:status>HTTP/1.1 200 OK</D:status> </D:propstat> </D:labeled-version-report> <D:status>HTTP/1.1 200 OK</D:status> </D:response> </D:multistatus>