[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (TOSCA-136) WD01 - Need rules to assure non-collision (uniqueness) of requirement or capability names
WD01 - Need rules to assure non-collision (uniqueness) of requirement or capability names ----------------------------------------------------------------------------------------- Key: TOSCA-136 URL: http://tools.oasis-open.org/issues/browse/TOSCA-136 Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC Issue Type: Improvement Components: Profile-YAML Affects Versions: CSD1 Reporter: Matthew Rutkowski Assignee: Thomas Spatzier Fix For: CSD1 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: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]