Assignment value type: container

[aclarkxyz]

The schema tree contains a mixture of branch nodes and leaf nodes. Many of the branch nodes are very generic concepts, and should never be used as explicit annotations, but the distinction is not always clear cut (e.g. some nodes are valid annotations that just happen to have child nodes that are even more specific).

The values that can be added to an assignment are currently [include/exclude/include*/exclude*]. We should add a 5th type, [container], which has the sole effect of signifying that that particular value should not be selected explicitly.

[kodecharlie]

I am looking into this issue. It is straightforward to add another branch / term type. As far as logic changes for container, is SchemaTree.buildTree the only module that is impacted? When you say "not explicitly selected", it seems like only the include branches are impacted here; ie, an excluded uri / branch is still excluded, whether it is a container or not.

Is this roughly the idea?