Hey all, Could anyone explain me what the benefit is of using node (or property) names that contain a namespace, instead of just using nodetypes to force rules on what can be placed on certain nodes? For example for the context aware config there has been chosen to call the node sling:settings and the property sling:configRef, or in AEM they use cq:dialog, cq:template and cq:editConfig Does this give any advantage over just using a normal node name with a custom primaryType? I have noticed you can not use arbitrarily namespaces if they haven't been registered, for example trying to make a node named custom:node will throw a RepositoryException if custom is not registered, so they definitely get checked specifically.
Thanks! Greetings, Roy
