Message-ID: <65B141FB11CCD211825700A0C9D609BC01D4D84F@chef.lex.rational.com> From: "Clemm, Geoff" <gclemm@Rational.Com> To: "DeltaV (E-mail)" <ietf-dav-versioning@w3.org> Date: Mon, 24 Apr 2000 18:20:43 -0400 Subject: RE: Versioning TeleConf Agenda, 4/24/00 (Monday) *1-2pm*EST We first discussed the DAV:body proposal, and David's Fetch/Save proposal in general. Jim Whitehead posted the results of this discussion under the header of "RE: Collection Fetch/Save proposal". In summary, my appreviated form of David's proposal (i.e. DAV:body) was deemed too limited in scope (since it only provided for XML with no DTD preamble), while a more comprehensive proposal (i.e. with mime multi-part marshalling) was deemed useful, but probably fairly complicated in the details. The consensus was that this was more appropriately handled independently from the versioning protocol, since it is not versioning specific, and is not required for versioning. We then discussed allowing an activity or a workspace as a URL, to mean that all working resources associated with that activity or workspace should be checked in atomically. It was pointed out that this is likely to be misleading (i.e. it would seem more natural for this to "create a new version of the activity/workspace", and furthermore, that atomic checkin of multiple working resources is currently not widely supported anyway. These are the last two issues appearing in the issues list I am maintaining in the protocol document. If anyone has any issues that they feel need to be discussed before final call, now would be a good time to send them to the mailing list! I am almost done with the revised "advanced versioning semantics" section, and hope to get that mailed out tomorrow. Cheers, Geoff -----Original Message----- From: Clemm, Geoff [mailto:gclemm@Rational.Com] Sent: Thursday, April 20, 2000 4:58 PM To: DeltaV (E-mail) Subject: Versioning TeleConf Agenda, 4/24/00 (Monday) *1-2pm*EST Note the time change. This is change is just for this week, and we'll be back to 2-3pm next week. phone: 888 819 8909 pass-code#97985 Agenda: - Should we support a DAV:body property? This would support David Goodenough's "batch fetch/update" scenario, i.e. fetching or updating the bodies of several resources in one request. - Should we allow an activity or a workspace as the request-URL to a CHECKIN request? This would checkin all working resources associated with that activity or workspace. Note: These are the last two issues on my issues list. If anyone has another issue, please let me know. Cheers, Geoff