[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New Topic: Export of calendar data and metadata
<x-html>
<br><font size=2 face="sans-serif">Maybe I'm missing something here, but should
it not be the responsibility of the client to ensure that there is an export c
apability. It seems to me that all we need to declare is that an import/e
xport capability be in place. Maybe we say it needs to be, at a minimum,
ASCII format. But, I believe all we need to state is the capability must
be there and it is handled by the client software.</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Doug Royer <Doug.Royer@software.com>
;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ietf-calendar@imc.org</font>
<p><font size=1 face="sans-serif">10/19/99 07:31 PM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:  
; CalSched IETF <ietf-calendar@imc.org></font>
<br><font size=1 face="sans-serif"> cc:  
; CalSched IETF <ietf-calendar@imc.org></font>
<br><font size=1 face="sans-serif"> Subject:
Re: New Topic: Export of calendar data and metadata</font><
/table>
<br>
<br><font size=2><tt><br>
<br>
David Madeo wrote:<br>
<br>
> ...<br>
> While I can certainly appreciate the complexity of a real moveuser tool, I
'd<br>
> like to see an agreement on at least the details of an export and import o
f<br>
> a Calendar. I just skimmed the CAP document quickly to look for refe
rences<br>
> on how to extract not only components, but the calendar properties and the
<br>
> VCAR's. While it certainly looks like you can do it, I'd appreciate
a<br>
> paragraph explicity explaining what we expect.<br>
> <br>
> Comments?<br>
<br>
Great issue. I have added it as 'W-29 import/export".<br>
<br>
I agree with you, it will be needed. Also for calendar synchronization<br>
with disconnected devices. There will need to be a way for a intermediate<br>
tool to pull calendars from 2 or more sources, compare, and perhaps<br>
with a users input - merge. The tool it self is not in scope, but<br>
I think it will be a need that we must address (in addition to<br>
import/export). And I think that import/export will also address<br>
the issue.<br>
<br>
I do however remember discussions (I forget the results) where this<br>
was discussed and some problems with supporting synchronization were<br>
deemed out of scope. Just supporting import/export may solve the<br>
issue and address the both needs.<br>
<br>
-Doug</tt></font>
<br>
<br></x-html>