AD review issue #4: Supporting both VTODO and VEVENT in
thesame iCalendar stream (was: Re: [Ietf-calsify] Re: AD review
TimHare at comcast.net
Tue Jun 17 09:47:40 PDT 2008
As an "informed user" - i.e. not a developer, I definitely support
NON-silent rejection. I can agree with non-support of certain components
only if I receive some notification; due to work requirements I am now
journalling my time on some projects, and it would be good to know if I
can't import that data into another tool.
Interested Bystander, Non-Inc.
From: ietf-calsify-bounces at osafoundation.org
[mailto:ietf-calsify-bounces at osafoundation.org] On Behalf Of Cyrus Daboo
Sent: Monday, June 16, 2008 12:33 PM
To: Lisa Dusseault
Cc: ietf-calsify at osafoundation.org; Bernard Desruisseaux
Subject: Re: AD review issue #4: Supporting both VTODO and VEVENT in thesame
iCalendar stream (was: Re: [Ietf-calsify] Re: AD review on2445bis)
--On June 16, 2008 9:25:14 AM -0700 Lisa Dusseault <lisa at osafoundation.org>
>> The suggestion of an implementation note that describes the "common
>> use" of the components and explains that some may be supported and
>> others not is fine. In fact telling implementors that they need to be
>> prepared for another system to reject a component would be good.
> I can get behind that. I'd also like to recommend that systems not
> reject a component silently -- a user needs to know if they imported a
> iCalendar file and lost 50 VJOURNAL components in the process.
Note that iTIP does have a status code for "Unsupported Component" (3.13) -
so informing the originator of the iCalendar data that they are sending
something that is not supported by the recipient is covered by that.
Ietf-calsify mailing list
Ietf-calsify at osafoundation.org
More information about the Ietf-calsify