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

Bugzilla 3613 - Framework, Compact Normalization

From: Frederick Hirsch <frederick.hirsch@nokia.com>
Date: Wed, 23 Aug 2006 14:07:30 -0400
Message-Id: <28D96DDD-282F-460E-8A76-B636833B57DE@nokia.com>
Cc: Hirsch Frederick <frederick.hirsch@nokia.com>
To: public-ws-policy@w3.org

Bugzilla 3613 [1] is with regard to Compact Normalization in the  
Framework Editors draft [2].

The primary issue is that all implementations of normalization might  
not interoperate if it isn't clear which steps are to be taken. The  
sections referenced from the normalization steps do not provide  
explicit normalization instructions, but rather note equivalences and  
properties.

For example, if the wsp:Optional attribute is not present, there is  
no step mandating that it be treated as False and processed  
accordingly, the text could be interpreted as a choice to do so.

Likewise I could find no step that specified that parameters are  
copied when elements are distributed.

The full text of the bugzilla follows the references below in this  
email. Part 3 of the proposal is incomplete, and it would be helpful  
if others on the list could summarize the required steps.

Thanks

regards, Frederick

Frederick Hirsch
Nokia

[1] <http://www.w3.org/Bugs/Public/show_bug.cgi?id=3613>

[2] <http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy- 
framework.html?content-type=text/html;% 
20charset=utf-8#Compact_Policy_Expression>

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>
Received on Wednesday, 23 August 2006 18:08:21 GMT

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