IETF Logo Mail Archive

Re: [calsify] review of draft-ietf-calext-eventpub-extensions-00

Ken Murchison <murch@andrew.cmu.edu> Wed, 19 October 2016 19:34 UTC

Return-Path: <murch@andrew.cmu.edu>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE401296AF for <calsify@ietfa.amsl.com>; Wed, 19 Oct 2016 12:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.631
X-Spam-Level:
X-Spam-Status: No, score=-4.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.431] autolearn=ham autolearn_force=no
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 RTvnWkSB6RfJ for <calsify@ietfa.amsl.com>; Wed, 19 Oct 2016 12:34:01 -0700 (PDT)
Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.105.203]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 099CB1296D2 for <calsify@ietf.org>; Wed, 19 Oct 2016 12:34:00 -0700 (PDT)
Received: from [172.31.25.241] (VPN-172-31-25-241.VPN.CMU.LOCAL [172.31.25.241]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.15.2/8.15.1) with ESMTPSA id u9JJXwSU055871 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <calsify@ietf.org>; Wed, 19 Oct 2016 15:33:59 -0400
To: "calsify@ietf.org" <calsify@ietf.org>
References: <CADZyTknz=cYREHPZunxmQHcT5+b=FfeWV3PQFxqoyzBv19rYUw@mail.gmail.com> <a2e1f1bb-91c1-f8f1-a843-8ecf69a2938f@gmail.com> <4700015a-bb03-f5c8-564f-690adb93aff8@andrew.cmu.edu> <33aceebe-624b-dc74-c23b-3bbbc4968a95@gmail.com>
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
Message-ID: <2da96ddb-ba41-0074-01cc-309482679791@andrew.cmu.edu>
Date: Wed, 19 Oct 2016 15:33:58 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <33aceebe-624b-dc74-c23b-3bbbc4968a95@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-PMX-Version: 6.3.0.2556906, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.10.19.192717
X-SMTP-Spam-Clean: 10% ( TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, FROM_EDU_TLD 0, IN_REP_TO 0, LEGITIMATE_NEGATE 0, LEGITIMATE_SIGNS 0, MSG_THREAD 0, REFERENCES 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __FRAUD_CONTACT_ADDY 0, __HAS_FROM 0, __HAS_MSGID 0, __HTTPS_URI 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0, __MOZILLA_USER_AGENT 0, __MULTIPLE_URI_TEXT 0, __PHISH_SPEAR_STRUCTURE_1 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT2 0, __TO_MALFORMED_2 0, __TO_NAME 0, __TO_NO_NAME 0, __URI_IN_BODY 0, __URI_NS , __URI_WITH_PATH 0, __USER_AGENT 0)
X-SMTP-Spam-Score: 10%
X-Scanned-By: MIMEDefang 2.78 on 128.2.105.203
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/aT3d0VK1A7JTLU1rqhNDgkD4k9Y>
Subject: Re: [calsify] review of draft-ietf-calext-eventpub-extensions-00
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 19 Oct 2016 19:34:09 -0000

OK, understood.  If future drafts will be using such a construct, we 
might as well introduce it in this draft.


On 10/19/2016 03:15 PM, Michael Douglass wrote:
>
>
> On 10/19/16 12:29, Ken Murchison wrote:
>> Hi Mike,
>>
>>
>> On 10/19/2016 11:16 AM, Michael Douglass wrote:
>>> Thanks for the comments - and sorry for the delay.
>>>
>>> I've added my responses to your comments below.
>>>
>>> I'll post a new draft in a short while: there are 2 issues at least
>>> I'd like to address:
>>>
>>> 1. Should the ASSOCIATE property really be a component?
>>> Other extensions to the iCalendar data model are requiring us to
>>> handle deeper nesting of components and in any case a component more
>>> closely matches XML and JSON representations
>>
>> I'm not opposed to making ASSOCIATE a component, but what other
>> meta-data would be needed for an ASSOCIATE beyond what is currently
>> specified to warrant the change?  Do you have an example in mind that
>> you could flesh out?
>
> So this is from https://tools.ietf.org/html/draft-apthorp-ical-tasks-01
>
>
> 3.4.2. Relating comments to status
>
>    The GROUP parameter is used with the STATUS or ATTENDEE properties to
>    relate an associated COMMENT property. The COMMENT property can then
>    be used to include additional human readable information about why
>    the associated STATUS or ATTENDEE property changed.
>
> STATUS;REASON="http://example.com/reason/delivery-failed";SUBSTATE
>        =ERROR;MODIFIED=20130212T120000Z;GROUP=G1:FAILED
>       COMMENT;MODIFIED=20130226T110451Z;GROUP=G1:Breakdown
>
> ATTENDEE;PARTSTAT=FAILED;MODIFIED=20130226T1104510Z;GROUP=G2:
>        REASON="http://example.com/reason/van-break-down":mailto:
>        xxx@example.com
>       COMMENT;MODIFIED=20130226T110451Z;GROUP=G2:Puncture
>
> (An aside - I think the example is faulty - a ":" wheer there should 
> eb a ";")
>
> The problem we had to address here is that we wanted a bunch of 
> properties to be related to a specific attendee - so we used the GROUP 
> parameter.
>
> Significantly more readable and probably easier to manipulate is the 
> approach of putting all that inside a component
>
> Inventing one...
>
> BEGIN VATTENDEE
> ATTENDEE:PARTSTAT=FAILED;MODIFIED=20130226T1104510Z:xxx@example.com
> REASON="http://example.com/reason/van-break-down"
> COMMENT;MODIFIED=20130226T110451Z:Puncture
> END VATTENDEE
>
>
> In fact any attendee attributes could be stored there. I think in 
> vpoll we ended up adopting tha approach for the voter - which could 
> also be an associate if we made it a component
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

-- 
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University

v2.23.0 | Report a Bug | By Email