This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3613 - Clarify conversion of compact to normal form in Framework section 4.3
Summary: Clarify conversion of compact to normal form in Framework section 4.3
Status: RESOLVED FIXED
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Framework (show other bugs)
Version: FPWD
Hardware: Macintosh All
: P2 normal
Target Milestone: ---
Assignee: Frederick Hirsch
QA Contact: Web Services Policy WG QA List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-21 21:44 UTC by Frederick Hirsch
Modified: 2006-09-13 21:58 UTC (History)
0 users

See Also:


Attachments

Description Frederick Hirsch 2006-08-21 21:44:27 UTC
Title
Clarify conversion of compact to normal form in Framework section 4.3 [1]

Description
Framework Section 4.3 describes a method for converting compact policy to normal form. It needs changes for clarity, including (1) description how parameter attributes and elements are handled during normalization (2) explicit steps for optional policy assertions (3) explicit steps for nested assertions (4) explicit steps for policy inclusion

Justification
The normalization items give a rough description of the steps but leave some details to interpretation which could lead to interop problems. How parameters are to be handled is not described. The subsequent sections on optional assertions, nested assertions and policy inclusion give equivalences but no specific steps to follow in normalization.

Without this detail an implementation might not handle normalization properly leading to interoperability issues

Target - Framework

Proposal 

[Part 1] in 4.3 Compact Policy, 

Change item #3- #1 by adding the following to the end "See 4.3.2 Policy Assertion Nesting."
Remove "and 4.3.2 Policy Assertion Nesting" from item #3-#2.

Part 2]
Add to end of 4.3.1 a new sub-section, 4.3.1.1 "Assertion Optionality Normalization", with the following text:

Normalize the assertion element as follows:

1. if the assertion element does not contain a wsp:Optional element, act as if it did, with the value of "False" in the following steps

2. If the value of the attribute is "True" then place in the output stream a wsp:ExactlyOne element. 
3. Place in the output stream a wsp:All element. 
4. Copy the assertion to the output stream with the Optional attribute removed, if it was present 
5. Put a wsp:All closing element 
6. if the Attribute value was True, put a wsp:ExactlyOne closing element to the output stream.

Part 3] Add to end of 4.3.3 a new sub-section, 4.3.1.1 "Operator Normalization", with the following text:

1. Replace every instance of wsp:Policy with wsp:All

do other steps like "distributing all" need to be mentioned explicitly?

Testing: Review of specification for clarity

Related to : 3549 discussion of normalization. This entry should replace that portion of 3549 discussion.

[1] editors draft of Framework
http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;%20charset=utf-8
Comment 1 Frederick Hirsch 2006-09-13 21:58:55 UTC
Working group agreed to close with no action as noted in proposal on list. Editors of guidelines may choose to add material to guidelines.

Proposal to close with no action
http://lists.w3.org/Archives/Public/public-ws-policy/2006Sep/0036

Decision to close recorded in working group minutes:
http://www.w3.org/2006/09/13-ws-policy-irc#T21-48-32