From: jamsden@us.ibm.com To: ietf-dav-versioning@w3.org Message-ID: <8525689F.005ED606.00@d54mta03.raleigh.ibm.com> Date: Sat, 11 Mar 2000 12:15:44 -0500 Subject: Adeliade IETF Meeting and Delta-V Yes, the working group has one 2 1/2 hour sessions scheduled. However, I will be there Tuesday through Thursday and plan to have Delta-V design team meetings Wedensday and Thursday. These are not scheduled by IETF as there are no meeting rooms available. Any member of the working group is welcome to join. I'll have get a meeting location when I get there and post it on the bulletin board. Hope to see you all there! |------------------------+------------------------> | | "Eric Sedlar" | | | <esedlar@us.oracle.co| | | m> | | | | | | 03/10/2000 06:48 PM | | | | |------------------------+------------------------> >------------------------| | | | To: | | Jim | | Amsden/Raleigh/IBM@IB| | MUS | | cc: | | Subject: | | Re: Defaults | >------------------------| All I saw was one 2 1/2 hour meeting on Wednesday, March 29th. Is it really the case that we'll go all the way to Australia and only talk about DeltaV for less than half a day? Are we going to talk informally at other times? --Eric ----- Original Message ----- From: <jamsden@us.ibm.com> To: Eric Sedlar <esedlar@us.oracle.com> Sent: Friday, March 10, 2000 12:33 PM Subject: Re: Defaults It's on. See http://www.ietf.org for details in case the schedule changes. Search for delta in the agenda. |------------------------+------------------------> | | "Eric Sedlar" | | | <esedlar@us.oracle.co| | | m> | | | | | | 03/10/2000 01:05 PM | | | | |------------------------+------------------------> >------------------------| | | | To: | | Jim | | Amsden/Raleigh/IBM@IB| | MUS | | cc: | | Subject: | | Re: Defaults | >------------------------| I guess the WebDAV meeting at Adelaide is on? Do you have any agenda & schedule information? Thanks, Eric ----- Original Message ----- From: <jamsden@us.ibm.com> To: <ietf-dav-versioning@w3.org> Sent: Thursday, March 09, 2000 1:13 PM Subject: Re: Defaults I think we need to simplify revision selection, the interaction with workspaces, and default selection. I have started writing up a proposal and will try to finish it soon. I'll have lots of time on the plan to Adelaide to do WebDAV stuff. Hope to see you all there! Note that I'm going to do Working group work while I'm there. So if you don't want me to resolve all the issues myself, you better show up! :-) |------------------------+------------------------> | | Tim Ellison/OTT/OTI | | | <Tim_Ellison@oti.com>| | | Sent by: | | | ietf-dav-versioning-r| | | equest@w3.org | | | | | | 03/09/2000 12:08 PM | | | | |------------------------+------------------------> >------------------------| | | | To: | | ietf-dav-versioning@w| | 3.org | | cc: | | Subject: | | Defaults | >------------------------| When is request is received that does not specify the Workspace: and/or Revision-Selector:, the revision selection seems quite complicated. Here's my interpretation (refs from 03.1 protocol doc): (1) (a) For each versioned collection being resolved, first use the collection's default workspace to pick a revision/working collection (ref. 10.1.1). (b) If there is no default workspace specified for the collection, choose the default revision (ref. 8.1). (c) If there is no default revision specified use the 'server determined default workspace' (ref. 9.1). (d) If there is still no revision selected then the reference is not found. (2) For the final resource being resolved, first consider the Revision-Selector in preference to anything else (ref. 7.2 & 3.3.3). If there is no Revision-Selector then use the resolution strategy of step (1) Section 3.3.3 says that the default-revision shoul donly be used if "no Workspace: or Revision-Selector: header is specified" -- I don't see how that fits in :-( Sounds a bit complicated doesn't it? Why do we want default workspaces for each collection, and default revisions for each resource? Comments. Tim