[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New Topic: Export of calendar data and metadata



<x-html>
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
pregen@egenconsulting.com wrote:
<blockquote TYPE=CITE>&nbsp;
<br><font face="sans-serif"><font size=-1>Maybe I'm missing something here,
but should it not be the responsibility of the client to ensure that there
is an export capability.&nbsp; It seems to me that all we need to declare
is that an import/export capability be in place.&nbsp; Maybe we say it
needs to be, at a minimum, ASCII format.&nbsp; But, I believe all we need
to state is the capability must be there and it is handled by the client
software.</font></font></blockquote>

<p><br>I'd like to make sure that we define what an "export" is, regardless
of which client you happen to use.&nbsp;&nbsp;&nbsp;&nbsp; CUA-1 exports
just the calendar data, but not the metadata.&nbsp; CUA-2 exports both.&nbsp;&n
bsp;&nbsp;
I've lost data if I'm using CUA-1
<p>I don't think this is a new function "EXPORT" or anything, though I'm
interested if others think that is the way to go.&nbsp; Personally, I suspect
it will be a paragraph explaining what it means to export/import a calendar,
and a list of queries.&nbsp; The queries will extract a single calendar
with both the calendar data as well as the metadata.&nbsp; If everyone
uses the same queries, then every product would produce identical export/import
files, which is a good thing.
<p>dmadeo
<p>PS: I'd hope that the servers which export data behind the scenes would
also use the same queries.</html>
</x-html>