- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 28 Nov 2006 23:47:24 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv8904
Modified Files:
ws-policy-guidelines-diff20061109.xml
ws-policy-guidelines-diff20061109.html
Log Message:
Regenerating the DIFF version
Index: ws-policy-guidelines-diff20061109.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines-diff20061109.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- ws-policy-guidelines-diff20061109.xml 26 Nov 2006 00:08:41 -0000 1.1
+++ ws-policy-guidelines-diff20061109.xml 28 Nov 2006 23:47:21 -0000 1.2
@@ -28,19 +28,41 @@
<latestloc>
<loc href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-guidelines.html?content-type=text/html;charset=utf-8" xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="replace">http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-guidelines.html?content-type=text/html;charset=utf-8</loc>
</latestloc>
- <authlist>
- <author role="editor">
+ <authlist>
+ <author role="editor">
+ <name diff="add"><phrase diff="add">Asir S Vedamuthu</phrase></name>
+ <affiliation diff="add"><phrase diff="add">Microsoft Corporation</phrase></affiliation>
+ </author>
+ <author role="editor" diff="add">
+ <name><phrase diff="add">David Orchard</phrase></name>
+ <affiliation><phrase diff="add">BEA Systems, Inc.</phrase></affiliation>
+ </author>
+ <author role="editor" diff="add">
+ <name><phrase diff="add">Frederick Hirsch</phrase></name>
+ <affiliation><phrase diff="add">Nokia</phrase></affiliation>
+ </author>
+ <author role="editor" diff="add">
+
<name>Maryann Hondo</name>
- <affiliation>IBM Corporation</affiliation>
- </author>
- <author role="editor">
- <name>Umit Yalcinalp</name>
+ <affiliation>IBM Corporation</affiliation>
+ </author>
+ <author role="editor">
+ <name><phrase diff="chg">Prasad Yendluri</phrase></name>
+ <affiliation diff="add"><phrase diff="add">webMethods, Inc.</phrase></affiliation>
+ </author>
+ <author role="editor" diff="add">
+ <name><phrase diff="add">Toufic Boubez</phrase></name>
+ <affiliation><phrase diff="add">Layer 7 Technologies</phrase></affiliation>
+ </author>
+ <author role="editor" diff="add">
+ <name><phrase diff="add">Ümit Yalçinalp</phrase></name>
+
<affiliation>SAP AG.</affiliation>
- </author>
- </authlist>
+ </author>
+ </authlist>
<abstract>
<p>
- <emph>Web Services Policy 1.5 - Guidelines for Policy Assertion Authors</emph> is <phrase diff="add">intended to</phrase><phrase diff="del">a </phrase><phrase diff="add">provide guidance</phrase><phrase diff="del">guideline </phrase>for assertion
+ <emph>Web Services Policy 1.5 - Guidelines for Policy Assertion Authors</emph> is <phrase diff="add">intended to provide</phrase><phrase diff="del">a </phrase><phrase diff="chg">guidance </phrase>for assertion
authors that will work with the Web Services Policy 1.5 - Framework [<bibref ref="WS-Policy"></bibref>] and Web Services Policy 1.5 - Attachment [<bibref ref="WS-PolicyAttachment"></bibref>] specifications to create domain
specific assertions. The focus of this document is to provide
best practices and patterns to follow as well as illustrate
@@ -136,7 +158,7 @@
Policy XML Namespace.)
</p>
<p diff="add"> <phrase diff="add">As a companion document to the primer, this document also follows
- the Socratic style of beginning with a question,</phrase><phrase diff="del">Basic </phrase><phrase diff="add">and then answering
+ the Socratic style of beginning with a question, and then</phrase><phrase diff="del">Basic </phrase><phrase diff="add">answering
the</phrase><phrase diff="del">Concepts: </phrase><phrase diff="add">question.
</phrase></p>
</div1>
@@ -450,8 +472,9 @@
<phrase diff="add">items
</phrase><phrase diff="del">factors when </phrase><phrase diff="chg">in </phrase>the <phrase diff="add">dialect</phrase><phrase diff="del">set of domain assertions as it
may make sense to factor out some assertions that can be
- used by multiple </phrase><phrase diff="chg">specification:
- </phrase></p>
+ used by </phrase><phrase diff="add">specification:
+ </phrase><phrase diff="del">multiple subjects:
+ </phrase></p>
<ulist>
<item>
<p>
@@ -568,10 +591,10 @@
using the <code>@optional</code> attribute as our example illustrates above.
</p>
- <p><phrase diff="add">Best practice: use the authoring style most appropriate
+ <p><phrase diff="add">Best practice: use the authoring style
- </phrase><phrase diff="del">Guidelines </phrase>for <phrase diff="chg">the target </phrase><phrase diff="add">audience </phrase></p>
+ </phrase><phrase diff="del">Guidelines </phrase><phrase diff="add">most appropriate </phrase>for <phrase diff="chg">the target </phrase><phrase diff="add">audience </phrase></p>
</div2><p diff="del">Assertions
</p><div2 id="new-guidelines-domains" diff="chg">
@@ -584,8 +607,8 @@
<p diff="add"><phrase diff="add">The</phrase><phrase diff="del">Some </phrase><phrase diff="chg">examples given in </phrase><phrase diff="add">this document reference WS-Policy</phrase><phrase diff="del">infrastructure
efforts </phrase>like WS-SecurityPolicy and WS-RM Policy.
<phrase diff="add">These </phrase><phrase diff="chg">policy </phrase><phrase diff="add">expressions</phrase><phrase diff="del">also
- anticipate </phrase><phrase diff="add">represent web services message exchange requirements, but policy authoring can
- be done by</phrase><phrase diff="del">that </phrase>individual <phrase diff="add">groups that wish to represent </phrase>web services <phrase diff="add">application requirements</phrase><phrase diff="del">applications </phrase>and
+ anticipate </phrase><phrase diff="add">represent web services message exchange requirements, but policy</phrase><phrase diff="del">that </phrase><phrase diff="add">authoring can
+ be done by </phrase>individual <phrase diff="add">groups that wish to represent </phrase>web services <phrase diff="add">application requirements</phrase><phrase diff="del">applications </phrase>and
deployments <phrase diff="chg">that </phrase>wish to reuse the WS-Policy framework in
order to enable dynamic negotiation of business requirements
and capabilities at runtime.
@@ -597,7 +620,7 @@
behavior. Sets of assertions can by grouped by an operator "all". This indicates that there is a relationship between
the assertions and they now constitute a policy alternative.
</p>
- <p><phrase diff="add">If grouping is utilized, choices</phrase><phrase diff="del">Choices </phrase>between alternatives can be indicated by
+ <p><phrase diff="add">If grouping is utilized,</phrase><phrase diff="del">Choices </phrase><phrase diff="add">choices </phrase>between alternatives can be indicated by
an "exactly one" operator. This basic set of operators allows
authors a wide range of options for expressing the possible combinations of assertions within their domain.
</p>
@@ -883,25 +906,25 @@
information that is necessary </phrase>to <phrase diff="add">determine</phrase><phrase diff="del">understand a </phrase><phrase diff="chg">when to </phrase><phrase diff="add">use</phrase><phrase diff="del">not
available, </phrase><phrase diff="chg">nested policy </phrase><phrase diff="add">expressions:</phrase><phrase diff="del">suffer.
</phrase></p>
- <p><phrase diff="add">Are</phrase><phrase diff="del">Policy assertions should not be
+ <p><phrase diff="chg">Are </phrase><phrase diff="add">these</phrase><phrase diff="del">assertions should not be
used to express the semantics of a message. Rather, if a property is
required to understand a message, it should be communicated in
the message, or be made available by some other means (e.g., being
- referenced </phrase><phrase diff="chg">these assertions designed for </phrase>the <phrase diff="add">same</phrase><phrase diff="del">message) instead of being communicated as a
+ referenced by </phrase><phrase diff="chg">assertions designed for </phrase>the <phrase diff="add">same</phrase><phrase diff="del">message) instead of being communicated as a
</phrase>policy <phrase diff="chg">subject? </phrase></p>
- <p><phrase diff="add">Do</phrase><phrase diff="del">For example, if the details </phrase><phrase diff="chg">these </phrase><phrase diff="add">assertions</phrase><phrase diff="del">a
+ <p><phrase diff="add">Do</phrase><phrase diff="del">For example, if </phrase><phrase diff="add">these</phrase><phrase diff="del">the details of </phrase><phrase diff="add">assertions</phrase><phrase diff="del">a
message's </phrase><phrase diff="chg">represent dependent </phrase><phrase diff="add">behaviors?</phrase></p>
<p diff="add"><phrase diff="add">If</phrase><phrase diff="del">e.g., </phrase>the <phrase diff="add">answers</phrase><phrase diff="del">cipher used, etc) </phrase>are <phrase diff="add">yes</phrase><phrase diff="del">expressed
in policy that isn't attached </phrase>to <phrase diff="add">both</phrase><phrase diff="del">the message, </phrase><phrase diff="chg">of these </phrase><phrase diff="add">questions</phrase><phrase diff="del">possible
to </phrase><phrase diff="chg">then leveraging nested </phrase><phrase diff="add">policy
expressions</phrase><phrase diff="del">This </phrase>is <phrase diff="chg">something to consider. Keep </phrase>in
- <phrase diff="del">policy, what </phrase><phrase diff="add">mind</phrase><phrase diff="del">ciphers (and so forth) </phrase><phrase diff="add">that</phrase><phrase diff="del">are supported by </phrase>a <phrase diff="add">nested</phrase><phrase diff="del">particular
+ <phrase diff="del">policy, what ciphers </phrase><phrase diff="add">mind</phrase><phrase diff="del">(and so forth) are supported </phrase><phrase diff="chg">that </phrase>a <phrase diff="add">nested</phrase><phrase diff="del">particular
endpoint, or those </phrase><phrase diff="chg">policy expression participates </phrase>in
<phrase diff="chg">the policy intersection </phrase><phrase diff="add">algorithm.</phrase><phrase diff="del">the
latter </phrase><phrase diff="chg">If a requester </phrase>uses <phrase diff="chg">policy intersection to </phrase><phrase diff="add">select</phrase><phrase diff="del">framework.
As </phrase>a
- <phrase diff="chg">compatible </phrase><phrase diff="add">policy</phrase><phrase diff="del">the assertion authors
+ <phrase diff="add">compatible </phrase><phrase diff="del">result, the assertion </phrase><phrase diff="add">policy</phrase><phrase diff="del">authors
should take into </phrase><phrase diff="chg">alternative then </phrase>the <phrase diff="del">following important concepts
when designing </phrase>assertions <phrase diff="add">in</phrase><phrase diff="del">and documenting the semantics of the
assertion types. </phrase><phrase diff="chg">a nested policy expression play </phrase>a
@@ -925,8 +948,8 @@
message as </phrase><phrase diff="chg">practice: If </phrase>the <phrase diff="add">domain
authors</phrase><phrase diff="del">assertion, it would be </phrase><phrase diff="chg">want </phrase>to
<phrase diff="del">determine the behaviors engaged at runtime by additional means. A
- general protocol </phrase><phrase diff="add">delegate</phrase><phrase diff="del">that aids in determining such behaviors may be
- utilized, however a standard protocol for this purpose is
+ general protocol that aids in determining such behaviors may be
+ utilized, however a standard protocol for this purpose </phrase><phrase diff="add">delegate</phrase><phrase diff="del">is
currently </phrase><phrase diff="chg">the processing </phrase>to <phrase diff="add">the</phrase><phrase diff="del">ensure interoperability. Thus, </phrase><phrase diff="chg">framework,
utilizing nesting </phrase>should be <phrase diff="add">considered.</phrase><phrase diff="del">used with care.
Another approach is to </phrase><phrase diff="chg">Otherwise, </phrase><phrase diff="add">domain
@@ -1100,7 +1123,7 @@
precise about their semantics and include information that
restricts their set of permissible policy subjects
appropriately and indicates which Qnames are associated with
- which subjects. </phrase>One way to <phrase diff="chg">disambiguate the </phrase><phrase diff="add">semantic </phrase>is to generally determine
+ which subjects. </phrase>One way to <phrase diff="chg">disambiguate </phrase><phrase diff="add">the semantic</phrase><phrase diff="del">this </phrase>is to generally determine
if an assertion is specific to a policy attachment
mechanism. An example could be identifying whether the
assertion expressed is associated with behaviors
@@ -1177,7 +1200,6 @@
policy subject. This topic is considered in detail in <bibref ref="WS-Policy-Primer"></bibref>
</p>
<p>The current set of subjects as mapped to the WSDL 1.1
-
elements, can also constrain the assertion constructs. For Example, In WS-RM,
the domain authors chose to support certain capabilities at
the endpoint level. This resulted in the finer granularity of
@@ -1260,10 +1282,29 @@
</item>
<item>
<p> Policy Language Extensibility </p>
+ <p><phrase diff="add">Over time, the Policy WG or third parties can version or extend the Policy Language with new
+ or modified constructs. These constructs may be compatible or incompatible with previous versions.
+ </phrase></p>
+ <p> <phrase diff="add">Policy authors should review the WS-Policy Primer </phrase><bibref ref="WS-Policy-Primer"></bibref>
+ <phrase diff="add">and the specifications </phrase><bibref ref="WS-Policy"></bibref> <bibref ref="WS-PolicyAttachment"></bibref>
+ <phrase diff="add">for details on extensibility.
+ </phrase></p>
+ <p> <phrase diff="add">The current WS-Policy language </phrase><bibref ref="WS-Policy"></bibref> <phrase diff="add">provides extensibility points
+ on 6 elements with a combination of attribute and/or element extensibility:</phrase></p>
+ <olist>
+ <item><p><phrase diff="add">Policy: element from ##other namespace and any attribute</phrase></p></item>
+ <item><p><phrase diff="add">PolicyReference: any attribute and a proposal to add any element ExactlyOne, All: element from ##other namespace, no attribute extensibility</phrase></p></item>
+
+ <item><p><phrase diff="add">PolicyAttachment: element from ##other namespace and any attribute</phrase></p></item>
+ <item><p><phrase diff="add">AppliesTo: any element and any attribute</phrase></p></item>
+ </olist>
+
</item>
<item>
<p> Subject attachment Extensibility </p>
- </item>
+ <p><phrase diff="add">PolicyAttachment and AppliesTo also have extensibility points.</phrase></p>
+
+ </item>
</ulist>
<div2 id="Referencing_Policy_Expressions">
@@ -1313,204 +1354,10 @@
</example>
<p>Best practice: use independent assertions for modeling multiple equivalent behaviors. </p>
<!-- EDS TO DO REconcile from Primer. GET THE REST FROM DAVE and Umit -->
-
- <div3 id="versioning-policy-language"><head><phrase diff="add">Versioning Policy Language</phrase></head>
- <p><phrase diff="add">Over time, the Policy WG or third parties can version or extend the Policy Language with new or modified constructs. These constructs may be compatible or incompatible with previous versions. Some of the possible new constructs that have been mentioned previously are: new operators, operator cardinality, policy identification, compact syntax, Policy Inclusion, security, referencing, attachment points, alternative
- priority, effective dating, negotiation. </phrase></p>
- <p><phrase diff="add">WS-Policy provides extensibility points on 6 elements with a combination of attribute and/or element extensibility.
- The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:</phrase></p>
- <olist>
- <item><p><phrase diff="add">Policy: element from ##other namespace and any attribute</phrase></p></item>
- <item><p><phrase diff="add">PolicyReference: any attribute and a proposal to add any element ExactlyOne, All: element from ##other namespace, no attribute extensibility</phrase></p></item>
- <item><p><phrase diff="add">PolicyAttachment: element from ##other namespace and any attribute</phrase></p></item>
- <item><p><phrase diff="add">AppliesTo: any element and any attribute</phrase></p></item>
- </olist>
- </div3>
- <div3 id="versioning-policy-framework"><head><phrase diff="add">Policy Framework</phrase></head>
- <p><phrase diff="add">WS-Policy Framework 1.5 specifies that any element that is not known inside a Policy, ExactlyOne or All will be treated as an assertion. The default value for wsp:Optional="false", which means after normalization it will be inside an ExactlyOne/All operator. </phrase></p>
- <p><phrase diff="add">Let us show an example with a hypothetical new operator that is a Choice with a minOccurs and a maxOccurs attributes, ala XSD:Choice, in a new namespace. We use the wsp16 prefix to indicate a hypothetical Policy Language 1.6 that is intended to be compatible with Policy Language 1.5:</phrase></p>
-<example><head><phrase diff="add">Policy containing 1.5 and 1.6 Policies.</phrase></head>
-<eg xml:space="preserve"><![CDATA[<wsp:Policy>
- <wsp:ExactlyOne>
- <wsp16:Choice wsp16:minOccurs="1" wsp16:maxOccurs="2">
- ...
- </wsp16:Choice>
- <wsp:All>
- ...
- </wsp:All>
- </wsp:ExactlyOne>
-</wsp:Policy>]]></eg>
-</example>
-<p><phrase diff="add">The normalization rule for wsp:Optional="false" would be applied to the wsp16:Choice, yielding the following expression:</phrase></p>
-<example><head><phrase diff="add">Normalized Policy containing 1.5 and 1.6 Policies</phrase></head>
-<eg xml:space="preserve"><![CDATA[<wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:ExactlyOne>
- <wsp:All>
- <wsp16:Choice wsp16:minOccurs="1" wsp16:maxOccurs="2">
- ...
- </wsp16:Choice>
- </wsp:All>
- </wsp:ExactlyOne>
- <wsp:All>
- ...
- </wsp:All>
- </wsp:ExactlyOne>
-</wsp:Policy>]]></eg>
-</example>
-<p><phrase diff="add">Alternatively, the wsp:Optional could be set to "true" on the choice, as
-in:</phrase></p>
-<example><head><phrase diff="add">Policy containing explicit wsp:Optional="true"</phrase></head>
-<eg xml:space="preserve"><![CDATA[<wsp:Policy>
- <wsp16:Choice wsp16:minOccurs="1" wsp16:maxOccurs="2"
-wsp:Optional="true">
- ...
- </wsp16:Choice>
-</wsp:Policy>]]></eg>
-</example>
-<p><phrase diff="add">The normalized form will be:</phrase></p>
-<example><head><phrase diff="add">Normalized policy</phrase></head>
-<eg xml:space="preserve"><![CDATA[<wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:All>
- <wsp16:Choice wsp16:minOccurs="1" wsp16:maxOccurs="2">
- ...
- </wsp16:Choice>
- </wsp:All>
- <wsp:All/>
- </wsp:ExactlyOne>
-</wsp:Policy>]]></eg>
-</example>
- <p><phrase diff="add">Because the wsp16:Choice alternative isn't understood in either normalized form, it will not be chosen as one of the alternatives and will effectively be ignored. Policy intersection may be more difficult with such compatible extensions. For example, the previous will "look"
- like it has a wsp16:Choice typed assertion. To determine intersection with a Policy that does not have the wsp16:Choice type assertion, domain specific processing would have to be done. However, there is an alternative that does not have the wsp16:Choice, so intersection would yield the expected result.
- </phrase></p>
- <p><phrase diff="add">Note: it is possible to add new names to the existing namespace, such as: </phrase></p>
-<example><head><phrase diff="add">Policy containing 1.5 and 1.6 Policies all in the 1.5 namespace</phrase></head>
-<eg xml:space="preserve"><![CDATA[<wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
- ...
- </wsp:Choice>
- <wsp:All>
- ...
- </wsp:All>
- </wsp:ExactlyOne>
-</wsp:Policy>]]></eg>
-</example>
-
- <p><phrase diff="add">Notice that using a new namespace can result in backwards and forwards compatibility if
- normalization results in an optional alternative. </phrase></p>
-
- <p><phrase diff="add">Best practice: insert new elements in an optional alternative or mark with wsp:Optional="true".
- </phrase></p>
-
- <p><phrase diff="add">Incompatible versions of the Policy language may be indicated by a new namespace name for at
- least the new and/or incompatible elements or attributes. Imagine that the Choice operator is
- required by a future version of Policy, then there will be a new namespace for the Policy element.
- We use the wsp20 prefix to indicate a hypothetical Policy Language 2.0 that is intended to be
- incompatible with Policy Language 1.5:</phrase></p>
-
-<example><head><phrase diff="add">Policy containing 2.0 only Policies.</phrase></head>
-<eg xml:space="preserve"><![CDATA[<wsp20:Policy>
- <wsp20:ExactlyOne>
- <wsp20:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
- ...
- </wsp20:Choice>
- ...
- </wsp20:ExactlyOne>
-</wsp20:Policy> ]]></eg>
-</example>
-
- <p><phrase diff="add">The new Policy operator could be embedded inside an existing Policy element:</phrase></p>
-
-<example><head><phrase diff="add">Policy containing 2.0 (incompatible with 1.5) Policies embedded in wsp 1.5 Policy.</phrase></head>
-<eg xml:space="preserve"><![CDATA[<wsp:Policy>
- <wsp20:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
- ...
- </wsp20:Choice>
- ...
-</wsp20:Policy> ]]></eg>
-</example>
-
- <p><phrase diff="add">This will be treated as an Assertion for normalization and intersection computation.
- This will result in only one alternative that requires the wsp20:Choice, the intended behaviour
- for incompatible changes.</phrase></p>
-
- <p><phrase diff="add">Best practice: use a new namespace for new incompatible construct and insert inside either: new Policy element OR existing All for future incompatible policy extensions.</phrase></p>
-
- <p><phrase diff="add">A future version of WS-Policy could support the current operators in the existing namespace,
- such as:</phrase></p>
-<example><head><phrase diff="add">Policy containing 1.5 operator in 2.0 Policy</phrase></head>
-<eg xml:space="preserve"><![CDATA[<wsp20:Policy>
- <wsp:ExactlyOne>
- <wsp20:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
- ...
- </wsp20:Choice>
- ...
- </wsp:ExactlyOne>
-</wsp20:Policy> ]]></eg>
-</example>
-
- <p><phrase diff="add">It is difficult to predict whether this functionality would be useful. The future version of WS-Policy doesn't appear to be precluded from doing this.</phrase></p>
- </div3>
- <div3 id="versioning-policy-attachment"><head><phrase diff="add">Policy Attachment</phrase></head>
- <p><phrase diff="add">Policy attachment provides WSDL 1.1 and UDDI attachment points. It appears that exchange of Policy will be in the
- context of WSDL or UDDI. WRT WSDL, the policy model is an extension of the WSDL definition. As such, it is likely that future versions of Policy will be exchanged as multiple Policy expressions within a WSDL. One alternative is that there would be a separate WSDL for each version of Policy. The problem of how to specify and query for compound documents is very difficult, so it is more likely that each version of Policy will be exchanged within a WSDL. </phrase></p>
- <p><phrase diff="add">We show an example of a new version of policy that allows QName reference to Policies in the PolicyReference:</phrase></p>
-
-<example><head><phrase diff="add">WSDL containing 1.5 and 2.0 (compatible with 2.0) Policy References.</phrase></head>
-<eg xml:space="preserve"><![CDATA[<wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >
- <wsoap12:binding style="document"
- transport="http://schemas.xmlsoap.org/soap/http" />
- <wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:All>
- <wsp:PolicyReference URI="#RmPolicy"
-wsdl11:required="true" />
- <wsp:PolicyReference URI="#X509EndpointPolicy"
-wsdl11:required="true" />
- </wsp:All>
- <wsp:All>
- <wsp:PolicyReferenceByQName ref="rmp:RMAssertion"
-wsdl11:required="true" />
- <wsp:PolicyReferenceByQName ref="sp:AsymmetricBinding"
-wsdl11:required="true" />
- </wsp:All>
- </wsp:ExactlyOne>
- </wsp:Policy>
- <wsdl11:operation name="GetLastTradePrice" > ....
- ...]]></eg>
- </example>
-
- <p><phrase diff="add">The PolicyReference element is attribute extensible. One example of an addition is a list of backup URIs for the PolicyReference:</phrase></p>
-
-<example><head><phrase diff="add">WSDL containing 1.5 and 2.0 (compatible with 2.0) Policy References.</phrase></head>
-<eg xml:space="preserve"><![CDATA[<wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >
- <wsoap12:binding style="document"
- transport="http://schemas.xmlsoap.org/soap/http" />
- <wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:All>
- <wsp:PolicyReference URI="" wsp16:alternateURIs="URI*"
-wsdl11:required="true" />
- <wsp:PolicyReference URI="" wsp16:alternateURIs="URI*"
-wsdl11:required="true" />
- </wsp:All>
- </wsp:ExactlyOne>
- </wsp:Policy>
- <wsdl11:operation name="GetLastTradePrice" > ....
- ...]]></eg>
-</example>
- <p><phrase diff="add">The policy framework specification says that any unknown attributes are ignored. A Policy 1.5 processor will not understand the wsp16:alternateURI attribute, it will be ignored. A Policy 1.6 processor will understand the alternate URIs so it won't be ignored.</phrase></p>
-
- <p><phrase diff="add">PolicyAttachment and AppliesTo also have extensibility points. We choose not to illustrate these at this time.</phrase></p>
- </div3>
+
</div2>
</div1>
-
-
-
<div1 id="inter-policy">
<head>Inter-domain Policy and Composition Issues</head>
<p>Domain authors must be aware of the interactions between their
@@ -1955,31 +1802,31 @@
</bibl>
<bibl id="WS-Policy" key="Web Services Policy Framework" href="http://www.w3.org/TR/ws-policy/" xlink:actuate="onRequest" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:show="replace" xlink:type="simple">
- <titleref xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="new">Web Services Policy 1.5 - Framework</titleref>, A. S. Vedamuthu, D. Orchard, M. Hondo, T.
- Boubez and P. Yendluri, Editors. World Wide Web Consortium, @@,
+ <titleref xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="new">Web Services Policy 1.5 - Framework</titleref>, A. S. Vedamuthu, D. Orchard, <phrase diff="add">F. Hirsch, </phrase>M. Hondo,
+ <phrase diff="add">P. Yendluri, </phrase>T. Boubez and <phrase diff="chg">Ü. Yalçinalp, </phrase>Editors. World Wide Web Consortium, @@,
@@@@ @@@@. This version of the
Web Services Policy 1.5 - Framework specification is at http://www.w3.org/TR/ws-policy/. The <loc href="http://www.w3.org/TR/ws-policy/" xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="replace">latest version of
Web Services Policy 1.5 - Framework</loc> is available at http://www.w3.org/TR/ws-policy/. </bibl>
<bibl id="WS-PolicyAttachment" key="Web Services Policy Attachment" href="http://www.w3.org/TR/ws-policy-attach/" xlink:actuate="onRequest" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:show="replace" xlink:type="simple">
- <titleref xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="new">Web Services Policy 1.5 - Attachment</titleref>, A. S. Vedamuthu, D. Orchard, M. Hondo, T.
- Boubez and P. Yendluri, Editors. World Wide Web Consortium, @@,
+ <titleref xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="new">Web Services Policy 1.5 - Attachment</titleref>, A. S. Vedamuthu, D. Orchard, <phrase diff="add">F. Hirsch, </phrase>M. Hondo,
+ <phrase diff="add">P. Yendluri, </phrase>T. Boubez and <phrase diff="chg">Ü. Yalçinalp, </phrase>Editors. World Wide Web Consortium, @@,
@@@@ @@@@. This version of the
Web Services Policy 1.5 - Attachment specification is at http://www.w3.org/TR/ws-policy-attach. The <loc href="http://www.w3.org/TR/ws-policy-attach/" xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="replace">latest version of
Web Services Policy 1.5 - Attachment</loc> is available at
http://www.w3.org/TR/ws-policy-attach/. </bibl>
<bibl id="WS-Policy-Primer" key="Web Services Policy Primer" href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html?content-type=text/html;%20charset=utf-8" xlink:actuate="onRequest" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:show="replace" xlink:type="simple">
- <titleref xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="new">Web Services Policy 1.5 - Primer</titleref>, A. S. Vedamuthu, D. Orchard, M. Hondo, T.
- Boubez and P. Yendluri, Editors. World Wide Web Consortium, Draft. </bibl>
+ <titleref xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="new">Web Services Policy 1.5 - Primer</titleref>, A. S. Vedamuthu, D. Orchard, <phrase diff="add">F. Hirsch, </phrase>M. Hondo,
+ <phrase diff="add">P. Yendluri, </phrase>T. Boubez and <phrase diff="chg">Ü. Yalçinalp, </phrase>Editors. World Wide Web Consortium, Draft. </bibl>
<bibl id="WS-RM" key="Web Services Reliable Messaging" href="http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-rddl-200608.html" xlink:actuate="onRequest" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:show="replace" xlink:type="simple">
<titleref xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="new">Web Services Reliable Messaging (WS-ReliableMessaging)</titleref>, Doug Davis (IBM), Anish Karmarkar (Oracle),
- Gilbert Pilz (BEA), Steve Winkler (SAP), Umit Yalcinalp
- (SAP), August 7th, 2006, available at:
+ Gilbert Pilz (BEA), Steve Winkler (SAP), <phrase diff="chg">Ü. Yalçinalp
+ </phrase>(SAP), August 7th, 2006, available at:
http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-rddl-200608.html
</bibl>
<bibl id="WS-RM-Policy" key="Web Services Reliable Messaging Policy" href="http://docs.oasis-open.org/ws-rx/wsrmp/200608/wsrmp-1.1-rddl-200608.html" xlink:actuate="onRequest" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:show="replace" xlink:type="simple">
<titleref xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="new">Web Services Reliable Messaging Policy Assertion v1.1</titleref>, Doug Davis (IBM), Anish Karmarkar (Oracle),
- Gilbert Pilz (BEA), Steve Winkler (SAP), Umit Yalcinalp
- (SAP), August 4, 2006, available at:
+ Gilbert Pilz (BEA), Steve Winkler (SAP), <phrase diff="chg">Ü. Yalçinalp
+ </phrase>(SAP), August 4, 2006, available at:
http://docs.oasis-open.org/ws-rx/wsrmp/200608/wsrmp-1.1-rddl-200608.html
</bibl>
<bibl id="WS-Security2004" key="WS-Security 2004" href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf" xlink:actuate="onRequest" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:show="replace" xlink:type="simple">
@@ -2123,6 +1970,22 @@
<td rowspan="1" colspan="1" diff="add">MH</td>
<td rowspan="1" colspan="1" diff="add">Restructure to address action items 64,77, which refer to bugzilla 3705 and F2F RESOLUTION 3792 </td>
</tr>
+ <tr diff="add">
+ <td rowspan="1" colspan="1" diff="add">20061127</td>
+ <td rowspan="1" colspan="1" diff="add">ASV</td>
+ <td rowspan="1" colspan="1" diff="add">Updated the list of editors. Added
+ <loc href="http://lists.w3.org/Archives/Public/public-ws-policy-eds/2006Nov/0033.html" xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">Frederick</phrase></loc> and
+ <loc href="http://lists.w3.org/Archives/Public/public-ws-policy-eds/2006Nov/0054.html" xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">Umit</phrase></loc> to the list of editors.
+ Editors' action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/86" xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">86</phrase></loc>.
+ </td>
+ </tr>
+ <tr diff="add">
+ <td rowspan="1" colspan="1" diff="add">20061128</td>
+ <td rowspan="1" colspan="1" diff="add">MH</td>
+ <td rowspan="1" colspan="1" diff="add">Replaced section in Lifecycle with pointer to the text in the primer: related to action 77
+ </td>
+ </tr>
+
</tbody>
</table>
</inform-div1>
Index: ws-policy-guidelines-diff20061109.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines-diff20061109.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- ws-policy-guidelines-diff20061109.html 26 Nov 2006 00:08:41 -0000 1.1
+++ ws-policy-guidelines-diff20061109.html 28 Nov 2006 23:47:22 -0000 1.2
@@ -74,12 +74,17 @@
</dd><dt>Latest version:</dt><dd>
<a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-guidelines.html?content-type=text/html;charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-guidelines.html?content-type=text/html;charset=utf-8</a>
</dd><dt>Editors:</dt>
- <dd>Maryann Hondo, IBM Corporation</dd>
- <dd>Umit Yalcinalp, SAP AG.</dd>
- </dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
+ <dd><span class="diff-add"><span class="diff-add">Asir S Vedamuthu</span></span><span class="diff-add">, <span class="diff-add">Microsoft Corporation</span></span></dd>
+ <dd><span class="diff-add"><span class="diff-add">David Orchard</span>, <span class="diff-add">BEA Systems, Inc.</span></span></dd>
+ <dd><span class="diff-add"><span class="diff-add">Frederick Hirsch</span>, <span class="diff-add">Nokia</span></span></dd>
+ <dd><span class="diff-add">Maryann Hondo, IBM Corporation</span></dd>
+ <dd><span class="diff-chg">Prasad Yendluri</span><span class="diff-add">, <span class="diff-add">webMethods, Inc.</span></span></dd>
+ <dd><span class="diff-add"><span class="diff-add">Toufic Boubez</span>, <span class="diff-add">Layer 7 Technologies</span></span></dd>
+ <dd><span class="diff-add"><span class="diff-add">Ümit Yalçinalp</span>, SAP AG.</span></dd>
+ </dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
<h2><a name="abstract">Abstract</a></h2>
<p>
- <em>Web Services Policy 1.5 - Guidelines for Policy Assertion Authors</em> is <span class="diff-add">intended to</span><span class="diff-del">a </span><span class="diff-add">provide guidance</span><span class="diff-del">guideline </span>for assertion
+ <em>Web Services Policy 1.5 - Guidelines for Policy Assertion Authors</em> is <span class="diff-add">intended to provide</span><span class="diff-del">a </span><span class="diff-chg">guidance </span>for assertion
authors that will work with the Web Services Policy 1.5 - Framework [<a href="#WS-Policy">[Web Services Policy Framework]</a>] and Web Services Policy 1.5 - Attachment [<a href="#WS-PolicyAttachment">[Web Services Policy Attachment]</a>] specifications to create domain
specific assertions. The focus of this document is to provide
best practices and patterns to follow as well as illustrate
@@ -91,7 +96,7 @@
<h2><a name="status">Status of this Document</a></h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p><p></p></div>
<hr><div class="toc">
-<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#introduction">Introduction</a><br>2. <a href="#Assertions">What is an Assertion? Assertion</a><br>3. <a href="#N1015E">Who is involved in authoring Assertions? Assertions</a><br> 3.1 <a href="#roles"> Roles and Responsibilities </a><br> 3.1.1 <a href="#domain-owners"> WS-Policy Authors</a><br> 3.1.2 <a href="#consumers">Consumers</a><br> 3.1.3 <a href="#providers">Providers</a><br>4. <a href="#general-guidelines">General Guidelines for WS-Policy Assertion Authors</a><br> 4.1 <a href="#assertion-target">Assertions and Their Target Use</a><br> 4.2 <a href="#compact-full">Authoring Styles </a><br> 4.3 <a href="#new-guidelines-domains">Considerations when Modeling New AssertionsDomains</a><br> &bsp; 4.3.1 <a href="#minimal-approach">Minimal approach</a><br> 4.3.2 <a href="#QName_and_XML_Information_Set_representation">QName and XML Information Set representation</a><br> 4.3.3 <a href="#self-describing"> Self Describing Messages </a><br> 4.3.4 <a href="#single-domains">Single Domains</a><br> 4.4 <a href="#comparison">Comparison of Nested and Parameterized Assertions</a><br> 4.4.1 <a href="#parameterized-assertions">Assertions with Parameters</a><br> 4.4.2 <a href="#nested-assertions">Nested Assertions</a><br> 4.4.3 <a href="#which-one-to-use">Considerations for choosing parameters vs nesting</a><br> 4.5 <a href="#optional-policy-assertion">Policy Asertions Designating Optional Behaviors</a><br> 4.5.1 <a href="#N10623">Optional behavior in Compact authoring</a><br> 4.5.2 <a href="#N10636">Optional behavior at runtime</a><br> 4.6 <a href="#typing-assertions">Typing Assertions</a><br> 4.7 <a href="#levels-of-abstraction">Levels of Abstraction in WSDL </a><br>5. <a href="#lifecycle">Lifecycle of Assertions</a><br> 5.1 <a href="#Referencing_Policy_Expressions">Referencing Policy Expressions</a><br> 5.2 <a href="#extending-assertions"> Factors in Extending Assertions within a Domain </a><br> 5.3 <a href="#assertion-evolution">Evolution of Assertions (Versioning and Compatibility)</a><br> 5.3.1 <a href="#versioning-policy-language">Versioning Policy Language</a><br>   5.3.2 <a href="#versioning-policy-framework">Policy Framework</a><br> 5.3.3 <a href="#versioning-policy-attachment">Policy Attachment</a><br>6. <a href="#inter-policy">Inter-domain Policy and Composition Issues</a><br>7. <a href="#best-practices-attachment">Applying Best Practices for Policy Attachment</a><br> 7.1 <a href="#context-free-policies">Appropriate Attachment: Preserving Context-Free Policies</a><br> 7.2 <a href="#appropriate-attachment-assertion-subjects">Appropriate Attachment: Identifying Assertion Subjects</a><br> 7.2.1 <a href="#interaction">Interaction between Subjects</a><br> 7.3 <a href="#identifying-assertion-sources">Appropriate Attachment: Identifying Assertion Sources </a><br>8. <a href="#scenerio">Scenario and a worked example</a><br></p>
+<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#introduction">Introduction</a><br>2. <a href="#Assertions">What is an Assertion? Assertion</a><br>3. <a href="#N1019C">Who is involved in authoring Assertions? Assertions</a><br> 3.1 <a href="#roles"> Roles and Responsibilities </a><br> 3.1.1 <a href="#domain-owners"> WS-Policy Authors</a><br> 3.1.2 <a href="#consumers">Consumers</a><br> 3.1.3 <a href="#providers">Providers</a><br>4. <a href="#general-guidelines">General Guidelines for WS-Policy Assertion Authors</a><br> 4.1 <a href="#assertion-target">Assertions and Their Target Use</a><br> 4.2 <a href="#compact-full">Authoring Styles </a><br> 4.3 <a href="#new-guidelines-domains">Considerations when Modeling New AssertionsDomains</a><br> &bsp; 4.3.1 <a href="#minimal-approach">Minimal approach</a><br> 4.3.2 <a href="#QName_and_XML_Information_Set_representation">QName and XML Information Set representation</a><br> 4.3.3 <a href="#self-describing"> Self Describing Messages </a><br> 4.3.4 <a href="#single-domains">Single Domains</a><br> 4.4 <a href="#comparison">Comparison of Nested and Parameterized Assertions</a><br> 4.4.1 <a href="#parameterized-assertions">Assertions with Parameters</a><br> 4.4.2 <a href="#nested-assertions">Nested Assertions</a><br> 4.4.3 <a href="#which-one-to-use">Considerations for choosing parameters vs nesting</a><br> 4.5 <a href="#optional-policy-assertion">Policy Asertions Designating Optional Behaviors</a><br> 4.5.1 <a href="#N10673">Optional behavior in Compact authoring</a><br> 4.5.2 <a href="#N10686">Optional behavior at runtime</a><br> 4.6 <a href="#typing-assertions">Typing Assertions</a><br> 4.7 <a href="#levels-of-abstraction">Levels of Abstraction in WSDL </a><br>5. <a href="#lifecycle">Lifecycle of Assertions</a><br> 5.1 <a href="#Referencing_Policy_Expressions">Referencing Policy Expressions</a><br> 5.2 <a href="#extending-assertions"> Factors in Extending Assertions within a Domain </a><br> 5.3 <a href="#assertion-evolution">Evolution of Assertions (Versioning and Compatibility)</a><br>6. <a href="#inter-policy">Inter-domain Policy and Composition Issues</a><br>7. <a href="#best-practices-attachment">Applying Best Practices for Policy Attachment</a>br> 7.1 <a href="#context-free-policies">Appropriate Attachment: Preserving Context-Free Policies</a><br> 7.2 <a href="#appropriate-attachment-assertion-subjects">Appropriate Attachment: Identifying Assertion Subjects</a><br> 7.2.1 <a href="#interaction">Interaction between Subjects</a><br> 7.3 <a href="#identifying-assertion-sources">Appropriate Attachment: Identifying Assertion Sources </a><br>8. <a href="#scenerio">Scenario and a worked example</a><br></p>
<h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#security-considerations">Security Considerations</a><br>B. <a href="#xml-namespaces">XML Namespaces</a><br>C. <a href="#references">References</a><br>D. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>E. <a href="#change-description">Changes in this Version of
the Document</a> (Non-Normative)<br>F. <a href="#change-log">Web Services Policy 1.5 - Guidelines for Policy Assertion Authors Change Log</a> (Non-Normative)<br></p></div><hr><div class="body">
<div class="div1">
@@ -173,7 +178,7 @@
Policy XML Namespace.)
</p>
<div class="diff-add"><p class="diff-add"> <span class="diff-add">As a companion document to the primer, this document also follows
- the Socratic style of beginning with a question,</span><span class="diff-del">Basic </span><span class="diff-add">and then answering
+ the Socratic style of beginning with a question, and then</span><span class="diff-del">Basic </span><span class="diff-add">answering
the</span><span class="diff-del">Concepts: </span><span class="diff-add">question.
</span></p></div>
</div>
@@ -292,7 +297,7 @@
-<h2><a name="N1015E"></a>3. <span class="diff-chg">Who is involved </span>in <span class="diff-chg">authoring Assertions? </span><span class="diff-del">Assertions</span></h2>
+<h2><a name="N1019C"></a>3. <span class="diff-chg">Who is involved </span>in <span class="diff-chg">authoring Assertions? </span><span class="diff-del">Assertions</span></h2>
<p>In order for the policy framework to enable communities to
express their own domain knowledge, it is necessary to provide basic
@@ -495,8 +500,9 @@
<span class="diff-add">items
</span><span class="diff-del">factors when </span><span class="diff-chg">in </span>the <span class="diff-add">dialect</span><span class="diff-del">set of domain assertions as it
may make sense to factor out some assertions that can be
- used by multiple </span><span class="diff-chg">specification:
- </span></p>
+ used by </span><span class="diff-add">specification:
+ </span><span class="diff-del">multiple subjects:
+ </span></p>
<ul>
<li>
<p>
@@ -614,10 +620,10 @@
using the <code>@optional</code> attribute as our example illustrates above.
</p>
- <p><span class="diff-add">Best practice: use the authoring style most appropriate
+ <p><span class="diff-add">Best practice: use the authoring style
- </span><span class="diff-del">Guidelines </span>for <span class="diff-chg">the target </span><span class="diff-add">audience </span></p>
+ </span><span class="diff-del">Guidelines </span><span class="diff-add">most appropriate </span>for <span class="diff-chg">the target </span><span class="diff-add">audience </span></p>
</div></div><div class="diff-del"><p class="diff-del">Assertions
</p></div><div class="diff-chg"><div class="div2">
@@ -631,8 +637,8 @@
<div class="diff-add"><p class="diff-add"><span class="diff-add">The</span><span class="diff-del">Some </span><span class="diff-chg">examples given in </span><span class="diff-add">this document reference WS-Policy</span><span class="diff-del">infrastructure
efforts </span>like WS-SecurityPolicy and WS-RM Policy.
<span class="diff-add">These </span><span class="diff-chg">policy </span><span class="diff-add">expressions</span><span class="diff-del">also
- anticipate </span><span class="diff-add">represent web services message exchange requirements, but policy authoring can
- be done by</span><span class="diff-del">that </span>individual <span class="diff-add">groups that wish to represent </span>web services <span class="diff-add">application requirements</span><span class="diff-del">applications </span>and
+ anticipate </span><span class="diff-add">represent web services message exchange requirements, but policy</span><span class="diff-del">that </span><span class="diff-add">authoring can
+ be done by </span>individual <span class="diff-add">groups that wish to represent </span>web services <span class="diff-add">application requirements</span><span class="diff-del">applications </span>and
deployments <span class="diff-chg">that </span>wish to reuse the WS-Policy framework in
order to enable dynamic negotiation of business requirements
and capabilities at runtime.
@@ -645,7 +651,7 @@
behavior. Sets of assertions can by grouped by an operator "all". This indicates that there is a relationship between
the assertions and they now constitute a policy alternative.
</p>
- <p><span class="diff-add">If grouping is utilized, choices</span><span class="diff-del">Choices </span>between alternatives can be indicated by
+ <p><span class="diff-add">If grouping is utilized,</span><span class="diff-del">Choices </span><span class="diff-add">choices </span>between alternatives can be indicated by
an "exactly one" operator. This basic set of operators allows
authors a wide range of options for expressing the possible combinations of assertions within their domain.
</p>
@@ -938,25 +944,25 @@
information that is necessary </span>to <span class="diff-add">determine</span><span class="diff-del">understand a </span><span class="diff-chg">when to </span><span class="diff-add">use</span><span class="diff-del">not
available, </span><span class="diff-chg">nested policy </span><span class="diff-add">expressions:</span><span class="diff-del">suffer.
</span></p>
- <p><span class="diff-add">Are</span><span class="diff-del">Policy assertions should not be
+ <p><span class="diff-chg">Are </span><span class="diff-add">these</span><span class="diff-del">assertions should not be
used to express the semantics of a message. Rather, if a property is
required to understand a message, it should be communicated in
the message, or be made available by some other means (e.g., being
- referenced </span><span class="diff-chg">these assertions designed for </span>the <span class="diff-add">same</span><span class="diff-del">message) instead of being communicated as a
+ referenced by </span><span class="diff-chg">assertions designed for </span>the <span class="diff-add">same</span><span class="diff-del">message) instead of being communicated as a
</span>policy <span class="diff-chg">subject? </span></p>
- <p><span class="diff-add">Do</span><span class="diff-del">For example, if the details </span><span class="diff-chg">these </span><span class="diff-add">assertions</span><span class="diff-del">a
+ <p><span class="diff-add">Do</span><span class="diff-del">For example, if </span><span class="diff-add">these</span><span class="diff-del">the details of </span><span class="diff-add">assertions</span><span class="diff-del">a
message's </span><span class="diff-chg">represent dependent </span><span class="diff-add">behaviors?</span></p>
<div class="diff-add"><p class="diff-add"><span class="diff-add">If</span><span class="diff-del">e.g., </span>the <span class="diff-add">answers</span><span class="diff-del">cipher used, etc) </span>are <span class="diff-add">yes</span><span class="diff-del">expressed
in policy that isn't attached </span>to <span class="diff-add">both</span><span class="diff-del">the message, </span><span class="diff-chg">of these </span><span class="diff-add">questions</span><span class="diff-del">possible
to </span><span class="diff-chg">then leveraging nested </span><span class="diff-add">policy
expressions</span><span class="diff-del">This </span>is <span class="diff-chg">something to consider. Keep </span>in
- <span class="diff-del">policy, what </span><span class="diff-add">mind</span><span class="diff-del">ciphers (and so forth) </span><span class="diff-add">that</span><span class="diff-del">are supported by </span>a <span class="diff-add">nested</span><span class="diff-del">particular
+ <span class="diff-del">policy, what ciphers </span><span class="diff-add">mind</span><span class="diff-del">(and so forth) are supported </span><span class="diff-chg">that </span>a <span class="diff-add">nested</span><span class="diff-del">particular
endpoint, or those </span><span class="diff-chg">policy expression participates </span>in
<span class="diff-chg">the policy intersection </span><span class="diff-add">algorithm.</span><span class="diff-del">the
latter </span><span class="diff-chg">If a requester </span>uses <span class="diff-chg">policy intersection to </span><span class="diff-add">select</span><span class="diff-del">framework.
As </span>a
- <span class="diff-chg">compatible </span><span class="diff-add">policy</span><span class="diff-del">the assertion authors
+ <span class="diff-add">compatible </span><span class="diff-del">result, the assertion </span><span class="diff-add">policy</span><span class="diff-del">authors
should take into </span><span class="diff-chg">alternative then </span>the <span class="diff-del">following important concepts
when designing </span>assertions <span class="diff-add">in</span><span class="diff-del">and documenting the semantics of the
assertion types. </span><span class="diff-chg">a nested policy expression play </span>a
@@ -980,8 +986,8 @@
message as </span><span class="diff-chg">practice: If </span>the <span class="diff-add">domain
authors</span><span class="diff-del">assertion, it would be </span><span class="diff-chg">want </span>to
<span class="diff-del">determine the behaviors engaged at runtime by additional means. A
- general protocol </span><span class="diff-add">delegate</span><span class="diff-del">that aids in determining such behaviors may be
- utilized, however a standard protocol for this purpose is
+ general protocol that aids in determining such behaviors may be
+ utilized, however a standard protocol for this purpose </span><span class="diff-add">delegate</span><span class="diff-del">is
currently </span><span class="diff-chg">the processing </span>to <span class="diff-add">the</span><span class="diff-del">ensure interoperability. Thus, </span><span class="diff-chg">framework,
utilizing nesting </span>should be <span class="diff-add">considered.</span><span class="diff-del">used with care.
Another approach is to </span><span class="diff-chg">Otherwise, </span><span class="diff-add">domain
@@ -1003,7 +1009,7 @@
<h3><a name="optional-policy-assertion"></a>4.5 <span class="diff-del">Policy Assertions </span>Designating Optional Behaviors</h3>
<div class="diff-add"><div class="div3">
-<h4><a name="N10623"></a>4.5.1 <span class="diff-add">Optional behavior in Compact authoring</span></h4>
+<h4><a name="N10673"></a>4.5.1 <span class="diff-add">Optional behavior in Compact authoring</span></h4>
<p>Optional behaviors represent behaviors which may be engaged by a consumer. When using the
compact authoring form for assertions, behaviors are marked by
using <code>wsp:optional</code> attribute that has a value,
@@ -1018,7 +1024,7 @@
</div></div>
<div class="diff-add"><div class="div3">
-<h4><a name="N10636"></a>4.5.2 <span class="diff-add">Optional behavior at runtime</span></h4>
+<h4><a name="N10686"></a>4.5.2 <span class="diff-add">Optional behavior at runtime</span></h4>
<p>The <a href="#WS-Policy-Primer">[Web Services Policy Primer]</a> document contains an
@@ -1159,7 +1165,7 @@
precise about their semantics and include information that
restricts their set of permissible policy subjects
appropriately and indicates which Qnames are associated with
- which subjects. </span>One way to <span class="diff-chg">disambiguate the </span><span class="diff-add">semantic </span>is to generally determine
+ which subjects. </span>One way to <span class="diff-chg">disambiguate </span><span class="diff-add">the semantic</span><span class="diff-del">this </span>is to generally determine
if an assertion is specific to a policy attachment
mechanism. An example could be identifying whether the
assertion expressed is associated with behaviors
@@ -1237,7 +1243,6 @@
policy subject. This topic is considered in detail in <a href="#WS-Policy-Primer">[Web Services Policy Primer]</a>
</p>
<p>The current set of subjects as mapped to the WSDL 1.1
-
elements, can also constrain the assertion constructs. For Example, In WS-RM,
the domain authors chose to support certain capabilities at
the endpoint level. This resulted in the finer granularity of
@@ -1321,10 +1326,29 @@
</li>
<li>
<p> Policy Language Extensibility </p>
+ <p><span class="diff-add">Over time, the Policy WG or third parties can version or extend the Policy Language with new
+ or modified constructs. These constructs may be compatible or incompatible with previous versions.
+ </span></p>
+ <p> <span class="diff-add">Policy authors should review the WS-Policy Primer </span><a href="#WS-Policy-Primer">[Web Services Policy Primer]</a>
+ <span class="diff-add">and the specifications </span><a href="#WS-Policy">[Web Services Policy Framework]</a> <a href="#WS-PolicyAttachment">[Web Services Policy Attachment]</a>
+ <span class="diff-add">for details on extensibility.
+ </span></p>
+ <p> <span class="diff-add">The current WS-Policy language </span><a href="#WS-Policy">[Web Services Policy Framework]</a> <span class="diff-add">provides extensibility points
+ on 6 elements with a combination of attribute and/or element extensibility:</span></p>
+ <ol>
+ <li><p><span class="diff-add">Policy: element from ##other namespace and any attribute</span></p></li>
+ <li><p><span class="diff-add">PolicyReference: any attribute and a proposal to add any element ExactlyOne, All: element from ##other namespace, no attribute extensibility</span></p></li>
+
+ <li><p><span class="diff-add">PolicyAttachment: element from ##other namespace and any attribute</span></p></li>
+ <li><p><span class="diff-add">AppliesTo: any element and any attribute</span></p></li>
+ </ol>
+
</li>
<li>
<p> Subject attachment Extensibility </p>
- </li>
+ <p><span class="diff-add">PolicyAttachment and AppliesTo also have extensibility points.</span></p>
+
+ </li>
</ul>
<div class="div2">
@@ -1377,207 +1401,10 @@
</div>
<p>Best practice: use independent assertions for modeling multiple equivalent behaviors. </p>
-
- <div class="div3">
-<h4><a name="versioning-policy-language"></a>5.3.1 <span class="diff-add">Versioning Policy Language</span></h4>
- <p><span class="diff-add">Over time, the Policy WG or third parties can version or extend the Policy Language with new or modified constructs. These constructs may be compatible or incompatible with previous versions. Some of the possible new constructs that have been mentioned previously are: new operators, operator cardinality, policy identification, compact syntax, Policy Inclusion, security, referencing, attachment points, alternative
- priority, effective dating, negotiation. </span></p>
- <p><span class="diff-add">WS-Policy provides extensibility points on 6 elements with a combination of attribute and/or element extensibility.
- The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:</span></p>
- <ol>
- <li><p><span class="diff-add">Policy: element from ##other namespace and any attribute</span></p></li>
- <li><p><span class="diff-add">PolicyReference: any attribute and a proposal to add any element ExactlyOne, All: element from ##other namespace, no attribute extensibility</span></p></li>
- <li><p><span class="diff-add">PolicyAttachment: element from ##other namespace and any attribute</span></p></li>
- <li><p><span class="diff-add">AppliesTo: any element and any attribute</span></p></li>
- </ol>
- </div>
- <div class="div3">
-<h4><a name="versioning-policy-framework"></a>5.3.2 <span class="diff-add">Policy Framework</span></h4>
- <p><span class="diff-add">WS-Policy Framework 1.5 specifies that any element that is not known inside a Policy, ExactlyOne or All will be treated as an assertion. The default value for wsp:Optional="false", which means after normalization it will be inside an ExactlyOne/All operator. </span></p>
- <p><span class="diff-add">Let us show an example with a hypothetical new operator that is a Choice with a minOccurs and a maxOccurs attributes, ala XSD:Choice, in a new namespace. We use the wsp16 prefix to indicate a hypothetical Policy Language 1.6 that is intended to be compatible with Policy Language 1.5:</span></p>
-<div class="exampleOuter"><p class="exampleHead" style="text-align: left"><i><span>Example 5-3. </span><span class="diff-add">Policy containing 1.5 and 1.6 Policies.</span></i></p>
-<div class="exampleInner"><pre><wsp:Policy>
- <wsp:ExactlyOne>
- <wsp16:Choice wsp16:minOccurs="1" wsp16:maxOccurs="2">
- ...
- </wsp16:Choice>
- <wsp:All>
- ...
- </wsp:All>
- </wsp:ExactlyOne>
-</wsp:Policy></pre></div>
-</div>
-<p><span class="diff-add">The normalization rule for wsp:Optional="false" would be applied to the wsp16:Choice, yielding the following expression:</span></p>
-<div class="exampleOuter"><p class="exampleHead" style="text-align: left"><i><span>Example 5-4. </span><span class="diff-add">Normalized Policy containing 1.5 and 1.6 Policies</span></i></p>
-<div class="exampleInner"><pre><wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:ExactlyOne>
- <wsp:All>
- <wsp16:Choice wsp16:minOccurs="1" wsp16:maxOccurs="2">
- ...
- </wsp16:Choice>
- </wsp:All>
- </wsp:ExactlyOne>
- <wsp:All>
- ...
- </wsp:All>
- </wsp:ExactlyOne>
-</wsp:Policy></pre></div>
-</div>
-<p><span class="diff-add">Alternatively, the wsp:Optional could be set to "true" on the choice, as
-in:</span></p>
-<div class="exampleOuter"><p class="exampleHead" style="text-align: left"><i><span>Example 5-5. </span><span class="diff-add">Policy containing explicit wsp:Optional="true"</span></i></p>
-<div class="exampleInner"><pre><wsp:Policy>
- <wsp16:Choice wsp16:minOccurs="1" wsp16:maxOccurs="2"
-wsp:Optional="true">
- ...
- </wsp16:Choice>
-</wsp:Policy></pre></div>
-</div>
-<p><span class="diff-add">The normalized form will be:</span></p>
-<div class="exampleOuter"><p class="exampleHead" style="text-align: left"><i><span>Example 5-6. </span><span class="diff-add">Normalized policy</span></i></p>
-<div class="exampleInner"><pre><wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:All>
- <wsp16:Choice wsp16:minOccurs="1" wsp16:maxOccurs="2">
- ...
- </wsp16:Choice>
- </wsp:All>
- <wsp:All/>
- </wsp:ExactlyOne>
-</wsp:Policy></pre></div>
-</div>
- <p><span class="diff-add">Because the wsp16:Choice alternative isn't understood in either normalized form, it will not be chosen as one of the alternatives and will effectively be ignored. Policy intersection may be more difficult with such compatible extensions. For example, the previous will "look"
- like it has a wsp16:Choice typed assertion. To determine intersection with a Policy that does not have the wsp16:Choice type assertion, domain specific processing would have to be done. However, there is an alternative that does not have the wsp16:Choice, so intersection would yield the expected result.
- </span></p>
- <p><span class="diff-add">Note: it is possible to add new names to the existing namespace, such as: </span></p>
-<div class="exampleOuter"><p class="exampleHead" style="text-align: left"><i><span>Example 5-7. </span><span class="diff-add">Policy containing 1.5 and 1.6 Policies all in the 1.5 namespace</span></i></p>
-<div class="exampleInner"><pre><wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
- ...
- </wsp:Choice>
- <wsp:All>
- ...
- </wsp:All>
- </wsp:ExactlyOne>
-</wsp:Policy></pre></div>
-</div>
-
- <p><span class="diff-add">Notice that using a new namespace can result in backwards and forwards compatibility if
- normalization results in an optional alternative. </span></p>
-
- <p><span class="diff-add">Best practice: insert new elements in an optional alternative or mark with wsp:Optional="true".
- </span></p>
-
- <p><span class="diff-add">Incompatible versions of the Policy language may be indicated by a new namespace name for at
- least the new and/or incompatible elements or attributes. Imagine that the Choice operator is
- required by a future version of Policy, then there will be a new namespace for the Policy element.
- We use the wsp20 prefix to indicate a hypothetical Policy Language 2.0 that is intended to be
- incompatible with Policy Language 1.5:</span></p>
-
-<div class="exampleOuter"><p class="exampleHead" style="text-align: left"><i><span>Example 5-8. </span><span class="diff-add">Policy containing 2.0 only Policies.</span></i></p>
-<div class="exampleInner"><pre><wsp20:Policy>
- <wsp20:ExactlyOne>
- <wsp20:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
- ...
- </wsp20:Choice>
- ...
- </wsp20:ExactlyOne>
-</wsp20:Policy> </pre></div>
-</div>
-
- <p><span class="diff-add">The new Policy operator could be embedded inside an existing Policy element:</span></p>
-
-<div class="exampleOuter"><p class="exampleHead" style="text-align: left"><i><span>Example 5-9. </span><span class="diff-add">Policy containing 2.0 (incompatible with 1.5) Policies embedded in wsp 1.5 Policy.</span></i></p>
-<div class="exampleInner"><pre><wsp:Policy>
- <wsp20:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
- ...
- </wsp20:Choice>
- ...
-</wsp20:Policy> </pre></div>
-</div>
-
- <p><span class="diff-add">This will be treated as an Assertion for normalization and intersection computation.
- This will result in only one alternative that requires the wsp20:Choice, the intended behaviour
- for incompatible changes.</span></p>
-
- <p><span class="diff-add">Best practice: use a new namespace for new incompatible construct and insert inside either: new Policy element OR existing All for future incompatible policy extensions.</span></p>
-
- <p><span class="diff-add">A future version of WS-Policy could support the current operators in the existing namespace,
- such as:</span></p>
-<div class="exampleOuter"><p class="exampleHead" style="text-align: left"><i><span>Example 5-10. </span><span class="diff-add">Policy containing 1.5 operator in 2.0 Policy</span></i></p>
-<div class="exampleInner"><pre><wsp20:Policy>
- <wsp:ExactlyOne>
- <wsp20:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
- ...
- </wsp20:Choice>
- ...
- </wsp:ExactlyOne>
-</wsp20:Policy> </pre></div>
-</div>
-
- <p><span class="diff-add">It is difficult to predict whether this functionality would be useful. The future version of WS-Policy doesn't appear to be precluded from doing this.</span></p>
- </div>
- <div class="div3">
-<h4><a name="versioning-policy-attachment"></a>5.3.3 <span class="diff-add">Policy Attachment</span></h4>
- <p><span class="diff-add">Policy attachment provides WSDL 1.1 and UDDI attachment points. It appears that exchange of Policy will be in the
- context of WSDL or UDDI. WRT WSDL, the policy model is an extension of the WSDL definition. As such, it is likely that future versions of Policy will be exchanged as multiple Policy expressions within a WSDL. One alternative is that there would be a separate WSDL for each version of Policy. The problem of how to specify and query for compound documents is very difficult, so it is more likely that each version of Policy will be exchanged within a WSDL. </span></p>
- <p><span class="diff-add">We show an example of a new version of policy that allows QName reference to Policies in the PolicyReference:</span></p>
-
-<div class="exampleOuter"><p class="exampleHead" style="text-align: left"><i><span>Example 5-11. </span><span class="diff-add">WSDL containing 1.5 and 2.0 (compatible with 2.0) Policy References.</span></i></p>
-<div class="exampleInner"><pre><wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >
- <wsoap12:binding style="document"
- transport="http://schemas.xmlsoap.org/soap/http" />
- <wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:All>
- <wsp:PolicyReference URI="#RmPolicy"
-wsdl11:required="true" />
- <wsp:PolicyReference URI="#X509EndpointPolicy"
-wsdl11:required="true" />
- </wsp:All>
- <wsp:All>
- <wsp:PolicyReferenceByQName ref="rmp:RMAssertion"
-wsdl11:required="true" />
- <wsp:PolicyReferenceByQName ref="sp:AsymmetricBinding"
-wsdl11:required="true" />
- </wsp:All>
- </wsp:ExactlyOne>
- </wsp:Policy>
- <wsdl11:operation name="GetLastTradePrice" > ....
- ...</pre></div>
- </div>
-
- <p><span class="diff-add">The PolicyReference element is attribute extensible. One example of an addition is a list of backup URIs for the PolicyReference:</span></p>
-
-<div class="exampleOuter"><p class="exampleHead" style="text-align: left"><i><span>Example 5-12. </span><span class="diff-add">WSDL containing 1.5 and 2.0 (compatible with 2.0) Policy References.</span></i></p>
-<div class="exampleInner"><pre><wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >
- <wsoap12:binding style="document"
- transport="http://schemas.xmlsoap.org/soap/http" />
- <wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:All>
- <wsp:PolicyReference URI="" wsp16:alternateURIs="URI*"
-wsdl11:required="true" />
- <wsp:PolicyReference URI="" wsp16:alternateURIs="URI*"
-wsdl11:required="true" />
- </wsp:All>
- </wsp:ExactlyOne>
- </wsp:Policy>
- <wsdl11:operation name="GetLastTradePrice" > ....
- ...</pre></div>
-</div>
- <p><span class="diff-add">The policy framework specification says that any unknown attributes are ignored. A Policy 1.5 processor will not understand the wsp16:alternateURI attribute, it will be ignored. A Policy 1.6 processor will understand the alternate URIs so it won't be ignored.</span></p>
-
- <p><span class="diff-add">PolicyAttachment and AppliesTo also have extensibility points. We choose not to illustrate these at this time.</span></p>
- </div>
+
</div>
</div></div>
-
-
-
<div class="div1">
<h2><a name="inter-policy"></a>6. Inter-domain Policy and Composition Issues</h2>
@@ -2032,31 +1859,31 @@
(See <a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/">http://www.w3.org/TR/2006/CR-wsdl20-20060327/</a>.)</dd>
<dt class="label"><a name="WS-Policy"></a>[Web Services Policy Framework] </dt><dd>
- <cite>Web Services Policy 1.5 - Framework</cite>, A. S. Vedamuthu, D. Orchard, M. Hondo, T.
- Boubez and P. Yendluri, Editors. World Wide Web Consortium, @@,
+ <cite>Web Services Policy 1.5 - Framework</cite>, A. S. Vedamuthu, D. Orchard, <span class="diff-add">F. Hirsch, </span>M. Hondo,
+ <span class="diff-add">P. Yendluri, </span>T. Boubez and <span class="diff-chg">Ü. Yalçinalp, </span>Editors. World Wide Web Consortium, @@,
@@@@ @@@@. This version of the
Web Services Policy 1.5 - Framework specification is at http://www.w3.org/TR/ws-policy/. The <a href="http://www.w3.org/TR/ws-policy/">latest version of
Web Services Policy 1.5 - Framework</a> is available at http://www.w3.org/TR/ws-policy/. (See <a href="http://www.w3.org/TR/ws-policy/">http://www.w3.org/TR/ws-policy/</a>.)</dd>
<dt class="label"><a name="WS-PolicyAttachment"></a>[Web Services Policy Attachment] </dt><dd>
- <cite>Web Services Policy 1.5 - Attachment</cite>, A. S. Vedamuthu, D. Orchard, M. Hondo, T.
- Boubez and P. Yendluri, Editors. World Wide Web Consortium, @@,
+ <cite>Web Services Policy 1.5 - Attachment</cite>, A. S. Vedamuthu, D. Orchard, <span class="diff-add">F. Hirsch, </span>M. Hondo,
+ <span class="diff-add">P. Yendluri, </span>T. Boubez and <span class="diff-chg">Ü. Yalçinalp, </span>Editors. World Wide Web Consortium, @@,
@@@@ @@@@. This version of the
Web Services Policy 1.5 - Attachment specification is at http://www.w3.org/TR/ws-policy-attach. The <a href="http://www.w3.org/TR/ws-policy-attach/">latest version of
Web Services Policy 1.5 - Attachment</a> is available at
http://www.w3.org/TR/ws-policy-attach/. (See <a href="http://www.w3.org/TR/ws-policy-attach/">http://www.w3.org/TR/ws-policy-attach/</a>.)</dd>
<dt class="label"><a name="WS-Policy-Primer"></a>[Web Services Policy Primer] </dt><dd>
- <cite>Web Services Policy 1.5 - Primer</cite>, A. S. Vedamuthu, D. Orchard, M. Hondo, T.
- Boubez and P. Yendluri, Editors. World Wide Web Consortium, Draft. (See <a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html?content-type=text/html;%20charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html?content-type=text/html;%20charset=utf-8</a>.)</dd>
+ <cite>Web Services Policy 1.5 - Primer</cite>, A. S. Vedamuthu, D. Orchard, <span class="diff-add">F. Hirsch, </span>M. Hondo,
+ <span class="diff-add">P. Yendluri, </span>T. Boubez and <span class="diff-chg">Ü. Yalçinalp, </span>Editors. World Wide Web Consortium, Draft. (See <a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html?content-type=text/html;%20charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html?content-type=text/html;%20charset=utf-8</a>.)</dd>
<dt class="label"><a name="WS-RM"></a>[Web Services Reliable Messaging] </dt><dd>
<cite>Web Services Reliable Messaging (WS-ReliableMessaging)</cite>, Doug Davis (IBM), Anish Karmarkar (Oracle),
- Gilbert Pilz (BEA), Steve Winkler (SAP), Umit Yalcinalp
- (SAP), August 7th, 2006, available at:
+ Gilbert Pilz (BEA), Steve Winkler (SAP), <span class="diff-chg">Ü. Yalçinalp
+ </span>(SAP), August 7th, 2006, available at:
http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-rddl-200608.html
(See <a href="http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-rddl-200608.html">http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-rddl-200608.html</a>.)</dd>
<dt class="label"><a name="WS-RM-Policy"></a>[Web Services Reliable Messaging Policy] </dt><dd>
<cite>Web Services Reliable Messaging Policy Assertion v1.1</cite>, Doug Davis (IBM), Anish Karmarkar (Oracle),
- Gilbert Pilz (BEA), Steve Winkler (SAP), Umit Yalcinalp
- (SAP), August 4, 2006, available at:
+ Gilbert Pilz (BEA), Steve Winkler (SAP), <span class="diff-chg">Ü. Yalçinalp
+ </span>(SAP), August 4, 2006, available at:
http://docs.oasis-open.org/ws-rx/wsrmp/200608/wsrmp-1.1-rddl-200608.html
(See <a href="http://docs.oasis-open.org/ws-rx/wsrmp/200608/wsrmp-1.1-rddl-200608.html">http://docs.oasis-open.org/ws-rx/wsrmp/200608/wsrmp-1.1-rddl-200608.html</a>.)</dd>
<dt class="label"><a name="WS-Security2004"></a>[WS-Security 2004] </dt><dd>
@@ -2197,6 +2024,22 @@
<div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">MH</td></div>
<div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">Restructure to address action items 64,77, which refer to bugzilla 3705 and F2F RESOLUTION 3792 </td></div>
</tr></div>
+ <div class="diff-add"><tr class="diff-add">
+ <div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">20061127</td></div>
+ <div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">ASV</td></div>
+ <div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">Updated the list of editors. Added
+ <a href="http://lists.w3.org/Archives/Public/public-ws-policy-eds/2006Nov/0033.html"><span class="diff-add">Frederick</span></a> and
+ <a href="http://lists.w3.org/Archives/Public/public-ws-policy-eds/2006Nov/0054.html"><span class="diff-add">Umit</span></a> to the list of editors.
+ Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/86"><span class="diff-add">86</span></a>.
+ </td></div>
+ </tr></div>
+ <div class="diff-add"><tr class="diff-add">
+ <div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">20061128</td></div>
+ <div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">MH</td></div>
+ <div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">Replaced section in Lifecycle with pointer to the text in the primer: related to action 77
+ </td></div>
+ </tr></div>
+
</tbody>
</table><br>
</div>
Received on Tuesday, 28 November 2006 23:48:17 UTC