- From: Zivkov, Sasa <sasa.zivkov@sap.com>
- Date: Wed, 31 Jul 2002 18:49:44 +0200
- To: ietf-dav-versioning@w3.org
> -----Original Message----- > From: Reschke, Julian > Sent: Mittwoch, 31. Juli 2002 18:25 > To: Zivkov, Sasa; ietf-dav-versioning@w3.org > Subject: RE: expand-property report, exapnding > version-controlled-binding- set ? > > > > > > Hi, > > > > > > > > The rfc3253 says: > > > > > > > > Many property values are defined as a DAV:href, or a set > > of DAV:href > > > > elements. The DAV:expand-property report provides a mechanism for > > > > retrieving in one request the properties from the resources > > > > identified by those DAV:href elements. ... > > > > > > > > Since DAV:version-controlled-binding-set is list of > > > > (binding-name, version-history) > > > > elements and not list of hrefs it seems to me that it is not > > possible to > > > > further expand this property. For example the next request tries > > > > to expand > > > > version-controlled-binding-set: > > > > > > > > REPORT /foo.html HTTP/1.1 > > > > Host: www.webdav.org > > > > Content-Type: text/xml; charset="utf-8" > > > > Content-Length: xxxx > > > > > > > > <?xml version="1.0" encoding="utf-8" ?> > > > > <D:expand-property xmlns:D="DAV:"> > > > > <D:property name="version-controlled-binding-set"> > > > > <D:property name="version-history"> > > > > <D:property name="creator-displayname"/> > > > > </D:property> > > > > </D:property> > > > > </D:expand-property> > > > > > > > > But, since members of version-controlled-binding-set are not > > > > href's (and they > > > > are not resources) we can not further expand this property. > > > > > > > > Is this correct ? > > > > > > The embedded version-history element has the href-format, so > > you should be > > > able to do: > > > > > > <?xml version="1.0" encoding="utf-8" ?> > > > <D:expand-property xmlns:D="DAV:"> > > > <D:property name="version-controlled-binding-set"> > > > <D:property name="creator-displayname"/> > > > </D:property> > > > </D:expand-property> > > > > > > (if what you're after is the DAV:creator-displayname of the version > > > history). > > > > version-controlled-binding-set members are version-controlled-binding's > > and version-controlled-binding is even not a resource so we can not > > ask it for its properties (creator-displayname is this case). > > As you said, version-controlled-bindings consists of binding-name > version-history. version-history has href format, so you *can* expand that > if you want to. An example: <version-controlled-binding-set> <version-controlled-binding> <binding-name>abc</binding-name> <version-history><href>/vh11</href></version-history> </version-controlled-binding> <version-controlled-binding> <binding-name>def</binding-name> <version-history><href>/vh12</href></version-history> </version-controlled-binding> ... </version-controlled-binding-set> So the version-history is at the second level after version-controlled-binding-set. And the members of version-controlled-binding-set are not DAV:href's but elements that contain href's. Again from rfc3253: Many property values are defined as a DAV:href, or a set of DAV:href elements. The DAV:expand-property report provides a mechanism for retrieving in one request the properties from the resources identified by those DAV:href elements. ... > > > Which part of the rfc3253 says that we should use version-history part > > of a version-controlled-binding element for property expansion ? > > None. It depends on whose property you want. You can't get the properties of > the binding name (it's not a resource), but you *can* get the properties of > the version history. > > > What if version-controlled-binding element (or any other) would have > > two href members, which one should be used for expand-property report ? > > Both.
Received on Wednesday, 31 July 2002 12:50:21 UTC