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 3985 - [Guidelines] Section 5.3.1 should use the definition of policy assertion parameters from the Framework spec
Summary: [Guidelines] Section 5.3.1 should use the definition of policy assertion para...
Status: RESOLVED FIXED
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Guidelines (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Felix Sasaki
QA Contact: Web Services Policy WG QA List
URL:
Whiteboard:
Keywords:
Depends on: 4141
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-18 01:24 UTC by Daniel Roth
Modified: 2007-02-02 16:17 UTC (History)
1 user (show)

See Also:


Attachments
Proposal (2.20 KB, text/html)
2006-11-18 01:25 UTC, Daniel Roth
Details

Description Daniel Roth 2006-11-18 01:24:29 UTC
Title: [Guidelines] Section 5.3.1 should use the definition of policy assertion parameters from the Framework spec

Description: Section 5.3.1 in the Guidelines document currently states [1]:

Note that parameters of assertions include the following:

·         Complex elements with element children that cannot be policy assertions. 
·         Elements that have attributes 

This definition is not accurate.  The Framework spec states in section 3.1 [2]:

"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."

Rather than redefine policy assertion parameters, the Guidelines doc should use and reference the definition in the Framework spec.

Justification: The current text in the Guidelines doc is inconsistent with text in the Framework spec.

Target: Guidelines for Policy Assertion Authors

Proposal: Change the third paragraph in section 5.3.1 in the Guidelines doc as shown in the attachment.

[1] http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-guidelines.html?rev=1.8&content-type=text/html;%20charset=utf-8#parameterized-assertions

[2] http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;%20charset=utf-8#rPolicy_Assertion
Comment 1 Daniel Roth 2006-11-18 01:25:45 UTC
Created attachment 445 [details]
Proposal
Comment 2 Christopher Ferris 2007-01-18 22:40:45 UTC
chris: maybe say "domain specific compatibility processing"
See http://www.w3.org/2007/01/18-ws-policy-irc#T22-39-02
RESOLUTION: Accept the proposal in message 187 for resolving issue 3985 and 3986 with Chris's ammendment above
Comment 3 Christopher Ferris 2007-02-02 16:17:12 UTC
http://lists.w3.org/Archives/Member/member-ws-policy/2007Feb/0003.html

Note: the original resolution SHOULD have been recorded as:

chris: maybe say "domain specific compatibility processing"
See http://www.w3.org/2007/01/18-ws-policy-irc#T22-39-02
RESOLUTION: Accept the proposal in message 187 for resolving issue 3985 and
3986 with Chris's ammendment above