OPEN - CSD04 - Need rules to assure non-collision (uniqueness) of requirement or capability names

When defining node types/templates we allow authors to defined named requirements (or capabilities). How do we prevent (name) collision if we allow others to augment a type or template definition with their own requirements or capabilities?

For example,with the following node template:

node_templates:
mysql:
type: tosca.nodes.MySQL
properties:
mysql_root_password:

{ get_input: my_mysql_rootpw }

mysql_port:

{ get_input: my_mysql_port }

requirements:

• host: db_server

What happens of a second named requirement of "host" is added?

What happens if a new Node Type that derives from MySQL is created and attempts to use the requirement name "host" which is already defined on the MySQL type?

---

Need prose and/or examples to discuss if these are errors or are side effects created (such as "choice" of "host".

---

In relation to this last thought, another bug will be opened in JIRA to ask this question.