W3C home > Mailing lists > Public > public-ws-policy@w3.org > January 2007

RE: NEW ISSUE: 3986 [Guidelines] Parameter vs. Nested Policy Decision at Domain Level?

From: Daniel Roth <Daniel.Roth@microsoft.com>
Date: Thu, 18 Jan 2007 14:24:36 -0800
To: Asir Vedamuthu <asirveda@microsoft.com>, "public-ws-policy@w3.org" <public-ws-policy@w3.org>
Message-ID: <E2903CF1E4B5B144B559237FDFB291CE4E9D8406@NA-EXMSG-C117.redmond.corp.microsoft.com>

Here is a revised proposal for this issue that replaces Section 4.4.1 in the Guidance doc [1], respectfully submitted by Dan, Asir, and Umit:

4.4.1 Assertions with Parameters
The framework allows WS-Policy domain authors to define policy assertion parameters to qualify an assertion.   Policy assertion parameters are the opaque payload of an assertion.  Assertion parameters carry additional useful pieces of information necessary for engaging the behavior described by an assertion.  Assertion parameters are not considered when performing policy intersection unless domain specific policy intersection semantics are specified by the assertion.  In the XML representation of a policy assertion the child elements and attributes of the assertion excluding child elements and attributes from the policy xml language namespace are the assertion parameters.

In the example below, sp:Body and sp:Header elements are the two assertion parameters of the sp:SignedParts policy assertion (this assertion requires the parts of a message to be protected).

Example 4-3. Policy Assertion with Assertion Parameters
<Policy>
  <sp:SignedParts>
    <sp:Body />
    <sp:Header />
  </sp:SignedParts>
</Policy>

Best practice: define policy assertion parameters for specifying useful pieces of information necessary for engaging the behavior described by an assertion but not relevant to policy intersection

Daniel Roth

[1] http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-guidelines.html?content-type=text/html;%20charset=utf-8#parameterized-assertions

-----Original Message-----
From: public-ws-policy-request@w3.org [mailto:public-ws-policy-request@w3.org] On Behalf Of Asir Vedamuthu
Sent: Friday, November 17, 2006 5:49 PM
To: public-ws-policy@w3.org
Subject: NEW ISSUE: 3986 [Guidelines] Parameter vs. Nested Policy Decision at Domain Level?


Title: Parameters vs. Nested Policy decision at the Domain Level?

Description: The Guidelines document says, 'For some domains it will be
appropriate to specify these parameters instead of nesting assertion
elements.'
[1]. But, the document does not provide any rationale (or motivations)
as to why the use of assertion parameters vs. nested policy should be
decided at the domain level.

Justification: there is no basis to support this statement.

Target: Guidelines for Assertion Authors.

Proposal: Drop this sentence.

[1]
http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-guidelines.
html?rev=1.8&content-type=text/html;%20charset=utf-8#parameterized-asser
tions

Regards,

Asir S Vedamuthu
Microsoft Corporation
Received on Thursday, 18 January 2007 22:24:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:45 GMT