[OASIS Issue Tracker] (SRAMP-72) Add specific details about how to map WS Policies to PolicyDocument/PolicyExpression

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

Brett Meyer created SRAMP-72:
--------------------------------

             Summary: Add specific details about how to map WS Policies to PolicyDocument/PolicyExpression
                 Key: SRAMP-72
                 URL: https://issues.oasis-open.org/browse/SRAMP-72
             Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
          Issue Type: Improvement
            Reporter: Brett Meyer


The foundational spec's "2.4.4 The Policy Model" is extremely vague and provides almost no information.  Further, the model itself needs expanded.

For example:
{code}
<wsp:ExactlyOne>
  <wsp:All>
    <!-- assertion a -->
  </wsp:All>
  <wsp:All>
    <!-- assertion b -->
  </wsp:All>
</wsp:ExactlyOne>
{code}

The ExactlyOne would be a PolicyExpression.  But what about the policy "alternatives" within that expression?  Shouldn't concepts like alternatives, nested expressions, assertions, etc. be modeled?  Or, if impls are expected to model that on their own through custom attributes, explicitly describe a notional system.



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