Why they prefer PROPERTIES over # + CATEGORNESS

Question

In the manual http://members.optusnet.com.au/~charles57/GTD/gtd_workflow.html under the heading Category tags, the author says that it is indicated that PROPERTIES should be preferred over CATEGORY. I can’t find a link that justifies it.

On the same page there is a link to authors who have cut out a version of their org file http://members.optusnet.com.au/~charles57/GTD/gtdsample.txt , which uses CATEGORY, not PROPERTIES.

Answer 1

#+CATEGORY distributed linearly through the org file (which is rather difficult to maintain in the tree structure), while the CATEGORY property will be applied to the subtree.

I personally use the #+CATEGORY declaration at the beginning of each file (to make sure all entries in the file have the category displayed on the agenda), and then configure the subtrees using the properties.

The reference manual has the same argument.