From calsify-bounces@ietf.org Fri Jul 9 08:27:52 2010 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 55D943A6832; Fri, 9 Jul 2010 08:27:52 -0700 (PDT) X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 941013A697D for ; Fri, 9 Jul 2010 08:27:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 RlYD-tSsLkgo for ; Fri, 9 Jul 2010 08:27:50 -0700 (PDT) Received: from smtp8.server.rpi.edu (smtp8.server.rpi.edu [128.113.2.228]) by core3.amsl.com (Postfix) with ESMTP id B02323A6832 for ; Fri, 9 Jul 2010 08:27:47 -0700 (PDT) Received: from [128.113.124.94] (decapod-09.dynamic.rpi.edu [128.113.124.94]) (authenticated bits=0) by smtp8.server.rpi.edu (8.13.1/8.13.1) with ESMTP id o69FRoDC013373 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 9 Jul 2010 11:27:51 -0400 Message-ID: <4C373FF6.30407@rpi.edu> Date: Fri, 09 Jul 2010 11:27:50 -0400 From: Mike Douglass User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Lightning/1.0b2pre Thunderbird/3.0.4 MIME-Version: 1.0 To: calsify@ietf.org X-RPI-SA-Score: undef - SENDER Whitelisted (douglm@rpi.edu: Mail from user authenticated via SMTP AUTH allowed always) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.228 Subject: [calsify] Fwd: New Version Notification for draft-douglass-link-extension-00 X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0699532886==" Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org This is a multi-part message in MIME format. --===============0699532886== Content-Type: multipart/alternative; boundary="------------000102020702010509070900" This is a multi-part message in MIME format. --------------000102020702010509070900 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Last week I submitted the first draft of a proposed extension to iCalendar - a LINK property, closely aligned to the proposed link header - http://tools.ietf.org/html/draft-nottingham-http-link-header-10 -------- Original Message -------- Subject: New Version Notification for draft-douglass-link-extension-00 Date: Wed, 30 Jun 2010 12:51:48 -0700 (PDT) From: IETF I-D Submission Tool To: douglm@rpi.edu A new version of I-D, draft-douglass-link-extension-00.txt has been successfully submitted by Mike Douglass and posted to the IETF repository. Filename: draft-douglass-link-extension Revision: 00 Title: Link Extension to Icalendar Creation_date: 2010-06-30 WG ID: Independent Submission Number_of_pages: 10 Abstract: This specification introduces a new iCalendar property LINK to provide ancillary information for iCalendar components. The IETF Secretariat. --------------000102020702010509070900 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit Last week I submitted the first draft of a proposed extension to iCalendar - a LINK property, closely aligned to the proposed link header -

http://tools.ietf.org/html/draft-nottingham-http-link-header-10




-------- Original Message --------
Subject: New Version Notification for draft-douglass-link-extension-00
Date: Wed, 30 Jun 2010 12:51:48 -0700 (PDT)
From: IETF I-D Submission Tool <idsubmission@ietf.org>
To: douglm@rpi.edu 


A new version of I-D, draft-douglass-link-extension-00.txt has been successfully submitted by Mike Douglass and posted to the IETF repository.

Filename:	 draft-douglass-link-extension
Revision:	 00
Title:		 Link Extension to Icalendar
Creation_date:	 2010-06-30
WG ID:		 Independent Submission
Number_of_pages: 10

Abstract:
This specification introduces a new iCalendar property LINK to
provide ancillary information for iCalendar components.
                                                                                  


The IETF Secretariat.
--------------000102020702010509070900-- --===============0699532886== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify --===============0699532886==-- From douglm@rpi.edu Fri Jul 9 08:27:51 2010 Return-Path: X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 941013A697D for ; Fri, 9 Jul 2010 08:27:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 RlYD-tSsLkgo for ; Fri, 9 Jul 2010 08:27:50 -0700 (PDT) Received: from smtp8.server.rpi.edu (smtp8.server.rpi.edu [128.113.2.228]) by core3.amsl.com (Postfix) with ESMTP id B02323A6832 for ; Fri, 9 Jul 2010 08:27:47 -0700 (PDT) Received: from [128.113.124.94] (decapod-09.dynamic.rpi.edu [128.113.124.94]) (authenticated bits=0) by smtp8.server.rpi.edu (8.13.1/8.13.1) with ESMTP id o69FRoDC013373 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 9 Jul 2010 11:27:51 -0400 Message-ID: <4C373FF6.30407@rpi.edu> Date: Fri, 09 Jul 2010 11:27:50 -0400 From: Mike Douglass User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Lightning/1.0b2pre Thunderbird/3.0.4 MIME-Version: 1.0 To: calsify@ietf.org Content-Type: multipart/alternative; boundary="------------000102020702010509070900" X-RPI-SA-Score: undef - SENDER Whitelisted (douglm@rpi.edu: Mail from user authenticated via SMTP AUTH allowed always) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.228 Subject: [calsify] Fwd: New Version Notification for draft-douglass-link-extension-00 X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2010 15:27:51 -0000 This is a multi-part message in MIME format. --------------000102020702010509070900 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Last week I submitted the first draft of a proposed extension to iCalendar - a LINK property, closely aligned to the proposed link header - http://tools.ietf.org/html/draft-nottingham-http-link-header-10 -------- Original Message -------- Subject: New Version Notification for draft-douglass-link-extension-00 Date: Wed, 30 Jun 2010 12:51:48 -0700 (PDT) From: IETF I-D Submission Tool To: douglm@rpi.edu A new version of I-D, draft-douglass-link-extension-00.txt has been successfully submitted by Mike Douglass and posted to the IETF repository. Filename: draft-douglass-link-extension Revision: 00 Title: Link Extension to Icalendar Creation_date: 2010-06-30 WG ID: Independent Submission Number_of_pages: 10 Abstract: This specification introduces a new iCalendar property LINK to provide ancillary information for iCalendar components. The IETF Secretariat. --------------000102020702010509070900 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit Last week I submitted the first draft of a proposed extension to iCalendar - a LINK property, closely aligned to the proposed link header -

