Re: Re: When is a TODO really a TODO ? ...

[Carsten Dominik <carsten.dominik@gmail.com>]

On  6Nov2007, at 4:28 AM, Bastien wrote:

> Bernt Hansen <bernt@alumni.uwaterloo.ca> writes:
>
>>> - pedagogically: Org-mode tries to be "easy-entry, but then
>>>   lots of stuff under the hood".
>>>   This is why TODO items are introduced the way they are.
>>>   You said that you have been confused by this, so maybe it
>>>   is not the right way after all.  Any proposals on how to
>>>   address this in the docs?
>>>
>>
>> Maybe just call todo items 'Tasks' and their current state is 'TODO',
>> 'DONE', etc ?
>
> Good idea.  Here is a list of possible conventions for the manual:

> - use "keyword" for TODO keyword
> - use "tasks" for entries that have a keyword
> - use "entries" for other entries (or entries "in general")
> - use "heading" when referring to the entry as "outline-able"
> - use "headline" in the context of exporting/publishing
>
> Maybe some typesetting conventions wouldn't hurt, too:
>
> - use uppercase for KEYWORD
> - use uppercase for drawers and special PROPERTIES
> - capitalized the first letter for user-defined properties
> - use lower-case for tags
>
> Maybe this would help make the examples even more clearer.  This is
> especially crucial when if comes to complex agenda searches.
>
> What do you think?


This sounds like exactly how things should be......
One possible hickup:  In a GTD setting, an entry becomes a task by
attaching a context, so possibly without a TODO keyword.

- Carsten