|
- Namespace Class
What is at the top of the element tree?
How should the kernel enforce the unique naming of elements whose superelement is null?
Should a single class track all the elements beneath? How?
Partial resolution: Separating the ideas of "container" and "element" in the semantics made
room for a new "namespace" class, which solves the unique naming bug and answers some of the
code architecture questions, though not all.
|