[NEW ISSUE] Primer: Absence of Policy Assertions (editorial) [Issue 4288]

See: http://www.w3.org/Bugs/Public/show_bug.cgi?id=4288

Title: Absence of policy assertions [Primer]
Target: Primer 
(http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html?content-type=text/html;%20charset=utf-8)
22 January 2007

Description and Justification:
Currently, a statement exists in Section 2.10, Primer, about the
absence of policy assertions only in the context of inline to a WSDL
document while no mention is made earlier where it more
appropriately applies such as in Section 2.6, Optional Policy
Assertion. Suggest we promote similar statements to Section 2.6 where it
applies rather than limit its relationship to policy expressions in
a WSDL document as a parenthetical comment. In other groups,
questions have arisen about this statement so promotion herein seems
a logical approach. This suggestion was also part of Issue 3602
proposal as well [1] and may have been missed.

Proposal:
A. At the end of Section 2.6, include a brief statement where optional 
policy assertions are discussed.

Change from:
Contoso is able to meet their customer needs by adding optional
support for the Optimized MIME Serialization. An optional policy
assertion represents a behavior that may be engaged.

Change to:
Contoso is able to meet their customer needs by adding optional
support for the Optimized MIME Serialization. An optional policy
assertion represents a behavior that may be engaged. Where the
behavior is not engaged, the absence of policy expressions does not
indicate anything about the capabilities and requirements of a
service. A policy aware client should not conclude anything (other
than ‘no claims’) about the absence of policy expressions.

B. Apply minor update to Section 2.10, Attaching Policy Expressions to 
WSDL.

Change from:
The absence of policy expressions in a WSDL document does not
indicate anything about the capabilities and requirements of a
service. The service may have capabilities and requirements that can
be expressed as policy expressions, such as the use of addressing,
security and optimization. Or, the service may not have such
capabilities and requirements. A policy aware client should not
conclude anything (other than ‘no claims’) about the absence of
policy expressions.

Change to:
The absence of policy expressions, for example in a WSDL document,
does not indicate anything about the capabilities and requirements
of a service. The service may have capabilities and requirements
that can be expressed as policy expressions, such as the use of
addressing, security and optimization. Or, the service may not have
such capabilities and requirements.

[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=3602, 
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3602#c3

Received on Tuesday, 30 January 2007 22:17:55 UTC