Task: Author Section A.1.1 "A.1.1 Rules to avoid namespace collisions "

Here is the current preface for the section along with bullets of use cases that need to be developed to show how namespaces are used by TOSCA orchestrators.

TOSCA Simple Profiles allows template authors to declare their own types and templates and assign them simple names with no apparent namespaces. Since TOSCA Service Templates can import other service templates to introduce new types and topologies of templates that can be used to provide concrete implementations (or substitute) for abstract nodes. Rules are needed so that TOSCA Orchestrators know how to avoid collisions and apply their own namespaces when import and nesting occur.

The following cases are considered:
• Duplicate property names within same entity (e.g., Node Type, Node Template, Relationship Type, etc.)
• Duplicate requirement names within same entity (e.g., Node Type, Node Template, Relationship Type, etc.)
• Duplicate capability names within same entity (e.g., Node Type, Node Template, Relationship Type, etc.)
• Collisions that occurs from “import” for any Type or Template.
• Collision that occurs from “substitution” of other Node Templates