@User > 1) what kind of use cases you currently have in mind for the note ids (uuid) which don't work with the "path ids" (some.note.in.the.hierarchy). - uuid are currently used to uniquely identify a note. this is mainly used for publishing to make sure the note link will stay constant even after renaming: https://github.com/dendronhq/dendron-template/blob/master/vault/dendron.topic.publishing.md#permanent-ids - otherwise, uuids are a hedge against future features that might make the path name not unique (eg. multiple vaults with the same paths though i supposed that could be mitigated by prefixing the vault) > 2) I believe schemas currently somehow rely on the concept of domains, however what would happen if there wouldn't be a separation between the domains and any other level in the hierarchy? the implementation for schemas is pretty simple right now - it constructs a glob pattern based on the 'root' of the schema and will match any hierarchy that matches that glob pattern. its related to domains in the sense that my convention has been to do one schema per domain. but with schema imports, you can also just construct an arbitrary schema, include it in an existing schema, and call it a day. for example, see the journal schema which is used inside the project schema: https://gist.github.com/kevinslin/5ca7a6f25a239add5ea374f329e6a19e i still own your an rfc about terms. i haven't forgotten about that. 😅