[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (TOSCA-14) Policy Language(s)
[ http://tools.oasis-open.org/issues/browse/TOSCA-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30043#action_30043 ]
Marvin Waschke commented on TOSCA-14:
--------------------------------------
There is a substantial reason for leaving the policy language open. As several people have pointed out, there are many, many policy languages extant. Many enterprises make extensive use of one policy language or another. Often they have management frameworks built around policies in their chosen language. Forcing them to use an unfamiliar policy language when they use Tosca will be a road block to acceptance of Tosca. I don't think it would be possible to choose a small number to support. There are too many, probably some of which are private languages built by the user.
Supporting multiple policy languages is a hindrance to interoperability and we ought to think through the available strategies for dealing with it, but I submit that the alternative is worse.
To add a voice to the "Tosca policy language" discussion, inventing a new language would be the worst of all possible worlds. It would be work to formulate and a guarantee that there would be no prior users. Not to mention being out of scope!
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]