- From: Maryann Hondo via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 08 May 2007 19:50:05 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv16515
Modified Files:
ws-policy-guidelines.xml
Log Message:
changes to section 5 to add G5,6,9,10 AI's 251,256
Index: ws-policy-guidelines.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.xml,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -d -r1.67 -r1.68
--- ws-policy-guidelines.xml 8 May 2007 01:05:29 -0000 1.67
+++ ws-policy-guidelines.xml 8 May 2007 19:50:02 -0000 1.68
@@ -648,6 +648,36 @@
</p>
<example>
<eg>
+ <sp:IssuedToken sp:IncludeToken="xs:anyURI"? ... >
+ <sp:Issuer> wsa:EndpointReferenceType</sp:Issuer>?
+ <sp:RequestSecurityTokenTemplate TrustVersion="xs:anyURI"? >
+ ...
+ </sp:RequestSecurityTokenTemplate >
+ <wsp:Policy >
+ <sp:RequireDerivedKeys /> ?
+ <sp:RequireExternalReference /> ?
+ <sp:RequireInternalReference /> ?
+ ...
+ </wsp:Policy> ?
+ ...
+</sp:IssuedToken>
+
+ </eg>
+ </example>
+
+ <p role="practice" id="AssertionDefinitions"> <quote>Clear Semantics</quote> >
+ <quote> An assertion description must clearly and completely specify the semantics of a policy
+ assertion.
+ </quote>
+ </p>
+ <p role="practice" id="XMLOutline"> <quote>XML Outline</quote> >
+ <quote> An assertion description should provide an XML outline plus an XML schema to specify the
+ syntax of the assertion.
+ </quote>
+ </p>
+
+ <example>
+ <eg>
<wsrmp:RMAssertion [wsp:Optional="true"]? ...>
...
</wsrmp:RMAssertion/>
@@ -936,7 +966,35 @@
to the WS-Policy framework.</quote>
</p>
</div3>
- </div2>
+ </div2>
+ <div2 id="Ignorable">
+ <head>Designating Ignorable Behavior</head>
+ <p>Policy assertions can be marked with an attribute to indicate that the assertion
+ can be ignored by the interstection algorithm. Assertion authors should consider
+ whether the behavior represented by the Assertion they are defining can be ignored for the purposes of
+ intersection, and indicate this in the definition of the assertion. The use of the
+ ignorable attribute influences whether or not certain assertions are part of the
+ compatability assessment between two alternatives. See [tbd] for details on the use
+ of the ignorable attribute.
+ </p>
+ <div3 id="doc-ignorable-assertions">
+ <head>Assertions and Ignorable Behavior</head>
+ <p role="practice" id="DefineIgnorable"><quote>Assertions Document Ignorable Behavior</quote> >
+ <quote> An assertion description should use the wsp:Ignorable attribute
+ to indicate that the behavior indicated by the QName may be ignored by policy intersection.
+ </quote>
+ </p>
+ </div3>
+ <div3 id="XML-ignorable-assertions">
+ <head>XML Outline for Ignorable </head>
+ <p role="practice" id="ignorableAssertions"> <quote>Ignorable Attribute in XML</quote> >
+ <quote> An assertion XML outline should allow for the use of the wsp:Ignorable attribute
+ to indicate ignorable behavior.
+ </quote>
+ </p>
+ </div3>
+ </div2>
+
<div2 id="optional-policy-assertion">
<head>Designating Optional Behaviors</head>
<div3>
@@ -2274,6 +2332,16 @@
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/227">227</loc>.
</td>
</tr>
+ <tr>
+ <td>20070508</td>
+ <td>MH</td>
+ <td>Updated Section 5 for adding guidelines G9, G10 on ignorable, and G5 , G6 (general)
+ to address editors' action items
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/251">251</loc>.
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/256">256</loc>.
+ </td>
+ </tr>
+
</tbody>
</table>
</inform-div1>
Received on Tuesday, 8 May 2007 19:50:07 UTC