AD review issue #4: Supporting both VTODO and VEVENT in thesame iCalendar stream (was: Re: [Ietf-calsify] Re: AD review on2445bis)

[Tim Hare]

No disagreement from me. 


Tim Hare
Interested Bystander, Non-Inc.

-----Original Message-----
From: Eliot Lear [mailto:lear at cisco.com] 
Sent: Saturday, June 28, 2008 10:19 AM
To: Tim Hare
Cc: 'Cyrus Daboo'; 'Lisa Dusseault'; 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)

I believe we have consensus as to Lisa's suggestion.  Any disagreement?

Eliot

Tim Hare wrote:
> 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.
>
>
> Tim Hare
> Interested Bystander, Non-Inc.
>
> -----Original Message-----
> 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)
>
> Hi Lisa,
>
> --On June 16, 2008 9:25:14 AM -0700 Lisa 
> Dusseault<lisa at osafoundation.org>
> wrote:
>
>    
>>> 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.
>>      
>
> Agreed.
>
> 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.
>
> --
> Cyrus Daboo
>
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>
>
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>
>