Re: CAP-12-e: TRANSP and -NOCONFLICT changes
Doug Royer <[email protected]> Wed, 02 Jun 2004 22:53:22 -0600
| Newsgroups | gmane.ietf.calendar |
|---|---|
| Message-ID | <[email protected]> |
Still irrelevant as even without CAP you have the same problem. CU's currently want to mark time around exiting objects. And with CAP the solution is 100% solvable with exiting objects - BUSY time. And some CUA' s already allow that from the UI. You seem to be asking for a new smart NO-CONFLICT object or command. The fact that CAP allows a CS to force a no-conflict feature upon a CUA for BOOKed objects is new to CAP. The problem is not new to CU's. Currently they solved the problem simply by marking all time as busy - and you still can. You can mark the entire week as busy and not have ANY no-conflict objects in your calendar. With CAP no-conflict means you can not BOOK an object. It does not mean that a REQUEST or other METHOD's can not be in the calendar. And existing CUA's will not have a clue what to do with NOCONFLICT anyway. So the solution needs to exist for iCal objects, not just CAP. And FYI I voted for the ALLOW-CONFLICT property to be used in objects and not extend the TRANSP property. -- Doug Royer | http://INET-Consulting.com -------------------------------|----------------------------- [email protected] | Office: (208)520-4044 http://Royer.com/People/Doug | Fax: (866)594-8574 | Cell: (208)520-4044 We Do Standards - You Need Standards
smime.p7s
(application/x-pkcs7-signature, 4.6 KB) - not displayed