[whpalmer4]

Originally Posted by macula

I don't see what the problem was with the original implementation. We all review our projects regularly, so upon completing all subtasks of a group/project, and during the next review at the latest, would always find out that a "childless" parent task exists, and we would cross it out as completed.

Ah, so in a paper-based GTD system done strictly by the book you would have waited until you did a weekly review to notice that a project was done, rather than observing you had come to the end of your list of next actions?

Quite clearly, OmniFocus is not a 100% GTD-compliant system anymore.

No offense intended, but when people start talking about things being "100% GTD-compliant" it makes it difficult to read the post due to all the eye-rolling going on, it's like trying to read on a roller-coaster :-) You can find plenty of hits in a Google search for "GTD-compliant" but none of them are on David Allen's websites. He does however have the following description:

http://www.davidco.com/what_is_gtd.php

regarding which one maker of a "GTD-compliant" app list observes:

This list is short to accommodate individual preferences, and because the David Co. official description of GTD is very broad.

Yet those of us who adhere to GTD as a system—some of us practitioners for years—this is a step backwards.

Maybe your last sentence might start as follows:

Yet for some of us who adhere to GTD as a system

Fair enough? I've also been a GTD practitioner for years, and I think Ken would likely consider himself one as well. For something that's apparently a step backwards, he's always seemed pretty enthusiastic about it :-)