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 5189 - Guidelines - BP 19 Lacks Motivation
Summary: Guidelines - BP 19 Lacks Motivation
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Guidelines (show other bugs)
Version: LC
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Felix Sasaki
QA Contact: Web Services Policy WG QA List
Depends on:
Reported: 2007-10-13 02:30 UTC by Asir V Selvasingh
Modified: 2007-10-24 17:30 UTC (History)
0 users

See Also:


Description Asir V Selvasingh 2007-10-13 02:30:40 UTC
Title: Guidelines - BP 19 Lacks Motivation


"Best Practice 19: Consider entire message exchange pattern when specifying Assertions that may be optional

Assertion Authors should associate optional assertions with the appropriate endpoint and use the smallest possible granularity to limit the degree to which optionality applies." [1]

The best practice that applies to granularity is covered by best practice 28 [2]. It is unclear why an assertion author would associate an assertion with "the appropriate endpoint". It is also unclear what behavior that the best practice is trying to motivate.

Justification: unclear best practice.

Target: Guidelines.

Proposal: This is a two part proposal -

a) Drop best practice 19.
b) s/This is important for an optional assertion where it may not be clear whether it is to apply in a message exchange when optionally used in part of that exchange (Best Practice: Consider entire message exchange pattern when specifying Assertions that may be optional).//



Asir S Vedamuthu
Microsoft Corporation
Comment 1 Paul Cotton 2007-10-24 17:30:39 UTC
Resolved at Oct 24 meeting by proposal in:
as amended by the text:

The approach taken by WS-RM Policy [Web Services Reliable Messaging Policy Assertion] is to provide for an RM assertion to be attached at either or both message and endpoint policy subjects. In order to eliminate the ambiguity associated with only using an message policy subject, the WS-RM Policy requires  a policy to be attached to an endpoint policy subject as well as a message policy subject whenever a policy is attached to a message policy subject.