This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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 identifed 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
once all editors actions and WG actions related to 3989 are completed, we will be ready to close 3988
RESOLUTION: issues 3988 and 4663 closed by removing g/l section 8 and taking no further action on the g/l, but starting a section on the public wg homepage where we can host links to various un-endorsed resources that may be of use/interest to assertion and policy expression authors http://www.w3.org/2007/07/18-ws-policy-irc#T08-51-59