Hello, tomos,
Illic and illac - well, I once attended a German "Gymnasium", and there I got the "Big Latinum", but that was ages ago, and my tries to differenciate the two, before using those terms here, by web search, was unsuccessful; they seem to be more or less synonyms, but perhaps not in all possible cases, so I'd be thankful for an expert to inform us of the minute differences in use of both (I suppose it's a "case" thing).
As for "viable tag M", "M" being "management", in all my posts (as "IM" is "information M" and "IMS" being "IM system"), but here, I just wanted to express that of course, a VERY basic condition for ANY tagging system should be to be able to (easily) combine tags not only in applicating them, but then again, when constituting any "collections" / "items' sub-groups" by combining them. (I'm even quite sure that in SOME way or another, that might be able in RN 3, but then, I asked for HOW to do this, explicitely in outlinersw forum, and, implicitely, here, but without getting any answer, and even IF it's possible in RN, it certainly is absolutely awful.)
Re clones: There's an "official" term for it used by some author, but which I quickly forgot; my today's synonym search for "clone" didn't bring it even (but brought "mimeo" which I kind of like). Again, the real prob doesn't lie in the term, but in its application:
Most outliners, once you clone an item, will NOT distinguish anymore between the "original" and the "clones", whilst conceptually, there should be an (updatable) difference, and which I call "natural parent" and "adoptive parent" - name it as you like, but it's evident any item in a tree hierarchy should have a "natural/main context", and then, perhaps multiple, "additional contexts" - and be it only for avoidance-of-recursion reasons: btw, I mentioned this problem within a discussion of InfoQube in the outlinerswforum, where the developer of IQ, Pierre Paul Landry, suberbly said (I'm citing from memory), "IQ allows for recursion"... when in fact, recursion is a PROBLEM of IM, and which has to be avoided/contained, and certainly not a feature of IM (development illac ;-) ).