> - Can root-element be defined as a namespace? i.e. have schema for its grand-children? > - not currently. schemas need a domain to attach to. have been thinking about a

global schema

concept that might fit what you're thinking about > - Could the term "namespace" be changed to "open" (true/false) more clearly pointing out that a schema node is "open for extensions" > - it could. though i'm not sure if that's more obvious than namespace > - Assuming the "domain" denotes some kind of important partition that should be the root for activities like inserting new notes; what if the structure is such that domains make sense only on the second level, i.e. new notes should appear on third level. Would this kind of use case make sense, or is it just a design decision for dendron to support domains on first level only. - domains are meant to be the root of your hierarchies. there's no concept of a

domain

at deeper levels. that being said, i think

domain namespace

is a kludge and would like to support marking arbitrary points in your schema as entry points. this way, you could specify

defaultAddBehavior

in terms of the schema (eg.

schema: ${domain}.{path/to/child})

. thus,

childOfDomainNamespace

can eventually be replaced with something like

${domain}.${namespace}?