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 3990 - [Guidelines] Content in Section 5.7 is unclear
Summary: [Guidelines] Content in Section 5.7 is unclear
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: Daniel Roth
QA Contact: Web Services Policy WG QA List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-18 02:57 UTC by Daniel Roth
Modified: 2007-03-14 18:49 UTC (History)
1 user (show)

See Also:


Attachments

Description Daniel Roth 2006-11-18 02:57:59 UTC
Title: [Guidelines] Content in Section 5.7 is unclear

Description: Section 5.7 in the Guidelines document currently discusses several topics: identifying assertions using QNames, versioning assertions, specifying admissible policy subjects for an assertion, defining new policy subjects, external policy attachment, etc [1].  Its unclear what the intent of this section is supposed to be:
    
The first paragraph covers assertion versioning.  This material belongs in 5.9 [2].

The second paragraph claims that allowing assertions to be associated with arbitrary policy subjects leads to ambiguity in the interpretation of the policy.  Its not clear what ambiguity is being referred to.  The example in this paragraph describes an encryption assertion attached to an endpoint.  Is the ambiguity in the definition of the assertion?

The third paragraph discusses restricting assertions to specific policy subjects, which is also addressed in 3.1 [3].  Is this repetition deliberate?  This paragraph also mentions determining if a policy assertion is specific to a policy attachment mechanism.  We are not aware of any reason why a policy assertion would depend on the policy attachment mechanism used.  Lastly, this paragraph calls endpoint policy subjects behaviors and message policy subjects artifacts.  It's not clear why this distinction is made.

The last paragraph emphasizes the existence of policy subjects other than the WSDL policy subjects.  Its not clear why this is significant.

The intent of this section needs to be clarified or the ambiguous points removed.  We suggest removing the section.

Justification: The content in section 5.7 is duplicated and some of it is unclear.  If this section is dropped, the significant bits are covered in other sections.

Target: Guidelines for Policy Assertion Authors

Proposal: Remove Section 5.7.

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

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

[3] http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-guidelines.html?rev=1.8&content-type=text/html;%20charset=utf-8#assertion-target
Comment 1 Christopher Ferris 2007-03-14 18:49:29 UTC
[14:47] scribe: RESOLUTION: Issue 3981 as proposed and update Issue 3989 to ensure that text in Section 4.6 is considered.
[14:48] scribe: Topic: Issue 4198
[14:48] cferris: rrsagent, where am i?
[14:48] RRSAgent: See http://www.w3.org/2007/03/14-ws-policy-irc#T18-49-05