> I like that, I'd even go as far as to consider dropping the concept of domain altogether and just talk about closest/farthest entrypoint. yeah, the

domain

concept is probably not required. i use it as short form to mean "the root of this hierarchy". but i suppose

root

will also do and its one less thing to think about. as long as people don't confuse that for

root.md

which is the root of your entire vault. will stew on this 🙂 > Didn't quite get that one... the

root

of a schema tree needs a something to match. the convention is for the root of a

schema tree

to match the root of a

note tree

(aka, its domain) (that being said, you could have a schema whose root matches the pattern

*

) > Yeah, personally I don't need it anymore after understanding the concept. Just thinking about new users, and potentially the ones who have not heard about schemas and namespaces before. What's the background for the "namespace"-term in this context, btw? using namespace in the computer science context (eg. a container of other things) --> https://en.wikipedia.org/wiki/Namespace - eg. my knowledge base has 12 hierarchies vs my knowledge base has 12 domains