[OASIS Issue Tracker] (TOSCA-288) Specification must state whether TOSCA string names are case sensitive or not

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

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

Chris Lauwers commented on TOSCA-288:
-------------------------------------

Another question about name conflicts: If a service template defines a type with a name that is also used by a normative type, does that create a name conflict or will the type defined in the service template take precedence over the normative type? For example, what if a service template defines a new "tosca.nodes.Root" type?

> Specification must state whether TOSCA string names are case sensitive or not
> -----------------------------------------------------------------------------
>
>                 Key: TOSCA-288
>                 URL: https://issues.oasis-open.org/browse/TOSCA-288
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>            Reporter: Chris Lauwers
>            Assignee: Matthew Rutkowski
>
> While it appears from the examples that TOSCA string names are case sensitive, the specification doesn't explicitly say this. Prose should be added to clarify this (likely in the section that talks about names and namespaces)



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