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 4141 - Policy parameter definition is not accurate
Summary: Policy parameter definition is not accurate
Status: RESOLVED FIXED
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Framework (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Umit Yalcinalp
QA Contact: Web Services Policy WG QA List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 3985
  Show dependency treegraph
 
Reported: 2007-01-03 00:24 UTC by Umit Yalcinalp
Modified: 2007-01-16 20:06 UTC (History)
0 users

See Also:


Attachments

Description Umit Yalcinalp 2007-01-03 00:24:29 UTC
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 it should not be rephrasing the framework document. On review, it is noted that the framework document is actually not accurate about what constitutes policy assertion parameters. 

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  



[Bug 3985] http://www.w3.org/Bugs/Public/show_bug.cgi?id=3985
Comment 1 Christopher Ferris 2007-01-16 20:06:14 UTC
See http://www.w3.org/2007/01/16-ws-policy-irc#T20-04-12
RESOLUTION: 4141 is closed with the proposal in http://lists.w3.org/Archives/Public/public-ws-policy/2007Jan/0048.html INCLUDING the proposal in Prasad's included previous note related to the proposed change to the Guidelines document