On Feb 10, 2006, at 5:28 PM, Phillip J. Eby wrote:
At 03:01 PM 2/10/2006 -0800, Katie Capps Parlante wrote:
(3) In the 0.7 timeframe, we're going to have midpoints (maybe
these are the same as milestones, full proposal coming) that the
user can download and use. This implies that we need to support a
path for users to migrate data from 0.6.1 --> 0.7m1, from 0.7m1 --
> 0.7m2, etc.
And will .ics be a sufficiently high-fidelity format for these
transfers?
Well, iCalendar can be sufficiently high-fidelity, it's fully
extensible. You could put the whole repository in that format though
I can't imagine why we'd want to export anything but calendar and
task data to that format. The reason we used iCalendar for
migrating at all was because we already had the ability to export and
import iCalendar and we scoped migrating requirements down to only
calendar items. I don't think there was much of an idea that we'd
extend the use of iCalendar as a migration tool beyond calendar items
and task items.
Perhaps I misunderstood the question..
Lisa
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
