From: Jim Whitehead <ejw@ics.uci.edu> To: Versioning <ietf-dav-versioning@w3.org> Date: Thu, 1 Apr 1999 17:03:31 -0800 Message-ID: <004701be7ca4$a027db80$d115c380@ics.uci.edu> Subject: Re: Version issues -----Original Message----- From: jamsden@us.ibm.com [mailto:jamsden@us.ibm.com] Sent: Thursday, March 11, 1999 1:56 PM To: jamsden@us.ibm.com; gclemm@atria.com; ejw@ics.uci.edu; dgd@cs.bu.edu; Cragun.Bruce@gw.novell.com; sridhar.iyengar@mv.unisys.com; ckaler@microsoft.com; bradley_sergeant@intersolv.com; ABabich@filenet.com Subject: RE: Version issues We should certainly discuss levels while designing the semantics of WebDAV versioning. However, this cannot be done without a better understanding of where we are headed. It is clear to me we are attempting to subset something that is not fully understood. I suggest we have reached a point where the leveling discussion is not helping any of our causes and we need a more complete strawman to act as a basis for leveling. This will take some iteration, and that's fine. I think we already know enough about leveling requirements that this strawman won't be too far out. So let's focus on getting a more complete understanding of the versioning model we have at the moment. We need to discover missing, unnecessary, or inconsistent semantics. Once we all give this a nod, we can tackle the leveling issue which may result in changing these semantics. I propose we defer leveling for at least the IETF 44 meeting so we can make some progress evaluating the full semantics. Next meeting can be devoted to leveling if appropriate.