OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Created: (TOSCA-46) Are "Plans" definition of the example given in Appendix E consistent with the BPMN SPEC?


Are "Plans" definition of the example given in Appendix E consistent with the BPMN SPEC?
----------------------------------------------------------------------------------------

                 Key: TOSCA-46
                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-46
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Improvement
            Reporter: Paul Zhang


In the current version of TOSCA, the Appendix E introduces an example where a Plan (with id="DeployApplication") is described in detail. In this plan, the PlanModel is described by BPMN 2.0. However, I found there is something not consistent with the BPMN2.0. For instance, in the example, the name of a task means the corresponding operation invoked during the runtime. But, the name of a task in BPMN2.0 is just the content read by human beings, rather than representing the task's corresponding operation. So, it is recommended to clarify this in the SPEC. 

-- 
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]