Re: [calsify] draft-ietf-calext-extensions-00
Cyrus Daboo <cyrus@daboo.name> Tue, 07 April 2015 18:50 UTC
Return-Path: <cyrus@daboo.name>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D54F61B3A99 for <calsify@ietfa.amsl.com>; Tue, 7 Apr 2015 11:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WqkzKtaURVR5 for <calsify@ietfa.amsl.com>; Tue, 7 Apr 2015 11:50:14 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8C911B3A94 for <calsify@ietf.org>; Tue, 7 Apr 2015 11:50:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 3C349106EEDE; Tue, 7 Apr 2015 14:50:13 -0400 (EDT)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aGKzSbO5xxcY; Tue, 7 Apr 2015 14:50:12 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 169FF106EED2; Tue, 7 Apr 2015 14:50:11 -0400 (EDT)
Date: Tue, 07 Apr 2015 14:50:08 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Ken Murchison <murch@andrew.cmu.edu>, Calsify <calsify@ietf.org>
Message-ID: <B46B5107484E2F99C494F2D8@caldav.corp.apple.com>
In-Reply-To: <5524223E.1050607@andrew.cmu.edu>
References: <5524223E.1050607@andrew.cmu.edu>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="1087"
Archived-At: <http://mailarchive.ietf.org/arch/msg/calsify/wdmyaZnYQP0GrolvrB6FsHZZ7RQ>
Subject: Re: [calsify] draft-ietf-calext-extensions-00
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 18:50:26 -0000
Hi Ken, --On April 7, 2015 at 2:30:22 PM -0400 Ken Murchison <murch@andrew.cmu.edu> wrote: > This all looks pretty straightforward to me and I will add/update support > for these properties and parameters to libical once we come to consensus > on the draft. > > However, I am somewhat unclear on the distinction between URL and SOURCE. As per 5545, URL is meant to be a pointer to an alternative representation ("more dynamic rendition") of the event - e.g., it could be a web page with details of the event. SOURCE, on the other hand, is meant to be a pointer to the original location where the iCalendar data itself was retrieved from. I could add the following sentence to the SOURCE property description to help clarify the differences: Note that the URL property (Section 3.8.4.6 of [RFC5545]) defines a URL for an alternative representation of the calendar information (which could take the form of a web page, or an image, etc), whereas the SOURCE property is used to refer to the location where updated iCalendar data can be found. -- Cyrus Daboo
- [calsify] draft-ietf-calext-extensions-00 Ken Murchison
- Re: [calsify] draft-ietf-calext-extensions-00 Cyrus Daboo
- Re: [calsify] draft-ietf-calext-extensions-00 Ken Murchison