[OASIS Issue Tracker] (TOSCA-302) Missing unique requirement for properties

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/TOSCA-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62898#comment-62898 ] 

Matthew Rutkowski commented on TOSCA-302:
-----------------------------------------

Actually, we do have requirements to avoid naming collision in section 3.1.3.1	Additional Requirements.  It includes text as follows:

•	Duplicate names for the following keynames within Types or Templates SHALL be considered an error.  These include, but are not limited to duplicate names found for the following keynames:
o	Properties (properties)
o	Attributes (attributes)
o	Artifacts (artifacts)
o	Requirements (requirements)
o	Capabilities (capabilities)
o	Interfaces (interfaces)


That being said we likely need to expand these lists for policy and group names.


> Missing unique requirement for properties
> -----------------------------------------
>
>                 Key: TOSCA-302
>                 URL: https://issues.oasis-open.org/browse/TOSCA-302
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Bug
>          Components: Profile-YAML
>    Affects Versions: V1.1_CSD04
>            Reporter: Luca Gioppo
>
> At the moment it seems that in 3.5.8.5 there is no requirement for having the property unique in the namespace of the entity so it could be possible to have multiple occurrences of:
> my_prop:
>   type: integer
> my_prop:
>   type: string
> This will default to the YAML merging behaviour, but that is not probably what we want so if we want to have just 1 property with that name is better to state it in the spec.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)