W3C home > Mailing lists > Public > public-ws-policy@w3.org > December 2006

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

From: Asir Vedamuthu <asirveda@microsoft.com>
Date: Fri, 1 Dec 2006 11:25:10 -0800
Message-ID: <1E0F0378382054439F14D5450650478F0B7EB4CC@RED-MSG-42.redmond.corp.microsoft.com>
To: Maryann Hondo <mhondo@us.ibm.com>
CC: <public-ws-policy@w3.org>

The Primer uses a simple story to introduce the features in the Web Services Policy language. The Guidelines would illustrate how to design assertions using concrete assertions where the enumerated list of design questions and good practices apply.

The Interop Scenarios would choose assertions that exercise substantial parts of the framework and attachment. For the Interop Scenarios, the WG would seriously consider the available testing time and would be hesitant to set a high bar when choosing assertions.

The Primer, Guidelines and Interop Scenarios target three different class of target audiences, serve three different purposes and have three different sets of constraints.

Given these and WG schedule constraints, don't see a reason why these deliverables shouldn't evolve independently.

Regards,
 
Asir S Vedamuthu
Microsoft Corporation




From: Maryann Hondo [mailto:mhondo@us.ibm.com] 
Sent: Thursday, November 30, 2006 6:27 AM
To: Asir Vedamuthu
Cc: public-ws-policy@w3.org; public-ws-policy-request@w3.org
Subject: 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 Friday, 1 December 2006 19:25:54 GMT

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