[OASIS Issue Tracker] (TOSCA-248) Consider mapping inputs and outputs and show different naming with example

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

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

Luca Gioppo commented on TOSCA-248:
-----------------------------------

If I understand well the issue there is the need to add some sort of labels to the input (at least) since those are used to ask dsata to the user and we could want not to expose an internal name that could not be easy to present.
We should also have some "validation" rule specified? (or we just keep the type of the input as minimal validation?)

> Consider mapping inputs and outputs and show different naming with example
> --------------------------------------------------------------------------
>
>                 Key: TOSCA-248
>                 URL: https://issues.oasis-open.org/browse/TOSCA-248
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Profile-YAML
>    Affects Versions: CSD03
>            Reporter: Sahdev Zala 
>            Assignee: Thomas Spatzier 
>             Fix For: CSD04
>
>
> Per discussion on 05/07/15 TOSCA TC Special 4 Hour Meeting:
> In Chapter 13.3, need to consider mapping inputs and outputs and show different naming with example. 



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