Re: [caldav] various question on scheduling draft

"Tim Hare" <TimHare@comcast.net> Thu, 15 October 2009 15:27 UTC

Return-Path: <timhare@comcast.net>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE94328C104 for <caldav@core3.amsl.com>; Thu, 15 Oct 2009 08:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wpuxdu2WY++e for <caldav@core3.amsl.com>; Thu, 15 Oct 2009 08:27:29 -0700 (PDT)
Received: from QMTA06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by core3.amsl.com (Postfix) with ESMTP id C82D628C0F1 for <caldav@ietf.org>; Thu, 15 Oct 2009 08:27:28 -0700 (PDT)
Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA06.westchester.pa.mail.comcast.net with comcast id t2L51c0010ldTLk563ST34; Thu, 15 Oct 2009 15:26:27 +0000
Received: from THARE ([71.203.105.66]) by OMTA04.westchester.pa.mail.comcast.net with comcast id t3TL1c0081RyUCv3Q3TMpL; Thu, 15 Oct 2009 15:27:21 +0000
From: Tim Hare <TimHare@comcast.net>
To: 'Bernard Desruisseaux' <bernard.desruisseaux@oracle.com>, 'Arnaud Quillaud' <Arnaud.Quillaud@Sun.COM>
References: <4AC23DBD.6020206@sun.com> <4AD737D5.7040300@oracle.com>
In-Reply-To: <4AD737D5.7040300@oracle.com>
Date: Thu, 15 Oct 2009 11:27:13 -0400
Message-ID: <002901ca4dab$f9ba6850$ed2f38f0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcpNp430WjwVLX9ETiW3qhVJU0jgFAAA48Ew
Content-Language: en-us
Cc: caldav@ietf.org
Subject: Re: [caldav] various question on scheduling draft
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2009 15:27:29 -0000

In RFC 5445 for PRODID

"   Purpose:  This property specifies the identifier for the product that
      created the iCalendar object."

While it doesn't say this is REQUIRED or 'MUST specify' I believe that is
the intent.  The language could perhaps specify that requirement in the
future, with some standardized form for 'hand-edited' items.  For interop
troubleshooting issues it is critical that we know what created the
particular object we're looking at.

Tim Hare
Interested Bystander, Non-Inc.

>> * implementation question:
>> This is a rather philosophical one: the server is now altering 
>> calendar resources as much as the client (even on a simple create, 
>> just to update the SCHEDULE-STATUS). Should we preserve the PRODID of 
>> the client although the server altered the content, possibly in some 
>> drastic way ?
>CalDAV doesn't impose additional requirements on the PRODID property. As 
>such, refer to RFC5545 for PRODID requirements.  In my opinion, PRODID 
>should be set to the application that generated the iCalendar 
>representation. If the server always (re)generate the iCalendar 
>representation then it should specify its own PROPID.
>
>Thanks a lot for your feedback!
>
>Cheers,
>Bernard