Yes. This is an implementation detail which doesn't need to be in CAP.
Ah, hah!So, by ARCHIVE/RESTORE you mean the server operation to put/get of the calendar store to a server-side storage device.
By IMPORT/EXPORT, you mean the act of asking the CS for a stream of iCalendar data representing the current state of the calendar store or pushing to the CS a stream of iCalendar data representing the current state of the calendar store?Yes. Except to mention that I may want to import calendars from a command line CUA, as well as a GUI or PDA.
The term "IMPORT/EXPORT" is confusing, then. It implies the common vernacular which would be a CUA file function.Ideally, when I do "File->Export", the CUA will do a "EXTRACT" (as you call it), and then save the results on the local machine somewhere. So while I see the distinction, I'm not sure it's important.
We want a EXTRACT/INSERT type of capability, then?I'm not too worried about what it's called. EXTRACT is fine with me.
dmadeo
begin:vcard n:Madeo;David tel;fax:212-762-1009 tel;work:212-762-2348 x-mozilla-html:FALSE url:www.ms.com org:Morgan Stanley Dean Witter and Discover;Information Technology version:2.1 email;internet:dmadeo@ms.com adr;quoted-printable:;;750 Seventh Ave=0D=0A;NY;NY;10019;USA x-mozilla-cpt:;0 fn:David Madeo end:vcard