[OASIS Issue Tracker] Commented: (TOSCA-14) Policy Language(s)

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

    [ http://tools.oasis-open.org/issues/browse/TOSCA-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30042#action_30042 ] 

Frank Leymann  commented on TOSCA-14:
-------------------------------------

I fully agree that inventing a new policy language is out of scope. In fact, I personally do believe that this would be a waste of time. There are quite a number of such languages around, creating "just another one" is not meaningful.

Ideally, we agree to support a single policy language. Supporting multiple such languages would increase our development effort and, thus, would jeopardize portability in case each vendor supports only a subset of these languages. 

> Policy Language(s)
> ------------------
>
>                 Key: TOSCA-14
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-14
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Sub-task
>          Components: Spec
>            Reporter: Frank Leymann 
>
> During review of the proposal to resolve issue TOSCA-3 a discussion about policy languages came up. See the following meeting notices:
> http://www.oasis-open.org/apps/org/workgroup/tosca/download.php/45574 
> Some TC members felt that a strong tie to WS-Policy is not appropriate. There are other approaches to define policies that are relevant for particular domains. Thus, this sub-task should review such other approaches and propose how to define policies in TOSCA.  Alternatives might be (i) to support multiple approaches, or (ii) to invent a new TOSCA policy language that abstracts the policy approaches considered to be relevant for TOSCA.

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