From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Brand <michael.ch.brand@gmail.com>
Subject: Re: Occurance property, or some similar name?
Date: Wed, 13 Apr 2011 17:42:19 +0200
Message-ID: <BANLkTikGc0h_o8d4GyJj6aeTgEaaXpzqAQ@mail.gmail.com>
References: <87d3ksqujv.fsf@dustycloud.org> <87oc4bxoew.fsf@fastmail.fm>
	<8739lnnqfb.fsf@dustycloud.org>
	<BANLkTikEknz-UDLh8M+OAhn+Fc0ziLE2Xw@mail.gmail.com>
	<87wriyl2o6.fsf@dustycloud.org>
	<BANLkTik_UXhoCSWxUs+MgCHbwwnY6R-sNQ@mail.gmail.com>
	<87oc4aky8m.fsf@dustycloud.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:35094)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <michael.ch.brand@gmail.com>) id 1QA2D4-0007VD-Hg
	for emacs-orgmode@gnu.org; Wed, 13 Apr 2011 11:42:32 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <michael.ch.brand@gmail.com>) id 1QA2Cy-0002eV-KW
	for emacs-orgmode@gnu.org; Wed, 13 Apr 2011 11:42:26 -0400
Received: from mail-iw0-f169.google.com ([209.85.214.169]:53367)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <michael.ch.brand@gmail.com>) id 1QA2Cy-0002eP-GI
	for emacs-orgmode@gnu.org; Wed, 13 Apr 2011 11:42:20 -0400
Received: by iwg8 with SMTP id 8so1004009iwg.0
	for <emacs-orgmode@gnu.org>; Wed, 13 Apr 2011 08:42:20 -0700 (PDT)
In-Reply-To: <87oc4aky8m.fsf@dustycloud.org>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: </archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: Matt Lundin <mdl@imapmail.org>, emacs-orgmode@gnu.org

On Wed, Apr 13, 2011 at 16:43, Christopher Allan Webber
<cwebber@dustycloud.org> wrote:
> Michael Brand <michael.ch.brand@gmail.com> writes:
>> * _appointment_ that _occurs_ at bike shop (keyword inside drawer)
>> =A0:PROPERTIES:
>> =A0:TIMESTAMP: <2011-04-12 Tue 19:00>
>> =A0:END:
>> * _appointment_ that _occurs_ at bike shop (keyword outside drawer)
>> =A0:TIMESTAMP: <2011-04-12 Tue 19:00>
>> * _appointment_ that _occurs_ at bike shop (keyword-less, at least for
>> backward compatibility)
>> =A0 <2011-04-12 Tue 19:00>
>
> Interesting, I like that style. =A0My main concern is that newer orgmode
> files written in this form might break in older versions of orgmode.

Are your concerns concrete?

I have thought about and tested this already before: The three example
items above show up in the agenda, and are still correct even after
changing with `S->'. So this "newer/future" Org file format works even
with the "older/today" Org software. This is because the Org software
of today flexibly binds the special property TIMESTAMP per item to the
first active timestamp (i. e. "<>", not "[]") that is not prefixed
with `SCHEDULED: ' or `DEADLINE: '. This binding is the reason why I
would stick to the name TIMESTAMP when it comes to possibly new
features that should write this special property keyword explicitly
for this kind of timestamp. The sibling (not `C-c .') of `C-c
C-s'/`C-c C-d' that you suggested originally would be such a feature.

Michael