- From: David Orchard via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 09 Aug 2006 00:32:02 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv29884
Modified Files:
ws-policy-attachment.html ws-policy-attachment.xml
Log Message:
issue 3545 (@any in notational conventions), AI 15 (termdef)
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- ws-policy-attachment.xml 28 Jul 2006 06:34:26 -0000 1.16
+++ ws-policy-attachment.xml 9 Aug 2006 00:31:59 -0000 1.17
@@ -147,7 +147,21 @@
treat it as an assertion.</p>
</item>
</ulist>
-
+ <p>Elements and Attributes defined by this specification are referred to in the text of this document using
+XPath 1.0 [XPATH 1.0] expressions. Extensibility points are referred to using an extended version of this
+syntax:</p>
+ <ulist>
+ <item>
+ <p>An element extensibility point is referred to using {any} in place of the element name. This
+indicates that any element name can be used, from any namespace other than the &nsuri;
+namespace. </p>
+ </item>
+ <item>
+ <p>An attribute extensibility point is referred to using @{any} in place of the attribute name. This
+indicates that any attribute name can be used, from any namespace other than the &nsuri;
+namespace. </p>
+ </item>
+ </ulist>
<p>Normative text within this specification takes precedence over
normative outlines, which in turn take precedence over the XML Schema
[<bibref ref='XMLSchemaPart1'/>] descriptions.</p>
@@ -277,8 +291,7 @@
</p>
<p>We introduce the following terms that are used throughout this document:</p>
-
-
+<p>EdNote: script will insert termdefs here</p>
<p><termdef id='policy' term='policy'>A <term>policy</term> is a
collection of <termref def='policy_alternative'>policy
alternatives</termref>. </termdef></p>
@@ -310,19 +323,6 @@
def='policy'>policy</termref> with one or more <termref
def='policy_scope'>policy scopes</termref>.</termdef></p>
-<p><termdef id='effective_policy' term='effective policy'>An
-<term>effective policy</term>, for a given <termref
-def='policy_subject'>policy subject</termref>, is the resultant
-combination of relevant policies. The relevant policies are those
-attached to <termref def='policy_scope'>policy scopes</termref> that
-contain the policy subject.</termdef></p>
-
-<p><termdef id='element_policy' term='element policy'>The
- <term>element policy</term> is the <termref
- def='policy'>policy</termref> attached to the <termref
- def='policy_subject'>policy subjects</termref> associated with
- the element information item that contains it.</termdef></p>
-
</div2>
<div2 id='Example'>
<head>Example</head>
@@ -436,14 +436,15 @@
at different points in a WSDL description that apply to a
subject, and other attachments may be made by UDDI and other
mechanisms.</p>
- <p>When multiple attachments are made, they must be combined
- to ascertain the <termref def='effective_policy'>effective
- policy</termref> for a particular <termref
- def='policy_subject'>policy subject</termref>. This is done by
- identifying which <termref def='policy_scope'>policy scopes</termref> a particular subject is in and
- combining the individual policies associated with those scopes
- to form an effective policy.</p>
- <p>This combination can be achieved by a <emph>merge</emph>
+
+ <p>When multiple attachments are made, <termdef id='effective_policy' term='effective policy'>the
+<term>effective policy</term>, for a given <termref
+def='policy_subject'>policy subject</termref>, is the
+combination of relevant policies. The relevant policies are those
+attached to <termref def='policy_scope'>policy scopes</termref> that
+contain the <termref def='policy_subject'>policy subject</termref>.</termdef>
+ </p>
+ <p>This combination can be achieved by a <emph>merge</emph>
operation. This consists of serializing each policy as a
<termref def='policy_expression'>policy expression</termref>, replacing their
<el>wsp:Policy</el> element with a
@@ -495,9 +496,14 @@
each of the values identifies a <termref def='policy_expression'>policy expression</termref> as defined by
[<bibref ref='WS-Policy'/>]. If more than one URI is specified, the
individual referenced <termref def='policy'>policies</termref> need to be <emph>merged</emph> together
-to form a single element <termref def='policy_expression'>policy expression</termref>. The resultant <termref def='policy'>policy</termref> is
+to form a single element <termref def='policy_expression'>policy expression</termref>.
+The resultant <termref def='policy'>policy</termref> is
then associated with the element information item's <termref def='element_policy'>element policy</termref>
-property. </p>
+property. <termdef id='element_policy' term='element policy'>The
+ <term>element policy</term> is the <termref
+ def='policy'>policy</termref> attached to the <termref
+ def='policy_subject'>policy subjects</termref> associated with
+ the element information item that contains it.</termdef></p>
<p>Note that the <termref def='policy_scope'>policy scope</termref> of the attachment is specific to the
<termref def='policy_attachment'>policy attachment</termref> Mechanism using it; accordingly, any <termref def='policy_attachment'>policy
@@ -1869,7 +1875,16 @@
<loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0107.html">XML
namespace URI versioning policy</loc> adopted by the WG.
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20060808</td>
+ <td>DBO</td>
+ <td>Completed action items: <loc href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action15">15</loc>
+ as early as possible in the doc, use the definition that are defined in the doc.
+ Issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3545">3545</loc>,
+ use of {any} and {@any} in xpath-like expressions not defined in Notational Conventions section
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -d -r1.20 -r1.21
--- ws-policy-attachment.html 28 Jul 2006 06:34:26 -0000 1.20
+++ ws-policy-attachment.html 9 Aug 2006 00:31:59 -0000 1.21
@@ -1,6 +1,5 @@
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Policy 1.5 - Attachment</title><style type="text/css">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
+<html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Policy 1.5 - Attachment</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -48,24 +47,40 @@
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
[...1966 lines suppressed...]
namespace URI versioning policy</a> adopted by the WG.
- </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060808</td>
+ <td rowspan="1" colspan="1">DBO</td>
+ <td rowspan="1" colspan="1">Completed action items: <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action15">15</a>
+ as early as possible in the doc, use the definition that are defined in the doc.
+ Issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3545">3545</a>,
+ use of {any} and {@any} in xpath-like expressions not defined in Notational Conventions section
+ </td>
+ </tr>
+ </tbody>
+ </table><br>
+ </div>
+</div>
+</body></html>
\ No newline at end of file
Received on Wednesday, 9 August 2006 00:32:11 UTC