I’m not sure what you mean @Catherine …with the ancestor element the request of the original poster is explicitly addressed, i.e.,
- ancestor element facilitates finding/returning “all the children of a matching element”, so all the items of a related subject do not require explicit tagging -by the nature of ancestor they all explicitly become descendants (which is a good thing, i.e., less work and less tagging for more flexible results).
Something to consider is that auto-tagging might produce challenges, even a barrier, when one needs to craft detailed exclusions with inclusions.
If I am not mistaken, from a coder’s perspective, auto-tagging would break (convolute) the useful functionality, whereas onboarding ancestor element leaves DL only two steps away from perfection.
The other two dimensions left would seem to be cascading tags and then perhaps backlinking. A possible third was mentioned in the Roam thread, which I had not heard of or considered before, which is tag qualification, i.e., #quantity>5, #thisthing=Xfactor, etc applications, which is freaking brilliant really, and I never associated with tagging before.
So what did I miss in the original poster’s request?