All SCDL models should declare a predefined child namespace for use by derived runtimes

[ChrisRus]

... or perhaps it's an extension point. Not sure. The point is that we need some prescribed binding point for derived runtime systems to attach their semantics to SCDL models. The supposition is that specific applications that leverage the SCDL data model (and by implication the encapsule/* libraries that operate on SCDL data), will leverage the prescribed binding namespace to extend the base semantics of SCDL with application-specific declaration chains...