[Ietf-calsify] Updated ABNF to address issues 52 & 56

[bernard.desruisseaux at oracle.com (Bernard Desruisseaux)]

+1 (Obviously!)

Cheers,
Bernard

Alexey Melnikov wrote:
> Here is the updated ABNF (based on feedback from Bernard) to address
> 
> * Issue 52: (Section 4.3.10 Recurrence Rule: x-name rule part?)
> * Issue 56: (Section 4.3.10: Order of rule parts (ABNF issue))
> 
> recur           = recur-rule-part *( ";" recur-rule-part )
>                ;
>                ; The rule parts are not ordered in any
>                ; particular sequence
>                ;
>                ; The FREQ rule part is REQUIRED,
>                ; but MUST NOT occur more than once
>                ;
>                ; The UNTIL or COUNT rule parts are OPTIONAL,
>                ; but they MUST NOT occur in the same 'recur'
>                ;
>                ; The other rule parts are OPTIONAL,
>                ; but MUST NOT occur more than once
> 
> recur-rule-part = ( "FREQ" "=" freq )
>                / ( "UNTIL" "=" enddate )
>                / ( "COUNT" "=" 1*DIGIT )
>                / ( "INTERVAL" "=" 1*DIGIT )
>                / ( "BYSECOND" "=" byseclist )
>                / ( "BYMINUTE" "=" byminlist )
>                / ( "BYHOUR" "=" byhrlist )
>                / ( "BYDAY" "=" bywdaylist )
>                / ( "BYMONTHDAY" "=" bymodaylist )
>                / ( "BYYEARDAY" "=" byyrdaylist )
>                / ( "BYWEEKNO" "=" bywknolist )
>                / ( "BYMONTH" "=" bymolist )
>                / ( "BYSETPOS" "=" bysplist )
>                / ( "WKST" "=" weekday )
> 
> Regards,
> Alexey
> 
> _______________________________________________
> Ietf-calsify mailing list
> [e-mail]
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
From aki.niemi at nokia.com  Mon Nov 27 01:08:22 2006
From: aki.niemi at nokia.com (Aki Niemi)
Date: Mon Nov 27 01:09:11 2006
Subject: [Ietf-calsify] Weekly Jabber Chat
Message-ID: <[e-mail]>

A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 1835 bytes
Desc: not available
Url : http://lists.osafoundation.org/pipermail/ietf-calsify/attachments/20061127/60744cec/attachment.icz
From aki.niemi at nokia.com  Wed Nov 29 00:23:42 2006
From: aki.niemi at nokia.com ([e-mail])
Date: Wed Nov 29 00:24:25 2006
Subject: [Ietf-calsify] Cancel: Weekly Jabber Chat
Message-ID: <[e-mail]>

After skipping a week due to the US Thanksgiving holiday, let's continue on our weekly Jabber chats again.

Agenda:

- Agenda bash, setting up
- Discussing the remaining open issues with RFC 2445bis.
- AOB

Resources:

Link to the Calsify WG issue tracker:

http://ofcourseimright.com/cgi-bin/roundup/calsify/

A good place to learn more about Jabber is at:

http://www.jabber.org

See you there.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/ietf-calsify/attachments/20061129/2c6d53a6/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2131 bytes
Desc: not available
Url : http://lists.osafoundation.org/pipermail/ietf-calsify/attachments/20061129/2c6d53a6/attachment.icz
From aki.niemi at nokia.com  Wed Nov 29 01:27:11 2006
From: aki.niemi at nokia.com (Aki Niemi)
Date: Wed Nov 29 02:10:09 2006
Subject: [Ietf-calsify] Cancel: Weekly Jabber Chat
In-Reply-To: <[e-mail]>
References: <[e-mail]>
Message-ID: <[e-mail]>

All,

We need to cancel this week's Jabber chat. Turns out we are not able to
get a reasonable attendance this time due to vacations and other
scheduling problems. 

We're still on for next week, though.

Cheers,
Aki

