W3C home > Mailing lists > Public > public-ws-policy@w3.org > January 2007

NEW ISSUE: Policy parameter definition is not accurate

From: Yalcinalp, Umit <umit.yalcinalp@sap.com>
Date: Tue, 2 Jan 2007 16:27:38 -0800
Message-ID: <2BA6015847F82645A9BB31C7F9D641650308B832@uspale20.pal.sap.corp>
To: <public-ws-policy@w3.org>

Title: Policy parameter definition is not accurate

Target: Framework 

Description: 

While reviewing another issue [Bug 3985], Dan and I encountered this.
The related issue was filed to indicate that the Guidelines document was
rephrasing the content of the framework document on what it means to
have parameters on assertions. It was noted that the guidelines should
not be rephrasing the framework document. On review, it is noted that
the framework document is actually not accurate about what  policy
assertion parameters may be. 

Currently, the specification states the following about policy assertion
parameters. 

The XML Infoset of a policy assertion <>  MAY contain a non-empty
[attributes] property and/or a non-empty [children] property. Such
properties are policy assertion parameters <>  and MAY be used to
parameterize the behavior indicated by the assertion. [Definition: A
policy assertion parameter qualifies the behavior indicated by a policy
assertion <> .] For example, an assertion identifying support for a
specific reliable messaging mechanism might include an attribute
information item to indicate how long an endpoint will wait before
sending an acknowledgement.
This representation is not sufficient to differentiate between policy
assertion parameters and nested assertions. According to this
definition, ANY child of a policy assertion is a parameter, which is
incorrect. A child element whose local name property is "Policy" and
namespace property is http://www.w3.org/2006/07/ws-policy must not be
included as a parameter. 


Justification: 

The framework specification is not accurate and misleading on what
constitutes parameters and nested assertions. According to the
definition, there is no distinguishing characteristic between parameters
and nested assertions. 

Proposal: 

Change the first 2 sentences to 

The XML Infoset of a policy assertion <>  MAY contain a non-empty
[attributes] property and/or a non-empty [children] property. Such
properties, excluding elements whose local name is "Policy" and
namespace is http://www.w3.org/2006/07/ws-policy, are policy assertion
parameters and ... 

This issue is filed as [Bug 4141]

[Bug 3985] http://www.w3.org/Bugs/Public/show_bug.cgi?id=3985
[Bug 4141] 
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4141
----------------------

Dr. Umit Yalcinalp
Research Scientist
SAP Labs, LLC
Email: umit.yalcinalp@sap.com Tel: (650) 320-3095 
SDN: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/36238
--------
"Nearly all men can stand adversity, but if you want to test a man's
character, give him power." Abraham Lincoln. 
Received on Wednesday, 3 January 2007 00:26:52 GMT

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