http://tools.ietf.org/html/draft-nottingham-http-link-header-10




-------- Original Message --------
Subject: New Version Notification for draft-douglass-link-extension-00
Date: Wed, 30 Jun 2010 12:51:48 -0700 (PDT)
From: IETF I-D Submission Tool <idsubmission@ietf.org>
To: douglm@rpi.edu 


A new version of I-D, draft-douglass-link-extension-00.txt has been successfully submitted by Mike Douglass and posted to the IETF repository.

Filename:	 draft-douglass-link-extension
Revision:	 00
Title:		 Link Extension to Icalendar
Creation_date:	 2010-06-30
WG ID:		 Independent Submission
Number_of_pages: 10

Abstract:
This specification introduces a new iCalendar property LINK to
provide ancillary information for iCalendar components.
                                                                                  


The IETF Secretariat.
--------------000102020702010509070900-- From calsify-bounces@ietf.org Fri Jul 9 19:22:32 2010 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BF563A6984; Fri, 9 Jul 2010 19:22:32 -0700 (PDT) X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 81F0D3A6984 for ; Fri, 9 Jul 2010 19:22:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001] 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 TWHvf8IVPPdY for ; Fri, 9 Jul 2010 19:22:30 -0700 (PDT) Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by core3.amsl.com (Postfix) with ESMTP id 20A623A6989 for ; Fri, 9 Jul 2010 19:22:30 -0700 (PDT) Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta07.westchester.pa.mail.comcast.net with comcast id g22V1e0040QuhwU572Ncbs; Sat, 10 Jul 2010 02:22:36 +0000 Received: from THARE ([71.203.98.77]) by omta02.westchester.pa.mail.comcast.net with comcast id g2Nb1e00M1gAkVz3N2Nc3P; Sat, 10 Jul 2010 02:22:36 +0000 From: "Tim Hare" To: "'Mike Douglass'" , References: <4C373FF6.30407@rpi.edu> In-Reply-To: <4C373FF6.30407@rpi.edu> Date: Fri, 9 Jul 2010 22:22:28 -0400 Message-ID: <019601cb1fd6$beac0cc0$3c042640$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acsfe0/FI195n34lTfOwq/xIutjS4gAWaKRg Content-Language: en-us Subject: Re: [calsify] Fwd: New Version Notification for draft-douglass-link-extension-00 X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org Questions: 1. Why LINK REL=CAL_(ACTIVE/INACTIVE)_PARTICIPANT rather than proposing ACTIVE / INACTIVE as possible values for the PARTSTAT parameter on an ATTENDEE property of a component? 2. Several, if not all, properties allow URIs as values or URIs can be specified in the ALTREP= parameter (for example, LOCATION). What advantage would the LINK property have over these schemes? I'm not criticizing the proposal per se, but I'd like to understand what it's advantages are and what problems it solves that don't have a solution in RFC 5545. Tim Hare Interested Bystander, Non-Inc. _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify From timhare@comcast.net Fri Jul 9 19:22:31 2010 Return-Path: X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 81F0D3A6984 for ; Fri, 9 Jul 2010 19:22:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001] 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 TWHvf8IVPPdY for ; Fri, 9 Jul 2010 19:22:30 -0700 (PDT) Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by core3.amsl.com (Postfix) with ESMTP id 20A623A6989 for ; Fri, 9 Jul 2010 19:22:30 -0700 (PDT) Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta07.westchester.pa.mail.comcast.net with comcast id g22V1e0040QuhwU572Ncbs; Sat, 10 Jul 2010 02:22:36 +0000 Received: from THARE ([71.203.98.77]) by omta02.westchester.pa.mail.comcast.net with comcast id g2Nb1e00M1gAkVz3N2Nc3P; Sat, 10 Jul 2010 02:22:36 +0000 From: "Tim Hare" To: "'Mike Douglass'" , References: <4C373FF6.30407@rpi.edu> In-Reply-To: <4C373FF6.30407@rpi.edu> Date: Fri, 9 Jul 2010 22:22:28 -0400 Message-ID: <019601cb1fd6$beac0cc0$3c042640$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acsfe0/FI195n34lTfOwq/xIutjS4gAWaKRg Content-Language: en-us Subject: Re: [calsify] Fwd: New Version Notification for draft-douglass-link-extension-00 X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2010 02:22:31 -0000 Questions: =20 1. Why LINK REL=3DCAL_(ACTIVE/INACTIVE)_PARTICIPANT rather than = proposing ACTIVE / INACTIVE as possible values for the PARTSTAT = parameter on an ATTENDEE property of a component? 2. Several, if not all, properties allow URIs as values or URIs can be = specified in the ALTREP=3D parameter (for example, LOCATION). What = advantage would the LINK property have over these schemes? I'm not criticizing the proposal per se, but I'd like to understand what = it's advantages are and what problems it solves that don't have a = solution in RFC 5545. Tim Hare Interested Bystander, Non-Inc. From calsify-bounces@ietf.org Fri Jul 9 21:13:17 2010 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FC6D3A68D8; Fri, 9 Jul 2010 21:13:17 -0700 (PDT) X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C59E03A6890 for ; Fri, 9 Jul 2010 21:13:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.185 X-Spam-Level: X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185] 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 AfK-extY+GMT for ; Fri, 9 Jul 2010 21:13:14 -0700 (PDT) Received: from smtp7.server.rpi.edu (smtp7.server.rpi.edu [128.113.2.227]) by core3.amsl.com (Postfix) with ESMTP id B02C43A68D8 for ; Fri, 9 Jul 2010 21:13:14 -0700 (PDT) Received: from [192.168.2.12] (cpe-24-92-49-115.nycap.res.rr.com [24.92.49.115]) (authenticated bits=0) by smtp7.server.rpi.edu (8.13.1/8.13.1) with ESMTP id o6A4DFPa027256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Jul 2010 00:13:16 -0400 Message-ID: <4C37F35B.2010107@rpi.edu> Date: Sat, 10 Jul 2010 00:13:15 -0400 From: Mike Douglass User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Lightning/1.0b2pre Thunderbird/3.0.4 MIME-Version: 1.0 To: Tim Hare References: <4C373FF6.30407@rpi.edu> <019601cb1fd6$beac0cc0$3c042640$@net> In-Reply-To: <019601cb1fd6$beac0cc0$3c042640$@net> X-RPI-SA-Score: undef - SENDER Whitelisted (douglm@rpi.edu: Mail from user authenticated via SMTP AUTH allowed always) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.227 Cc: calsify@ietf.org Subject: Re: [calsify] Fwd: New Version Notification for draft-douglass-link-extension-00 X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org Attendees and Organizers are not valid on non-group scheduling events. One common invalid event we see when importing events are attempts to set those properties. As event publishers we have a strong need to indicate who is organizing the event and who are participants, for example a baseball team or their parents. Even for real group scheduling, the altrep parameter doesn't allow us to specify the type, e.g vcard, html etc nor does it allow us to specify multiple variants of the same information. Locations are a typical case and indeed where this all started. altrep is allowed but only once. In event publishing especially, it is important to have rich location information in a form clients can download and display or use to guide people to their destination. Vcard seems a good choice for this but clients need to be able to determine that the reference is indeed for location information and is in a form they can process. We also have a need to link to other information that is not covered by current rfc5545 properties but is vital to event publishers, sponsors for example. Event organizers also have a need for a standard way to link back to pages that provide access to media, for example video feeds or directly to that video feed. On 07/09/2010 10:22 PM, Tim Hare wrote: > Questions: > > 1. Why LINK REL=CAL_(ACTIVE/INACTIVE)_PARTICIPANT rather than proposing ACTIVE / INACTIVE as possible values for the PARTSTAT parameter on an ATTENDEE property of a component? > 2. Several, if not all, properties allow URIs as values or URIs can be specified in the ALTREP= parameter (for example, LOCATION). What advantage would the LINK property have over these schemes? > > > I'm not criticizing the proposal per se, but I'd like to understand what it's advantages are and what problems it solves that don't have a solution in RFC 5545. > > > Tim Hare > Interested Bystander, Non-Inc. > > > -- Mike Douglass douglm@rpi.edu Senior Systems Programmer Communication& Collaboration Technologies 518 276 6780(voice) 2809 (fax) Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180 _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify From douglm@rpi.edu Fri Jul 9 21:13:15 2010 Return-Path: X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C59E03A6890 for ; Fri, 9 Jul 2010 21:13:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.185 X-Spam-Level: X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185] 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 AfK-extY+GMT for ; Fri, 9 Jul 2010 21:13:14 -0700 (PDT) Received: from smtp7.server.rpi.edu (smtp7.server.rpi.edu [128.113.2.227]) by core3.amsl.com (Postfix) with ESMTP id B02C43A68D8 for ; Fri, 9 Jul 2010 21:13:14 -0700 (PDT) Received: from [192.168.2.12] (cpe-24-92-49-115.nycap.res.rr.com [24.92.49.115]) (authenticated bits=0) by smtp7.server.rpi.edu (8.13.1/8.13.1) with ESMTP id o6A4DFPa027256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Jul 2010 00:13:16 -0400 Message-ID: <4C37F35B.2010107@rpi.edu> Date: Sat, 10 Jul 2010 00:13:15 -0400 From: Mike Douglass User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Lightning/1.0b2pre Thunderbird/3.0.4 MIME-Version: 1.0 To: Tim Hare References: <4C373FF6.30407@rpi.edu> <019601cb1fd6$beac0cc0$3c042640$@net> In-Reply-To: <019601cb1fd6$beac0cc0$3c042640$@net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-RPI-SA-Score: undef - SENDER Whitelisted (douglm@rpi.edu: Mail from user authenticated via SMTP AUTH allowed always) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.227 Cc: calsify@ietf.org Subject: Re: [calsify] Fwd: New Version Notification for draft-douglass-link-extension-00 X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2010 04:13:15 -0000 Attendees and Organizers are not valid on non-group scheduling events. One common invalid event we see when importing events are attempts to set those properties. As event publishers we have a strong need to indicate who is organizing the event and who are participants, for example a baseball team or their parents. Even for real group scheduling, the altrep parameter doesn't allow us to specify the type, e.g vcard, html etc nor does it allow us to specify multiple variants of the same information. Locations are a typical case and indeed where this all started. altrep is allowed but only once. In event publishing especially, it is important to have rich location information in a form clients can download and display or use to guide people to their destination. Vcard seems a good choice for this but clients need to be able to determine that the reference is indeed for location information and is in a form they can process. We also have a need to link to other information that is not covered by current rfc5545 properties but is vital to event publishers, sponsors for example. Event organizers also have a need for a standard way to link back to pages that provide access to media, for example video feeds or directly to that video feed. On 07/09/2010 10:22 PM, Tim Hare wrote: > Questions: > > 1. Why LINK REL=CAL_(ACTIVE/INACTIVE)_PARTICIPANT rather than proposing ACTIVE / INACTIVE as possible values for the PARTSTAT parameter on an ATTENDEE property of a component? > 2. Several, if not all, properties allow URIs as values or URIs can be specified in the ALTREP= parameter (for example, LOCATION). What advantage would the LINK property have over these schemes? > > > I'm not criticizing the proposal per se, but I'd like to understand what it's advantages are and what problems it solves that don't have a solution in RFC 5545. > > > Tim Hare > Interested Bystander, Non-Inc. > > > -- Mike Douglass douglm@rpi.edu Senior Systems Programmer Communication& Collaboration Technologies 518 276 6780(voice) 2809 (fax) Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180 From calsify-bounces@ietf.org Sat Jul 10 06:40:14 2010 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A4373A69C5; Sat, 10 Jul 2010 06:40:14 -0700 (PDT) X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2975C3A69BB for ; Sat, 10 Jul 2010 06:40:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.301 X-Spam-Level: X-Spam-Status: No, score=0.301 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_50=0.001, J_CHICKENPOX_35=0.6] 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 GKUjecW1dkTu for ; Sat, 10 Jul 2010 06:40:12 -0700 (PDT) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by core3.amsl.com (Postfix) with ESMTP id 4DBBE3A699D for ; Sat, 10 Jul 2010 06:40:12 -0700 (PDT) Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta14.westchester.pa.mail.comcast.net with comcast id gClE1e0050SCNGk5EDgKbd; Sat, 10 Jul 2010 13:40:19 +0000 Received: from THARE ([71.203.98.77]) by omta09.westchester.pa.mail.comcast.net with comcast id gDgJ1e0021gAkVz3VDgJDp; Sat, 10 Jul 2010 13:40:19 +0000 From: "Tim Hare" To: "'Mike Douglass'" References: <4C373FF6.30407@rpi.edu> <019601cb1fd6$beac0cc0$3c042640$@net> <4C37F35B.2010107@rpi.edu> In-Reply-To: <4C37F35B.2010107@rpi.edu> Date: Sat, 10 Jul 2010 09:40:09 -0400 Message-ID: <01a001cb2035$6a8556b0$3f900410$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acsf5jtrZrLj9FaaTfqkOexiUY6dmQATFFOw Content-Language: en-us Cc: calsify@ietf.org Subject: Re: [calsify] Fwd: New Version Notification for draft-douglass-link-extension-00 X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org Thanks that clears it up somewhat. For your first point - I believe 'large attendance' events like concerts, theater, etc. are, technically, group scheduling events and could be scheduled as such but I see the advantages to your method now, when I didn't before. I think, coming from my particular background, I can get hung up on the appointment / meeting view of calendaring and forget things like events and conferences. Now after reading this a second time, a couple of other things: 1. You require 'fmttypeparam' on a LINK property, but it's not described in the document. TYPE= is used in examples, but TYPE isn't defined like TITLE is. 2. Personal opinion, maybe, but I think NAME= is a more generic, and therefore more generally applicable, thing than TITLE= 3. IF TYPE= uses MIME types, then I would think for your media feeds it would be better to have REL="MEDIA" (or something like it) and allow TYPE= to determine the type. MIME types are already used in many places to determine what will process a file, and I think most clients would already have functions to do so. I don't think it an undue burden on things to search for REL=MEDIA AND TYPE="whatever". As always these are one man's opinions, offered in the spirit of "let's get calendaring to where everyone can use it". Tim Hare Interested Bystander, Non-Inc. _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify From timhare@comcast.net Sat Jul 10 06:40:13 2010 Return-Path: X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2975C3A69BB for ; Sat, 10 Jul 2010 06:40:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.301 X-Spam-Level: X-Spam-Status: No, score=0.301 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_50=0.001, J_CHICKENPOX_35=0.6] 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 GKUjecW1dkTu for ; Sat, 10 Jul 2010 06:40:12 -0700 (PDT) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by core3.amsl.com (Postfix) with ESMTP id 4DBBE3A699D for ; Sat, 10 Jul 2010 06:40:12 -0700 (PDT) Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta14.westchester.pa.mail.comcast.net with comcast id gClE1e0050SCNGk5EDgKbd; Sat, 10 Jul 2010 13:40:19 +0000 Received: from THARE ([71.203.98.77]) by omta09.westchester.pa.mail.comcast.net with comcast id gDgJ1e0021gAkVz3VDgJDp; Sat, 10 Jul 2010 13:40:19 +0000 From: "Tim Hare" To: "'Mike Douglass'" References: <4C373FF6.30407@rpi.edu> <019601cb1fd6$beac0cc0$3c042640$@net> <4C37F35B.2010107@rpi.edu> In-Reply-To: <4C37F35B.2010107@rpi.edu> Date: Sat, 10 Jul 2010 09:40:09 -0400 Message-ID: <01a001cb2035$6a8556b0$3f900410$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acsf5jtrZrLj9FaaTfqkOexiUY6dmQATFFOw Content-Language: en-us Cc: calsify@ietf.org Subject: Re: [calsify] Fwd: New Version Notification for draft-douglass-link-extension-00 X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2010 13:40:13 -0000 Thanks that clears it up somewhat. For your first point - I believe = 'large attendance' events like concerts, theater, etc. are, technically, = group scheduling events and could be scheduled as such but I see the = advantages to your method now, when I didn't before. I think, coming = from my particular background, I can get hung up on the appointment / = meeting view of calendaring and forget things like events and = conferences. Now after reading this a second time, a couple of other things: 1. You require 'fmttypeparam' on a LINK property, but it's not described = in the document. TYPE=3D is used in examples, but TYPE isn't defined = like TITLE is. 2. Personal opinion, maybe, but I think NAME=3D is a more generic, and = therefore more generally applicable, thing than TITLE=3D=20 3. IF TYPE=3D uses MIME types, then I would think for your media feeds = it would be better to have REL=3D"MEDIA" (or something like it) and = allow TYPE=3D to determine the type. MIME types are already used in many = places to determine what will process a file, and I think most clients = would already have functions to do so. I don't think it an undue burden = on things to search for REL=3DMEDIA AND TYPE=3D"whatever". As always these are one man's opinions, offered in the spirit of "let's = get calendaring to where everyone can use it". Tim Hare Interested Bystander, Non-Inc. From calsify-bounces@ietf.org Mon Jul 12 10:24:32 2010 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B4813A6BA3; Mon, 12 Jul 2010 10:24:32 -0700 (PDT) X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B0193A684E for ; Mon, 12 Jul 2010 10:24:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001] 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 s3SONyfvETES for ; Mon, 12 Jul 2010 10:24:30 -0700 (PDT) Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 89C973A6BA3 for ; Mon, 12 Jul 2010 10:24:26 -0700 (PDT) Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o6CHOXMV018041 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 12 Jul 2010 17:24:34 GMT Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o6CFHj1x029438 for ; Mon, 12 Jul 2010 17:24:32 GMT Received: from abhmt016.oracle.com by acsmt354.oracle.com with ESMTP id 419163311278955361; Mon, 12 Jul 2010 10:22:41 -0700 Received: from dhcp-usca15-127-193.Red.IPlanet.COM (/192.18.127.193) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 12 Jul 2010 10:22:41 -0700 Message-Id: From: Ciny Joy To: calsify@ietf.org Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 12 Jul 2010 10:22:41 -0700 X-Mailer: Apple Mail (2.936) X-Source-IP: acsmt353.oracle.com [141.146.40.153] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090209.4C3B4FD0.01E0:SCFMA4539814,ss=1,fgs=0 Subject: [calsify] Request for review - New version of Schema for representing resources for calendaring and scheduling services X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes" Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org Hi, A new version of the draft describing a schema for Resources in the calendaring context has been published - http://tools.ietf.org/html/draft-cal-resource-schema-01 . I would really appreciate any comments and corrections. Changes made from 00 draft . Make Common Name a MUST . Remove uid and KIND from MUST . Redefine ResourceKind to just KIND to better align with KIND in VCARD . Redefine uid as a new vcard uid in LDAP to better align with UID in VCARD . Added new related attribute . Redefine free to nocost to prevent confusion with free from freebusy . Removed ResourceNotes which was redundant considering we already use Description field to put all additional notes. . Fix typos, put explanation on what it is before LDAP definitions, and remove comment on which attributes may be used for query Thanks, Ciny _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify From ciny.joy@oracle.com Mon Jul 12 10:24:31 2010 Return-Path: X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B0193A684E for ; Mon, 12 Jul 2010 10:24:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001] 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 s3SONyfvETES for ; Mon, 12 Jul 2010 10:24:30 -0700 (PDT) Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 89C973A6BA3 for ; Mon, 12 Jul 2010 10:24:26 -0700 (PDT) Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o6CHOXMV018041 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 12 Jul 2010 17:24:34 GMT Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o6CFHj1x029438 for ; Mon, 12 Jul 2010 17:24:32 GMT Received: from abhmt016.oracle.com by acsmt354.oracle.com with ESMTP id 419163311278955361; Mon, 12 Jul 2010 10:22:41 -0700 Received: from dhcp-usca15-127-193.Red.IPlanet.COM (/192.18.127.193) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 12 Jul 2010 10:22:41 -0700 Message-Id: From: Ciny Joy To: calsify@ietf.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 12 Jul 2010 10:22:41 -0700 X-Mailer: Apple Mail (2.936) X-Source-IP: acsmt353.oracle.com [141.146.40.153] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090209.4C3B4FD0.01E0:SCFMA4539814,ss=1,fgs=0 Subject: [calsify] Request for review - New version of Schema for representing resources for calendaring and scheduling services X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jul 2010 17:24:31 -0000 Hi, A new version of the draft describing a schema for Resources in the calendaring context has been published - http://tools.ietf.org/html/draft-cal-resource-schema-01 . I would really appreciate any comments and corrections. Changes made from 00 draft . Make Common Name a MUST . Remove uid and KIND from MUST . Redefine ResourceKind to just KIND to better align with KIND in VCARD . Redefine uid as a new vcard uid in LDAP to better align with UID in VCARD . Added new related attribute . Redefine free to nocost to prevent confusion with free from freebusy . Removed ResourceNotes which was redundant considering we already use Description field to put all additional notes. . Fix typos, put explanation on what it is before LDAP definitions, and remove comment on which attributes may be used for query Thanks, Ciny From douglm@rpi.edu Tue Jul 13 11:59:32 2010 Return-Path: X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C1733A6849; Tue, 13 Jul 2010 11:59:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.399 X-Spam-Level: X-Spam-Status: No, score=-0.399 tagged_above=-999 required=5 tests=[AWL=-2.200, BAYES_50=0.001, J_CHICKENPOX_45=0.6, J_CHICKENPOX_48=0.6, J_CHICKENPOX_64=0.6] 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 tMg47O93Sjry; Tue, 13 Jul 2010 11:59:31 -0700 (PDT) Received: from smtp5.server.rpi.edu (smtp5.server.rpi.edu [128.113.2.225]) by core3.amsl.com (Postfix) with ESMTP id 7AA333A6832; Tue, 13 Jul 2010 11:59:31 -0700 (PDT) Received: from [128.113.124.94] (decapod-09.dynamic.rpi.edu [128.113.124.94]) (authenticated bits=0) by smtp5.server.rpi.edu (8.13.1/8.13.1) with ESMTP id o6DIxcsv021682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Jul 2010 14:59:39 -0400 Message-ID: <4C3CB79A.6050604@rpi.edu> Date: Tue, 13 Jul 2010 14:59:38 -0400 From: Mike Douglass User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Lightning/1.0b2pre Thunderbird/3.0.4 MIME-Version: 1.0 To: vcarddav@ietf.org, calsify@ietf.org References: <36FF8BB750F3694C0400EAC1@caldav.corp.apple.com> <4C3C8815.4010304@viagenie.ca> In-Reply-To: <4C3C8815.4010304@viagenie.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RPI-SA-Score: undef - SENDER Whitelisted (douglm@rpi.edu: Mail from user authenticated via SMTP AUTH allowed always) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.225 Subject: [calsify] Alignment of CUTYPE and KIND X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jul 2010 18:59:32 -0000 While implementing calendar client support using carddav for attendee lookup we came across the inconsistencies in vcard KIND and attendee CUTYPE which I believe ought to be addressed. KIND has KIND-param = "VALUE=text" / any-param KIND-value = "individual" / "group" / "org" / "location" / "thing" CUTYPE has cutypeparam = "CUTYPE" "=" ("INDIVIDUAL" ; An individual / "GROUP" ; A group of individuals / "RESOURCE" ; A physical resource / "ROOM" ; A room resource / "UNKNOWN" ; Otherwise not known / x-name ; Experimental type / iana-token) ; Other IANA-registered ; type ; Default is INDIVIDUAL So INDIVIDUAL and GROUP align OK CUTYPE.RESOURCE = KIND.thing? No CUTYPE equivalent for KIND.ORG KIND.LOCATION is better than CUTYPE.ROOM (an event might take place on a sports field) On 07/13/2010 11:36 AM, Simon Perreault wrote: > On 2010-07-13 10:59, Cyrus Daboo wrote: > >> So there is a real problem here. For example, if in the future I define >> a new property FOO that uses a ;-delimited compound value, then I want >> to be sure that clients not aware of this property will properly >> "round-trip" it. So if I send such a client this: >> >> FOO:delimited;text\;string >> > Right, there is a problem with the current text. > > Assume we specify that semicolons that are not component separators MUST > be escaped. Then a client can correctly interpret this unknown property > as having two components. And it will always output it exactly the way > it received it. That fixes the problem, right? > > If so, this would point toward the acceptance of proposal 1. > > Simon > -- Mike Douglass douglm@rpi.edu Senior Systems Programmer Communication& Collaboration Technologies 518 276 6780(voice) 2809 (fax) Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180 From calsify-bounces@ietf.org Tue Jul 13 11:59:33 2010 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69B783A6849; Tue, 13 Jul 2010 11:59:33 -0700 (PDT) X-Original-To: calsify@core3.amsl.com Delivered-To: calsify@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C1733A6849; Tue, 13 Jul 2010 11:59:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.399 X-Spam-Level: X-Spam-Status: No, score=-0.399 tagged_above=-999 required=5 tests=[AWL=-2.200, BAYES_50=0.001, J_CHICKENPOX_45=0.6, J_CHICKENPOX_48=0.6, J_CHICKENPOX_64=0.6] 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 tMg47O93Sjry; Tue, 13 Jul 2010 11:59:31 -0700 (PDT) Received: from smtp5.server.rpi.edu (smtp5.server.rpi.edu [128.113.2.225]) by core3.amsl.com (Postfix) with ESMTP id 7AA333A6832; Tue, 13 Jul 2010 11:59:31 -0700 (PDT) Received: from [128.113.124.94] (decapod-09.dynamic.rpi.edu [128.113.124.94]) (authenticated bits=0) by smtp5.server.rpi.edu (8.13.1/8.13.1) with ESMTP id o6DIxcsv021682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Jul 2010 14:59:39 -0400 Message-ID: <4C3CB79A.6050604@rpi.edu> Date: Tue, 13 Jul 2010 14:59:38 -0400 From: Mike Douglass User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Lightning/1.0b2pre Thunderbird/3.0.4 MIME-Version: 1.0 To: vcarddav@ietf.org, calsify@ietf.org References: <36FF8BB750F3694C0400EAC1@caldav.corp.apple.com> <4C3C8815.4010304@viagenie.ca> In-Reply-To: <4C3C8815.4010304@viagenie.ca> X-RPI-SA-Score: undef - SENDER Whitelisted (douglm@rpi.edu: Mail from user authenticated via SMTP AUTH allowed always) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.225 Subject: [calsify] Alignment of CUTYPE and KIND X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org While implementing calendar client support using carddav for attendee lookup we came across the inconsistencies in vcard KIND and attendee CUTYPE which I believe ought to be addressed. KIND has KIND-param = "VALUE=text" / any-param KIND-value = "individual" / "group" / "org" / "location" / "thing" CUTYPE has cutypeparam = "CUTYPE" "=" ("INDIVIDUAL" ; An individual / "GROUP" ; A group of individuals / "RESOURCE" ; A physical resource / "ROOM" ; A room resource / "UNKNOWN" ; Otherwise not known / x-name ; Experimental type / iana-token) ; Other IANA-registered ; type ; Default is INDIVIDUAL So INDIVIDUAL and GROUP align OK CUTYPE.RESOURCE = KIND.thing? No CUTYPE equivalent for KIND.ORG KIND.LOCATION is better than CUTYPE.ROOM (an event might take place on a sports field) On 07/13/2010 11:36 AM, Simon Perreault wrote: > On 2010-07-13 10:59, Cyrus Daboo wrote: > >> So there is a real problem here. For example, if in the future I define >> a new property FOO that uses a ;-delimited compound value, then I want >> to be sure that clients not aware of this property will properly >> "round-trip" it. So if I send such a client this: >> >> FOO:delimited;text\;string >> > Right, there is a problem with the current text. > > Assume we specify that semicolons that are not component separators MUST > be escaped. Then a client can correctly interpret this unknown property > as having two components. And it will always output it exactly the way > it received it. That fixes the problem, right? > > If so, this would point toward the acceptance of proposal 1. > > Simon > -- Mike Douglass douglm@rpi.edu Senior Systems Programmer Communication& Collaboration Technologies 518 276 6780(voice) 2809 (fax) Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180 _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify From ietf-calsify-bounces@osafoundation.org Wed Jul 28 01:16:23 2010 Return-Path: X-Original-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BA4128C11D for ; Wed, 28 Jul 2010 01:16:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.418 X-Spam-Level: X-Spam-Status: No, score=-102.418 tagged_above=-999 required=5 tests=[AWL=0.181, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 i23RDvlGC-0R for ; Wed, 28 Jul 2010 01:16:06 -0700 (PDT) Received: from leka.osafoundation.org (leka.osafoundation.org [149.20.54.96]) by core3.amsl.com (Postfix) with ESMTP id 5757628C108 for ; Wed, 28 Jul 2010 01:16:03 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 13E4377D6F9; Wed, 28 Jul 2010 01:16:24 -0700 (PDT) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DTdV59XYvIfu; Wed, 28 Jul 2010 01:16:07 -0700 (PDT) Received: from leka.osafoundation.org (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 9C0DE77D702; Wed, 28 Jul 2010 01:16:01 -0700 (PDT) X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 0958477D6F9 for ; Wed, 28 Jul 2010 01:15:58 -0700 (PDT) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Ac+at0mLfs8 for ; Wed, 28 Jul 2010 01:15:42 -0700 (PDT) Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by leka.osafoundation.org (Postfix) with ESMTP id CD32A77D702 for ; Wed, 28 Jul 2010 01:15:40 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 0) id 37D7B3A6986; Wed, 28 Jul 2010 01:15:06 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100728081513.37D7B3A6986@core3.amsl.com> Date: Wed, 28 Jul 2010 01:15:06 -0700 (PDT) Cc: ietf-calsify@osafoundation.org Subject: [ietf-calsify] I-D ACTION:draft-ietf-calsify-rfc2447bis-10.txt X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RFC2445, 2446 and 2447 Discusions" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ietf-calsify-bounces@osafoundation.org Errors-To: ietf-calsify-bounces@osafoundation.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Calendaring and Scheduling Standards Simplification Working Group of the IETF. Title : iCalendar Message-Based Interoperability Protocol (iMIP) Author(s) : A. Melnikov Filename : draft-ietf-calsify-rfc2447bis-10.txt Pages : 22 Date : 2010-7-28 This document, iCalendar Message-Based Interoperability Protocol (iMIP), specifies a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to Internet email-based transports. Calendaring entries defined by the iCalendar Object Model (iCalendar) are wrapped using constructs from RFC 5322 and MIME (RFC 2045, RFC 2046, RFC 2047 and RFC 2049), and then transported over SMTP. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-calsify-rfc2447bis-10.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-calsify-rfc2447bis-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-7-28010744.I-D@ietf.org> --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ietf-calsify mailing list ietf-calsify@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/ietf-calsify --NextPart-- From ietf-calsify-bounces@osafoundation.org Wed Jul 28 12:01:17 2010 Return-Path: X-Original-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 684D03A68AB for ; Wed, 28 Jul 2010 12:01:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.599 X-Spam-Level: X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=-2.000, 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 UyLiP-qDvMJ7 for ; Wed, 28 Jul 2010 12:01:16 -0700 (PDT) Received: from leka.osafoundation.org (leka.osafoundation.org [149.20.54.96]) by core3.amsl.com (Postfix) with ESMTP id E6D633A681A for ; Wed, 28 Jul 2010 12:01:09 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 234B277D6F9; Wed, 28 Jul 2010 12:01:33 -0700 (PDT) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nGXUIdIUhf4N; Wed, 28 Jul 2010 12:01:22 -0700 (PDT) Received: from leka.osafoundation.org (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id CF8B777D715; Wed, 28 Jul 2010 12:01:18 -0700 (PDT) X-Original-To: ietf-calsify@osafoundation.org Delivered-To: ietf-calsify@osafoundation.org Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 429A877D6F9 for ; Wed, 28 Jul 2010 12:01:14 -0700 (PDT) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9TbodbG4tGe for ; Wed, 28 Jul 2010 12:01:01 -0700 (PDT) Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by leka.osafoundation.org (Postfix) with ESMTP id B181377D718 for ; Wed, 28 Jul 2010 12:01:01 -0700 (PDT) Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o6SJ0xoq020796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 28 Jul 2010 19:01:00 GMT Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o6SDSh40002454 for ; Wed, 28 Jul 2010 19:00:57 GMT Received: from abhmt014.oracle.com by acsmt353.oracle.com with ESMTP id 465435851280343634; Wed, 28 Jul 2010 12:00:34 -0700 MIME-Version: 1.0 Message-ID: <4b9ab0d7-4aed-4be7-987f-ab8681f378b5@default> Date: Wed, 28 Jul 2010 12:00:34 -0700 (PDT) From: ciny.joy@oracle.com To: ietf-calsify@osafoundation.org X-Source-IP: acsmt353.oracle.com [141.146.40.153] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090206.4C507E6A.00DB:SCFMA4539814,ss=1,fgs=0 Subject: [ietf-calsify] Auto Reply: ietf-calsify Digest, Vol 71, Issue 1 X-BeenThere: ietf-calsify@osafoundation.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RFC2445, 2446 and 2447 Discusions" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-calsify-bounces@osafoundation.org Errors-To: ietf-calsify-bounces@osafoundation.org This is an auto-replied message. I am on vacation and unable to get to my mail. I will try and reply as soon as possible. Thanks, Ciny _______________________________________________ ietf-calsify mailing list ietf-calsify@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/ietf-calsify