On Wed, 2006-11-29 at 10:23 +0200, ext
[e-mail] wrote:
> After skipping a week due to the US Thanksgiving holiday, let's
> continue on our weekly Jabber chats again.
> 
> Agenda:
> 
> - Agenda bash, setting up
> - Discussing the remaining open issues with RFC 2445bis.
> - AOB
> 
> Resources:
> 
> Link to the Calsify WG issue tracker:
> 
> http://ofcourseimright.com/cgi-bin/roundup/calsify/
> 
> A good place to learn more about Jabber is at:
> 
> http://www.jabber.org
> 
> See you there.
> 
> _______________________________________________
> Ietf-calsify mailing list
> [e-mail]
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id DFB127F76F for <[e-mail]>; Wed, 29 Nov 2006 02:10:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id D1B50142256 for <[e-mail]>; Wed, 29 Nov 2006 02:10:07 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19927-08 for <[e-mail]>; Wed, 29 Nov 2006 02:10:06 -0800 (PST)
Received: from mgw-ext13.nokia.com (mgw-ext13.nokia.com [131.228.20.172]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id F075C142253 for <[e-mail]>; Wed, 29 Nov 2006 02:10:05 -0800 (PST)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id kATA9fEx002743; Wed, 29 Nov 2006 12:09:59 +0200
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 29 Nov 2006 12:09:45 +0200
Received: from [10.162.253.136] ([10.162.253.136]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);  Wed, 29 Nov 2006 12:09:44 +0200
Subject: Re: [Ietf-calsify] Cancel: Weekly Jabber Chat
From: Aki Niemi <[e-mail]>
To: Calsify WG <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
Content-Type: text/plain
Organization: Nokia-NRC/Helsinki
Date: Wed, 29 Nov 2006 11:27:11 +0200
Message-Id: <[e-mail]>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Nov 2006 10:09:44.0739 (UTC) FILETIME=[7E426730:01C7139E]
X-Nokia-AV: Clean
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.4 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Wed, 29 Nov 2006 10:10:08 -0000

All,

We need to cancel this week's Jabber chat. Turns out we are not able to
get a reasonable attendance this time due to vacations and other
scheduling problems. 

We're still on for next week, though.

Cheers,
Aki

On Wed, 2006-11-29 at 10:23 +0200, ext
[e-mail] wrote:
> After skipping a week due to the US Thanksgiving holiday, let's
> continue on our weekly Jabber chats again.
> 
> Agenda:
> 
> - Agenda bash, setting up
> - Discussing the remaining open issues with RFC 2445bis.
> - AOB
> 
> Resources:
> 
> Link to the Calsify WG issue tracker:
> 
> http://ofcourseimright.com/cgi-bin/roundup/calsify/
> 
> A good place to learn more about Jabber is at:
> 
> http://www.jabber.org
> 
> See you there.
> 
> _______________________________________________
> Ietf-calsify mailing list
> [e-mail]
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 6407B7F5EB for <[e-mail]>; Wed, 29 Nov 2006 00:24:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 54D4C142262 for <[e-mail]>; Wed, 29 Nov 2006 00:24:24 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17580-07 for <[e-mail]>; Wed, 29 Nov 2006 00:24:22 -0800 (PST)
Received: from mgw-ext11.nokia.com (mgw-ext11.nokia.com [131.228.20.170]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 5DD90142260 for <[e-mail]>; Wed, 29 Nov 2006 00:24:21 -0800 (PST)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext11.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id kAT8Nep6004280; Wed, 29 Nov 2006 10:24:05 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 29 Nov 2006 10:23:44 +0200
Received: from esebe106.NOE.Nokia.com ([172.21.143.51]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 29 Nov 2006 10:23:44 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: from 10.162.252.152 ([10.162.252.152]) by esebe106.NOE.Nokia.com ([172.21.143.51]) with Microsoft Exchange Server HTTP-DAV ; Wed, 29 Nov 2006 08:23:44 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7138F.AEF9F58B"
Received: from macbuster by ESEBE106.noe.nokia.com; 29 Nov 2006 10:23:42 +0200
Content-class: urn:content-classes:calendarmessage
Date: Wed, 29 Nov 2006 10:23:42 +0200
Message-ID: <[e-mail]>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cancel: Weekly Jabber Chat
Thread-Index: AccTj675rD8VyWD6QJSHfp73HmN8vA==
From: <[e-mail]>
To: <[e-mail]>, <[e-mail]>
X-OriginalArrivalTime: 29 Nov 2006 08:23:44.0528 (UTC) FILETIME=[AF473900:01C7138F]
X-Nokia-AV: Clean
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.3 tagged_above=-50.0 required=4.0 tests=AWL, HTML_50_60, HTML_MESSAGE, NO_REAL_NAME, UPPERCASE_25_50
X-Spam-Level: 
Subject: [Ietf-calsify] Cancel: Weekly Jabber Chat
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Wed, 29 Nov 2006 08:24:24 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7138F.AEF9F58B
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

QWZ0ZXIgc2tpcHBpbmcgYSB3ZWVrIGR1ZSB0byB0aGUgVVMgVGhhbmtzZ2l2aW5nIGhvbGlkYXks
IGxldCdzIGNvbnRpbnVlIG9uIG91ciB3ZWVrbHkgSmFiYmVyIGNoYXRzIGFnYWluLg0KDQpBZ2Vu
ZGE6DQoNCi0gQWdlbmRhIGJhc2gsIHNldHRpbmcgdXANCi0gRGlzY3Vzc2luZyB0aGUgcmVtYWlu
aW5nIG9wZW4gaXNzdWVzIHdpdGggUkZDIDI0NDViaXMuDQotIEFPQg0KDQpSZXNvdXJjZXM6DQoN
CkxpbmsgdG8gdGhlIENhbHNpZnkgV0cgaXNzdWUgdHJhY2tlcjoNCg0KaHR0cDovL29mY291cnNl
aW1yaWdodC5jb20vY2dpLWJpbi9yb3VuZHVwL2NhbHNpZnkvDQoNCkEgZ29vZCBwbGFjZSB0byBs
ZWFybiBtb3JlIGFib3V0IEphYmJlciBpcyBhdDoNCg0KaHR0cDovL3d3dy5qYWJiZXIub3JnDQoN
ClNlZSB5b3UgdGhlcmUuDQo=

------_=_NextPart_001_01C7138F.AEF9F58B
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMg
RXhjaGFuZ2UgU2VydmVyIHZlcnNpb24gNi41Ljc2NTAuMjEiPg0KPFRJVExFPkNhbmNlbDogV2Vl
a2x5IEphYmJlciBDaGF0PC9USVRMRT4NCjwvSEVBRD4NCjxCT0RZPg0KPCEtLSBDb252ZXJ0ZWQg
ZnJvbSB0ZXh0L3BsYWluIGZvcm1hdCAtLT4NCg0KPFA+PEZPTlQgU0laRT0yPkFmdGVyIHNraXBw
aW5nIGEgd2VlayBkdWUgdG8gdGhlIFVTIFRoYW5rc2dpdmluZyBob2xpZGF5LCBsZXQncyBjb250
aW51ZSBvbiBvdXIgd2Vla2x5IEphYmJlciBjaGF0cyBhZ2Fpbi48QlI+DQo8QlI+DQpBZ2VuZGE6
PEJSPg0KPEJSPg0KLSBBZ2VuZGEgYmFzaCwgc2V0dGluZyB1cDxCUj4NCi0gRGlzY3Vzc2luZyB0
aGUgcmVtYWluaW5nIG9wZW4gaXNzdWVzIHdpdGggUkZDIDI0NDViaXMuPEJSPg0KLSBBT0I8QlI+
DQo8QlI+DQpSZXNvdXJjZXM6PEJSPg0KPEJSPg0KTGluayB0byB0aGUgQ2Fsc2lmeSBXRyBpc3N1
ZSB0cmFja2VyOjxCUj4NCjxCUj4NCjxBIEhSRUY9Imh0dHA6Ly9vZmNvdXJzZWltcmlnaHQuY29t
L2NnaS1iaW4vcm91bmR1cC9jYWxzaWZ5LyI+aHR0cDovL29mY291cnNlaW1yaWdodC5jb20vY2dp
LWJpbi9yb3VuZHVwL2NhbHNpZnkvPC9BPjxCUj4NCjxCUj4NCkEgZ29vZCBwbGFjZSB0byBsZWFy
biBtb3JlIGFib3V0IEphYmJlciBpcyBhdDo8QlI+DQo8QlI+DQo8QSBIUkVGPSJodHRwOi8vd3d3
LmphYmJlci5vcmciPmh0dHA6Ly93d3cuamFiYmVyLm9yZzwvQT48QlI+DQo8QlI+DQpTZWUgeW91
IHRoZXJlLjwvRk9OVD4NCjwvUD4NCg0KPC9CT0RZPg0KPC9IVE1MPg==

------_=_NextPart_001_01C7138F.AEF9F58B
Content-class: urn:content-classes:calendarmessage
Content-Type: text/calendar;
	method=CANCEL;
	name="meeting.ics"
Content-Transfer-Encoding: 8bit

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft CDO for Microsoft Exchange
VERSION:2.0
BEGIN:VTIMEZONE
TZID:/softwarestudio.org/Olson_20011030_5/Europe/Helsinki
BEGIN:STANDARD
DTSTART:16010101T040000
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
X-MICROSOFT-CDO-MODPROPS;X-MODPARAM=1:BEGIN,dtend,dtstart,END,recurrence-id
DTSTAMP:20061129T082339Z
DTSTART;TZID="/softwarestudio.org/Olson_20011030_5/Europe/Helsinki":2006113
 0T180000
SUMMARY:Cancel: Weekly Jabber Chat
UID:20061127T090257Z-4863-1000-1-0@macbuster
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Calsify W
 G":MAILTO:[e-mail]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Eliot Lea
 r":MAILTO:[e-mail]
ORGANIZER;CN="Niemi Aki (Nokia-NRC/Helsinki)":MAILTO:[e-mail]
LOCATION:[e-mail]
DTEND;TZID="/softwarestudio.org/Olson_20011030_5/Europe/Helsinki":20061130T
 190000
RRULE:FREQ=DAILY;COUNT=4;INTERVAL=7
DESCRIPTION:After skipping a week due to the US Thanksgiving holiday\, let'
 s continue on our weekly Jabber chats again.\N\NAgenda:\N\N- Agenda bash\,
  setting up\N- Discussing the remaining open issues with RFC 2445bis.\N- A
 OB\N\NResources:\N\NLink to the Calsify WG issue tracker:\N\Nhttp://ofcour
 seimright.com/cgi-bin/roundup/calsify/\N\NA good place to learn more about
  Jabber is at:\N\Nhttp://www.jabber.org\N\NSee you there.
RECURRENCE-ID;TZID="/softwarestudio.org/Olson_20011030_5/Europe/Helsinki":2
 0061130T180000
SEQUENCE:2
PRIORITY:5
CLASS:
CREATED:20061127T070917Z
LAST-MODIFIED:20061127T070917Z
STATUS:CANCELLED
TRANSP:OPAQUE
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-OWNERAPPTID:-1
X-MICROSOFT-CDO-ATTENDEE-CRITICAL-CHANGE:20061127T070917Z
X-MICROSOFT-CDO-OWNER-CRITICAL-CHANGE:20061129T082339Z
END:VEVENT
END:VCALENDAR

------_=_NextPart_001_01C7138F.AEF9F58B--


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 50C237F5CE for <[e-mail]>; Mon, 27 Nov 2006 01:09:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 4196114225C for <[e-mail]>; Mon, 27 Nov 2006 01:09:10 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13070-06 for <[e-mail]>; Mon, 27 Nov 2006 01:09:08 -0800 (PST)
Received: from mgw-ext13.nokia.com (mgw-ext13.nokia.com [131.228.20.172]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 86EE2142257 for <[e-mail]>; Mon, 27 Nov 2006 01:09:08 -0800 (PST)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id kAR98hZK004835; Mon, 27 Nov 2006 11:08:56 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 27 Nov 2006 11:08:23 +0200
Received: from esebe106.NOE.Nokia.com ([172.21.143.51]) by esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 27 Nov 2006 11:08:22 +0200
Received: from 172.21.36.67 ([172.21.36.67]) by esebe106.NOE.Nokia.com ([172.21.143.51]) with Microsoft Exchange Server HTTP-DAV ;  Mon, 27 Nov 2006 09:08:22 +0000
Received: from macbuster by ESEBE106.noe.nokia.com; 27 Nov 2006 11:08:22 +0200
From: Aki Niemi <[e-mail]>
To: Calsify WG <[e-mail]>, Eliot Lear <[e-mail]>
Content-Type: text/calendar; name=calendar.ics; charset=utf-8; METHOD=REQUEST
Content-Transfer-Encoding: 7bit
Organization: Nokia-NRC/Helsinki
Date: Mon, 27 Nov 2006 11:08:22 +0200
Message-Id: <[e-mail]>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.1 
X-OriginalArrivalTime: 27 Nov 2006 09:08:22.0072 (UTC) FILETIME=[96648380:01C71203]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061127110856-11F47BB0-4023204B/0-0/0-1
X-Nokia-AV: Clean
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.4 tagged_above=-50.0 required=4.0 tests=AWL, UPPERCASE_50_75
X-Spam-Level: 
Subject: [Ietf-calsify] Weekly Jabber Chat
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 27 Nov 2006 09:09:10 -0000

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:-//Ximian//NONSGML Evolution Calendar//EN
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:/softwarestudio.org/Olson_20011030_5/Europe/Helsinki
X-LIC-LOCATION:Europe/Helsinki
BEGIN:DAYLIGHT
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
TZNAME:EEST
DTSTART:19700329T030000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
TZNAME:EET
DTSTART:19701025T040000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:20061127T090257Z-4863-1000-1-0@macbuster
DTSTAMP:20061127T090822Z
DTSTART;TZID=/softwarestudio.org/Olson_20011030_5/Europe/Helsinki:
 20061130T180000
DTEND;TZID=/softwarestudio.org/Olson_20011030_5/Europe/Helsinki:
 20061130T190000
SEQUENCE:2
SUMMARY:Weekly Jabber Chat
LOCATION:[e-mail]
DESCRIPTION:After skipping a week due to the US Thanksgiving holiday\, 
 let's continue on our weekly Jabber chats again.\n\nAgenda:\n\n- Agenda 
 bash\, setting up\n- Discussing the remaining open issues with RFC 
 2445bis.\n- AOB\n\nResources:\n\nLink to the Calsify WG issue tracker:
 \n\nhttp://ofcourseimright.com/cgi-bin/roundup/calsify/\n\nA good place 
 to learn more about Jabber is at:\n\nhttp://www.jabber.org\n\nSee you 
 there.
CLASS:PUBLIC
TRANSP:OPAQUE
ORGANIZER;CN=Aki Niemi:MAILTO:[e-mail]
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;
 RSVP=TRUE;CN=Aki Niemi;LANGUAGE=en:MAILTO:[e-mail]
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;
 RSVP=TRUE;CN=Calsify WG;LANGUAGE=en:MAILTO:[e-mail]
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;
 RSVP=TRUE;CN=Eliot Lear;LANGUAGE=en:MAILTO:[e-mail]
RRULE:FREQ=DAILY;COUNT=4;INTERVAL=7
END:VEVENT
END:VCALENDAR


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 2631E80BAE for <[e-mail]>; Fri, 17 Nov 2006 12:30:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 166FF14226C for <[e-mail]>; Fri, 17 Nov 2006 12:30:52 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06242-05 for <[e-mail]>; Fri, 17 Nov 2006 12:30:49 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id A8842142254 for <[e-mail]>; Fri, 17 Nov 2006 12:30:49 -0800 (PST)
Received: from rgmgw1.us.oracle.com (rgmgw1.us.oracle.com [138.1.186.110]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kAHKUkfs004131; Fri, 17 Nov 2006 13:30:46 -0700
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgmgw1.us.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id kAHKUjH5008045; Fri, 17 Nov 2006 13:30:46 -0700
Received: from bdesruis-ca.ca.oracle.com by rcsmt251.oracle.com with ESMTP id 2214144881163795387; Fri, 17 Nov 2006 13:29:47 -0700
Message-ID: <[e-mail]>
Date: Fri, 17 Nov 2006 15:29:44 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Alexey Melnikov <[e-mail]>
Subject: Re: [Ietf-calsify] Updated ABNF to address issues 52 & 56
References: <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.1 tagged_above=-50.0 required=4.0 tests=AWL, TW_YW,  TW_YY
X-Spam-Level: 
Cc: [e-mail]
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Fri, 17 Nov 2006 20:30:52 -0000

+1 (Obviously!)

Cheers,
Bernard

Alexey Melnikov wrote:
> Here is the updated ABNF (based on feedback from Bernard) to address
> 
> * Issue 52: (Section 4.3.10 Recurrence Rule: x-name rule part?)
> * Issue 56: (Section 4.3.10: Order of rule parts (ABNF issue))
> 
> recur           = recur-rule-part *( ";" recur-rule-part )
>                ;
>                ; The rule parts are not ordered in any
>                ; particular sequence
>                ;
>                ; The FREQ rule part is REQUIRED,
>                ; but MUST NOT occur more than once
>                ;
>                ; The UNTIL or COUNT rule parts are OPTIONAL,
>                ; but they MUST NOT occur in the same 'recur'
>                ;
>                ; The other rule parts are OPTIONAL,
>                ; but MUST NOT occur more than once
> 
> recur-rule-part = ( "FREQ" "=" freq )
>                / ( "UNTIL" "=" enddate )
>                / ( "COUNT" "=" 1*DIGIT )
>                / ( "INTERVAL" "=" 1*DIGIT )
>                / ( "BYSECOND" "=" byseclist )
>                / ( "BYMINUTE" "=" byminlist )
>                / ( "BYHOUR" "=" byhrlist )
>                / ( "BYDAY" "=" bywdaylist )
>                / ( "BYMONTHDAY" "=" bymodaylist )
>                / ( "BYYEARDAY" "=" byyrdaylist )
>                / ( "BYWEEKNO" "=" bywknolist )
>                / ( "BYMONTH" "=" bymolist )
>                / ( "BYSETPOS" "=" bysplist )
>                / ( "WKST" "=" weekday )
> 
> Regards,
> Alexey
> 
> _______________________________________________
> Ietf-calsify mailing list
> [e-mail]
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 0625280C2B for <[e-mail]>; Fri, 17 Nov 2006 10:58:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id D1FAF142276 for <[e-mail]>; Fri, 17 Nov 2006 10:58:24 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27749-10 for <[e-mail]>; Fri, 17 Nov 2006 10:58:23 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by laweleka.osafoundation.org (Postfix) with ESMTP id 39F5A14226F for <[e-mail]>; Fri, 17 Nov 2006 10:58:23 -0800 (PST)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <[e-mail]>; Fri, 17 Nov 2006 18:58:21 +0000
Message-ID: <[e-mail]>
Date: Fri, 17 Nov 2006 18:58:06 +0000
From: Alexey Melnikov <[e-mail]>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: [e-mail]
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.2 tagged_above=-50.0 required=4.0 tests=AWL, TW_YW,  TW_YY, UPPERCASE_25_50
X-Spam-Level: 
Subject: [Ietf-calsify] Updated ABNF to address issues 52 & 56
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Fri, 17 Nov 2006 18:58:26 -0000

Here is the updated ABNF (based on feedback from Bernard) to address

* Issue 52: (Section 4.3.10 Recurrence Rule: x-name rule part?)
* Issue 56: (Section 4.3.10: Order of rule parts (ABNF issue))

recur           = recur-rule-part *( ";" recur-rule-part )
                ;
                ; The rule parts are not ordered in any
                ; particular sequence
                ;
                ; The FREQ rule part is REQUIRED,
                ; but MUST NOT occur more than once
                ;
                ; The UNTIL or COUNT rule parts are OPTIONAL,
                ; but they MUST NOT occur in the same 'recur'
                ;
                ; The other rule parts are OPTIONAL,
                ; but MUST NOT occur more than once

recur-rule-part = ( "FREQ" "=" freq )
                / ( "UNTIL" "=" enddate )
                / ( "COUNT" "=" 1*DIGIT )
                / ( "INTERVAL" "=" 1*DIGIT )
                / ( "BYSECOND" "=" byseclist )
                / ( "BYMINUTE" "=" byminlist )
                / ( "BYHOUR" "=" byhrlist )
                / ( "BYDAY" "=" bywdaylist )
                / ( "BYMONTHDAY" "=" bymodaylist )
                / ( "BYYEARDAY" "=" byyrdaylist )
                / ( "BYWEEKNO" "=" bywknolist )
                / ( "BYMONTH" "=" bymolist )
                / ( "BYSETPOS" "=" bysplist )
                / ( "WKST" "=" weekday )

Regards,
Alexey



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 18ED2801FB for <[e-mail]>; Thu, 16 Nov 2006 15:39:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 09DB714227D for <[e-mail]>; Thu, 16 Nov 2006 15:39:39 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24795-09 for <[e-mail]>; Thu, 16 Nov 2006 15:39:36 -0800 (PST)
Received: from mo-p00-ob.rzone.de (mo-p00-ob.rzone.de [81.169.146.162]) by laweleka.osafoundation.org (Postfix) with ESMTP id 1C70D142267 for <[e-mail]>; Thu, 16 Nov 2006 15:39:35 -0800 (PST)
Received: from ollie.block.home (dslb-084-063-170-193.pools.arcor-ip.net [84.63.170.193]) by post.webmailer.de (mrclete mo51) (RZmta 3.1) with ESMTP id iAGNQ4X7069adC for <[e-mail]>; Fri, 17 Nov 2006 00:29:18 +0100 (MET)
Date: Fri, 17 Nov 2006 00:29:18 +0100 (MET)
From: Oliver Block <[e-mail]>
To: [e-mail]
Subject: Re: Issue 56: Re: [Ietf-calsify] Section 4.3.10 Recurrence Rule: Order of rule parts
User-Agent: KMail/1.7.1
References: <[e-mail]> <[e-mail]> <[e-mail]>
In-Reply-To: <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain;  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2006 23:39:39 -0000

Am Donnerstag, 16. November 2006 21:26 schrieben Sie:

> As far as I know, neither RRULE nor EXRULE allowed a comma separated
> list of RECUR values.

> First, if we don't want applications to specify more than one RRULE,
> I don't see the point of allowing properties of RECUR value type to
> specify multiple RECUR values.

Now I remember that discussion. I wasn't aware of it. 

> BTW, Alexey has been given the action item to come up with a new
> "recur" ABNF rule during the Jabber session today.

So it's in good hands then.:)

Regards,

Oliver

-- 
Leben ist mehr als ... 
<http://www.nak-nrw.de/index.php?id=72>


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 427BB801FB; Thu, 16 Nov 2006 13:45:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 30D58142279; Thu, 16 Nov 2006 13:45:26 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09913-03; Thu, 16 Nov 2006 13:45:24 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 7304214225A; Thu, 16 Nov 2006 13:45:24 -0800 (PST)
Received: from [17.101.32.44] ([17.101.32.44]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kAGLjIrc008597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Nov 2006 16:45:20 -0500
Date: Thu, 16 Nov 2006 16:45:13 -0500
From: Cyrus Daboo <[e-mail]>
To: CalDAV DevList <[e-mail]>
Message-ID: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-1.7 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED, AWL
X-Spam-Level: 
Cc: [e-mail]
Subject: [Ietf-calsify] Calendar availability specification
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2006 21:45:26 -0000

Hi folks,
I would like to draw your attention to:

<http://www.ietf.org/internet-drafts/draft-daboo-calendar-availability-00.txt>

This draft defines a new iCalendar component whose purpose is to convey 
user availability time periods. This differs from VFREEBUSY in that the 
components can specify repeating/recurring periods. So it is useful for 
defining regular "office hours" etc.

In addition to defining the new VAVAILABILITY component and explaining how 
it affects free-busy determination, the spec also describes how CalDAV can 
use these in its own free-busy operations.

Please note that discussion of this draft should take place on the 
ietf-caldav mailing list:

<mailto:[e-mail]>

So please reply there with any comments you might have.

This specification comes from work done in the Calendaring & Scheduling 
Consortium and is being submitted to the IETF for further discussion, 
review and hopefully on to standardization. This draft does have a 
dependency on the Calsify 2445bis work (specifically IANA registration of 
the new component), so it will follow that down standardization path.

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id E610280B17 for <[e-mail]>; Thu, 16 Nov 2006 13:22:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id D77E114227E for <[e-mail]>; Thu, 16 Nov 2006 13:22:55 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08242-08 for <[e-mail]>; Thu, 16 Nov 2006 13:22:55 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 08ABC142279 for <[e-mail]>; Thu, 16 Nov 2006 13:22:54 -0800 (PST)
Received: from [17.101.32.44] ([17.101.32.44]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kAGLMdQL008569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Nov 2006 16:22:44 -0500
Date: Thu, 16 Nov 2006 16:22:34 -0500
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Oliver Block <[e-mail]>
Subject: Re: Issue 56: Re: [Ietf-calsify] Section 4.3.10 Recurrence Rule: Order	of rule parts
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]> <[e-mail]> <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-1.7 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED, AWL
X-Spam-Level: 
Cc: [e-mail]
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2006 21:22:56 -0000

Hi Bernard,

--On November 16, 2006 3:26:48 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

> Second, I think it's was a terrible idea to use COMMA as a delimiter
> for multiple RECUR values, given that COMMA is already used as a
> delimiter for multi-valued rule parts.

The only way comma would work is if FREQ were required to be the first item 
in each rule, then you could tell when a new rule part started. But in any 
case we are not allowing multiple rules so it doesn't matter now.

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 7D10C802EE for <[e-mail]>; Thu, 16 Nov 2006 12:27:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 64B9D14225E for <[e-mail]>; Thu, 16 Nov 2006 12:27:35 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32501-05 for <[e-mail]>; Thu, 16 Nov 2006 12:27:35 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id DF3D4142254 for <[e-mail]>; Thu, 16 Nov 2006 12:27:34 -0800 (PST)
Received: from rgmgw3.us.oracle.com (rgmgw3.us.oracle.com [138.1.186.112]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kAGKRTPQ009864; Thu, 16 Nov 2006 13:27:29 -0700
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgmgw3.us.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id kAGIJQMI029305; Thu, 16 Nov 2006 13:27:28 -0700
Received: from bdesruis-ca.ca.oracle.com by rcsmt250.oracle.com with ESMTP id 2210410381163708810; Thu, 16 Nov 2006 13:26:50 -0700
Message-ID: <[e-mail]>
Date: Thu, 16 Nov 2006 15:26:48 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Oliver Block <[e-mail]>
Subject: Issue 56: Re: [Ietf-calsify] Section 4.3.10 Recurrence Rule: Order of rule parts
References: <[e-mail]> <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Whitelist: TRUE
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.1 tagged_above=-50.0 required=4.0 tests=AWL, TW_YW,  TW_YY
X-Spam-Level: 
Cc: [e-mail]
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2006 20:27:35 -0000

Oliver,

This issue is only about the order of *rule parts* in a RECUR value.
For instance, can one specify:
    RRULE:BYDAY=MO;FREQ=WEEKLY
or does FREQ really need to be the first rule part, that is:
    RRULE:FREQ=WEEKLY;BYDAY=MO

Now, we respect to comma separated list of RECUR values, the text
for the RECUR value type clearly specified "If the property permits".
As far as I know, neither RRULE nor EXRULE allowed a comma separated
list of RECUR values.

You'll notice that I removed the first sentence of the Description
field of the RECUR value type in draft -03 at the same time I
addressed the issue 13, 14, 24 and 25.

First, if we don't want applications to specify more than one RRULE,
I don't see the point of allowing properties of RECUR value type to
specify multiple RECUR values.

Second, I think it's was a terrible idea to use COMMA as a delimiter
for multiple RECUR values, given that COMMA is already used as a
delimiter for multi-valued rule parts.

BTW, Alexey has been given the action item to come up with a new
"recur" ABNF rule during the Jabber session today.

Cheers,
Bernard

Oliver Block wrote:
> Am Sonntag, 5. November 2006 23:24 schrieb Bernard Desruisseaux:
>> In section 4.3.10 Recurrence Rule of RFC 2445 it says:
>> I'm not sure how the "recur" rule should be rewritten.
> 
> from page 118:
>>     rrule      = "RRULE" rrulparam ":" recur CRLF
>>
>>     rrulparam  = *(";" xparam)
> 
> combined with text from page 42:
>>   Description: If the property permits, multiple "recur" values are
>>   specified by a COMMA character (US-ASCII decimal 44) separated list
>>   of values.
> 
> Result:
>>     rrule      = "RRULE" rrulparam ":" recur *("," recur) CRLF
>>
>>     rrulparam  = *(";" xparam)
> 
> 
> from page 42:
> 
>>  The rule parts are separated from each other by
>>   the SEMICOLON character (US-ASCII decimal 59).
> 
> from page 40:
> 
>>     recur      = "FREQ"=freq *( ...)
> 
> Result:
>> recur = rpart *( ";" rpart)
>>
>> rpart = "FREQ" "=" freq 
>>               ( ( ";" "UNTIL" "=" enddate ) /
>>                ( ";" "COUNT" "=" 1*DIGIT ) )
>>
>>                [ ";" "INTERVAL" "=" 1*DIGIT ]
>>                [ ";" "BYSECOND" "=" byseclist ]
>>                [ ";" "BYMINUTE" "=" byminlist ]
>>                [ ";" "BYHOUR" "=" byhrlist ]
>>                [ ";" "BYDAY" "=" bywdaylist ]
>>                [ ";" "BYMONTHDAY" "=" bymodaylist ]
>>                [ ";" "BYYEARDAY" "=" byyrdaylist ]
>>                [ ";" "BYWEEKNO" "=" bywknolist ]
>>                [ ";" "BYMONTH" "=" bymolist ]
>>                [ ";" "BYSETPOS" "=" bysplist ]
>>                [ ";" "WKST" "=" weekday ]
>>                *( ";" x-name "=" text )
>>
> 
> If UNTIL or COUNT are not to be required
> 
>>               ( ( ";" "UNTIL" "=" enddate ) /
>>                ( ";" "COUNT" "=" 1*DIGIT ) )
> 
> should be
> 
>>               *1( ( ";" "UNTIL" "=" enddate ) /
>>                     ( ";" "COUNT" "=" 1*DIGIT ) )
> 
> or
> 
>>               [ ( ";" "UNTIL" "=" enddate ) /
>>                ( ";" "COUNT" "=" 1*DIGIT ) ]
> 
> 
> Regards,
> 
> Oliver
>  
> 


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 7F8F680767 for <[e-mail]>; Thu, 16 Nov 2006 07:41:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 693B1142280 for <[e-mail]>; Thu, 16 Nov 2006 07:41:40 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13572-10 for <[e-mail]>; Thu, 16 Nov 2006 07:41:39 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by laweleka.osafoundation.org (Postfix) with ESMTP id 2BD3014227E for <[e-mail]>; Thu, 16 Nov 2006 07:41:39 -0800 (PST)
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-5.cisco.com with ESMTP; 16 Nov 2006 07:41:39 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kAGFfc7D019497 for <[e-mail]>; Thu, 16 Nov 2006 07:41:38 -0800
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id kAGFfcW4029284 for <[e-mail]>; Thu, 16 Nov 2006 07:41:38 -0800 (PST)
Received: from [212.254.247.4] ([10.61.65.207]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id kAGFRnWs000667 for <[e-mail]>; Thu, 16 Nov 2006 07:27:50 -0800
Message-ID: <[e-mail]>
Date: Thu, 16 Nov 2006 16:41:35 +0100
From: Eliot Lear <[e-mail]>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: "[e-mail]" <[e-mail]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=52; t=1163691698; x=1164555698; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=[e-mail]; z=From:=20Eliot=20Lear=20<[e-mail]> |Subject:=20reminder=3A=20jabber=20starts=20today=20in=2020=20minutes |Sender:=20; bh=37HmePtzoKQdvqre+2lDjgqBUC3kHm8J+Bpdf49v3PU=; b=TNuJvsi+NM2CsHmKUJ77a5f4U2ZvwOyg6lurTBFbe7kbECuDeRUvqHOhWgI5V6DARqiZcfc/ LqexHw4apFtK0L33itXwdARHkr4tz/TzL5F5vFnBTESV7wxrqNTt1i67;
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=52; t=1163690870; x=1164554870; c=relaxed/simple; s=oregon; h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;  d=cisco.com; i=[e-mail]; z=From:=20Eliot=20Lear=20<[e-mail]> |Subject:=20reminder=3A=20jabber=20starts=20today=20in=2020=20minutes |Sender:=20 |To:=20=[e-mail]=22=20<ietf-calsify@osafoundation .org>; bh=37HmePtzoKQdvqre+2lDjgqBUC3kHm8J+Bpdf49v3PU=; b=S3LL0mEDl0NXz6y/Gna3EeOlB7Koy1I9MUv6jTXkBmdzvDUGkBrnaWX07llAI5zBMugxVOdl X7b05pjOqjkwFERQEtAd5OfDsGWwx9jff0EXbmxfjfu43ZzLtNnTynHU;
Authentication-Results: sj-dkim-2; header.From=[e-mail]; dkim=pass (si g from cisco.com/sjdkim2002 verified; );  header.From=[e-mail]; dkim=pass ( sig from cisco.com/oregon verified; ); 
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.2 tagged_above=-50.0 required=4.0 tests=AWL, TO_ADDRESS_EQ_REAL
X-Spam-Level: 
Subject: [Ietf-calsify] reminder: jabber starts today in 20 minutes
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2006 15:41:40 -0000

That's 5:00pm CET, 8:00am PST.

Thanks!

Eliot


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 3767380C07 for <[e-mail]>; Thu, 16 Nov 2006 07:24:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 2919314226E for <[e-mail]>; Thu, 16 Nov 2006 07:24:52 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21521-01 for <[e-mail]>; Thu, 16 Nov 2006 07:24:51 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by laweleka.osafoundation.org (Postfix) with ESMTP id 7B52514225A for <[e-mail]>; Thu, 16 Nov 2006 07:24:51 -0800 (PST)
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-5.cisco.com with ESMTP; 16 Nov 2006 07:24:50 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id kAGFOoMd027366;  Thu, 16 Nov 2006 07:24:50 -0800
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id kAGFOoW4018112; Thu, 16 Nov 2006 07:24:50 -0800 (PST)
Received: from [212.254.247.4] ([10.61.65.207]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id kAGFB0w6032434; Thu, 16 Nov 2006 07:11:01 -0800
Message-ID: <[e-mail]>
Date: Thu, 16 Nov 2006 16:24:47 +0100
From: Eliot Lear <[e-mail]>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Jonathan Lennox <[e-mail]>
Subject: Re: [Ietf-calsify] DST discontinuities part 2: discontinuities for recurring event start times
References: <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=687; t=1163690690; x=1164554690; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=[e-mail]; z=From:=20Eliot=20Lear=20<[e-mail]> |Subject:=20Re=3A=20[Ietf-calsify]=20DST=20discontinuities=20part=202=3A= 20discontinuities=20for=0A=20recurring=20event=20start=20times |Sender:=20; bh=9wq7J+YuLPkpdsBWs4JRb+rEzhGsFNKP13qltxs1fDE=; b=X7KrwVzJevMeGyQzyPAJBhuKHM6zwZERVSTftqeJEOZMIX/EXA/Qtwshvc4kxx1UwBF9ppcQ P/6Yret7A3qShpQSIjasmHvY2agxbb2jZtCKUVBseMg3KVcjBufR9AJw;
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=687; t=1163689862; x=1164553862; c=relaxed/simple; s=oregon; h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;  d=cisco.com; i=[e-mail]; z=From:=20Eliot=20Lear=20<[e-mail]> |Subject:=20Re=3A=20[Ietf-calsify]=20DST=20discontinuities=20part=202=3A= 20discontinuities=20for=0A=20recurring=20event=20start=20times |Sender:=20 |To:=20Jonathan=20Lennox=20<[e-mail]>; bh=9wq7J+YuLPkpdsBWs4JRb+rEzhGsFNKP13qltxs1fDE=; b=R0DLOql5C8LyfC2gExYFPTqNGHhY86gW1dAEFLNl4w0fOMZKzCCTN+5YBYlrXQ7RitrJX5RB Oc/B+nKx5v338yUB3/0iSsvhXGUvM4vu5lsReWsgy5tjEPyIlQfbjEln;
Authentication-Results: sj-dkim-3; header.From=[e-mail]; dkim=pass (si g from cisco.com/sjdkim3002 verified; );  header.From=[e-mail]; dkim=pass ( sig from cisco.com/oregon verified; ); 
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.2 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Cc: Calsify WG <[e-mail]>
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2006 15:24:52 -0000

John,

> Issue 2 has to do with how you handle the case when a recurrence's
> start time falls within a discontinuity.
>
> I suggest that by default, the "naive" behavior should be followed: i.e.,
> events that would fall at non-existent times do not occur, and events that
> fall at repeated times occur twice.  Calendar authors that want other
> behaviors should use RDATE and EXDATE to get what they want.
>   

It may be illustrative to note that Vixie cron with the -s flag does not 
behave in this way because it is not what one would want or expect 
intuitively, at least by his estimation.  His changes only involve 
events that occur minutely or hourly.

Eliot


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id A86E080708 for <[e-mail]>; Thu, 16 Nov 2006 07:18:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 2BA9414226E for <[e-mail]>; Thu, 16 Nov 2006 07:18:58 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17330-09 for <[e-mail]>; Thu, 16 Nov 2006 07:18:57 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by laweleka.osafoundation.org (Postfix) with ESMTP id 91A6114225A for <[e-mail]>; Thu, 16 Nov 2006 07:18:57 -0800 (PST)
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-4.cisco.com with ESMTP; 16 Nov 2006 07:18:57 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id kAGFIvOh000556;  Thu, 16 Nov 2006 07:18:57 -0800
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id kAGFIuW4014167; Thu, 16 Nov 2006 07:18:56 -0800 (PST)
Received: from [212.254.247.4] ([10.61.65.207]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id kAGF58TY032228; Thu, 16 Nov 2006 07:05:09 -0800
Message-ID: <[e-mail]>
Date: Thu, 16 Nov 2006 16:18:55 +0100
From: Eliot Lear <[e-mail]>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Jonathan Lennox <[e-mail]>
Subject: Re: [Ietf-calsify] DST discontinuities part 1: date-times that fall in	discontinutities
References: <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=797; t=1163690337; x=1164554337; c=relaxed/simple; s=sjdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=[e-mail]; z=From:=20Eliot=20Lear=20<[e-mail]> |Subject:=20Re=3A=20[Ietf-calsify]=20DST=20discontinuities=20part=201=3A= 20date-times=20that=20fall=0A=20in=09discontinutities |Sender:=20; bh=IsTfT8AMxAtu+PFqi0nD0nxovtkgf6o0mMYvyH9W6E0=; b=iPZ3mbiAjXwzxaOZ+Gb+/Xt4r5gzybbJMQWRH3tuSyC8JYYGyiKnAAWzcAOwjjbPyStcfIgZ LWnOzjrXKHew3NUyKUAMVOb6McE/xbD/Ke3BfDTMvuX/HNy6zvjN8Vl9;
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=797; t=1163689509; x=1164553509; c=relaxed/simple; s=oregon; h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;  d=cisco.com; i=[e-mail]; z=From:=20Eliot=20Lear=20<[e-mail]> |Subject:=20Re=3A=20[Ietf-calsify]=20DST=20discontinuities=20part=201=3A= 20date-times=20that=20fall=0A=20in=09discontinutities |Sender:=20 |To:=20Jonathan=20Lennox=20<[e-mail]>; bh=IsTfT8AMxAtu+PFqi0nD0nxovtkgf6o0mMYvyH9W6E0=; b=O9JbcliKuVUwfy8jAUWOI4V53LfX44cTIdO7vsa0JCurYWa1evjqsSLmTaZU3uviDPR9c2OF qemslMDHdcs84jD/XCBSEcTtvtVON+S1xstMYSQxvmZ42imdMKeCQs3E;
Authentication-Results: sj-dkim-1; header.From=[e-mail]; dkim=pass (si g from cisco.com/sjdkim1002 verified; );  header.From=[e-mail]; dkim=pass ( sig from cisco.com/oregon verified; ); 
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.2 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Cc: Calsify WG <[e-mail]>
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2006 15:18:58 -0000

Jonathan Lennox wrote:
> In the meeting today, we brought up the issue of DST discontinuities for
> RRULEs, and Eliot asked for text to be sent to the mailing list.
>
> The first issue has to do with how you handle an ambiguous or nonexistent
> DATE-TIME value.  E.g. (assuming America/New_York describes the U.S. Eastern
> Time Zone) how do you handle the two cases
>
> DTSTART;TZID=America/New_York:20060402T023000 (which does not exist)
>
> DTSTART;TZID=America/New_York:20061029T013000 (which occurs twice)
>
> I would suggest that both these examples be forbidden.  For the latter case,
> clients MUST use UTC (or potentially, some other timezone which does not
> have a jump at that time) to describe the event.
>
>   
Chair hat off, I agree with your suggestion.

Eliot


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 4836C8092F for <[e-mail]>; Thu, 16 Nov 2006 04:34:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 386D614227D for <[e-mail]>; Thu, 16 Nov 2006 04:34:56 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25903-08 for <[e-mail]>; Thu, 16 Nov 2006 04:34:54 -0800 (PST)
Received: from mo-p00-ob.rzone.de (mo-p00-ob.rzone.de [81.169.146.162]) by laweleka.osafoundation.org (Postfix) with ESMTP id 9085B142271 for <[e-mail]>; Thu, 16 Nov 2006 04:34:54 -0800 (PST)
Received: from ollie.block.home (dslb-084-063-170-193.pools.arcor-ip.net [84.63.170.193]) by post.webmailer.de (mrclete mo39) (RZmta 3.1) with ESMTP id iAGBQGmd06979I for <[e-mail]>; Thu, 16 Nov 2006 13:29:39 +0100 (MET)
Date: Thu, 16 Nov 2006 13:29:39 +0100 (MET)
From: Oliver Block <[e-mail]>
To: [e-mail]
Subject: Re: [Ietf-calsify] Section 4.3.10 Recurrence Rule: Order of rule parts
User-Agent: KMail/1.7.1
References: <[e-mail]> <[e-mail]>
In-Reply-To: <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain;  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.1 tagged_above=-50.0 required=4.0 tests=AWL, TW_YW,  TW_YY, UPPERCASE_25_50
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2006 12:34:56 -0000

Am Donnerstag, 16. November 2006 12:59 schrieb Oliver Block:



> > recur = rpart *( ";" rpart)
> >
> > rpart = "FREQ" "=" freq
> >               ( ( ";" "UNTIL" "=" enddate ) /
> >                ( ";" "COUNT" "=" 1*DIGIT ) )
> >
> >                [ ";" "INTERVAL" "=" 1*DIGIT ]
> >                [ ";" "BYSECOND" "=" byseclist ]
> >                [ ";" "BYMINUTE" "=" byminlist ]
> >                [ ";" "BYHOUR" "=" byhrlist ]
> >                [ ";" "BYDAY" "=" bywdaylist ]
> >                [ ";" "BYMONTHDAY" "=" bymodaylist ]
> >                [ ";" "BYYEARDAY" "=" byyrdaylist ]
> >                [ ";" "BYWEEKNO" "=" bywknolist ]
> >                [ ";" "BYMONTH" "=" bymolist ]
> >                [ ";" "BYSETPOS" "=" bysplist ]
> >                [ ";" "WKST" "=" weekday ]
> >                *( ";" x-name "=" text )
>

There is a problem with the above. The semicolon should either appear in

> > recur = rpart *( ";" rpart)

or in

> > rpart = ...

Therefore I would change the above to

> > rpart = "FREQ" "=" freq
> >               ( ("UNTIL" "=" enddate ) /
> >                ( "COUNT" "=" 1*DIGIT ) )
> >
> >                [ "INTERVAL" "=" 1*DIGIT ]
> >                [ "BYSECOND" "=" byseclist ]
> >                [ "BYMINUTE" "=" byminlist ]
> >                [ "BYHOUR" "=" byhrlist ]
> >                [ "BYDAY" "=" bywdaylist ]
> >                [ "BYMONTHDAY" "=" bymodaylist ]
> >                [ "BYYEARDAY" "=" byyrdaylist ]
> >                [ "BYWEEKNO" "=" bywknolist ]
> >                [ "BYMONTH" "=" bymolist ]
> >                [ "BYSETPOS" "=" bysplist ]
> >                [ "WKST" "=" weekday ]
> >                *(x-name "=" text )

Regards,

OIiver

-- 
Leben ist mehr als ... 
<http://www.nak-nrw.de/index.php?id=71>


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id DF66180B0F for <[e-mail]>; Thu, 16 Nov 2006 04:04:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id D0029142279 for <[e-mail]>; Thu, 16 Nov 2006 04:04:15 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25103-04 for <[e-mail]>; Thu, 16 Nov 2006 04:04:13 -0800 (PST)
Received: from mo-p00-ob.rzone.de (mo-p00-ob.rzone.de [81.169.146.160]) by laweleka.osafoundation.org (Postfix) with ESMTP id 3049A14226C for <[e-mail]>; Thu, 16 Nov 2006 04:04:13 -0800 (PST)
Received: from ollie.block.home (dslb-084-063-170-193.pools.arcor-ip.net [84.63.170.193]) by post.webmailer.de (mrclete mo1) (RZmta 3.1) with ESMTP id iAGBiMYp068dbL for <[e-mail]>; Thu, 16 Nov 2006 12:59:12 +0100 (MET)
Date: Thu, 16 Nov 2006 12:59:12 +0100 (MET)
From: Oliver Block <[e-mail]>
To: [e-mail]
Subject: Re: [Ietf-calsify] Section 4.3.10 Recurrence Rule: Order of rule parts
User-Agent: KMail/1.7.1
References: <[e-mail]>
In-Reply-To: <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain;  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.1 tagged_above=-50.0 required=4.0 tests=AWL, TW_YW,  TW_YY
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2006 12:04:16 -0000

Am Sonntag, 5. November 2006 23:24 schrieb Bernard Desruisseaux:
> In section 4.3.10 Recurrence Rule of RFC 2445 it says:
> I'm not sure how the "recur" rule should be rewritten.

from page 118:
>
>     rrule      = "RRULE" rrulparam ":" recur CRLF
>
>     rrulparam  = *(";" xparam)

combined with text from page 42:
>
>   Description: If the property permits, multiple "recur" values are
>   specified by a COMMA character (US-ASCII decimal 44) separated list
>   of values.

Result:
>     rrule      = "RRULE" rrulparam ":" recur *("," recur) CRLF
>
>     rrulparam  = *(";" xparam)


from page 42:

>  The rule parts are separated from each other by
>   the SEMICOLON character (US-ASCII decimal 59).

from page 40:

>     recur      = "FREQ"=freq *( ...)

Result:
> recur = rpart *( ";" rpart)
>
> rpart = "FREQ" "=" freq 
>               ( ( ";" "UNTIL" "=" enddate ) /
>                ( ";" "COUNT" "=" 1*DIGIT ) )
>
>                [ ";" "INTERVAL" "=" 1*DIGIT ]
>                [ ";" "BYSECOND" "=" byseclist ]
>                [ ";" "BYMINUTE" "=" byminlist ]
>                [ ";" "BYHOUR" "=" byhrlist ]
>                [ ";" "BYDAY" "=" bywdaylist ]
>                [ ";" "BYMONTHDAY" "=" bymodaylist ]
>                [ ";" "BYYEARDAY" "=" byyrdaylist ]
>                [ ";" "BYWEEKNO" "=" bywknolist ]
>                [ ";" "BYMONTH" "=" bymolist ]
>                [ ";" "BYSETPOS" "=" bysplist ]
>                [ ";" "WKST" "=" weekday ]
>                *( ";" x-name "=" text )
>

If UNTIL or COUNT are not to be required

>               ( ( ";" "UNTIL" "=" enddate ) /
>                ( ";" "COUNT" "=" 1*DIGIT ) )

should be

>               *1( ( ";" "UNTIL" "=" enddate ) /
>                     ( ";" "COUNT" "=" 1*DIGIT ) )

or

>               [ ( ";" "UNTIL" "=" enddate ) /
>                ( ";" "COUNT" "=" 1*DIGIT ) ]


Regards,

Oliver
 

-- 
Leben ist mehr als ... 
<http://www.nak-nrw.de/index.php?id=72>


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 05D0080A77 for <[e-mail]>; Wed, 15 Nov 2006 07:13:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id EAD5514228D for <[e-mail]>; Wed, 15 Nov 2006 07:13:52 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12153-06 for <[e-mail]>; Wed, 15 Nov 2006 07:13:51 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 24470142286 for <[e-mail]>; Wed, 15 Nov 2006 07:13:51 -0800 (PST)
Received: from [17.101.32.44] ([17.101.32.44]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kAFFDggC032315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Nov 2006 10:13:45 -0500
Date: Wed, 15 Nov 2006 10:13:37 -0500
From: Cyrus Daboo <[e-mail]>
To: Reinhold Kainhofer <[e-mail]>, CALSIFY Mailinglist <[e-mail]>
Subject: Re: [Ietf-calsify] Another recurrence rule question
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-1.6 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED, AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Wed, 15 Nov 2006 15:13:53 -0000

Hi Reinhold,

--On November 15, 2006 3:19:41 PM +0100 Reinhold Kainhofer 
<[e-mail]> wrote:

> Another issue to be cleared in a possible clearing FAQ about RFC 2445.
>
> In a weekly recurrence rule, when exactly is the weekday (Monday,
> Tuesday,  etc.) taken from DTSTART and when not.
> In particular, take a recurrence rule:
>    RRULE:FREQ=WEEKLY
> This event recurs every week on the same weekday as DTSTART.
>
> Now, what about:
>   RRULE:FREQ=WEEKLY;BYMONTHDAY=15
> Does this event recur on every 15 of each month, regardless of the
> weekday, or  on every 15th of each month if it is the same weekday as
> DTSTART?
>
> In other words, does FREQ=WEEKLY always imply an implicit BYDAY=.. (value
> taken from DTSTART)?

I don't see why FREQ=WEEKLY should imply any implicit BYDAY= part. It just 
means repeat the first instance at 7 day intervals. It does not matter what 
day the first instance is. Of course repeating every 7 days means that you 
will always repeat on the same day of the week.

Remember: one change we have agreed upon is that the DTSTART must now match 
the RRULE. So if you did:

RRULE:FREQ=WEEKLY;BYMONTHDAY=15

The DTSTART would have to be the 15th of some month. The week day does not 
enter into it - other than the fact that that is the weekday for all 
instances. If you did:

RRULE:FREQ=WEEKLY;BYMONTHDAY=15;BYDAY=TU

then you would have to specific a DTSTART that was the 15th of some month 
AND a Tuesday.


-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id B2D9380A09 for <[e-mail]>; Wed, 15 Nov 2006 06:23:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id A37E8142285 for <[e-mail]>; Wed, 15 Nov 2006 06:23:59 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06523-03 for <[e-mail]>; Wed, 15 Nov 2006 06:23:59 -0800 (PST)
Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 0B2A2142282 for <[e-mail]>; Wed, 15 Nov 2006 06:23:58 -0800 (PST)
Received: from rgmgw2.us.oracle.com (rgmgw2.us.oracle.com [138.1.186.111]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id kAFENtWp002113; Wed, 15 Nov 2006 08:23:55 -0600
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgmgw2.us.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id kAFDvXaQ030067; Wed, 15 Nov 2006 07:23:54 -0700
Received: from bdesruis-ca.ca.oracle.com by rcsmt250.oracle.com with ESMTP id 2205538541163600601; Wed, 15 Nov 2006 07:23:21 -0700
Message-ID: <[e-mail]>
Date: Wed, 15 Nov 2006 09:23:16 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Mike Douglass <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.1.2 Multiple Values: LANGUAGE parameter
References: <[e-mail]> <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Whitelist: TRUE
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Cc: Calsify WG <[e-mail]>
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Wed, 15 Nov 2006 14:23:59 -0000

Hi Mike,

We've had this discussion at the last WG meeting in San Diego.

The conclusion was that iCalendar wasn't designed to allow one to
specify property values and property parameter values in multiple
languages, and that one should use other mechanisms to provide
iCalendar data in multiple languages (e.g., multipart/alternative
with iMIP, HTTP content negotiation (RFC2295) with CalDAV).

Cheers,
Bernard

Mike Douglass wrote:
> Would it make sense if all properties that can take a language parameter 
> be allowed to appear multiple times?
> 
> Currently I can internally support multiple languages for a vevent 
> description but there's no legal way to export the entire data as ics.
> 
> There's also no way via caldav for example to update more than one 
> language in a single request
> 
> RFC 2445 has the following properties with a language param:
> 
> ATTENDEE    (cn param)
> CATEGORIES
> COMMENT
> CONTACT
> DESCRIPTION
> LOCATION
> ORGANIZER   (cn param)
> REQUEST-STATUS
> RESOURCES
> SUMMARY
> TZNAME
> 
> 
> 
> Bernard Desruisseaux wrote:
>> RFC 2445 allows some properties of TEXT value type to be specified
>> multiple times. In some cases (e.g., "TZNAME") it is specified that
>> the property can be specified more than once for specifying multiple
>> language variants of the property value.
>>
>> I think section 4.1.2 Multiple Values should clarify how the
>> "LANGUAGE" parameter should be handled with multi-valued TEXT
>> properties.
>>
>> For instance, in a "VJOURNAL" calendar component, can I have two
>> "DESCRIPTION" with "LANGUAGE=en", but only one "DESCRIPTION" with
>> "LANGUAGE=fr"?  If so, should my client only display the one in
>> French, or should it display all three values?
>>
>> Currently, I think it should display all three values...
>>
>> Cheers,
>> Bernard
>> _______________________________________________
>> Ietf-calsify mailing list
>> [e-mail]
>> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>>
>>
> 


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 3B74480A09 for <[e-mail]>; Wed, 15 Nov 2006 06:19:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 2C2F714228F for <[e-mail]>; Wed, 15 Nov 2006 06:19:51 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02802-04 for <[e-mail]>; Wed, 15 Nov 2006 06:19:48 -0800 (PST)
Received: from doob.fam.tuwien.ac.at (doob.fam.tuwien.ac.at [128.130.51.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 49B37142282 for <[e-mail]>; Wed, 15 Nov 2006 06:19:48 -0800 (PST)
Received: from curie.fam.tuwien.ac.at ([e-mail] [128.130.51.116]) by doob.fam.tuwien.ac.at (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id kAFEJhFC016998 for <[e-mail]>; Wed, 15 Nov 2006 15:19:45 +0100
From: Reinhold Kainhofer <[e-mail]>
Organization: FAM, Vienna University of Technology
To: CALSIFY Mailinglist <[e-mail]>
Date: Wed, 15 Nov 2006 15:19:41 +0100
User-Agent: KMail/1.9.5
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.2 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Another recurrence rule question
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Wed, 15 Nov 2006 14:19:51 -0000

Hi all,

Another issue to be cleared in a possible clearing FAQ about RFC 2445.

In a weekly recurrence rule, when exactly is the weekday (Monday, Tuesday, 
etc.) taken from DTSTART and when not.
In particular, take a recurrence rule:
   RRULE:FREQ=WEEKLY
This event recurs every week on the same weekday as DTSTART.

Now, what about:
  RRULE:FREQ=WEEKLY;BYMONTHDAY=15
Does this event recur on every 15 of each month, regardless of the weekday, or 
on every 15th of each month if it is the same weekday as DTSTART?

In other words, does FREQ=WEEKLY always imply an implicit BYDAY=.. (value 
taken from DTSTART)?

Cheers,
Reinhold
-- 
------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: [e-mail], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 03FB980A2A for <[e-mail]>; Wed, 15 Nov 2006 06:01:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id E8CF214228F for <[e-mail]>; Wed, 15 Nov 2006 06:01:47 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00492-06 for <[e-mail]>; Wed, 15 Nov 2006 06:01:46 -0800 (PST)
Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 741D814228B for <[e-mail]>; Wed, 15 Nov 2006 06:01:46 -0800 (PST)
Received: from rgmgw1.us.oracle.com (rgmgw1.us.oracle.com [138.1.186.110]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id kAFE1dI3014477; Wed, 15 Nov 2006 08:01:39 -0600
Received: from rcsmt251.oracle.com (rcsmt251.oracle.com [148.87.90.196]) by rgmgw1.us.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id kAFDmNEg011179; Wed, 15 Nov 2006 07:01:38 -0700
Received: from bdesruis-ca.ca.oracle.com by rcsmt250.oracle.com with ESMTP id 2205508621163599266; Wed, 15 Nov 2006 07:01:06 -0700
Message-ID: <[e-mail]>
Date: Wed, 15 Nov 2006 09:01:00 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Oliver Block <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.3.10 Recurrence Rule: Order of rule parts
References: <[e-mail]> <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Whitelist: TRUE
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Cc: [e-mail]
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Wed, 15 Nov 2006 14:01:48 -0000

Oliver Block wrote:
> Am Sonntag, 5. November 2006 23:24 schrieb Bernard Desruisseaux:
>> In section 4.3.10 Recurrence Rule of RFC 2445 it says:
>>  > The rule parts are not ordered in any particular sequence.
>>
>> On the other hand, the way the ABNF of the "recur" rule is
>> written, the "FREQ" rule should always appear first.
> 
> Some RFC's explicitly say that text takes precedence over ABNF. That could 
> also be applied here.

It is my understanding that the text takes precedence over the ABNF.
It wouldn't hurt to state it clearly in the document.

> 
>> I'm not sure how the "recur" rule should be rewritten.
>> Any help appreciated...
> 
> I would say that there is a typo in it
> 
>> recur = "FREQ" = freq *( ...)
> 
> should IMHO be
> 
> recur = "FREQ" "=" freq *( ...)

Yep.  It's already fixed in draft -03.

Cheers,
Bernard

> 
> Regards,
> 
> Oliver
> 


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 56BFC809A5 for <[e-mail]>; Wed, 15 Nov 2006 05:32:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 4919B142288 for <[e-mail]>; Wed, 15 Nov 2006 05:32:17 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29364-09 for <[e-mail]>; Wed, 15 Nov 2006 05:32:15 -0800 (PST)
Received: from mgw-ext13.nokia.com (mgw-ext13.nokia.com [131.228.20.172]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 76473142286 for <[e-mail]>; Wed, 15 Nov 2006 05:32:15 -0800 (PST)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id kAFC4ag7014548 for <[e-mail]>; Wed, 15 Nov 2006 14:07:01 +0200
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 15 Nov 2006 14:05:43 +0200
Received: from [172.21.36.67] ([172.21.36.67]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 15 Nov 2006 14:05:43 +0200
Subject: Reminder: calsify Jabber session tomorrow (was: Re: [Ietf-calsify] Jabber session next week)
From: Aki Niemi <[e-mail]>
To: [e-mail]
In-Reply-To: <[e-mail]>
References: <[e-mail]>
Content-Type: text/plain
Organization: Nokia-NRC/Helsinki
Date: Wed, 15 Nov 2006 14:05:42 +0200
Message-Id: <[e-mail]>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Nov 2006 12:05:43.0325 (UTC) FILETIME=[601DDCD0:01C708AE]
X-Nokia-AV: Clean
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.4 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Wed, 15 Nov 2006 13:32:17 -0000

As a remainder, we have scheduled a jabber chat for tomorrow, Nov 16, at
17:00 CET / 11:00 EST / 8:00am PST.

Send me a note if you plan to attend. 

Cheers,
Aki

ti, 2006-11-07 kello 14:29 -0800, ext Aki Niemi kirjoitti:
> All,
> 
> During yesterday's WG meeting here in sunny California, we decided to
> continue with our weekly chat sessions.
> 
> However, the usual time was difficult for some, so we decided to propose
> a better one. Does Thursday, November 16, at 17:00 CET / 11:00 EST /
> 8:00am PST work for everyone?
> 
> Send me a note if this works for you; I'll send a calendar invitation to
> this list as well.
> 
> Cheers,
> Aki
> 
> 
> 
> _______________________________________________
> Ietf-calsify mailing list
> [e-mail]
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id D8EF6808BB for <[e-mail]>; Tue, 14 Nov 2006 07:54:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id CAEF114227E for <[e-mail]>; Tue, 14 Nov 2006 07:54:50 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09424-03 for <[e-mail]>; Tue, 14 Nov 2006 07:54:48 -0800 (PST)
Received: from mo-p06-ob.rzone.de (mo-p06-ob.rzone.de [81.169.146.184]) by laweleka.osafoundation.org (Postfix) with ESMTP id DA3A214227D for <[e-mail]>; Tue, 14 Nov 2006 07:54:47 -0800 (PST)
Received: from ollie.block.home (dslb-084-063-166-248.pools.arcor-ip.net [84.63.166.248]) by post.webmailer.de (fondel mo6) (RZmta 3.1) with ESMTP id iAEFBDW902730Q for <[e-mail]>; Tue, 14 Nov 2006 16:49:29 +0100 (MET)
Date: Tue, 14 Nov 2006 16:49:29 +0100 (MET)
From: Oliver Block <[e-mail]>
To: [e-mail]
Subject: Re: [Ietf-calsify] Section 4.3.10 Recurrence Rule: Order of rule parts
User-Agent: KMail/1.7.1
References: <[e-mail]>
In-Reply-To: <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain;  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Tue, 14 Nov 2006 15:54:51 -0000

Am Sonntag, 5. November 2006 23:24 schrieb Bernard Desruisseaux:
> In section 4.3.10 Recurrence Rule of RFC 2445 it says:
>  > The rule parts are not ordered in any particular sequence.
>
> On the other hand, the way the ABNF of the "recur" rule is
> written, the "FREQ" rule should always appear first.

Some RFC's explicitly say that text takes precedence over ABNF. That could 
also be applied here.

> I'm not sure how the "recur" rule should be rewritten.
> Any help appreciated...

I would say that there is a typo in it

> recur = "FREQ" = freq *( ...)

should IMHO be

recur = "FREQ" "=" freq *( ...)

Regards,

Oliver

-- 
Leben ist mehr als ... 
<http://www.nak-nrw.de/index.php?id=72>


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id BE5FF80813 for <[e-mail]>; Tue, 14 Nov 2006 06:20:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id AF9381422C1 for <[e-mail]>; Tue, 14 Nov 2006 06:20:20 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22226-02 for <[e-mail]>; Tue, 14 Nov 2006 06:20:18 -0800 (PST)
Received: from smtp5.server.rpi.edu (smtp5.server.rpi.edu [128.113.2.225]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id BA83A1422BB for <[e-mail]>; Tue, 14 Nov 2006 06:20:17 -0800 (PST)
Received: from [128.113.124.129] (crustacean-01.dynamic.rpi.edu [128.113.124.129]) by smtp5.server.rpi.edu (8.13.1/8.13.1) with ESMTP id kAEEKFjf007978 for <[e-mail]>; Tue, 14 Nov 2006 09:20:15 -0500
Message-ID: <[e-mail]>
Date: Tue, 14 Nov 2006 09:20:33 -0500
From: Mike Douglass <[e-mail]>
User-Agent: Thunderbird 1.5.0.5 (X11/20060808)
MIME-Version: 1.0
Cc: Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.1.2 Multiple Values: LANGUAGE parameter
References: <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-CanItPRO-Stream: default
X-RPI-SA-Score: undef - spam-scanning disabled
X-Scanned-By: CanIt (www . canit . ca)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.3 tagged_above=-50.0 required=4.0 tests=AWL, MISSING_HEADERS
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Tue, 14 Nov 2006 14:20:20 -0000

Would it make sense if all properties that can take a language parameter 
be allowed to appear multiple times?

Currently I can internally support multiple languages for a vevent 
description but there's no legal way to export the entire data as ics.

There's also no way via caldav for example to update more than one 
language in a single request

 RFC 2445 has the following properties with a language param:

 ATTENDEE    (cn param)
 CATEGORIES
 COMMENT
 CONTACT
 DESCRIPTION
 LOCATION
 ORGANIZER   (cn param)
 REQUEST-STATUS
 RESOURCES
 SUMMARY
 TZNAME



Bernard Desruisseaux wrote:
> RFC 2445 allows some properties of TEXT value type to be specified
> multiple times. In some cases (e.g., "TZNAME") it is specified that
> the property can be specified more than once for specifying multiple
> language variants of the property value.
>
> I think section 4.1.2 Multiple Values should clarify how the
> "LANGUAGE" parameter should be handled with multi-valued TEXT
> properties.
>
> For instance, in a "VJOURNAL" calendar component, can I have two
> "DESCRIPTION" with "LANGUAGE=en", but only one "DESCRIPTION" with
> "LANGUAGE=fr"?  If so, should my client only display the one in
> French, or should it display all three values?
>
> Currently, I think it should display all three values...
>
> Cheers,
> Bernard
> _______________________________________________
> Ietf-calsify mailing list
> [e-mail]
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>
>

-- 

Mike Douglass                           [e-mail]
Senior Systems Programmer
Communication & Collaboration Technologies      518 276 6780(voice) 2809
(fax)
Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 4F3B4809A1 for <[e-mail]>; Tue,  7 Nov 2006 21:01:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 415901422E9 for <[e-mail]>; Tue,  7 Nov 2006 21:01:59 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07552-08 for <[e-mail]>; Tue, 7 Nov 2006 21:01:57 -0800 (PST)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by laweleka.osafoundation.org (Postfix) with ESMTP id 499431422A8 for <[e-mail]>; Tue,  7 Nov 2006 21:01:57 -0800 (PST)
Received: by nf-out-0910.google.com with SMTP id k27so373009nfc for <[e-mail]>; Tue, 07 Nov 2006 21:01:56 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hOLaXSTupjsnzvsVNSJ5TkEwKMFm30gPKxUsiVlM7npjnWZCWXnz0PwYzOCA8vVsNqQw8R+0tJu7UvRR0eaA505HtCp/KAL2Wkmldj598vP3Rpmp1JFlE55gQx0c2iGMdOC1uxgQABNN4+03G/Ek3lUFafEoXByuHNhnhpxkPUg=
Received: by 10.82.111.8 with SMTP id j8mr1645969buc.1162962115907; Tue, 07 Nov 2006 21:01:55 -0800 (PST)
Received: by 10.82.175.5 with HTTP; Tue, 7 Nov 2006 21:01:55 -0800 (PST)
Message-ID: <[e-mail]>
Date: Tue, 7 Nov 2006 21:01:55 -0800
From: "Mike Samuel" <[e-mail]>
To: "Jonathan Lennox" <[e-mail]>
Subject: Re: [Ietf-calsify] BYSETPOS and contracting BY* rules
In-Reply-To: <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.1 tagged_above=-50.0 required=4.0 tests=RCVD_BY_IP
X-Spam-Level: 
Cc: Calsify WG <[e-mail]>
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: [e-mail]
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Wed, 08 Nov 2006 05:01:59 -0000

On 06/11/06, Jonathan Lennox <[e-mail]> wrote:
> In a hallway discussion today, I happened to remember another ambiguity in
> the iCalendar spec, which was brought up back on the old ietf-calendar
> mailing list but not, I think, ever resolved.
>
> The issue is that BYSETPOS is specified only as
>
>     The BYSETPOS rule part specifies a COMMA character (US-ASCII
>     decimal 44) separated list of values which corresponds to the nth
>     occurrence within the set of events specified by the rule.
>
> and the meaning of "the set of events specified by the rule" is very
> unclear.
>
> Particularly, the case that none of the RFC 2445 examples illustrates is
> what happens when BYSETPOS is used in conjunction with contracting BY*
> rules, i.e. BY* rules describing intervals larger than the FREQ.
>
> The examples I came up with back in June 2001 (see the thread starting at
> <http://www.imc.org/ietf-calendar/mail-archive/thrd11.html#01781> if you
> really care about all the gory details) were:
>
>        RRULE:DTSTART;TZID=America/New_York:20010401T090000
>        RECUR:FREQ=WEEKLY;BYMONTH=4,6;BYDAY=FR;BYSETPOS=-1
>
>        RRULE:DTSTART;TZID=America/New_York:20010401T090000
>        RECUR:FREQ=MONTHLY;BYMONTH=4,6;BYDAY=FR;BYSETPOS=-1
>
>        RRULE:DTSTART;TZID=America/New_York:20010401T090000
>        RECUR:FREQ=YEARLY;BYMONTH=4,6;BYDAY=FR;BYSETPOS=-1
>
> My proposal at the time was that these mean, respectively, "the last Friday
> of the week, in April and June" (i.e. "Fridays in April and June", with
> BYSETPOS irrelevant); "the last Friday of April, and the last Friday of
> June"; and "the last Friday of (April or June)" (i.e., given DTSTART, "the
> last Friday of June").
>
> I still think this is right, but at the time not everyone agreed.
>
> (Note that these examples don't obey the new "DTSTART must be a set member"
> constraint.  It's an interesting question how to obey that for rules that
> contain "BYSETPOS=-1".)
>
> Eric Busboom's 2445 revision draft at the time defined this by saying
>
>        BYSETPOS operates on a set of events in one interval of the
>        recurrence rule. For a WEEKLY rule, the interval is one week, for a
>        MONTHLY rule, one month, and for a YEARLY rule, one year.
>
> This wording seems not to have made it into the current 2445bis draft.
>
> How do existing CUAs (if they implement BYSETPOS at all) interpret my three
> examples above?  Do people agree with my suggested interpretation?

Google Calendar will generate each Friday in April and June for
FREQ=WEEKLY;BYMONTH=4,6;BYDAY=FR;BYSETPOS=-1

It applies the BYSETPOS to each period, so each week independently in
this case..  Since the set of Fridays in a given week has cardinality
1, the BYSETPOS has no effect.


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 34F07810AE for <[e-mail]>; Tue,  7 Nov 2006 20:56:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 268591422E9 for <[e-mail]>; Tue,  7 Nov 2006 20:56:05 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12314-02 for <[e-mail]>; Tue, 7 Nov 2006 20:56:04 -0800 (PST)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by laweleka.osafoundation.org (Postfix) with ESMTP id 4D48D1422E7 for <[e-mail]>; Tue,  7 Nov 2006 20:56:04 -0800 (PST)
Received: by nf-out-0910.google.com with SMTP id k27so371637nfc for <[e-mail]>; Tue, 07 Nov 2006 20:56:03 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LoVNMrnFaFf0l8Rfhuay9u0FVOfLVUVh6sQ6UPK2k9081+W/VZoVO9+MmPFhekXHcLpUnkktRXTXOo2v12lOKaKViBsWG7KyN1YkKi+DfzCSIxOUzsZ0NqQSGr2w8lf60B9LNEQj3+Zfpc0QzyNGMsdF05VBHJOw05dmmd0Ss+U=
Received: by 10.82.111.8 with SMTP id j8mr1645328buc.1162961762713; Tue, 07 Nov 2006 20:56:02 -0800 (PST)
Received: by 10.82.175.5 with HTTP; Tue, 7 Nov 2006 20:56:02 -0800 (PST)
Message-ID: <[e-mail]>
Date: Tue, 7 Nov 2006 20:56:02 -0800
From: "Mike Samuel" <[e-mail]>
To: "Jonathan Lennox" <[e-mail]>
Subject: Re: [Ietf-calsify] BYDAY integers with other BY* rules (was: BYSETPOS and contracting BY* rules)
In-Reply-To: <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <[e-mail]> <[e-mail]> <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.1 tagged_above=-50.0 required=4.0 tests=RCVD_BY_IP
X-Spam-Level: 
Cc: [e-mail]
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: [e-mail]
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Wed, 08 Nov 2006 04:56:05 -0000

On 07/11/06, Jonathan Lennox <[e-mail]> wrote:
> On Tuesday, November 7 2006, "Reinhold Kainhofer" wrote to "[e-mail]" saying:
>
> > AFAIU RFC 2445, the -1FR means the last friday in the set of dates that match
> > the rule evaluation so far. Thus, I get the same results as with BYSETPOS:
>
> I've always agreed with your second interpretation of RFC 2445: the numbers
> in the BYDAY rule refer to the period of time described by the FREQ.  "-1FR"
> means the last Friday of the month in a MONTHLY rule, and the last Friday of
> the year in a YEARLY rule.
>
> This seems to me to be the most straightforward reading of the BYDAY
> definition:
>
>       Each BYDAY value can also be preceded by a positive (+n) or
>       negative (-n) integer.  If present, this indicates the nth
>       occurrence of the specific day within the MONTHLY or YEARLY RRULE.
>       For example, within a MONTHLY rule, +1MO (or simply 1MO)
>       represents the first Monday within the month, whereas -1MO
>       represents the last Monday of the month.  If an integer modifier
>       is not present, it means all days of this type within the
>       specified frequency.  For example, within a MONTHLY rule, MO
>       represents all Mondays within the month.
>
> That would indeed mean that the other BY* rules in the rule aren't relevant
> to the interpretation of BYDAY, and that the order of interpretation of BY*
> rules other than BYSETPOS isn't important.
>
> Unfortunately, this interpretation is directly contradicted by RFC 2445's
> VTIMEZONE example, which describes US-Eastern DST transitions as
>
>         RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
>

> I've always interpreted this VTIMEZONE example as a bug in the spec, but I
> see how it can make sense if BYDAY integers are interpreted as being like
> BYSETPOS.
>
> What do other implementations do?

Google Calendar treats this as the last Sunday of the year, if it
happens to fall in October, which it never can, so this recurrence
will generate no results.


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id AE1BE80D50 for <[e-mail]>; Tue,  7 Nov 2006 14:33:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 572431422FD for <[e-mail]>; Tue,  7 Nov 2006 14:33:47 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11894-08 for <[e-mail]>; Tue, 7 Nov 2006 14:33:47 -0800 (PST)
Received: from mgw-ext11.nokia.com (mgw-ext11.nokia.com [131.228.20.170]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id A0B241422EA for <[e-mail]>; Tue,  7 Nov 2006 14:33:46 -0800 (PST)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext11.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id kA7MXejq005003; Wed, 8 Nov 2006 00:33:42 +0200
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 8 Nov 2006 00:33:41 +0200
Received: from [10.162.253.76] ([10.162.253.76]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);  Wed, 8 Nov 2006 00:33:40 +0200
From: Aki Niemi <[e-mail]>
To: [e-mail], Eliot Lear <[e-mail]>
Content-Type: text/calendar; name=calendar.ics; charset=utf-8; METHOD=REQUEST
Organization: Nokia-NRC/Helsinki
Date: Tue, 07 Nov 2006 22:33:35 +0000
Message-Id: <[e-mail]>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Nov 2006 22:33:40.0597 (UTC) FILETIME=[C6375250:01C702BC]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061108003342-122C6BB0-3D4EF648/0-0/0-1
X-Nokia-AV: Clean
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.4 tagged_above=-50.0 required=4.0 tests=AWL, UPPERCASE_50_75
X-Spam-Level: 
Subject: [Ietf-calsify] Calsify Jabber chat session
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2006 22:33:47 -0000

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:-//Ximian//NONSGML Evolution Calendar//EN
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:/softwarestudio.org/Olson_20011030_5/Europe/Helsinki
X-LIC-LOCATION:Europe/Helsinki
BEGIN:DAYLIGHT
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
TZNAME:EEST
DTSTART:19700329T030000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
TZNAME:EET
DTSTART:19701025T040000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:20061107T220248Z-6983-1000-1-0@macbuster
DTSTAMP:20061107T223333Z
DTSTART;TZID=/softwarestudio.org/Olson_20011030_5/Europe/Helsinki:
 20061116T180000
DTEND;TZID=/softwarestudio.org/Olson_20011030_5/Europe/Helsinki:
 20061116T190000
SEQUENCE:5
SUMMARY:Calsify Jabber chat session
LOCATION:[e-mail]
CLASS:PUBLIC
ORGANIZER;CN=Aki Niemi:MAILTO:[e-mail]
CREATED:20061107T222919
LAST-MODIFIED:20061107T223248
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
TRANSP:OPAQUE
DESCRIPTION:Please RSVP to me either using iTIP or via email.\n\nAgenda:
 \n\nDiscussing the remaining open issues.\n\nResources:\n\nLink to the 
 Calsify WG issue tracker:\n\nhttp:
 //ofcourseimright.com/cgi-bin/roundup/calsify/\n\nA good place to learn 
 more about Jabber is at:\n\nhttp://www.jabber.org\n\nSee you there.
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;
 RSVP=TRUE;CN=Aki Niemi;LANGUAGE=en:MAILTO:[e-mail]
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;
 RSVP=TRUE;LANGUAGE=en:MAILTO:[e-mail]
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;
 RSVP=TRUE;CN=Eliot Lear;LANGUAGE=en:MAILTO:[e-mail]
END:VEVENT
END:VCALENDAR



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 3C47C80CEA for <[e-mail]>; Tue,  7 Nov 2006 14:29:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 2DCD31422FD for <[e-mail]>; Tue,  7 Nov 2006 14:29:24 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08723-10 for <[e-mail]>; Tue, 7 Nov 2006 14:29:22 -0800 (PST)
Received: from mgw-ext13.nokia.com (mgw-ext13.nokia.com [131.228.20.172]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 7555F1422FE for <[e-mail]>; Tue,  7 Nov 2006 14:29:22 -0800 (PST)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id kA7MTHFK029542 for <[e-mail]>; Wed, 8 Nov 2006 00:29:20 +0200
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 8 Nov 2006 00:29:09 +0200
Received: from [10.162.253.76] ([10.162.253.76]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);  Wed, 8 Nov 2006 00:29:09 +0200
Message-ID: <[e-mail]>
Date: Tue, 07 Nov 2006 14:29:05 -0800
From: Aki Niemi <[e-mail]>
Organization: Nokia-NRC/Helsinki
User-Agent: Thunderbird 1.5.0.7 (X11/20060918)
MIME-Version: 1.0
To: [e-mail]
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Nov 2006 22:29:09.0846 (UTC) FILETIME=[24D5FF60:01C702BC]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061108002920-6FB5ABB0-0AE6F9DD/0-0/0-1
X-Nokia-AV: Clean
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.4 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Jabber session next week
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2006 22:29:24 -0000

All,

During yesterday's WG meeting here in sunny California, we decided to
continue with our weekly chat sessions.

However, the usual time was difficult for some, so we decided to propose
a better one. Does Thursday, November 16, at 17:00 CET / 11:00 EST /
8:00am PST work for everyone?

Send me a note if this works for you; I'll send a calendar invitation to
this list as well.

Cheers,
Aki





Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 1CE3F810B8 for <[e-mail]>; Tue,  7 Nov 2006 08:45:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 0E3941422D0 for <[e-mail]>; Tue,  7 Nov 2006 08:45:11 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23703-07 for <[e-mail]>; Tue, 7 Nov 2006 08:45:09 -0800 (PST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 76B871422B3 for <[e-mail]>; Tue,  7 Nov 2006 08:45:09 -0800 (PST)
Received: from metro-north.cs.columbia.edu (metro-north.cs.columbia.edu [128.59.19.61]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA7Ghm7l023660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <[e-mail]>; Tue, 7 Nov 2006 11:45:07 -0500 (EST)
Received: from metro-north.cs.columbia.edu (localhost [127.0.0.1]) by metro-north.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA7Ghmha014029 for <[e-mail]>; Tue, 7 Nov 2006 11:43:48 -0500 (EST)
Received: (from lennox@localhost) by metro-north.cs.columbia.edu (8.12.10/8.12.10/Submit) id kA7Ghltp014026; Tue, 7 Nov 2006 11:43:47 -0500 (EST)
X-Authentication-Warning: metro-north.cs.columbia.edu: lennox set sender to [e-mail] using -f
From: Jonathan Lennox <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[e-mail]>
Date: Tue, 7 Nov 2006 11:43:47 -0500
To: Calsify WG <[e-mail]>
X-Mailer: VM 7.19 under Emacs 20.7.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, X-Seen-By filter2.cs.columbia.edu
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=
X-Spam-Level: 
Subject: [Ietf-calsify] RRULEs with DTSTART and DTEND in different time zones
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2006 16:45:11 -0000

People have mentioned that the case needs to be handled when DTSTART and
DTEND are in different time zones -- for example, for plane flights.

Have people thought about what this means for recurrence durations, when the
two time zones have varying relative UTC offsets?

Specifically:

   DTSTART;TZID=America/Phoenix:20061027T150000
   DTEND;TZID=America/Los_Angeles:20061027T160000
   RRULE:FREQ=WEEKLY;COUNT=2

The first instance of the recurrence starts at 2006-10-27 15:00:00 MST (GMT+7), and
ends at 2006-10-27 16:00:00 PDT (GMT+7), 1 hour later.

The second instance of the recurrence starts at 2006-11-03 15:00:00 MST
(GMT+7), and ends -- when?  One could argue for either 2006-11-03 15:00:00
PST (GMT+8), 1 hour later, or 2006-11-03 16:00:00 PST (GMT+8), 2 hours
later.

Does anyone handle this case?  If UIs allow separate timezones for event
starting and ending times, this actually seems like something that could
poentially be constructed in a calendar UI.

-- 
Jonathan Lennox
[e-mail]


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id A1A3280DB6 for <[e-mail]>; Tue,  7 Nov 2006 06:55:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 93D8014229E for <[e-mail]>; Tue,  7 Nov 2006 06:55:13 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14725-10 for <[e-mail]>; Tue, 7 Nov 2006 06:55:12 -0800 (PST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id DD2B3142287 for <[e-mail]>; Tue,  7 Nov 2006 06:55:11 -0800 (PST)
Received: from metro-north.cs.columbia.edu (metro-north.cs.columbia.edu [128.59.19.61]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA7Et57l005564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Nov 2006 09:55:06 -0500 (EST)
Received: from metro-north.cs.columbia.edu (localhost [127.0.0.1]) by metro-north.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA7Et5ha013651; Tue, 7 Nov 2006 09:55:05 -0500 (EST)
Received: (from lennox@localhost) by metro-north.cs.columbia.edu (8.12.10/8.12.10/Submit) id kA7Et4nb013648; Tue, 7 Nov 2006 09:55:04 -0500 (EST)
X-Authentication-Warning: metro-north.cs.columbia.edu: lennox set sender to [e-mail] using -f
From: Jonathan Lennox <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[e-mail]>
Date: Tue, 7 Nov 2006 09:55:04 -0500
To: Reinhold Kainhofer <[e-mail]>
Subject: Re: [Ietf-calsify] BYDAY integers with other BY* rules (was: BYSETPOS and contracting BY* rules)
In-Reply-To: <[e-mail]>
References: <[e-mail]> <[e-mail]>
X-Mailer: VM 7.19 under Emacs 20.7.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, X-Seen-By filter1.cs.columbia.edu
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=
X-Spam-Level: 
Cc: [e-mail]
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2006 14:55:13 -0000

On Tuesday, November 7 2006, "Reinhold Kainhofer" wrote to "[e-mail]" saying:

> AFAIU RFC 2445, the -1FR means the last friday in the set of dates that match 
> the rule evaluation so far. Thus, I get the same results as with BYSETPOS:

I've always agreed with your second interpretation of RFC 2445: the numbers
in the BYDAY rule refer to the period of time described by the FREQ.  "-1FR"
means the last Friday of the month in a MONTHLY rule, and the last Friday of
the year in a YEARLY rule.

This seems to me to be the most straightforward reading of the BYDAY
definition:

      Each BYDAY value can also be preceded by a positive (+n) or
      negative (-n) integer.  If present, this indicates the nth
      occurrence of the specific day within the MONTHLY or YEARLY RRULE.
      For example, within a MONTHLY rule, +1MO (or simply 1MO)
      represents the first Monday within the month, whereas -1MO
      represents the last Monday of the month.  If an integer modifier
      is not present, it means all days of this type within the
      specified frequency.  For example, within a MONTHLY rule, MO
      represents all Mondays within the month.

That would indeed mean that the other BY* rules in the rule aren't relevant
to the interpretation of BYDAY, and that the order of interpretation of BY*
rules other than BYSETPOS isn't important.

Unfortunately, this interpretation is directly contradicted by RFC 2445's
VTIMEZONE example, which describes US-Eastern DST transitions as

        RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10

I've always interpreted this VTIMEZONE example as a bug in the spec, but I
see how it can make sense if BYDAY integers are interpreted as being like
BYSETPOS.

What do other implementations do?

-- 
Jonathan Lennox
[e-mail]


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id C528380D1D for <[e-mail]>; Tue,  7 Nov 2006 02:24:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id B66501422E9 for <[e-mail]>; Tue,  7 Nov 2006 02:24:56 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01755-10 for <[e-mail]>; Tue, 7 Nov 2006 02:24:55 -0800 (PST)
Received: from doob.fam.tuwien.ac.at (doob.fam.tuwien.ac.at [128.130.51.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id A3F5F1422E8 for <[e-mail]>; Tue,  7 Nov 2006 02:24:54 -0800 (PST)
Received: from einstein.kainhofer.com (localhost [127.0.0.1]) by doob.fam.tuwien.ac.at (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id kA7AOp50032330 for <[e-mail]>; Tue, 7 Nov 2006 11:24:51 +0100
From: Reinhold Kainhofer <[e-mail]>
Organization: Vienna University of Technology
To: [e-mail]
Subject: Re: [Ietf-calsify] BYSETPOS and contracting BY* rules
Date: Tue, 7 Nov 2006 11:21:52 +0100
User-Agent: KMail/1.9.5
References: <[e-mail]>
In-Reply-To: <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.2 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2006 10:24:56 -0000

Am Dienstag, 7. November 2006 04:13 schrieb Jonathan Lennox:
> The examples I came up with back in June 2001 (see the thread starting at
> <http://www.imc.org/ietf-calendar/mail-archive/thrd11.html#01781> if you
> really care about all the gory details) were:
>
> =A0 =A0 =A0 =A0RRULE:DTSTART;TZID=3DAmerica/New_York:20010401T090000
> =A0 =A0 =A0 =A0RECUR:FREQ=3DWEEKLY;BYMONTH=3D4,6;BYDAY=3DFR;BYSETPOS=3D-1
>
> =A0 =A0 =A0 =A0RRULE:DTSTART;TZID=3DAmerica/New_York:20010401T090000
> =A0 =A0 =A0 =A0RECUR:FREQ=3DMONTHLY;BYMONTH=3D4,6;BYDAY=3DFR;BYSETPOS=3D-1
>
> =A0 =A0 =A0 =A0RRULE:DTSTART;TZID=3DAmerica/New_York:20010401T090000
> =A0 =A0 =A0 =A0RECUR:FREQ=3DYEARLY;BYMONTH=3D4,6;BYDAY=3DFR;BYSETPOS=3D-1
>
> My proposal at the time was that these mean, respectively, "the last Frid=
ay
> of the week, in April and June" (i.e. "Fridays in April and June", with
> BYSETPOS irrelevant); "the last Friday of April, and the last Friday of
> June"; and "the last Friday of (April or June)" (i.e., given DTSTART, "the
> last Friday of June").

I think so, too.

A similar issue happens with BYDAY, which is similar to BYSETPOS, only that=
 it=20
is evaluated before all BY(HOUR|MINUTE|SECOND) are evaluated and that it ha=
s=20
an additional constraint of giving one or more weekdays, too.

        DTSTART;TZID=3DAmerica/New_York:20010401T090000
        RRULE:FREQ=3DWEEKLY;BYMONTH=3D4,6;BYDAY=3D-1FR

        DTSTART;TZID=3DAmerica/New_York:20010401T090000
        RRULE:FREQ=3DMONTHLY;BYMONTH=3D4,6;BYDAY=3D-1FR

        DTSTART;TZID=3DAmerica/New_York:20010401T090000
        RRULE:FREQ=3DYEARLY;BYMONTH=3D4,6;BYDAY=3D-1FR

AFAIU RFC 2445, the -1FR means the last friday in the set of dates that mat=
ch=20
the rule evaluation so far. Thus, I get the same results as with BYSETPOS:

In the first example, where we loop over each week, that set contains only =
one=20
Mon-Sun of that week, so the -1 is irrelevant.
In the second example, we loop over all months, the bymonth returns an empt=
y=20
set for all months other than april and jung. But in april and in june, the=
=20
set contains all days of that month, so -1FR is the last friday of april wh=
en=20
the loop is in april, and the last friday of june, when the loop reache jun=
e.
In the third example, we loop over all years, then choose only all days fro=
m=20
april and june, and finally the BYDAY selects the last friday of that set,=
=20
which is the last friday of june.

It's even more interesting when we add BYWEEKNO...

Or am I misunderstanding the BYDAY rule part here, and=20
        RRULE:FREQ=3DYEARLY;BYWEEKNO=3D3;BYDAY=3D-1FR
matches only the last friday of the year if it is in week #3?
If so, why is the order of the evaluation relevant? The only thing that is=
=20
important in that case is that BYSETPOS are evaluated last, all other BY*=20
rule parts else can be evaluated in any order...

That's another example that would help a lot if it appeared in an official=
=20
=46AQ. As I already mentioned several times, the RFC explains only some ver=
y=20
simple RRULEs, which are quite clear anyway, but forgets to give examples=20
where the details are important (e.g. in the examples given, the order of t=
he=20
evaluation of the rule parts is irrelevant, while in reality there are=20
several cases, where you get a different result if you evaluate the parts i=
n=20
a different order).

Cheers,
Reinhol
 =20
=2D-=20
=2D-----------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: [e-mail], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.a=
t/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 30BD480C2E for <[e-mail]>; Mon,  6 Nov 2006 19:31:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 21FF71422CD for <[e-mail]>; Mon,  6 Nov 2006 19:31:31 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17342-05 for <[e-mail]>; Mon, 6 Nov 2006 19:31:30 -0800 (PST)
Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.200.82]) by laweleka.osafoundation.org (Postfix) with ESMTP id 9DCCF1422C6 for <[e-mail]>; Mon,  6 Nov 2006 19:31:30 -0800 (PST)
Received: from thare (c-68-84-31-33.hsd1.fl.comcast.net[68.84.31.33]) by comcast.net (sccrmhc12) with SMTP id <2006110703312901200nhtuie>; Tue, 7 Nov 2006 03:31:29 +0000
From: "Tim Hare" <[e-mail]>
To: "'Calsify WG'" <[e-mail]>
Subject: RE: [Ietf-calsify] Section 4.1.2 Multiple Values: LANGUAGE parameter
Date: Mon, 6 Nov 2006 22:31:28 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <[e-mail]>
Thread-Index: AccBtOFcmYW5yi2RS5uhr9WLwYpEZQAZ8HEQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=2.6 tagged_above=-50.0 required=4.0 tests=AWL, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS, MSGID_FROM_MTA_ID
X-Spam-Level: **
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2006 03:31:31 -0000

The MIME approach makes all of the components in an iCalendar/iTIP set
match, language-wise, which probably is a good thing.


Tim Hare
Interested Bystander, Non-Inc.

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]] On Behalf Of Cyrus Daboo
Sent: Monday, November 06, 2006 10:04 AM
To: Bernard Desruisseaux; Calsify WG
Subject: Re: [Ietf-calsify] Section 4.1.2 Multiple Values: LANGUAGE
parameter

Hi Bernard,

--On November 5, 2006 5:29:25 PM -0500 Bernard Desruisseaux
<[e-mail]> wrote:

> RFC 2445 allows some properties of TEXT value type to be specified 
> multiple times. In some cases (e.g., "TZNAME") it is specified that 
> the property can be specified more than once for specifying multiple 
> language variants of the property value.
>
> I think section 4.1.2 Multiple Values should clarify how the 
> "LANGUAGE" parameter should be handled with multi-valued TEXT 
> properties.
>
> For instance, in a "VJOURNAL" calendar component, can I have two 
> "DESCRIPTION" with "LANGUAGE=en", but only one "DESCRIPTION" with 
> "LANGUAGE=fr"?  If so, should my client only display the one in 
> French, or should it display all three values?
>
> Currently, I think it should display all three values...

Its really not clear how multi-lingual 'alternatives' of an iCalendar
component should be handled. The suggestion of using multiple properties
with different LANGUAGES really does not work as there is no way to
unambiguously tie the variants together as alternatives.

A better approach might be to say that language alternatives should be
constructed at the MIME level - i.e. as separate components in separate MIME
parts inside a multipart/alternative.

--
Cyrus Daboo

_______________________________________________
Ietf-calsify mailing list
[e-mail]
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify




Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id A0FE28092A for <[e-mail]>; Mon,  6 Nov 2006 19:14:27 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 91B50142276 for <[e-mail]>; Mon,  6 Nov 2006 19:14:27 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18251-01 for <[e-mail]>; Mon, 6 Nov 2006 19:14:26 -0800 (PST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id ABB8B14227F for <[e-mail]>; Mon,  6 Nov 2006 19:14:25 -0800 (PST)
Received: from metro-north.cs.columbia.edu (metro-north.cs.columbia.edu [128.59.19.61]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA73Dh7l011498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <[e-mail]>; Mon, 6 Nov 2006 22:14:23 -0500 (EST)
Received: from metro-north.cs.columbia.edu (localhost [127.0.0.1]) by metro-north.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA73Dgha008718 for <[e-mail]>; Mon, 6 Nov 2006 22:13:42 -0500 (EST)
Received: (from lennox@localhost) by metro-north.cs.columbia.edu (8.12.10/8.12.10/Submit) id kA73DgGb008715; Mon, 6 Nov 2006 22:13:42 -0500 (EST)
X-Authentication-Warning: metro-north.cs.columbia.edu: lennox set sender to [e-mail] using -f
From: Jonathan Lennox <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[e-mail]>
Date: Mon, 6 Nov 2006 22:13:42 -0500
To: Calsify WG <[e-mail]>
X-Mailer: VM 7.19 under Emacs 20.7.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, X-Seen-By filter2.cs.columbia.edu
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=
X-Spam-Level: 
Subject: [Ietf-calsify] BYSETPOS and contracting BY* rules
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2006 03:14:27 -0000

In a hallway discussion today, I happened to remember another ambiguity in
the iCalendar spec, which was brought up back on the old ietf-calendar
mailing list but not, I think, ever resolved.

The issue is that BYSETPOS is specified only as

    The BYSETPOS rule part specifies a COMMA character (US-ASCII
    decimal 44) separated list of values which corresponds to the nth
    occurrence within the set of events specified by the rule. 

and the meaning of "the set of events specified by the rule" is very
unclear.

Particularly, the case that none of the RFC 2445 examples illustrates is
what happens when BYSETPOS is used in conjunction with contracting BY*
rules, i.e. BY* rules describing intervals larger than the FREQ.

The examples I came up with back in June 2001 (see the thread starting at
<http://www.imc.org/ietf-calendar/mail-archive/thrd11.html#01781> if you
really care about all the gory details) were:

       RRULE:DTSTART;TZID=America/New_York:20010401T090000
       RECUR:FREQ=WEEKLY;BYMONTH=4,6;BYDAY=FR;BYSETPOS=-1

       RRULE:DTSTART;TZID=America/New_York:20010401T090000
       RECUR:FREQ=MONTHLY;BYMONTH=4,6;BYDAY=FR;BYSETPOS=-1

       RRULE:DTSTART;TZID=America/New_York:20010401T090000
       RECUR:FREQ=YEARLY;BYMONTH=4,6;BYDAY=FR;BYSETPOS=-1

My proposal at the time was that these mean, respectively, "the last Friday
of the week, in April and June" (i.e. "Fridays in April and June", with
BYSETPOS irrelevant); "the last Friday of April, and the last Friday of
June"; and "the last Friday of (April or June)" (i.e., given DTSTART, "the
last Friday of June").

I still think this is right, but at the time not everyone agreed.

(Note that these examples don't obey the new "DTSTART must be a set member"
constraint.  It's an interesting question how to obey that for rules that
contain "BYSETPOS=-1".)

Eric Busboom's 2445 revision draft at the time defined this by saying

       BYSETPOS operates on a set of events in one interval of the
       recurrence rule. For a WEEKLY rule, the interval is one week, for a
       MONTHLY rule, one month, and for a YEARLY rule, one year.

This wording seems not to have made it into the current 2445bis draft.

How do existing CUAs (if they implement BYSETPOS at all) interpret my three
examples above?  Do people agree with my suggested interpretation?

-- 
Jonathan Lennox
[e-mail]


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id A5FE580B95 for <[e-mail]>; Mon,  6 Nov 2006 16:41:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 96B181422E0 for <[e-mail]>; Mon,  6 Nov 2006 16:41:53 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25369-05 for <[e-mail]>; Mon, 6 Nov 2006 16:41:53 -0800 (PST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 075FA1422BA for <[e-mail]>; Mon,  6 Nov 2006 16:41:52 -0800 (PST)
Received: from metro-north.cs.columbia.edu (metro-north.cs.columbia.edu [128.59.19.61]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA70b97l013652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <[e-mail]>; Mon, 6 Nov 2006 19:41:49 -0500 (EST)
Received: from metro-north.cs.columbia.edu (localhost [127.0.0.1]) by metro-north.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA70b9ha006246 for <[e-mail]>; Mon, 6 Nov 2006 19:37:09 -0500 (EST)
Received: (from lennox@localhost) by metro-north.cs.columbia.edu (8.12.10/8.12.10/Submit) id kA70b9kg006243; Mon, 6 Nov 2006 19:37:09 -0500 (EST)
X-Authentication-Warning: metro-north.cs.columbia.edu: lennox set sender to [e-mail] using -f
From: Jonathan Lennox <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[e-mail]>
Date: Mon, 6 Nov 2006 19:37:09 -0500
To: Calsify WG <[e-mail]>
X-Mailer: VM 7.19 under Emacs 20.7.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, X-Seen-By filter2.cs.columbia.edu
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=
X-Spam-Level: 
Subject: [Ietf-calsify] The "other" time discontinuity: leap-seconds
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2006 00:41:54 -0000

While I was thinking about the DST discontinuities, it occurred to me that
we should also address the "other" time discontinuity, leap-seconds.

My proposal is that iCalendar be completely ignorant of leap-seconds,
i.e. treat time as a fixed-radix 24:60:60 timescale.  (Pedants can treat
this as UT1, TAI, or "POSIX Time", as they like.)

Thus, calendar authors MUST NOT put "60" in the seconds field of a DATE-TIME
value, and the "nominal duration" rules assume that there are always 60
seconds in a minute.

That is, all occurences of each of the following events end at 00:00:00 of
the day after they start (even though there was a leap second at 2005-12-31
23:59:60 UTC):

DTSTART:20051231T235900Z
DURATION:PT1M

DTSTART:20051231T235900Z
DURATION:PT60S

DTSTART:20051231T235900Z
DURATION:PT1M
FREQ=DAILY;COUNT=2

DTSTART:20051231T235900Z
DURATION:PT60S
FREQ=DAILY;COUNT=2

DTSTART:20051230T235900Z
DURATION:PT1M
FREQ=DAILY;COUNT=2

DTSTART:20051230T235900Z
DURATION:PT60S
FREQ=DAILY;COUNT=2


I feel quite confident that this is the behavior you'll see from every
existing calendaring client.

-- 
Jonathan Lennox
[e-mail]


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id CE4D9805C3 for <[e-mail]>; Mon,  6 Nov 2006 16:25:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id BFE5E1422D0 for <[e-mail]>; Mon,  6 Nov 2006 16:25:10 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25766-02 for <[e-mail]>; Mon, 6 Nov 2006 16:25:10 -0800 (PST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 1095C14225D for <[e-mail]>; Mon,  6 Nov 2006 16:25:09 -0800 (PST)
Received: from metro-north.cs.columbia.edu (metro-north.cs.columbia.edu [128.59.19.61]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA70Lg7l007394 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <[e-mail]>; Mon, 6 Nov 2006 19:25:03 -0500 (EST)
Received: from metro-north.cs.columbia.edu (localhost [127.0.0.1]) by metro-north.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA70Lgha006220 for <[e-mail]>; Mon, 6 Nov 2006 19:21:42 -0500 (EST)
Received: (from lennox@localhost) by metro-north.cs.columbia.edu (8.12.10/8.12.10/Submit) id kA70LfuT006217; Mon, 6 Nov 2006 19:21:41 -0500 (EST)
X-Authentication-Warning: metro-north.cs.columbia.edu: lennox set sender to [e-mail] using -f
From: Jonathan Lennox <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[e-mail]>
Date: Mon, 6 Nov 2006 19:21:41 -0500
To: Calsify WG <[e-mail]>
X-Mailer: VM 7.19 under Emacs 20.7.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, X-Seen-By filter1.cs.columbia.edu
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=
X-Spam-Level: 
Subject: [Ietf-calsify] DST discontinuities part 3: discontinuities for event end times
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2006 00:25:10 -0000

My third issue has to do with how you handle the case when an event's end
time "would" occur within a DST discontinuity.

It's hard to even define this issue without a resolution to Issue 27 -- what
DTEND/DURATION mean for events that cross a DST transition.

It sounded like the consensus in the room was leaning towards the idea that
durations are "nominal" durations, not "real" durations, i.e. in
America/New_York, a PT8H event that starts at 2006-04-02 00:00:00, or
2006-10-29 00:00:00, ends at 08:00:00 in both cases (for a real duration of
seven hours or nine hours, respectively).

If that is indeed the case, the question needs to be answered: when does the
event

   DTSTART;TZID=America/New_York:20060402T000000
   DURATION:PT2H30M

end?  The nominal duration would imply an end at 2006-04-02 02:30:00, which
in America/New_York doesn't exist.

Similarly, the nominal-duration rules would indicate that

   DTSTART;TZID=America/New_York:20061029T000000
   DURATION:PT1H30M

would end at 2006-10-29 01:30:00, which could refer to either 2006-10-29
01:30:00 EDT or 2006-10-29 01:30:00 EST.

To be clear, the fact that my examples used sub-day duration lengths isn't
relevant here; the problem also occurs with 

   DTSTART;TZID=America/New_York:20060401T023000
   DURATION:P1D

   DTSTART;TZID=America/New_York:20061028T013000
   DURATION:P1D

as well.  My inclination would be to say that the resolution should be the
same for these both cases, but others may disagree.


This issue is the same both for single events and for recurring events, i.e.

   DTSTART;TZID=America/New_York:20060331T023000
   DURATION:P1D
   RRULE:FREQ=DAILY;COUNT=2

   DTSTART;TZID=America/New_York:20061027T013000
   DURATION:P1D
   RRULE:FREQ=DAILY;COUNT=2

have this problem for their second occurrence.

-- 
Jonathan Lennox
[e-mail]


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id AE99A80ECF for <[e-mail]>; Mon,  6 Nov 2006 15:58:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id A0F2314225D for <[e-mail]>; Mon,  6 Nov 2006 15:58:13 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10992-10 for <[e-mail]>; Mon, 6 Nov 2006 15:58:11 -0800 (PST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 08E5B1422D0 for <[e-mail]>; Mon,  6 Nov 2006 15:58:10 -0800 (PST)
Received: from metro-north.cs.columbia.edu (metro-north.cs.columbia.edu [128.59.19.61]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA6NvT7l028355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <[e-mail]>; Mon, 6 Nov 2006 18:58:09 -0500 (EST)
Received: from metro-north.cs.columbia.edu (localhost [127.0.0.1]) by metro-north.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA6NvTha006084 for <[e-mail]>; Mon, 6 Nov 2006 18:57:29 -0500 (EST)
Received: (from lennox@localhost) by metro-north.cs.columbia.edu (8.12.10/8.12.10/Submit) id kA6NvTsX006081; Mon, 6 Nov 2006 18:57:29 -0500 (EST)
X-Authentication-Warning: metro-north.cs.columbia.edu: lennox set sender to [e-mail] using -f
From: Jonathan Lennox <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[e-mail]>
Date: Mon, 6 Nov 2006 18:57:29 -0500
To: Calsify WG <[e-mail]>
X-Mailer: VM 7.19 under Emacs 20.7.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, X-Seen-By filter1.cs.columbia.edu
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=
X-Spam-Level: 
Subject: [Ietf-calsify] DST discontinuities part 2: discontinuities for recurring event start times
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 23:58:13 -0000

Issue 2 has to do with how you handle the case when a recurrence's
start time falls within a discontinuity.

I suggest that by default, the "naive" behavior should be followed: i.e.,
events that would fall at non-existent times do not occur, and events that
fall at repeated times occur twice.  Calendar authors that want other
behaviors should use RDATE and EXDATE to get what they want.

(If existing clients consistently do something different, we should define
that behavior instead; this could use testing.)

The two relevant examples are, first, a forward jump in time:

   DTSTART;TZID=America/New_York:20060331T023000
   DURATION:PT1H
   RRULE:FREQ=DAILY;COUNT=4

In my suggested resolution, the event recurs at:

2006-03-31 02:30:00 EST
2006-04-01 02:30:00 EST
2006-04-03 02:30:00 EDT
2006-04-04 02:30:00 EDT


The second example, a backward jump in time:

   DTSTART;TZID=America/New_York:20061028T013000
   DURATION:PT1H
   RRULE:FREQ=DAILY;COUNT=4

In my suggested resolution, the event recurs at:

2006-10-28 01:30:00 EDT
2006-10-29 01:30:00 EDT
2006-10-29 01:30:00 EST
2006-10-30 01:30:00 EST

-- 
Jonathan Lennox
[e-mail]


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 2327780BB0 for <[e-mail]>; Mon,  6 Nov 2006 15:52:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 14C101422E2 for <[e-mail]>; Mon,  6 Nov 2006 15:52:32 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15783-10 for <[e-mail]>; Mon, 6 Nov 2006 15:52:30 -0800 (PST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 7C5331422E0 for <[e-mail]>; Mon,  6 Nov 2006 15:52:30 -0800 (PST)
Received: from metro-north.cs.columbia.edu (metro-north.cs.columbia.edu [128.59.19.61]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA6NqO7l027415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <[e-mail]>; Mon, 6 Nov 2006 18:52:25 -0500 (EST)
Received: from metro-north.cs.columbia.edu (localhost [127.0.0.1]) by metro-north.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id kA6NqOha006069 for <[e-mail]>; Mon, 6 Nov 2006 18:52:24 -0500 (EST)
Received: (from lennox@localhost) by metro-north.cs.columbia.edu (8.12.10/8.12.10/Submit) id kA6NqNbg006066; Mon, 6 Nov 2006 18:52:23 -0500 (EST)
X-Authentication-Warning: metro-north.cs.columbia.edu: lennox set sender to [e-mail] using -f
From: Jonathan Lennox <[e-mail]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[e-mail]>
Date: Mon, 6 Nov 2006 18:52:23 -0500
To: Calsify WG <[e-mail]>
X-Mailer: VM 7.19 under Emacs 20.7.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, X-Seen-By filter2.cs.columbia.edu
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=
X-Spam-Level: 
Subject: [Ietf-calsify] DST discontinuities part 1: date-times that fall in discontinutities
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 23:52:32 -0000

In the meeting today, we brought up the issue of DST discontinuities for
RRULEs, and Eliot asked for text to be sent to the mailing list.

The first issue has to do with how you handle an ambiguous or nonexistent
DATE-TIME value.  E.g. (assuming America/New_York describes the U.S. Eastern
Time Zone) how do you handle the two cases

DTSTART;TZID=America/New_York:20060402T023000 (which does not exist)

DTSTART;TZID=America/New_York:20061029T013000 (which occurs twice)

I would suggest that both these examples be forbidden.  For the latter case,
clients MUST use UTC (or potentially, some other timezone which does not
have a jump at that time) to describe the event.

-- 
Jonathan Lennox
[e-mail]


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 31BE57F577 for <[e-mail]>; Mon,  6 Nov 2006 10:37:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id F336A14227E for <[e-mail]>; Mon,  6 Nov 2006 10:37:42 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02400-04 for <[e-mail]>; Mon, 6 Nov 2006 10:37:39 -0800 (PST)
Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 1E3A514228B for <[e-mail]>; Mon,  6 Nov 2006 10:37:39 -0800 (PST)
Received: from rcsmt251.oracle.com (rcsmt251.oracle.com [148.87.90.196]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id kA6DKRFC021775; Mon, 6 Nov 2006 12:37:18 -0600
Received: from dhcp-amer-rmdc-csvpn-gw6-141-144-112-225.vpn.oracle.com by rcsmt250.oracle.com with ESMTP id 2174067021162838226; Mon, 06 Nov 2006 11:37:06 -0700
Message-ID: <[e-mail]>
Date: Mon, 06 Nov 2006 13:37:03 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Cyrus Daboo <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.6.1 Event Component: Default duration of	day events
References: <[e-mail]> <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Cc: Calsify WG <[e-mail]>
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 18:37:44 -0000

Hi Cyrus,

 > This issue begs the question of whether all day events should
 > automatically appear as opaque in free-busy lookups. I suspect most
 > implementations do not add TRANS:TRANSPARENT when adding an
 > 'anniversary' event - but having that block out time would be bad.

If so, please provide a list of such implementations.

 From what I've seen, implementations do specify DTEND or DURATION and
TRANSP explicitly.  As such, in most cases there are no ambiguity.

 >
 > This would be a change to 2445, but one solution is to say the default
 > TRANSP for all day events is TRANSPARENT rather than OPAQUE.
 >

I'd prefer not to introduce an exception for all day events.

Cheers,
Bernard


Cyrus Daboo wrote:
> Hi Bernard,
> 
> --On November 5, 2006 5:26:48 PM -0500 Bernard Desruisseaux 
> <[e-mail]> wrote:
> 
>> In section 4.6.1 Event Component of RFC 2445 it says:
>>
>>  > For cases where a "VEVENT" calendar component specifies a "DTSTART"
>>  > property with a DATE data type but no "DTEND" property, the events
>>  > non-inclusive end is the end of the calendar date specified by the
>>  > "DTSTART" property.
>>
>> As such, the last sentence of the paragraph before the following example
>> is wrong. This event would actually appear as opaque in a search for busy
>> time.
>>
>>  > The following is an example of the "VEVENT" calendar component used
>>  > to represent an anniversary that will occur annually. Since it takes
>>  > up no time, it will not appear as opaque in a search for busy time;
>>  > no matter what the value of the "TRANSP" property indicates:
>>  >
>>  >   BEGIN:VEVENT
>>  >   UID:[e-mail]
>>  >   DTSTAMP:19970901T1300Z
>>  >   DTSTART:19971102
>>  >   SUMMARY:Our Blissful Anniversary
>>  >   CLASS:CONFIDENTIAL
>>  >   CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
>>  >   RRULE:FREQ=YEARLY
>>  >   END:VEVENT
>>
>> I propose to remove this sentence and to add the TRANSP property to
>> the example.
>>
>> Proposed text:
>>
>>  > The following is an example of the "VEVENT" calendar component used
>>  > to represent an anniversary that will occur annually.
>>  >
>>  >   BEGIN:VEVENT
>>  >   UID:[e-mail]
>>  >   DTSTAMP:19970901T1300Z
>>  >   DTSTART:19971102
>>  >   SUMMARY:Our Blissful Anniversary
>>  >   TRANSP:TRANSPARENT
>>  >   CLASS:CONFIDENTIAL
>>  >   CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
>>  >   RRULE:FREQ=YEARLY
>>  >   END:VEVENT
>>
>> Similarly, in section 4.8.2.4 Date/Time Start of RFC 2445 it says:
>>
>>  > Description: Within the "VEVENT" calendar component, this property
>>  > defines the start date and time for the event. The property is
>>  > REQUIRED in "VEVENT" calendar components. Events can have a start
>>  > date/time but no end date/time. In that case, the event does not take
>>  > up any time.
>>
>> I propose to remove the last two sentences of this paragraph.
>>
>> Proposed text:
>>
>>  > Description: Within the "VEVENT" calendar component, this property
>>  > defines the start date and time for the event. The property is
>>  > REQUIRED in "VEVENT" calendar components.
>>
>> Finally, in section 6 Recommended Practices of RFC 2445 it says:
>>
>>  > 2.  A calendar entry with a "DTSTART" property but no "DTEND"
>>  >     property does not take up any time. It is intended to represent
>>  >     an event that is associated with a given calendar date and time
>>  >     of day, such as an anniversary. Since the event does not take up
>>  >     any time, it MUST NOT be used to record busy time no matter what
>>  >     the value for the "TRANSP" property.
>>
>> This is actually wrong. I would simply remove this text. The proper
>> behave is described in section 4.6.1 Event Component.
> 
> This issue begs the question of whether all day events should 
> automatically appear as opaque in free-busy lookups. I suspect most 
> implementations do not add TRANS:TRANSPARENT when adding an 
> 'anniversary' event - but having that block out time would be bad.
> 
> This would be a change to 2445, but one solution is to say the default 
> TRANSP for all day events is TRANSPARENT rather than OPAQUE.
> 


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 7890680D18; Mon,  6 Nov 2006 08:59:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 6549414228B; Mon,  6 Nov 2006 08:59:09 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23805-07; Mon, 6 Nov 2006 08:59:06 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by laweleka.osafoundation.org (Postfix) with ESMTP id D932C142287; Mon,  6 Nov 2006 08:59:06 -0800 (PST)
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-5.cisco.com with ESMTP; 06 Nov 2006 08:59:05 -0800
X-IronPort-AV: i="4.09,392,1157353200";  d="scan'208"; a="339943913:sNHT47232898"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id kA6Gx5v0017904; Mon, 6 Nov 2006 08:59:05 -0800
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kA6Gx4in004653; Mon, 6 Nov 2006 08:59:04 -0800 (PST)
Received: from [130.129.69.48] (sjc-vpn7-582.cisco.com [10.21.146.70]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id kA6GjskZ015228; Mon, 6 Nov 2006 08:45:54 -0800
Message-ID: <[e-mail]>
Date: Mon, 06 Nov 2006 08:59:07 -0800
From: Eliot Lear <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909)
MIME-Version: 1.0
To: Bernard Desruisseaux <[e-mail]>, Lisa Dusseault <[e-mail]>, Cyrus Daboo <[e-mail]>, Aki Niemi <[e-mail]>, Alexey Melnikov <[e-mail]>, "[e-mail]" <[e-mail]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Authentication-Results: sj-dkim-1.cisco.com; header.From=[e-mail]; dkim=pass ( sig from cisco.com verified; ); 
DKIM-Signature: a=rsa-sha1; q=dns; l=126; t=1162832346; x=1163696346; c=relaxed/simple; s=sjdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=[e-mail]; z=From:Eliot=20Lear=20<[e-mail]> |Subject:Calsify=20Lunch=20is=20@=2011=3A45=20at=20the=20restaurant=20in=20the=20 Main=20Sheraton=20Tower=0A=20(East); X=v=3Dcisco.com=3B=20h=3DQ51wBr8tmMvlVmuSan81/QYrGq4=3D; b=czKk8n1FdjCEqOfVMmk6Lj9/JVw2TTr1JILqCAhrlvAUJekivEQxD1UHTNDKJm+13GQcako1 cA/brw4gcoHtgZCD//6CeuHp9GeAoEdtTJpQpbAEtppsJt3y6xdEG97Y;
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.2 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Calsify Lunch is @ 11:45 at the restaurant in the Main Sheraton Tower (East)
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 16:59:09 -0000

We have a reservation for 10.  This includes authors, chairs, AD.  
Others are welcome as the reservation permits.

Eliot


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 5BEFA80F02 for <[e-mail]>; Mon,  6 Nov 2006 08:49:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 41885142297 for <[e-mail]>; Mon,  6 Nov 2006 08:49:32 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23805-04; Mon, 6 Nov 2006 08:49:31 -0800 (PST)
Received: from [130.129.70.115] (dhcp70-115.ietf67.org [130.129.70.115]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id AFD53142279; Mon,  6 Nov 2006 08:49:31 -0800 (PST)
In-Reply-To: <[e-mail]>
References: <[e-mail]> <[e-mail]> <[e-mail]>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: multipart/alternative; boundary=Apple-Mail-3--159023265
Message-Id: <[e-mail]>
From: Lisa Dusseault <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.8.5.3 Recurrence Date/Times: RDATE < DTSTART
Date: Mon, 6 Nov 2006 08:49:30 -0800
To: Bernard Desruisseaux <[e-mail]>
X-Mailer: Apple Mail (2.752.2)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.1 tagged_above=-50.0 required=4.0 tests=AWL, HTML_50_60, HTML_MESSAGE
X-Spam-Level: 
Cc: [e-mail]
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 16:49:32 -0000

--Apple-Mail-3--159023265
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

That's one of those cases that I think we could handle *not* having  
all in the same recurrence rule, or by having EXDates rather than  
make RDATE an implicit EXDATE.  There are so many ways of expressing  
the logical meeting you describe...

Lisa

On Nov 6, 2006, at 6:00 AM, Bernard Desruisseaux wrote:

>
> Let's say I want to have a meeting today (Monday) with three
> further instances on the next upcoming Tuesday. I could easily
> do that with an RDATE set to today (Monday) and a DTSTART set
> to tomorrow (Tuesday) and RRULE:FREQ=WEEKLY;BYDAY=TU;COUNT=3.


--Apple-Mail-3--159023265
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">That's one of those cases that I =
think we could handle *not* having all in the same recurrence rule, or =
by having EXDates rather than make RDATE an implicit EXDATE.=A0 There =
are so many ways of expressing the logical meeting you =
describe...<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Lisa<DIV><BR><DIV><DIV>On =
Nov 6, 2006, at 6:00 AM, Bernard Desruisseaux wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; =
min-height: 14.0px"><BR></P> <P style=3D"margin: 0.0px 0.0px 0.0px =
0.0px"><FONT face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">Let's say I want to have a meeting today (Monday) with =
three</FONT></P> <P style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><FONT =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px Helvetica">further =
instances on the next upcoming Tuesday. I could easily</FONT></P> <P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><FONT face=3D"Helvetica" =
size=3D"3" style=3D"font: 12.0px Helvetica">do that with an RDATE set to =
today (Monday) and a DTSTART set</FONT></P> <P style=3D"margin: 0.0px =
0.0px 0.0px 0.0px"><FONT face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">to tomorrow (Tuesday) and =
RRULE:FREQ=3DWEEKLY;BYDAY=3DTU;COUNT=3D3.</FONT></P> =
</BLOCKQUOTE></DIV><BR></DIV></DIV></BODY></HTML>=

--Apple-Mail-3--159023265--


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 2D96B80844 for <[e-mail]>; Mon,  6 Nov 2006 07:46:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 1ECDA1422C6 for <[e-mail]>; Mon,  6 Nov 2006 07:46:37 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08850-08 for <[e-mail]>; Mon, 6 Nov 2006 07:46:33 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 91E5B142274 for <[e-mail]>; Mon,  6 Nov 2006 07:46:33 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA6ARl5J030631; Mon, 6 Nov 2006 08:46:21 -0700
Received: from dhcp-amer-rmdc-csvpn-gw4-141-144-99-22.vpn.oracle.com by rcsmt251.oracle.com with ESMTP id 2173418031162827956; Mon, 06 Nov 2006 08:45:56 -0700
Message-ID: <[e-mail]>
Date: Mon, 06 Nov 2006 10:45:48 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Cyrus Daboo <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.8.8.2 Request Status: 3-tuples or pairs?
References: <[e-mail]> <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Cc: Calsify WG <[e-mail]>
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:46:37 -0000

Cyrus,

I think we should only allow pairs and 3-tuples, as such it should be:

statcode   = 1*DIGIT 1*2("." 1*DIGIT)
                      ^
Cheers,
Bernard

Cyrus Daboo wrote:
> Hi Bernard,
> 
> --On November 5, 2006 5:33:51 PM -0500 Bernard Desruisseaux 
> <[e-mail]> wrote:
> 
>> In Section 4.8.8.2 Request Status of RFC 2445 it says:
>>
>>  > The short return status is a PERIOD character (US-ASCII decimal 46)
>>  > separated 3-tuple of integers. For example, "3.1.1". The successive
>>  > levels of integers provide for a successive level of status code
>>  > granularity.
>>
>> But all the examples in the draft specify REQUEST-STATUS values with
>> only a pair of integers (e.g., "2.0").
>>
>> Furthermore, all the values specified in section 3.6 Status Replies of
>> RFC 2246 are only pair of integers.
>>
>> I see two options:
>>
>> a) Change text to allow pairs and 3-tuples;
>>
>> b) Change text to allow pairs only.
> 
> Actually the ABNF for statuscode shows that it can contain an arbitrary 
> number of 'tuples':
> 
> statcode   = 1*DIGIT *("." 1*DIGIT)
> 
> What we could do is:
> 
> statcode   = 1*DIGIT *2("." 1*DIGIT)
> 
> That would allow for up to three levels of tuples. It would be 
> consistent with the ones currently defined in 2445/2446.
> 


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id BF0B880F42 for <[e-mail]>; Mon,  6 Nov 2006 07:41:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id B119D1422C6 for <[e-mail]>; Mon,  6 Nov 2006 07:41:56 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08259-04 for <[e-mail]>; Mon, 6 Nov 2006 07:41:53 -0800 (PST)
Received: from plumcanary.com (mail.plumcanary.com [216.154.222.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 19AB01422C1 for <[e-mail]>; Mon,  6 Nov 2006 07:41:53 -0800 (PST)
Received: from [192.168.1.100] (c-71-233-21-41.hsd1.ma.comcast.net [71.233.21.41]) by plumcanary.com (8.12.11.20060308/8.12.11) with ESMTP id kA6FjZim024881 for <[e-mail]>; Mon, 6 Nov 2006 10:45:36 -0500
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <[e-mail]>
References: <[e-mail]> <[e-mail]>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <[e-mail]>
Content-Transfer-Encoding: 7bit
From: Jay Batson <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.6.3 Journal Component: DESCRIPTION property
Date: Mon, 6 Nov 2006 10:41:47 -0500
To: Calsify WG <[e-mail]>
X-Mailer: Apple Mail (2.752.2)
Received-SPF: softfail (plumcanary.com: domain of transitioning [e-mail] does not designate 71.233.21.41 as permitted sender) receiver=plumcanary.com; client-ip=71.233.21.41; helo=[192.168.1.100]; envelope-from=[e-mail]; x-software=spfmilter 0.97 http://www.acme.com/software/spfmilter/ with libspf2-1.0.0; 
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:41:56 -0000

On Nov 6, 2006, at 9:57 AM, Cyrus Daboo wrote:
> Hi Bernard,
> --On November 5, 2006 5:27:32 PM -0500 Bernard Desruisseaux  
> <[e-mail]> wrote:
>>  > jourprop   = *(
>>  >
>>  >            ; the following are optional,
>>  >            ; but MUST NOT occur more than once
>>  >
>>  >            class / created / description / dtstart / dtstamp /
>>  >            last-mod / organizer / recurid / seq / status /
>>  >            summary / uid / url /
>>
>> But according to section 4.8.1.5 Description, the "DESCRIPTION"
>> property can be specified multiple times within a "VJOURNAL"
>> calendar component.
>>
>> As such, I propose to modify the "jourprop" rule in section
>> 4.6.3 to be in accordance with the text in section 4.8.1.5.
>
> +1

+1


-------------
Jay Batson
[e-mail]
[phone] (w)
[phone] (m)




Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id CD10080C51 for <[e-mail]>; Mon,  6 Nov 2006 07:32:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id BE4931422E0 for <[e-mail]>; Mon,  6 Nov 2006 07:32:44 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08850-05 for <[e-mail]>; Mon, 6 Nov 2006 07:32:44 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 1EB561422DF for <[e-mail]>; Mon,  6 Nov 2006 07:32:44 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6FW8Yb021349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 10:32:13 -0500
Date: Mon, 06 Nov 2006 07:32:02 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Tim Hare <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: Allowed forms for	aDATE-TIME
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]> <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED, AWL
X-Spam-Level: 
Cc: 'Calsify WG' <[e-mail]>
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:32:44 -0000

Hi Bernard,

--On November 5, 2006 6:53:01 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

>> Wait! Are you saying that recurrence rules cannot use "floating"
>> date-time?
>
> Humm.  I was.  On second thought, I realize that this needs to be
> possible.
>
>> There's a very good use case for it: conference scheduling. There might
>> be an "administrivia" meeting every morning of the conference week at
>> the same time and place - a clear case for recurrence - yet, many
>> attendees do not like to set their devices to the local time of the
>> conference (unless the device changes to local time automatically as
>> cell phones do) and so the conference schedule is published in
>> "floating" time.
>
> I don't believe anybody should publish a conference schedule in "floating
> time", but I agree that one might want to publish recurring floating
> events such as "Lunch" or "Diner"...

Yes - we must allow floating time recurring events.

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id E940980BAB for <[e-mail]>; Mon,  6 Nov 2006 07:31:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id DA6941422DF for <[e-mail]>; Mon,  6 Nov 2006 07:31:09 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24976-10 for <[e-mail]>; Mon, 6 Nov 2006 07:31:09 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 38BDC14227B for <[e-mail]>; Mon,  6 Nov 2006 07:31:09 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6FUrvv021335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 10:30:59 -0500
Date: Mon, 06 Nov 2006 07:30:47 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.8.8.2 Request Status: 3-tuples or pairs?
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:31:10 -0000

Hi Bernard,

--On November 5, 2006 5:33:51 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

> In Section 4.8.8.2 Request Status of RFC 2445 it says:
>
>  > The short return status is a PERIOD character (US-ASCII decimal 46)
>  > separated 3-tuple of integers. For example, "3.1.1". The successive
>  > levels of integers provide for a successive level of status code
>  > granularity.
>
> But all the examples in the draft specify REQUEST-STATUS values with
> only a pair of integers (e.g., "2.0").
>
> Furthermore, all the values specified in section 3.6 Status Replies of
> RFC 2246 are only pair of integers.
>
> I see two options:
>
> a) Change text to allow pairs and 3-tuples;
>
> b) Change text to allow pairs only.

Actually the ABNF for statuscode shows that it can contain an arbitrary 
number of 'tuples':

statcode   = 1*DIGIT *("." 1*DIGIT)

What we could do is:

statcode   = 1*DIGIT *2("." 1*DIGIT)

That would allow for up to three levels of tuples. It would be consistent 
with the ones currently defined in 2445/2446.

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 4128F80EA6 for <[e-mail]>; Mon,  6 Nov 2006 07:25:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 31E841422DF for <[e-mail]>; Mon,  6 Nov 2006 07:25:45 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08850-01 for <[e-mail]>; Mon, 6 Nov 2006 07:25:44 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 800731422C6 for <[e-mail]>; Mon,  6 Nov 2006 07:25:44 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6FPPXM021312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 10:25:31 -0500
Date: Mon, 06 Nov 2006 07:25:19 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.8.2.5 Duration: VFREEBUSY request
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:25:45 -0000

Hi Bernard,

--On November 5, 2006 5:36:05 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

>  > In a "VFREEBUSY" calendar component the property may be
>  > used to specify the interval of free time being requested.
>
> Yet, section 3.3.2 REQUEST of RFC 2446 (iTIP) specifies that
> the DURATION property is not allowed in a VFREEBUSY request.
>
> I see three options:
>
> a) Remove statement from iCalendar to be in sync with iTIP;
>
> b) Change iTIP to allow the DURATION property in a VFREEBUSY
>     request and define the semantic as specified in iCalendar.
>
> c) Status quo.

We should rule out (c) as it represents an inconsistency between the two 
specs. Note that 2445 does not clearly define what it means to have 
DURATION present. e.g. is it allowed for the responder to only return free 
times slots that are equal to or larger than the DURATION, or should they 
still return the full list? If we can clearly specify the behavior then I 
think (b) is reasonable, otherwise we have to do (a).

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 10F9D80C14 for <[e-mail]>; Mon,  6 Nov 2006 07:18:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 011921422E6 for <[e-mail]>; Mon,  6 Nov 2006 07:18:00 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05683-05 for <[e-mail]>; Mon, 6 Nov 2006 07:17:59 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 6074B1422E5 for <[e-mail]>; Mon,  6 Nov 2006 07:17:59 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6FHf3G021283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 10:17:47 -0500
Date: Mon, 06 Nov 2006 07:17:35 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 6 Recommended Practices #4: Precedence of	duration of RDATE
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:18:00 -0000

Hi Bernard,

--On November 5, 2006 5:35:33 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

> In section 6 Recommended Practices of RFC 2445 it says:
>
>  > 4.  When the combination of the "RRULE" and "RDATE" properties on an
>  >     iCalendar object produces multiple instances having the same
>  >     start date/time, they should be collapsed to, and considered as,
>  >     a single instance.
>
> We should probably clarify that if the "RDATE" property is specified as
> a PERIOD, its duration has precedence over the duration of the recurrence
> instance defined by the "DTSTART" property.

+1

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id B89C280AF0 for <[e-mail]>; Mon,  6 Nov 2006 07:16:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id A81F214226F for <[e-mail]>; Mon,  6 Nov 2006 07:16:58 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11370-02 for <[e-mail]>; Mon, 6 Nov 2006 07:16:58 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 1017C142258 for <[e-mail]>; Mon,  6 Nov 2006 07:16:57 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6FGbxv021272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 10:16:43 -0500
Date: Mon, 06 Nov 2006 07:16:31 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 6 Recommended Practices #3: Different TZID?
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:16:58 -0000

Hi Bernard,

--On November 5, 2006 5:35:01 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

>  > 3.  When the "DTSTART" and "DTEND", for "VEVENT", "VJOURNAL" and
>  >     "VFREEBUSY" calendar components, and "DTSTART" and "DUE", for
>  >     "VTODO" calendar components, have the same value data type (e.g.,
>  >     DATE-TIME), they SHOULD specify values in the same time format
>  >     (e.g., UTC time format).
>
> What about DATE-TIME values with different TZID parameter values
> (e.g., airline flights, that start in one time zone and end in
> another)?  Obviously, I think this should be okay.

Yes - we must allow different TZID's on DTSTART/DTEND/DUE.

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 2731980692 for <[e-mail]>; Mon,  6 Nov 2006 07:15:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 185791422E0 for <[e-mail]>; Mon,  6 Nov 2006 07:15:06 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27348-05 for <[e-mail]>; Mon, 6 Nov 2006 07:15:05 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 822B11422DF for <[e-mail]>; Mon,  6 Nov 2006 07:15:05 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6FEnTH021256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 10:14:55 -0500
Date: Mon, 06 Nov 2006 07:14:42 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.8.5.3 Recurrence Date/Times: RDATE <	DTSTART
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED, AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:15:06 -0000

Hi Bernard,

--On November 5, 2006 5:33:14 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

> In section 4.8.5.3 Recurrence Date/Times of RFC 2445 it says:
>
>  > The "DTSTART" property defines the first instance in the
>  > recurrence set.
>
> I believe this section should clarify that the "RDATE" property
> value can actually be earlier in time than the value of the
> "DTSTART" property.

+1

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 6AA9880692 for <[e-mail]>; Mon,  6 Nov 2006 07:14:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 5CA2D1422DF for <[e-mail]>; Mon,  6 Nov 2006 07:14:32 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27348-04 for <[e-mail]>; Mon, 6 Nov 2006 07:14:32 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id B4B2E142278 for <[e-mail]>; Mon,  6 Nov 2006 07:14:31 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6FE0es021245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 10:14:13 -0500
Date: Mon, 06 Nov 2006 07:13:54 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.8.3.1 Time Zone Identifier: Scope of TZID
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED, AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:14:32 -0000

Hi Bernard,

--On November 5, 2006 5:30:36 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

> In section 4.8.3.1 Time Zone Identifier of RFC 2445 it says:
>
>  > Purpose: This property specifies the text value that uniquely
>  > identifies the "VTIMEZONE" calendar component.
>
> This section should specify the "scope" in which a TZID MUST be
> unique when the "TZID" property value does not start with a
> SOLIDUS character.
>
> I believe the "TZID" MUST be unique in the scope of an iCalendar
> object, but not in the context of an iCalendar stream...

Right - inside of a BEGIN/END VCALENDAR, TZID must be unqiue, but it does 
not need to be unique across all BEGIN/END VCALENDAR's in a stream. I guess 
we need to add text for this now that we are using 'object' and 'stream' 
terminology.

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id E774280D2D for <[e-mail]>; Mon,  6 Nov 2006 07:05:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id D82BC1422DF for <[e-mail]>; Mon,  6 Nov 2006 07:05:56 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09459-08 for <[e-mail]>; Mon, 6 Nov 2006 07:05:56 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 444DD14227B for <[e-mail]>; Mon,  6 Nov 2006 07:05:56 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6F5gog021220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 10:05:47 -0500
Date: Mon, 06 Nov 2006 07:05:36 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.2 Property Parameters: ianaparam
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:05:57 -0000

Hi Bernard,

--On November 5, 2006 5:29:56 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

> Section 4.2 Property Parameters of RFC 2445 defines a "ianaparam"
> rule in its ABNF, but while all the properties allow "xparam",
> none of them currently allow "ianaparam".
>
> Shouldn't all properties allow "ianaparam"? That is, parameters
> *not* defined in this specification, but registered to IANA.

Suggestion: use 'other-param' here and then define:

other-param = *(iana-param / x-param)

That will make the ABNF a little shorter.

You might also want to do the same for iana-prop/x-prop.

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id E4FBB80D04 for <[e-mail]>; Mon,  6 Nov 2006 07:04:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id D6F941422DD for <[e-mail]>; Mon,  6 Nov 2006 07:04:36 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03335-07 for <[e-mail]>; Mon, 6 Nov 2006 07:04:36 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 307E714227B for <[e-mail]>; Mon,  6 Nov 2006 07:04:36 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6F4HbL021207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 10:04:22 -0500
Date: Mon, 06 Nov 2006 07:04:11 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.1.2 Multiple Values: LANGUAGE parameter
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:04:37 -0000

Hi Bernard,

--On November 5, 2006 5:29:25 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

> RFC 2445 allows some properties of TEXT value type to be specified
> multiple times. In some cases (e.g., "TZNAME") it is specified that
> the property can be specified more than once for specifying multiple
> language variants of the property value.
>
> I think section 4.1.2 Multiple Values should clarify how the
> "LANGUAGE" parameter should be handled with multi-valued TEXT
> properties.
>
> For instance, in a "VJOURNAL" calendar component, can I have two
> "DESCRIPTION" with "LANGUAGE=en", but only one "DESCRIPTION" with
> "LANGUAGE=fr"?  If so, should my client only display the one in
> French, or should it display all three values?
>
> Currently, I think it should display all three values...

Its really not clear how multi-lingual 'alternatives' of an iCalendar 
component should be handled. The suggestion of using multiple properties 
with different LANGUAGES really does not work as there is no way to 
unambiguously tie the variants together as alternatives.

A better approach might be to say that language alternatives should be 
constructed at the MIME level - i.e. as separate components in separate 
MIME parts inside a multipart/alternative.

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 9A4E280C71 for <[e-mail]>; Mon,  6 Nov 2006 07:01:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 8C3AC14229A for <[e-mail]>; Mon,  6 Nov 2006 07:01:01 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07413-03 for <[e-mail]>; Mon, 6 Nov 2006 07:01:01 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id DA6D5142278 for <[e-mail]>; Mon,  6 Nov 2006 07:01:00 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6F0e75021178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 10:00:46 -0500
Date: Mon, 06 Nov 2006 07:00:34 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.6.5 Time Zone Component: Not required when DTSTART is a DATE
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED, AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:01:03 -0000

Hi Bernard,

--On November 5, 2006 5:28:29 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

> Proposed new text:
>
>  > The "VTIMEZONE" calendar component MUST be present if the calendar
>  > component contains an "RRULE" that generates recurrence instances on
>  > both sides of a time zone shift (e.g., both in Standard Time and
>  > Daylight Saving Time) unless the "DTSTART" property of the calendar
>  > component is specified as a DATE value or as a "floating" DATE-TIME
>  > value (See section 3.3.12 for proper interpretation of floating time).

Actually what is being said here is that a recurring event that uses a 
DATE-TIME value for DTSTART MUST either be floating or local time (i.e. 
timezone). Whether VTIMEZONE is present or not is then determined by the 
requirement of having it present if a DTSTART uses a TZID property. i.e. 
the RRULE does not drive the requirement for VTIMEZONE, instead the DTSTART 
does.

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 1D97980C58 for <[e-mail]>; Mon,  6 Nov 2006 07:01:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 0E63D142278 for <[e-mail]>; Mon,  6 Nov 2006 07:01:00 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09169-03 for <[e-mail]>; Mon, 6 Nov 2006 07:00:56 -0800 (PST)
Received: from doob.fam.tuwien.ac.at (doob.fam.tuwien.ac.at [128.130.51.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 0F3EE14227B for <[e-mail]>; Mon,  6 Nov 2006 07:00:55 -0800 (PST)
Received: from curie.fam.tuwien.ac.at ([e-mail] [128.130.51.116]) by doob.fam.tuwien.ac.at (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id kA6F0p4r031072 for <[e-mail]>; Mon, 6 Nov 2006 16:00:54 +0100
From: Reinhold Kainhofer <[e-mail]>
Organization: FAM, Vienna University of Technology
To: [e-mail]
Subject: Re: [Ietf-calsify] Section 4.6.1 Event Component: DURATION when =?iso-8859-1?q?DTSTART=09is_a?= DATE
Date: Mon, 6 Nov 2006 16:00:48 +0100
User-Agent: KMail/1.9.5
References: <[e-mail]> <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.2 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 15:01:00 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Montag, 6. November 2006 15:44 schrieb Cyrus Daboo:
> Hi Bernard,
>
> --On November 5, 2006 5:25:58 PM -0500 Bernard Desruisseaux
>
> <[e-mail]> wrote:
> >  > The "VEVENT" is also the calendar component used to specify an
> >  > anniversary or daily reminder within a calendar. These events have a
> >  > DATE value type for the "DTSTART" property instead of the default
> >  > data type of DATE-TIME. If such a "VEVENT" has a "DTEND" property, it
> >  > MUST be specified as a DATE value also.
> >
> > I believe the text should also specify the following with respect
> >
> > to the DURATION property:
> >  > If such a "VEVENT" has a "DURATION" property, it MUST be specified
> >  > as a "dur-day" or "dur-week" values.
>
> +1

Completely agree, too.
The problem with rfc 2445 is inter alias that it only standardizes a syntax, 
but does not care about internal consistency of data. E.g. it was never 
explicitly forbidden to create an event with a DATE-TIME value for DTSTART 
and a DATE value for DTEND. Or an DATE value for DTSTART and a DATE-TIME 
value of RDATE (what should be the duration of that instance??) 

Looking at the archives, F. Dawson or M. Stenerson stated that it was 
understood that the types should match, but that the rfc never tried to 
enforce something like this. 

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: [e-mail], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFT04jTqjEwhXvPN0RAro3AJsFzQv/zFFCZlNZMQYNrU+QKc37OQCgwEDw
lwp93mz2QKudT4WZCBsz6jQ=
=P6zC
-----END PGP SIGNATURE-----


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 10C8480B60 for <[e-mail]>; Mon,  6 Nov 2006 06:58:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 0109F1422E0 for <[e-mail]>; Mon,  6 Nov 2006 06:58:03 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06806-01 for <[e-mail]>; Mon, 6 Nov 2006 06:58:02 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 5ADC3142284 for <[e-mail]>; Mon,  6 Nov 2006 06:58:02 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6EvaUg021163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 09:57:45 -0500
Date: Mon, 06 Nov 2006 06:57:31 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.6.3 Journal Component: DESCRIPTION property
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 14:58:03 -0000

Hi Bernard,

--On November 5, 2006 5:27:32 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

>  > jourprop   = *(
>  >
>  >            ; the following are optional,
>  >            ; but MUST NOT occur more than once
>  >
>  >            class / created / description / dtstart / dtstamp /
>  >            last-mod / organizer / recurid / seq / status /
>  >            summary / uid / url /
>
> But according to section 4.8.1.5 Description, the "DESCRIPTION"
> property can be specified multiple times within a "VJOURNAL"
> calendar component.
>
> As such, I propose to modify the "jourprop" rule in section
> 4.6.3 to be in accordance with the text in section 4.8.1.5.

+1

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 92B83808CF for <[e-mail]>; Mon,  6 Nov 2006 06:49:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 828C31422E0 for <[e-mail]>; Mon,  6 Nov 2006 06:49:14 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02711-10 for <[e-mail]>; Mon, 6 Nov 2006 06:49:13 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 9661D142284 for <[e-mail]>; Mon,  6 Nov 2006 06:49:13 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6EmpXC021111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 09:48:59 -0500
Date: Mon, 06 Nov 2006 06:48:45 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.6.1 Event Component: Default duration of	day events
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 14:49:14 -0000

Hi Bernard,

--On November 5, 2006 5:26:48 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

> In section 4.6.1 Event Component of RFC 2445 it says:
>
>  > For cases where a "VEVENT" calendar component specifies a "DTSTART"
>  > property with a DATE data type but no "DTEND" property, the events
>  > non-inclusive end is the end of the calendar date specified by the
>  > "DTSTART" property.
>
> As such, the last sentence of the paragraph before the following example
> is wrong. This event would actually appear as opaque in a search for busy
> time.
>
>  > The following is an example of the "VEVENT" calendar component used
>  > to represent an anniversary that will occur annually. Since it takes
>  > up no time, it will not appear as opaque in a search for busy time;
>  > no matter what the value of the "TRANSP" property indicates:
>  >
>  >   BEGIN:VEVENT
>  >   UID:[e-mail]
>  >   DTSTAMP:19970901T1300Z
>  >   DTSTART:19971102
>  >   SUMMARY:Our Blissful Anniversary
>  >   CLASS:CONFIDENTIAL
>  >   CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
>  >   RRULE:FREQ=YEARLY
>  >   END:VEVENT
>
> I propose to remove this sentence and to add the TRANSP property to
> the example.
>
> Proposed text:
>
>  > The following is an example of the "VEVENT" calendar component used
>  > to represent an anniversary that will occur annually.
>  >
>  >   BEGIN:VEVENT
>  >   UID:[e-mail]
>  >   DTSTAMP:19970901T1300Z
>  >   DTSTART:19971102
>  >   SUMMARY:Our Blissful Anniversary
>  >   TRANSP:TRANSPARENT
>  >   CLASS:CONFIDENTIAL
>  >   CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
>  >   RRULE:FREQ=YEARLY
>  >   END:VEVENT
>
> Similarly, in section 4.8.2.4 Date/Time Start of RFC 2445 it says:
>
>  > Description: Within the "VEVENT" calendar component, this property
>  > defines the start date and time for the event. The property is
>  > REQUIRED in "VEVENT" calendar components. Events can have a start
>  > date/time but no end date/time. In that case, the event does not take
>  > up any time.
>
> I propose to remove the last two sentences of this paragraph.
>
> Proposed text:
>
>  > Description: Within the "VEVENT" calendar component, this property
>  > defines the start date and time for the event. The property is
>  > REQUIRED in "VEVENT" calendar components.
>
> Finally, in section 6 Recommended Practices of RFC 2445 it says:
>
>  > 2.  A calendar entry with a "DTSTART" property but no "DTEND"
>  >     property does not take up any time. It is intended to represent
>  >     an event that is associated with a given calendar date and time
>  >     of day, such as an anniversary. Since the event does not take up
>  >     any time, it MUST NOT be used to record busy time no matter what
>  >     the value for the "TRANSP" property.
>
> This is actually wrong. I would simply remove this text. The proper
> behave is described in section 4.6.1 Event Component.

This issue begs the question of whether all day events should automatically 
appear as opaque in free-busy lookups. I suspect most implementations do 
not add TRANS:TRANSPARENT when adding an 'anniversary' event - but having 
that block out time would be bad.

This would be a change to 2445, but one solution is to say the default 
TRANSP for all day events is TRANSPARENT rather than OPAQUE.

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 3FDDD7FE03 for <[e-mail]>; Mon,  6 Nov 2006 06:45:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 30E021422E1 for <[e-mail]>; Mon,  6 Nov 2006 06:45:26 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04162-09 for <[e-mail]>; Mon, 6 Nov 2006 06:45:24 -0800 (PST)
Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 74654142284 for <[e-mail]>; Mon,  6 Nov 2006 06:45:24 -0800 (PST)
Received: from [130.129.34.132] (127host128.starwoodbroadband.com [12.105.242.128]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kA6Ej3j4021097 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2006 09:45:08 -0500
Date: Mon, 06 Nov 2006 06:44:56 -0800
From: Cyrus Daboo <[e-mail]>
To: Bernard Desruisseaux <[e-mail]>, Calsify WG <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.6.1 Event Component: DURATION when DTSTART	is a DATE
Message-ID: <[e-mail]>
In-Reply-To: <[e-mail]>
References: <[e-mail]>
X-Mailer: Mulberry/4.0.7b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-3.3 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 14:45:26 -0000

Hi Bernard,

--On November 5, 2006 5:25:58 PM -0500 Bernard Desruisseaux 
<[e-mail]> wrote:

>  > The "VEVENT" is also the calendar component used to specify an
>  > anniversary or daily reminder within a calendar. These events have a
>  > DATE value type for the "DTSTART" property instead of the default
>  > data type of DATE-TIME. If such a "VEVENT" has a "DTEND" property, it
>  > MUST be specified as a DATE value also.
>
> I believe the text should also specify the following with respect
> to the DURATION property:
>
>  > If such a "VEVENT" has a "DURATION" property, it MUST be specified
>  > as a "dur-day" or "dur-week" values.

+1

-- 
Cyrus Daboo



Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 5B36F80DFF for <[e-mail]>; Mon,  6 Nov 2006 06:01:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 4D7C61422DF for <[e-mail]>; Mon,  6 Nov 2006 06:01:07 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10891-09 for <[e-mail]>; Mon, 6 Nov 2006 06:01:04 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 9F35A14225E for <[e-mail]>; Mon,  6 Nov 2006 06:01:04 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA6E0tY9032083; Mon, 6 Nov 2006 07:00:55 -0700
Received: from dhcp-amer-rmdc-csvpn-gw4-141-144-99-22.vpn.oracle.com by rcsmt251.oracle.com with ESMTP id 2173321851162821643; Mon, 06 Nov 2006 07:00:43 -0700
Message-ID: <[e-mail]>
Date: Mon, 06 Nov 2006 09:00:37 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Reinhold Kainhofer <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.8.5.3 Recurrence Date/Times: RDATE < DTSTART
References: <[e-mail]> <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Cc: [e-mail]
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 14:01:07 -0000

Reinhold,

In my opinion we need to allow RDATE to be less than DTSTART,
even more so now that DTSTART should be synchronized with the
recurrence rule.

Let's say I want to have a meeting today (Monday) with three
further instances on the next upcoming Tuesday. I could easily
do that with an RDATE set to today (Monday) and a DTSTART set
to tomorrow (Tuesday) and RRULE:FREQ=WEEKLY;BYDAY=TU;COUNT=3.

Cheers,
Bernard

Reinhold Kainhofer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Am Sonntag, 5. November 2006 23:33 schrieb Bernard Desruisseaux:
>> In section 4.8.5.3 Recurrence Date/Times of RFC 2445 it says:
>>  > The "DTSTART" property defines the first instance in the
>>  > recurrence set.
>>
>> I believe this section should clarify that the "RDATE" property
>> value can actually be earlier in time than the value of the
>> "DTSTART" property.
> 
> I always understood this sentence that the DTSTART is always the first 
> date/time of the event and RDATE cannot be earlier. Otherwise, to determine 
> whether an event happens today, one would have to look at all recurrences of 
> all events, future or past. If the DTSTART is always the first time, then it 
> suffices to look at all events that have already started at the given date 
> (i.e. DTSTART<=givenDateTime).
> 
> Cheers,
> Reinhold
> - -- 
> - ------------------------------------------------------------------
> Reinhold Kainhofer, Vienna University of Technology, Austria
> email: [e-mail], http://reinhold.kainhofer.com/
>  * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
>  * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
>  * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> 
> iD8DBQFFTvUFTqjEwhXvPN0RAsPDAJ4n+XOsCnoXHjZIfHS//FrbChScywCfeHY6
> RUXtgVx4DX3mzyaAq+CT9j4=
> =5sgz
> -----END PGP SIGNATURE-----
> _______________________________________________
> Ietf-calsify mailing list
> [e-mail]
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id B60AE80BCF; Mon,  6 Nov 2006 05:35:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id A6EA9142250; Mon,  6 Nov 2006 05:35:16 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28919-02; Mon, 6 Nov 2006 05:35:12 -0800 (PST)
Received: from capricorn.notesdev.ibm.com (capricorn.notesdev.ibm.com [205.159.212.202]) by laweleka.osafoundation.org (Postfix) with ESMTP id AEC181422DF; Mon,  6 Nov 2006 05:35:12 -0800 (PST)
In-Reply-To: <[e-mail]>
To: "Tim Hare" <[e-mail]>
Subject: RE: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: RECURRENCE-ID of an instance might change?
Message-ID: <OF69C06291.AB26FA1A-ON8525721E.004A2F93-8525721E.004A98E9@LocalDomain>
Date: Mon, 6 Nov 2006 08:35:10 -0500
From: "Robert Ransdell" <[e-mail]>
Content-Type: multipart/alternative; boundary="=_alternative 004A98DD8525721E_="
MIME-Version: 1.0
X-KeepSent: 69C06291:AB26FA1A-8525721E:004A2F93; name=$KeepSent; type=4
X-Mailer: Lotus Notes Build V703_10172006NP October 17, 2006
X-Disclaimed: 25399
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.2 tagged_above=-50.0 required=4.0 tests=AWL, HTML_30_40, HTML_MESSAGE
X-Spam-Level: 
Cc: 'Calsify WG' <[e-mail]>, [e-mail]
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 13:35:16 -0000

--=_alternative 004A98DD8525721E_=
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

If  I remember correctly from those discussions, the only time the=20
RECURRENCE=5FID's can change, is when ORGANIZER changes the repeat rule for=
=20
the entire set.  I was part of that long heated discussion, so this will=20
be my only response/reminder of what was said.




"Tim Hare" <[e-mail]>=20
Sent by: [e-mail]
11/05/2006 06:16 PM

To
"'Calsify WG'" <[e-mail]>
cc

Subject
RE: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: RECURRENCE-ID of an=20
instance might change?






=20
Before making any changes in the SEQUENCE/RECURRENCE-ID area, I would
suggest you thoroughly search the archives (for this WG and for the=20
previous
WG)  for the many lengthy (and sometimes heated) discussions about this=20
very
thing.  Who "owns" those archives? This subject has been so confusing that
it would be worthwhile to collect all of those messages into their own=20
space
somewhere.

Tim Hare
Interested Bystander, Non-Inc.

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]] On Behalf Of Bernard
Desruisseaux
Sent: Sunday, November 05, 2006 5:33 PM
To: Calsify WG
Subject: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: RECURRENCE-ID of an
instance might change?

In section 4.8.4.4 Recurrence ID of RFC 2445 it says:

 > When the definition of the recurrence set for a calendar component  >
changes, and hence the "SEQUENCE" property value changes, the  >
"RECURRENCE-ID" for a given recurrence instance might also change.

How could one possibly correlate the specific recurrence instance for=20
which
the "RECURRENCE-ID" changed?

When the definition of the recurrence set for a calendar component=20
changes,
specific recurrence instances might be added or removed from the=20
recurrence
set.

I propose to remove the text mentioned above.

Cheers,
Bernard
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Ietf-calsify mailing list
[e-mail]
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Ietf-calsify mailing list
[e-mail]
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify



--=_alternative 004A98DD8525721E_=
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable


<br><font size=3D2 face=3D"sans-serif">If &nbsp;I remember correctly from t=
hose
discussions, the only time the </font><tt><font size=3D2>RECURRENCE</font><=
/tt><font size=3D2 face=3D"sans-serif">=5FID's
can change, is when ORGANIZER changes the repeat rule for the entire set.
<i>&nbsp;</i>I was part of that long heated discussion, so this will be
my only response/reminder of what was said.</font><br><br><br><br><table wi=
dth=3D100%><tr valign=3Dtop><td width=3D40%><font size=3D1 face=3D"sans-ser=
if"><b>&quot;Tim Hare&quot; &lt;[e-mail]&gt;</b></font><br><font=
 size=3D1 face=3D"sans-serif">Sent by: ietf-calsify-bounces@osafoundation.o=
rg</font><p><font size=3D1 face=3D"sans-serif">11/05/2006 06:16 PM</font><t=
d width=3D59%><table width=3D100%><tr valign=3Dtop><td><div align=3Dright><=
font size=3D1 face=3D"sans-serif">To</font></div><td><font size=3D1 face=3D=
"sans-serif">&quot;'Calsify WG'&quot; &lt;[e-mail]&gt=
;</font><tr valign=3Dtop><td><div align=3Dright><font size=3D1 face=3D"sans=
-serif">cc</font></div><td><tr valign=3Dtop><td><div align=3Dright><font si=
ze=3D1 face=3D"sans-serif">Subject</font></div><td><font size=3D1 face=3D"s=
ans-serif">RE: [Ietf-calsify] Section 4.8.4.4 Recurrence
ID: RECURRENCE-ID of an &nbsp; &nbsp; &nbsp; &nbsp;instance might
change?</font></table><br><table><tr valign=3Dtop><td><td></table><br></tab=
le><br><br><br><tt><font size=3D2>&nbsp;<br>Before making any changes in th=
e SEQUENCE/RECURRENCE-ID area, I would<br>suggest you thoroughly search the=
 archives (for this WG and for the previous<br>WG) &nbsp;for the many lengt=
hy (and sometimes heated) discussions about
this very<br>thing. &nbsp;Who &quot;owns&quot; those archives? This subject=
 has been
so confusing that<br>it would be worthwhile to collect all of those message=
s into their own
space<br>somewhere.<br><br>Tim Hare<br>Interested Bystander, Non-Inc.<br><b=
r>-----Original Message-----<br>From: [e-mail]=
g<br>[mailto:[e-mail]] On Behalf Of Bernard<b=
r>Desruisseaux<br>Sent: Sunday, November 05, 2006 5:33 PM<br>To: Calsify WG=
<br>Subject: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: RECURRENCE-ID of
an<br>instance might change?<br><br>In section 4.8.4.4 Recurrence ID of RFC=
 2445 it says:<br><br> &gt; When the definition of the recurrence set for a=
 calendar component
&nbsp;&gt;<br>changes, and hence the &quot;SEQUENCE&quot; property value ch=
anges, the
&nbsp;&gt;<br>&quot;RECURRENCE-ID&quot; for a given recurrence instance mig=
ht also change.<br><br>How could one possibly correlate the specific recurr=
ence instance for which<br>the &quot;RECURRENCE-ID&quot; changed?<br><br>Wh=
en the definition of the recurrence set for a calendar component changes,<b=
r>specific recurrence instances might be added or removed from the recurren=
ce<br>set.<br><br>I propose to remove the text mentioned above.<br><br>Chee=
rs,<br>Bernard<br>=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F<br>Ietf-calsify mailing list<br>[e-mail]<br=
>http://lists.osafoundation.org/mailman/listinfo/ietf-calsify<br><br><br>=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>Ietf-=
calsify mailing list<br>[e-mail]<br>http://lists.osaf=
oundation.org/mailman/listinfo/ietf-calsify<br></font></tt><br><BR>
--=_alternative 004A98DD8525721E_=--


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 761B680DC8 for <[e-mail]>; Mon,  6 Nov 2006 00:40:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 3E0751422D8 for <[e-mail]>; Mon,  6 Nov 2006 00:40:42 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12507-10 for <[e-mail]>; Mon, 6 Nov 2006 00:40:39 -0800 (PST)
Received: from doob.fam.tuwien.ac.at (doob.fam.tuwien.ac.at [128.130.51.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 528B91422C1 for <[e-mail]>; Mon,  6 Nov 2006 00:40:39 -0800 (PST)
Received: from einstein.kainhofer.com (localhost [127.0.0.1]) by doob.fam.tuwien.ac.at (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id kA68ebXa004946 for <[e-mail]>; Mon, 6 Nov 2006 09:40:37 +0100
From: Reinhold Kainhofer <[e-mail]>
Organization: Vienna University of Technology
To: [e-mail]
Subject: Re: [Ietf-calsify] Section 4.8.5.3 Recurrence Date/Times: RDATE < DTSTART
Date: Mon, 6 Nov 2006 09:40:37 +0100
User-Agent: KMail/1.9.5
References: <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.2 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 08:40:42 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Sonntag, 5. November 2006 23:33 schrieb Bernard Desruisseaux:
> In section 4.8.5.3 Recurrence Date/Times of RFC 2445 it says:
>  > The "DTSTART" property defines the first instance in the
>  > recurrence set.
>
> I believe this section should clarify that the "RDATE" property
> value can actually be earlier in time than the value of the
> "DTSTART" property.

I always understood this sentence that the DTSTART is always the first 
date/time of the event and RDATE cannot be earlier. Otherwise, to determine 
whether an event happens today, one would have to look at all recurrences of 
all events, future or past. If the DTSTART is always the first time, then it 
suffices to look at all events that have already started at the given date 
(i.e. DTSTART<=givenDateTime).

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: [e-mail], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFTvUFTqjEwhXvPN0RAsPDAJ4n+XOsCnoXHjZIfHS//FrbChScywCfeHY6
RUXtgVx4DX3mzyaAq+CT9j4=
=5sgz
-----END PGP SIGNATURE-----


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id A637580CF6 for <[e-mail]>; Mon,  6 Nov 2006 00:40:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 975C41422D8 for <[e-mail]>; Mon,  6 Nov 2006 00:40:38 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20510-01 for <[e-mail]>; Mon, 6 Nov 2006 00:40:37 -0800 (PST)
Received: from doob.fam.tuwien.ac.at (doob.fam.tuwien.ac.at [128.130.51.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id A79211422C1 for <[e-mail]>; Mon,  6 Nov 2006 00:40:36 -0800 (PST)
Received: from einstein.kainhofer.com (localhost [127.0.0.1]) by doob.fam.tuwien.ac.at (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id kA68eTog004876 for <[e-mail]>; Mon, 6 Nov 2006 09:40:29 +0100
From: Reinhold Kainhofer <[e-mail]>
Organization: Vienna University of Technology
To: [e-mail]
Subject: Re: [Ietf-calsify] Section 6 Recommended Practices #3: Different TZID?
Date: Mon, 6 Nov 2006 09:40:26 +0100
User-Agent: KMail/1.9.5
References: <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-0.2 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2006 08:40:38 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Sonntag, 5. November 2006 23:35 schrieb Bernard Desruisseaux:
> In section 6 Recommended Practices of RFC 2445 it says:
>  > 3.  When the "DTSTART" and "DTEND", for "VEVENT", "VJOURNAL" and
>  >     "VFREEBUSY" calendar components, and "DTSTART" and "DUE", for
>  >     "VTODO" calendar components, have the same value data type (e.g.,
>  >     DATE-TIME), they SHOULD specify values in the same time format
>  >     (e.g., UTC time format).
>
> What about DATE-TIME values with different TZID parameter values
> (e.g., airline flights, that start in one time zone and end in
> another)?  Obviously, I think this should be okay.

I also think that's okay with the formulation above, as long as both are given 
with TZID. What's not allowed is to have e.g. DTSTART in "Z"-notation and 
DTEND in floating or timezone notation.

Cheers,
Reinhold

- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: [e-mail], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFTvT9TqjEwhXvPN0RAt7eAJ0XHsM21QuyOIUeLAruQAqV3794tACfQcdl
NeVRw1PU+dO14mKICzOI8iE=
=XIMb
-----END PGP SIGNATURE-----


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id C705980F48 for <[e-mail]>; Sun,  5 Nov 2006 15:53:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id B95D91422C2 for <[e-mail]>; Sun,  5 Nov 2006 15:53:28 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10821-04 for <[e-mail]>; Sun, 5 Nov 2006 15:53:27 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 082FB1422C1 for <[e-mail]>; Sun,  5 Nov 2006 15:53:26 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5LbRaW023786; Sun, 5 Nov 2006 16:53:24 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt250.oracle.com with ESMTP id 2172047831162770782; Sun, 05 Nov 2006 16:53:02 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 18:53:01 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Tim Hare <[e-mail]>
Subject: Re: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: Allowed forms for aDATE-TIME
References: <[e-mail]>
In-Reply-To: <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Cc: 'Calsify WG' <[e-mail]>
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 23:53:28 -0000

Tim Hare wrote:
> Wait! Are you saying that recurrence rules cannot use "floating" date-time?

Humm.  I was.  On second thought, I realize that this needs to be possible.

> There's a very good use case for it: conference scheduling. There might be
> an "administrivia" meeting every morning of the conference week at the same
> time and place - a clear case for recurrence - yet, many attendees do not
> like to set their devices to the local time of the conference (unless the
> device changes to local time automatically as cell phones do) and so the
> conference schedule is published in "floating" time. 

I don't believe anybody should publish a conference schedule in "floating
time", but I agree that one might want to publish recurring floating
events such as "Lunch" or "Diner"...

Cheers,
Bernard

> 
> 
> Tim Hare
> Interested Bystander, Non-Inc.
> 
> -----Original Message-----
> From: [e-mail]
> [mailto:[e-mail]] On Behalf Of Bernard
> Desruisseaux
> Sent: Sunday, November 05, 2006 5:31 PM
> To: Calsify WG
> Subject: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: Allowed forms for
> aDATE-TIME
> 
> In section 4.8.4.4 Recurrence ID of RFC 2445 it says:
> 
>  > Value Type: The default value type for this property is DATE-TIME.
>  > The time format can be any of the valid forms defined for a DATE-TIME  >
> value type. See DATE-TIME value type definition for specific  >
> interpretations of the various forms. The value type can be set to  > DATE.
> 
> I don't believe it should be possible to specify a "RECURRENCE-ID"
> property with a "floating" date-time.
> 
> Proposed text:
> 
>  > Value Type: The default value type is DATE-TIME. The date-time
>  >    value MUST be either a date with UTC time, or a date with
>  >    local time and time zone reference. The value type can be
>  >    set to a DATE value type.
> 
> Cheers,
> Bernard
> _______________________________________________
> Ietf-calsify mailing list
> [e-mail]
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
> 
> 
> _______________________________________________
> Ietf-calsify mailing list
> [e-mail]
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id AE89080D48 for <[e-mail]>; Sun,  5 Nov 2006 15:16:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 9EF6D1422BD for <[e-mail]>; Sun,  5 Nov 2006 15:16:01 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31782-06 for <[e-mail]>; Sun, 5 Nov 2006 15:16:00 -0800 (PST)
Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.200.82]) by laweleka.osafoundation.org (Postfix) with ESMTP id 2D28D1422BA for <[e-mail]>; Sun,  5 Nov 2006 15:16:00 -0800 (PST)
Received: from thare (c-68-84-31-33.hsd1.fl.comcast.net[68.84.31.33]) by comcast.net (sccrmhc12) with SMTP id <2006110523155901200ngo4je>; Sun, 5 Nov 2006 23:15:59 +0000
From: "Tim Hare" <[e-mail]>
To: "'Calsify WG'" <[e-mail]>
Subject: RE: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: RECURRENCE-ID of an instance might change?
Date: Sun, 5 Nov 2006 18:15:58 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <[e-mail]>
Thread-Index: AccBKpX9UqmdZAjXQpe5urZ5+CIe4QABWkwA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=2.6 tagged_above=-50.0 required=4.0 tests=AWL, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS, MSGID_FROM_MTA_ID
X-Spam-Level: **
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 23:16:01 -0000

 
Before making any changes in the SEQUENCE/RECURRENCE-ID area, I would
suggest you thoroughly search the archives (for this WG and for the previous
WG)  for the many lengthy (and sometimes heated) discussions about this very
thing.  Who "owns" those archives? This subject has been so confusing that
it would be worthwhile to collect all of those messages into their own space
somewhere.

Tim Hare
Interested Bystander, Non-Inc.

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]] On Behalf Of Bernard
Desruisseaux
Sent: Sunday, November 05, 2006 5:33 PM
To: Calsify WG
Subject: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: RECURRENCE-ID of an
instance might change?

In section 4.8.4.4 Recurrence ID of RFC 2445 it says:

 > When the definition of the recurrence set for a calendar component  >
changes, and hence the "SEQUENCE" property value changes, the  >
"RECURRENCE-ID" for a given recurrence instance might also change.

How could one possibly correlate the specific recurrence instance for which
the "RECURRENCE-ID" changed?

When the definition of the recurrence set for a calendar component changes,
specific recurrence instances might be added or removed from the recurrence
set.

I propose to remove the text mentioned above.

Cheers,
Bernard
_______________________________________________
Ietf-calsify mailing list
[e-mail]
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify




Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 6E38180C68 for <[e-mail]>; Sun,  5 Nov 2006 15:13:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 5F4931422BD for <[e-mail]>; Sun,  5 Nov 2006 15:13:18 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01969-04 for <[e-mail]>; Sun, 5 Nov 2006 15:13:16 -0800 (PST)
Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [63.240.77.81]) by laweleka.osafoundation.org (Postfix) with ESMTP id D85361422C2 for <[e-mail]>; Sun,  5 Nov 2006 15:13:15 -0800 (PST)
Received: from thare (c-68-84-31-33.hsd1.fl.comcast.net[68.84.31.33]) by comcast.net (sccrmhc11) with SMTP id <2006110523131401100cenmqe>; Sun, 5 Nov 2006 23:13:15 +0000
From: "Tim Hare" <[e-mail]>
To: "'Calsify WG'" <[e-mail]>
Subject: RE: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: Allowed forms for aDATE-TIME
Date: Sun, 5 Nov 2006 18:13:12 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <[e-mail]>
Thread-Index: AccBKk8PCqolWE52T4WLZQKQX3EVpgABRu/w
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Message-Id: <[e-mail]>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=2.6 tagged_above=-50.0 required=4.0 tests=AWL, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS, MSGID_FROM_MTA_ID
X-Spam-Level: **
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 23:13:18 -0000

Wait! Are you saying that recurrence rules cannot use "floating" date-time?
There's a very good use case for it: conference scheduling. There might be
an "administrivia" meeting every morning of the conference week at the same
time and place - a clear case for recurrence - yet, many attendees do not
like to set their devices to the local time of the conference (unless the
device changes to local time automatically as cell phones do) and so the
conference schedule is published in "floating" time. 


Tim Hare
Interested Bystander, Non-Inc.

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]] On Behalf Of Bernard
Desruisseaux
Sent: Sunday, November 05, 2006 5:31 PM
To: Calsify WG
Subject: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: Allowed forms for
aDATE-TIME

In section 4.8.4.4 Recurrence ID of RFC 2445 it says:

 > Value Type: The default value type for this property is DATE-TIME.
 > The time format can be any of the valid forms defined for a DATE-TIME  >
value type. See DATE-TIME value type definition for specific  >
interpretations of the various forms. The value type can be set to  > DATE.

I don't believe it should be possible to specify a "RECURRENCE-ID"
property with a "floating" date-time.

Proposed text:

 > Value Type: The default value type is DATE-TIME. The date-time
 >    value MUST be either a date with UTC time, or a date with
 >    local time and time zone reference. The value type can be
 >    set to a DATE value type.

Cheers,
Bernard
_______________________________________________
Ietf-calsify mailing list
[e-mail]
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify




Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 631B2808F1 for <[e-mail]>; Sun,  5 Nov 2006 14:36:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 542741422B3 for <[e-mail]>; Sun,  5 Nov 2006 14:36:41 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29950-01 for <[e-mail]>; Sun, 5 Nov 2006 14:36:39 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 6B7771422D7 for <[e-mail]>; Sun,  5 Nov 2006 14:36:39 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5JWiMO012935 for <[e-mail]>; Sun, 5 Nov 2006 15:36:37 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt250.oracle.com with ESMTP id 2172031071162766134; Sun, 05 Nov 2006 15:35:34 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:35:33 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 6 Recommended Practices #4: Precedence of duration of RDATE
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:36:41 -0000

In section 6 Recommended Practices of RFC 2445 it says:

 > 4.  When the combination of the "RRULE" and "RDATE" properties on an
 >     iCalendar object produces multiple instances having the same
 >     start date/time, they should be collapsed to, and considered as,
 >     a single instance.

We should probably clarify that if the "RDATE" property is specified as
a PERIOD, its duration has precedence over the duration of the recurrence
instance defined by the "DTSTART" property.

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 00C6A8084C for <[e-mail]>; Sun,  5 Nov 2006 14:36:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id E5E7E1422D8 for <[e-mail]>; Sun,  5 Nov 2006 14:36:39 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27060-06 for <[e-mail]>; Sun, 5 Nov 2006 14:36:39 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 7C4D41422CD for <[e-mail]>; Sun,  5 Nov 2006 14:36:39 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5LNrwr025875 for <[e-mail]>; Sun, 5 Nov 2006 15:36:37 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt250.oracle.com with ESMTP id 2171170371162766166; Sun, 05 Nov 2006 15:36:06 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:36:05 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.8.2.5 Duration: VFREEBUSY request
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:36:40 -0000

In section 4.8.2.5 Duration of RFC 2445 it says:

 > In a "VFREEBUSY" calendar component the property may be
 > used to specify the interval of free time being requested.

Yet, section 3.3.2 REQUEST of RFC 2446 (iTIP) specifies that
the DURATION property is not allowed in a VFREEBUSY request.

I see three options:

a) Remove statement from iCalendar to be in sync with iTIP;

b) Change iTIP to allow the DURATION property in a VFREEBUSY
    request and define the semantic as specified in iCalendar.

c) Status quo.

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id E07888092A for <[e-mail]>; Sun,  5 Nov 2006 14:36:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id B12DF1422CD for <[e-mail]>; Sun,  5 Nov 2006 14:36:40 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29602-04 for <[e-mail]>; Sun, 5 Nov 2006 14:36:39 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 7AA7B1422B3 for <[e-mail]>; Sun,  5 Nov 2006 14:36:39 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5MSWDD024764 for <[e-mail]>; Sun, 5 Nov 2006 15:36:37 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt250.oracle.com with ESMTP id 2171717261162766101; Sun, 05 Nov 2006 15:35:01 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:35:01 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 6 Recommended Practices #3: Different TZID?
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:36:41 -0000

In section 6 Recommended Practices of RFC 2445 it says:

 > 3.  When the "DTSTART" and "DTEND", for "VEVENT", "VJOURNAL" and
 >     "VFREEBUSY" calendar components, and "DTSTART" and "DUE", for
 >     "VTODO" calendar components, have the same value data type (e.g.,
 >     DATE-TIME), they SHOULD specify values in the same time format
 >     (e.g., UTC time format).

What about DATE-TIME values with different TZID parameter values
(e.g., airline flights, that start in one time zone and end in
another)?  Obviously, I think this should be okay.

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 801E980694 for <[e-mail]>; Sun,  5 Nov 2006 14:34:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 722FD1422B3 for <[e-mail]>; Sun,  5 Nov 2006 14:34:39 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29527-04 for <[e-mail]>; Sun, 5 Nov 2006 14:34:38 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 275CA1422CD for <[e-mail]>; Sun,  5 Nov 2006 14:34:38 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5LHFuv011591 for <[e-mail]>; Sun, 5 Nov 2006 15:34:36 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt251.oracle.com with ESMTP id 2172030841162765994; Sun, 05 Nov 2006 15:33:14 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:33:14 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.8.5.3 Recurrence Date/Times: RDATE < DTSTART
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:34:41 -0000

In section 4.8.5.3 Recurrence Date/Times of RFC 2445 it says:

 > The "DTSTART" property defines the first instance in the
 > recurrence set.

I believe this section should clarify that the "RDATE" property
value can actually be earlier in time than the value of the
"DTSTART" property.

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 9C46380694 for <[e-mail]>; Sun,  5 Nov 2006 14:34:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 8B67B1422D8 for <[e-mail]>; Sun,  5 Nov 2006 14:34:38 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29939-02 for <[e-mail]>; Sun, 5 Nov 2006 14:34:38 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 20D051422B3 for <[e-mail]>; Sun,  5 Nov 2006 14:34:38 -0800 (PST)
Received: from rcsmt251.oracle.com (rcsmt251.oracle.com [148.87.90.196]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5LnZX7015909 for <[e-mail]>; Sun, 5 Nov 2006 15:34:36 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt251.oracle.com with ESMTP id 2172030921162766031; Sun, 05 Nov 2006 15:33:51 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:33:51 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.8.8.2 Request Status: 3-tuples or pairs?
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:34:38 -0000

In Section 4.8.8.2 Request Status of RFC 2445 it says:

 > The short return status is a PERIOD character (US-ASCII decimal 46)
 > separated 3-tuple of integers. For example, "3.1.1". The successive
 > levels of integers provide for a successive level of status code
 > granularity.

But all the examples in the draft specify REQUEST-STATUS values with
only a pair of integers (e.g., "2.0").

Furthermore, all the values specified in section 3.6 Status Replies of
RFC 2246 are only pair of integers.

I see two options:

a) Change text to allow pairs and 3-tuples;

b) Change text to allow pairs only.

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id C43A280699 for <[e-mail]>; Sun,  5 Nov 2006 14:34:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id B5C491422B3 for <[e-mail]>; Sun,  5 Nov 2006 14:34:38 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24347-06 for <[e-mail]>; Sun, 5 Nov 2006 14:34:38 -0800 (PST)
Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 4D5781422D7 for <[e-mail]>; Sun,  5 Nov 2006 14:34:38 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id kA5JoKhR013948 for <[e-mail]>; Sun, 5 Nov 2006 16:34:36 -0600
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt250.oracle.com with ESMTP id 2172030681162765964; Sun, 05 Nov 2006 15:32:44 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:32:44 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: RECURRENCE-ID of an instance might change?
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:34:38 -0000

In section 4.8.4.4 Recurrence ID of RFC 2445 it says:

 > When the definition of the recurrence set for a calendar component
 > changes, and hence the "SEQUENCE" property value changes, the
 > "RECURRENCE-ID" for a given recurrence instance might also change.

How could one possibly correlate the specific recurrence instance
for which the "RECURRENCE-ID" changed?

When the definition of the recurrence set for a calendar component
changes, specific recurrence instances might be added or removed
from the recurrence set.

I propose to remove the text mentioned above.

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id C38157F70F for <[e-mail]>; Sun,  5 Nov 2006 14:32:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id B51771422D7 for <[e-mail]>; Sun,  5 Nov 2006 14:32:38 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30691-04 for <[e-mail]>; Sun, 5 Nov 2006 14:32:37 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 032241422CD for <[e-mail]>; Sun,  5 Nov 2006 14:32:36 -0800 (PST)
Received: from rcsmt251.oracle.com (rcsmt251.oracle.com [148.87.90.196]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5LlYRE016046 for <[e-mail]>; Sun, 5 Nov 2006 15:32:35 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt251.oracle.com with ESMTP id 2171716471162765836; Sun, 05 Nov 2006 15:30:36 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:30:36 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.8.3.1 Time Zone Identifier: Scope of TZID
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:32:39 -0000

In section 4.8.3.1 Time Zone Identifier of RFC 2445 it says:

 > Purpose: This property specifies the text value that uniquely
 > identifies the "VTIMEZONE" calendar component.

This section should specify the "scope" in which a TZID MUST be
unique when the "TZID" property value does not start with a
SOLIDUS character.

I believe the "TZID" MUST be unique in the scope of an iCalendar
object, but not in the context of an iCalendar stream...

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 812397F70F for <[e-mail]>; Sun,  5 Nov 2006 14:32:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 71DF51422D8 for <[e-mail]>; Sun,  5 Nov 2006 14:32:37 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29527-02 for <[e-mail]>; Sun, 5 Nov 2006 14:32:37 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 073F21422D7 for <[e-mail]>; Sun,  5 Nov 2006 14:32:36 -0800 (PST)
Received: from rcsmt251.oracle.com (rcsmt251.oracle.com [148.87.90.196]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5LlYYA016023 for <[e-mail]>; Sun, 5 Nov 2006 15:32:35 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt250.oracle.com with ESMTP id 2172030211162765888; Sun, 05 Nov 2006 15:31:28 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:31:27 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.8.4.4 Recurrence ID: Allowed forms for a DATE-TIME
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:32:37 -0000

In section 4.8.4.4 Recurrence ID of RFC 2445 it says:

 > Value Type: The default value type for this property is DATE-TIME.
 > The time format can be any of the valid forms defined for a DATE-TIME
 > value type. See DATE-TIME value type definition for specific
 > interpretations of the various forms. The value type can be set to
 > DATE.

I don't believe it should be possible to specify a "RECURRENCE-ID"
property with a "floating" date-time.

Proposed text:

 > Value Type: The default value type is DATE-TIME. The date-time
 >    value MUST be either a date with UTC time, or a date with
 >    local time and time zone reference. The value type can be
 >    set to a DATE value type.

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 050648100E for <[e-mail]>; Sun,  5 Nov 2006 14:30:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id E96B11422D7 for <[e-mail]>; Sun,  5 Nov 2006 14:30:36 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29243-02 for <[e-mail]>; Sun, 5 Nov 2006 14:30:36 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id E3E5F1422CD for <[e-mail]>; Sun,  5 Nov 2006 14:30:35 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5ImHgr004067 for <[e-mail]>; Sun, 5 Nov 2006 15:30:34 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt251.oracle.com with ESMTP id 2169953351162765796; Sun, 05 Nov 2006 15:29:56 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:29:56 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.2 Property Parameters: ianaparam
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:30:37 -0000

Section 4.2 Property Parameters of RFC 2445 defines a "ianaparam"
rule in its ABNF, but while all the properties allow "xparam",
none of them currently allow "ianaparam".

Shouldn't all properties allow "ianaparam"? That is, parameters
*not* defined in this specification, but registered to IANA.

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 648408100E for <[e-mail]>; Sun,  5 Nov 2006 14:30:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 555051422D7 for <[e-mail]>; Sun,  5 Nov 2006 14:30:36 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26957-05 for <[e-mail]>; Sun, 5 Nov 2006 14:30:36 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id E2AEA1422B3 for <[e-mail]>; Sun,  5 Nov 2006 14:30:35 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5ImHlC004082 for <[e-mail]>; Sun, 5 Nov 2006 15:30:34 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt251.oracle.com with ESMTP id 2171716261162765766; Sun, 05 Nov 2006 15:29:26 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:29:25 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.1.2 Multiple Values: LANGUAGE parameter
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:30:36 -0000

RFC 2445 allows some properties of TEXT value type to be specified
multiple times. In some cases (e.g., "TZNAME") it is specified that
the property can be specified more than once for specifying multiple
language variants of the property value.

I think section 4.1.2 Multiple Values should clarify how the
"LANGUAGE" parameter should be handled with multi-valued TEXT
properties.

For instance, in a "VJOURNAL" calendar component, can I have two
"DESCRIPTION" with "LANGUAGE=en", but only one "DESCRIPTION" with
"LANGUAGE=fr"?  If so, should my client only display the one in
French, or should it display all three values?

Currently, I think it should display all three values...

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 4D49980FE7 for <[e-mail]>; Sun,  5 Nov 2006 14:28:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 3DA1D1422B3 for <[e-mail]>; Sun,  5 Nov 2006 14:28:36 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30230-01 for <[e-mail]>; Sun, 5 Nov 2006 14:28:34 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 8290F1422D7 for <[e-mail]>; Sun,  5 Nov 2006 14:28:34 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5MSWDB024764 for <[e-mail]>; Sun, 5 Nov 2006 15:28:32 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt251.oracle.com with ESMTP id 2171716211162765709; Sun, 05 Nov 2006 15:28:29 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:28:29 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.6.5 Time Zone Component: Not required when DTSTART is a DATE
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:28:36 -0000

In section 4.6.5 Time Zone Component of RFC 2445 it says:

 > The "VTIMEZONE" calendar component MUST be present if the iCalendar
 > object contains an RRULE that generates dates on both sides of a time
 > zone shift (e.g. both in Standard Time and Daylight Saving Time)
 > unless the iCalendar object intends to convey a floating time (See
 > the section "4.1.10.11 Time" for proper interpretation of floating
 > time).

I believe the text should further clarify that a "VTIMEZONE"
calendar component is not required when the calendar component
has a DATE value type for the "DTSTART" property.

Proposed new text:

 > The "VTIMEZONE" calendar component MUST be present if the calendar
 > component contains an "RRULE" that generates recurrence instances on
 > both sides of a time zone shift (e.g., both in Standard Time and
 > Daylight Saving Time) unless the "DTSTART" property of the calendar
 > component is specified as a DATE value or as a "floating" DATE-TIME
 > value (See section 3.3.12 for proper interpretation of floating time).

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 227E280FE7 for <[e-mail]>; Sun,  5 Nov 2006 14:28:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id E77751422D8 for <[e-mail]>; Sun,  5 Nov 2006 14:28:34 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30216-04 for <[e-mail]>; Sun, 5 Nov 2006 14:28:34 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 6F7C11422CD for <[e-mail]>; Sun,  5 Nov 2006 14:28:34 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5LNrwp025875 for <[e-mail]>; Sun, 5 Nov 2006 15:28:32 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt251.oracle.com with ESMTP id 2172029521162765654; Sun, 05 Nov 2006 15:27:34 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:27:32 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.6.3 Journal Component: DESCRIPTION property
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:28:35 -0000

In section 4.6.3 Journal Component of RFC 2445 it says:

 > jourprop   = *(
 >
 >            ; the following are optional,
 >            ; but MUST NOT occur more than once
 >
 >            class / created / description / dtstart / dtstamp /
 >            last-mod / organizer / recurid / seq / status /
 >            summary / uid / url /

But according to section 4.8.1.5 Description, the "DESCRIPTION"
property can be specified multiple times within a "VJOURNAL"
calendar component.

As such, I propose to modify the "jourprop" rule in section
4.6.3 to be in accordance with the text in section 4.8.1.5.

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 36EA280FE9 for <[e-mail]>; Sun,  5 Nov 2006 14:28:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 268601422CD for <[e-mail]>; Sun,  5 Nov 2006 14:28:35 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29602-02 for <[e-mail]>; Sun, 5 Nov 2006 14:28:34 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 6C9C91422B3 for <[e-mail]>; Sun,  5 Nov 2006 14:28:34 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5JWiMM012935 for <[e-mail]>; Sun, 5 Nov 2006 15:28:32 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt250.oracle.com with ESMTP id 2172029411162765610; Sun, 05 Nov 2006 15:26:50 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:26:48 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.6.1 Event Component: Default duration of day events
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:28:35 -0000

In section 4.6.1 Event Component of RFC 2445 it says:

 > For cases where a "VEVENT" calendar component specifies a "DTSTART"
 > property with a DATE data type but no "DTEND" property, the events
 > non-inclusive end is the end of the calendar date specified by the
 > "DTSTART" property.

As such, the last sentence of the paragraph before the following example
is wrong. This event would actually appear as opaque in a search for busy
time.

 > The following is an example of the "VEVENT" calendar component used
 > to represent an anniversary that will occur annually. Since it takes
 > up no time, it will not appear as opaque in a search for busy time;
 > no matter what the value of the "TRANSP" property indicates:
 >
 >   BEGIN:VEVENT
 >   UID:[e-mail]
 >   DTSTAMP:19970901T1300Z
 >   DTSTART:19971102
 >   SUMMARY:Our Blissful Anniversary
 >   CLASS:CONFIDENTIAL
 >   CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
 >   RRULE:FREQ=YEARLY
 >   END:VEVENT

I propose to remove this sentence and to add the TRANSP property to
the example.

Proposed text:

 > The following is an example of the "VEVENT" calendar component used
 > to represent an anniversary that will occur annually.
 >
 >   BEGIN:VEVENT
 >   UID:[e-mail]
 >   DTSTAMP:19970901T1300Z
 >   DTSTART:19971102
 >   SUMMARY:Our Blissful Anniversary
 >   TRANSP:TRANSPARENT
 >   CLASS:CONFIDENTIAL
 >   CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
 >   RRULE:FREQ=YEARLY
 >   END:VEVENT

Similarly, in section 4.8.2.4 Date/Time Start of RFC 2445 it says:

 > Description: Within the "VEVENT" calendar component, this property
 > defines the start date and time for the event. The property is
 > REQUIRED in "VEVENT" calendar components. Events can have a start
 > date/time but no end date/time. In that case, the event does not take
 > up any time.

I propose to remove the last two sentences of this paragraph.

Proposed text:

 > Description: Within the "VEVENT" calendar component, this property
 > defines the start date and time for the event. The property is
 > REQUIRED in "VEVENT" calendar components.

Finally, in section 6 Recommended Practices of RFC 2445 it says:

 > 2.  A calendar entry with a "DTSTART" property but no "DTEND"
 >     property does not take up any time. It is intended to represent
 >     an event that is associated with a given calendar date and time
 >     of day, such as an anniversary. Since the event does not take up
 >     any time, it MUST NOT be used to record busy time no matter what
 >     the value for the "TRANSP" property.

This is actually wrong. I would simply remove this text. The proper
behave is described in section 4.6.1 Event Component.

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 833A180FA6 for <[e-mail]>; Sun,  5 Nov 2006 14:26:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 756EC1422D7 for <[e-mail]>; Sun,  5 Nov 2006 14:26:34 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27308-03 for <[e-mail]>; Sun, 5 Nov 2006 14:26:34 -0800 (PST)
Received: from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 0D7111422CD for <[e-mail]>; Sun,  5 Nov 2006 14:26:33 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id kA5LZQp7023215 for <[e-mail]>; Sun, 5 Nov 2006 16:26:31 -0600
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt250.oracle.com with ESMTP id 2172029241162765558; Sun, 05 Nov 2006 15:25:58 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:25:58 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.6.1 Event Component: DURATION when DTSTART is a DATE
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:26:34 -0000

In section 4.6.1 Event Component of RFC 2445 it says:

 > The "VEVENT" is also the calendar component used to specify an
 > anniversary or daily reminder within a calendar. These events have a
 > DATE value type for the "DTSTART" property instead of the default
 > data type of DATE-TIME. If such a "VEVENT" has a "DTEND" property, it
 > MUST be specified as a DATE value also.

I believe the text should also specify the following with respect
to the DURATION property:

 > If such a "VEVENT" has a "DURATION" property, it MUST be specified
 > as a "dur-day" or "dur-week" values.

Cheers,
Bernard


Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id CF65380FA6 for <[e-mail]>; Sun,  5 Nov 2006 14:26:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id C0F4A1422CD for <[e-mail]>; Sun,  5 Nov 2006 14:26:34 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29785-02 for <[e-mail]>; Sun, 5 Nov 2006 14:26:33 -0800 (PST)
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 5A2211422B3 for <[e-mail]>; Sun,  5 Nov 2006 14:26:33 -0800 (PST)
Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id kA5FBPjL025817 for <[e-mail]>; Sun, 5 Nov 2006 15:26:31 -0700
Received: from dhcp-amer-rmdc-csvpn-gw5-141-144-104-86.vpn.oracle.com by rcsmt250.oracle.com with ESMTP id 2172028961162765474; Sun, 05 Nov 2006 15:24:34 -0700
Message-ID: <[e-mail]>
Date: Sun, 05 Nov 2006 17:24:33 -0500
From: Bernard Desruisseaux <[e-mail]>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Calsify WG <[e-mail]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelist: TRUE
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=AWL
X-Spam-Level: 
Subject: [Ietf-calsify] Section 4.3.10 Recurrence Rule: Order of rule parts
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:[e-mail]?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2006 22:26:34 -0000

In section 4.3.10 Recurrence Rule of RFC 2445 it says:

 > The rule parts are not ordered in any particular sequence.

On the other hand, the way the ABNF of the "recur" rule is
written, the "FREQ" rule should always appear first.

I'm not sure how the "recur" rule should be rewritten.
Any help appreciated...

Cheers,
Bernard