Re: NEW ISSUE: 3988 [Guidelines] Section 8 Doesn't Illustrate How to Design an Assertion

Asir,

Maybe the group should consider constructing a single scenario outside 
either the primer or the guidelines
containing both policy assertions like security and rm, and then reference 
the example in the primer for illustration of use
and  the guidelines could point to those assertion that illustrate a 
particular facet of the best practices.
This example could potentially be used as a base for interoperability 
testing.

Maryann



Asir Vedamuthu <asirveda@microsoft.com> 
Sent by: public-ws-policy-request@w3.org
11/17/2006 08:53 PM

To
<public-ws-policy@w3.org>
cc

Subject
NEW ISSUE: 3988 [Guidelines] Section 8 Doesn't Illustrate How to Design an 
Assertion







Title: Section 8 doesn't illustrate how to design an assertion.

Description:

Section 8 [1] in the Guidelines document describes a scenario and
illustrates how to use transport binding security policy assertion (and
other assertions such as addressing and asymmetric binding), how to name
and reference policy expressions, how to attach policy expressions to
WSDL 11 constructs, etc. Such topics are widely covered in the Primer.

Given the scope of this document - 'Guidelines for Policy Assertion
Authors' - it will be very useful to illustrate how to design an
assertion by answering a set of questions identified by this document
and applying best practices or guidelines outlined in this document.

Justification: The Guidelines document is for the assertion authors. The
Guidelines document should illustrate how to design an assertion using a
concrete example. Illustrating how to use policy features should be
delegated to the Primer.

Proposal: Illustrate the design of one or more existing assertions from
the WS-SecurityPolicy specification (and or from another assertion
specification).

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

Regards,
 
Asir S Vedamuthu
Microsoft Corporation

Received on Thursday, 30 November 2006 14:26:21 UTC