[caldav] All Day Events

Michael Rasmussen <mir@datanom.net> Wed, 09 March 2011 02:20 UTC

Return-Path: <mir@datanom.net>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F3E63A6808 for <caldav@core3.amsl.com>; Tue, 8 Mar 2011 18:20:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level:
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, WEIRD_PORT=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yWEKqnZH-8Mm for <caldav@core3.amsl.com>; Tue, 8 Mar 2011 18:20:31 -0800 (PST)
Received: from mail.datanom.net (unknown [90.184.69.179]) by core3.amsl.com (Postfix) with ESMTP id 2AC1A3A6800 for <caldav@ietf.org>; Tue, 8 Mar 2011 18:20:31 -0800 (PST)
Received: from sleipner.datanom.net (sleipner.datanom.net [192.168.2.79]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mir@datanom.net) by mail.datanom.net (Postfix) with ESMTPSA id 47D505826DEF for <caldav@ietf.org>; Wed, 9 Mar 2011 03:21:46 +0100 (CET)
Date: Wed, 9 Mar 2011 03:21:45 +0100
From: Michael Rasmussen <mir@datanom.net>
To: <caldav@ietf.org>
Message-ID: <20110309032145.0988bf9a@sleipner.datanom.net>
X-Mailer: Claws Mail 3.7.8cvs57 (GTK+ 2.20.1; x86_64-unknown-linux-gnu)
X-Face: +UpSPFkh3^t&rI|{Ou$3/l]vjTk; D5c0k; *3p?O2c+:bV#y*0q4EWQ[Kdd2=; <u7g2~aE~I k%*K{!Q#D)Vaiiqy~hxUz_8)mTt:m#WPV$ls:"s,.; p7SNdq>PR}nK
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A/wD/oL2nkwAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9kKERcdBc2f4noAAAHfSURBVGje7VmxkYMwEDwYKIE6FIhc9OCUkCbcADRBSOoeRAlE9CAVcZ88HoOBEUJwwvbNKMG7Hi26uV3ZgZQS4YKVZVkAAABSSjQpKtwSdxAS2qhv2xaCIHiutm3JTiK02XyWZdPjJBMRWvTepufeCfCtvk+AlHLTc+8ECCHeNiulBCEEiYDIhiSEAEQ//C8aRqPpCHWJc1Jf6cQ+OXZ45ObPcOzDBJzl2BHlBHFxGqQCbL3jVXh44HTb9FxrDVVVQZqmEMcxxHEMaZpCVVWgtaYZo//j7rmmnw3V9z1yzjGKotnFOce+788fo4NjD2uuZbTWkOc5dF23+D1d10Ge57MnQe7EdV2vbv5VRF3XcL/f/XLitdaZa6XVFjJ1Tpc4k7e/hg23OqdrnDMnNnVO1zjGmPFm57DkV8rb7bYLSy6gKAqjU2CMQVEUywJMndM1LkkSaJpmVQRjDJqmgSRJ1p3Y1Dld4xARlVJYluVorHLOsSxLVEotXmgufyMLvubX6SPe4iF3YutYS8XdG2upuG8ClFJGwYpz/pwKlNy3Ftoaa/dEYlfckYDH42E8AaZYKu5IwJ5YS8X9rP8H9sRaKu5IwJ5YS8X9iDH6OUZmG2upuJvjtK9h7vpx+lfE9QdGLGM23Jk+0QAAAABJRU5ErkJggg==
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/F0libmNe=mc5GyZUrp8N8az"; protocol="application/pgp-signature"
Subject: [caldav] All Day Events
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2011 02:20:32 -0000

Hi list,

Is there any normative way of handling all-day events on its way into
the specification?

The current situation seems to be split between two idioms. An all-day
event of 2011-03-03 is expressed in either of these two ways:
1)
DTSTART;VALUE=DATE:20110303
DTEND;VALUE=DATE:20110303 
2)
DTSTART;VALUE=DATE:20110303
DTEND;VALUE=DATE:20110304 

Personally I tend to vote for option 1) since option 2) clashes with
the possibility of specifying a two day event.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
Write clearly - don't be too clever.
            - The Elements of Programming Style (Kernighan & Plaugher)