- From: Felix Sasaki via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 10 Oct 2006 02:02:08 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv27446/ws/policy
Modified Files:
ws-policy-attachment.html ws-policy-attachment.xml
ws-policy-framework.html ws-policy-framework.xml
xmlspec-policy.xsl
Log Message:
Finished AI 20. See http://lists.w3.org/Archives/Public/public-ws-policy-eds/2006Oct/0038.html .
Index: xmlspec-policy.xsl
===================================================================
RCS file: /sources/public/2006/ws/policy/xmlspec-policy.xsl,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- xmlspec-policy.xsl 23 Sep 2006 05:23:23 -0000 1.3
+++ xmlspec-policy.xsl 10 Oct 2006 02:02:05 -0000 1.4
@@ -1,5 +1,5 @@
<?xml version="1.0"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0">
<xsl:import href="xmlspec.xsl"/>
<xsl:import href="changelog.xsl"/>
<xsl:output method="html" encoding="utf-8"
@@ -105,7 +105,7 @@
</xsl:otherwise>
</xsl:choose>
</xsl:template>
-<!--
+ <!--
<xsl:template match="b">
<b>
<xsl:apply-templates/>
@@ -123,9 +123,85 @@
</xsl:template>
-->
<xsl:template match="emph[@role='infoset-property']">
- <strong><xsl:text>[</xsl:text><xsl:apply-templates/><xsl:text>]</xsl:text></strong>
+ <strong>
+ <xsl:text>[</xsl:text>
+ <xsl:apply-templates/>
+ <xsl:text>]</xsl:text>
+ </strong>
+ </xsl:template>
+
+ <!-- Filtering term definitions in the terminology section. These are taken from the WS-Policy-Framework document and are handled separately in extract-glist.xsl .-->
+ <xsl:template match="ulist[@role='termreference']"/>
+
+ <!-- Adding numbers to examples automatically. Template taken from xmlspec.xsl and modified. -->
+ <xsl:template match="eg[@role='needs-numbering']">
+ <xsl:variable name="content">
+ <pre>
+ <xsl:if test="@diff and $show.diff.markup='1'">
+ <xsl:attribute name="class">
+ <xsl:text>diff-</xsl:text>
+ <xsl:value-of select="@diff"/>
+ </xsl:attribute>
+ </xsl:if>
+ <xsl:call-template name="addLineNumbers"/>
+ </pre>
+ </xsl:variable>
+ <xsl:choose>
+ <xsl:when test="$tabular.examples = 0">
+ <div class="exampleInner">
+ <xsl:copy-of select="$content"/>
+ </div>
+ </xsl:when>
+ <xsl:otherwise>
+ <table class="eg" cellpadding="5" border="1" bgcolor="#99ffff" width="100%"
+ summary="Example">
+ <tr>
+ <td>
+ <xsl:copy-of select="$content"/>
+ </td>
+ </tr>
+ </table>
+ </xsl:otherwise>
+ </xsl:choose>
+ </xsl:template>
+ <xsl:template name="addLineNumbers">
+ <xsl:variable name="egWithLb" as="item()*">
+ <egWithLb>
+ <lb/>
+ <xsl:for-each select="text()|node()">
+ <xsl:choose>
+ <xsl:when test="self::text()">
+ <xsl:analyze-string select="." regex="
">
+ <xsl:matching-substring>
+ <xsl:text>
</xsl:text>
+ <lb/>
+ </xsl:matching-substring>
+ <xsl:non-matching-substring>
+ <xsl:value-of select="."/>
+ </xsl:non-matching-substring>
+ </xsl:analyze-string>
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:copy-of select="."/>
+ </xsl:otherwise>
+ </xsl:choose>
+ </xsl:for-each>
+ </egWithLb>
+ </xsl:variable>
+ <xsl:apply-templates select="$egWithLb/node()" mode="addLineNumbers"/>
+ </xsl:template>
+ <xsl:template match="lb" mode="addLineNumbers">
+ <xsl:choose>
+ <xsl:when
+ test="not(contains(self::lb/following-sibling::text()[1],'xmlns'))">
+ <xsl:text>(</xsl:text>
+ <xsl:number format="01"
+ count="lb[not(contains(self::lb/following-sibling::text()[1],'xmlns'))]"/>
+ <xsl:text>) </xsl:text>
+ </xsl:when>
+ </xsl:choose>
+ </xsl:template>
+ <xsl:template match="node()" mode="addLineNumbers">
+ <xsl:copy-of select="."/>
</xsl:template>
-
- <!-- Filtering term definitions in the terminology section. These are taken from the WS-Policy-Framework document and are handled separately in extract-glist.xsl .-->
-<xsl:template match="ulist[@role='termreference']"/>
</xsl:stylesheet>
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -d -r1.66 -r1.67
--- ws-policy-framework.xml 9 Oct 2006 13:18:23 -0000 1.66
+++ ws-policy-framework.xml 10 Oct 2006 02:02:05 -0000 1.67
@@ -542,7 +542,7 @@
enumerate each of their assertions. The schema outline for
the normal form of a policy expression is as follows:</p>
- <eg xml:space="preserve"><wsp:Policy … >
+ <eg xml:space="preserve" role="needs-numbering"><wsp:Policy … >
<wsp:ExactlyOne>
( <wsp:All> ( <<emph>Assertion</emph> …> … </<emph>Assertion</emph>> )* </wsp:All> )*
</wsp:ExactlyOne>
@@ -624,7 +624,7 @@
<rfc2119>MAY</rfc2119> be associated with an IRI [<bibref ref='RFC3987'/>]. The schema outline
for attributes to associate an IRI is as follows:</p>
-<eg xml:space="preserve"><wsp:Policy ( Name="<emph>xs:anyURI</emph>" )?
+<eg xml:space="preserve" role="needs-numbering"><wsp:Policy ( Name="<emph>xs:anyURI</emph>" )?
( wsu:Id="<emph>xs:ID</emph>" | xml:id="<emph>xs:ID</emph>" )?
… >
…
@@ -731,18 +731,18 @@
that is a compact authoring style for expressing a pair of policy alternatives,
one with and one without that assertion. The schema outline for
this attribute is as follows:</p>
-<eg xml:space="preserve"><<emph>Assertion</emph> ( wsp:Optional="<emph>xs:boolean</emph>" )? …> … </<emph>Assertion</emph>></eg>
+<eg xml:space="preserve" role="needs-numbering"><<emph>Assertion</emph> ( wsp:Optional="<emph>xs:boolean</emph>" )? …> … </<emph>Assertion</emph>></eg>
<p>The following describes the Attribute Information Item defined in
the schema outline above:</p>
<glist><gitem>
<label><att>/Assertion/@wsp:Optional</att></label>
<def><p>If the actual value (See XML Schema Part 1 [<bibref ref="XMLSchemaPart1"/>]) is true, the expression of the assertion is semantically equivalent to the following:</p>
-<eg xml:space="preserve"><wsp:ExactlyOne>
+<eg xml:space="preserve" role="needs-numbering"><wsp:ExactlyOne>
<wsp:All> <<emph>Assertion</emph> …> … </<emph>Assertion</emph>> </wsp:All>
<wsp:All />
</wsp:ExactlyOne></eg>
<p>If the actual value (See XML Schema Part 1 [<bibref ref="XMLSchemaPart1"/>]) is false, the expression of the assertion is semantically equivalent to the following:</p>
-<eg xml:space="preserve"><wsp:ExactlyOne>
+<eg xml:space="preserve" role="needs-numbering"><wsp:ExactlyOne>
<wsp:All> <<emph>Assertion</emph> …> … </<emph>Assertion</emph>> </wsp:All>
</wsp:ExactlyOne></eg>
@@ -787,7 +787,7 @@
role="infoset-property">children</emph> property of a <termref def='policy_assertion'>policy assertion</termref>.</termdef> The schema
outline for a <termref def="nested_policy_expression">nested policy expression</termref> is:</p>
-<eg xml:space="preserve"><<emph>Assertion</emph> …>
+<eg xml:space="preserve" role="needs-numbering"><<emph>Assertion</emph> …>
…
( <wsp:Policy …> … </wsp:Policy> )?
…
@@ -956,67 +956,67 @@
ordered (see <specref ref="rPolicy_Alternative"/> and <specref ref="rPolicy"/>, respectively), <el>wsp:All</el> and
<el>wsp:ExactlyOne</el> are commutative. For example,</p>
-<eg xml:space="preserve"><wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All></eg>
+<eg xml:space="preserve" role="needs-numbering"><wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All></eg>
<p>is equivalent to:</p>
-<eg xml:space="preserve"><wsp:All> <emph><!-- assertion 2 --> <!-- assertion 1 --> </emph></wsp:All></eg>
+<eg xml:space="preserve" role="needs-numbering"><wsp:All> <emph><!-- assertion 2 --> <!-- assertion 1 --> </emph></wsp:All></eg>
<p>and:</p>
-<eg xml:space="preserve"><wsp:ExactlyOne>
+<eg xml:space="preserve" role="needs-numbering"><wsp:ExactlyOne>
<emph><!-- assertion 1 --> <!-- assertion 2 --></emph>
</wsp:ExactlyOne></eg>
<p>is equivalent to:</p>
-<eg xml:space="preserve"><wsp:ExactlyOne>
+<eg xml:space="preserve" role="needs-numbering"><wsp:ExactlyOne>
<emph><!-- assertion 2 --> <!-- assertion 1 --></emph>
</wsp:ExactlyOne></eg></def>
</gitem>
<gitem>
<label>Associative</label>
<def><p><el>wsp:All</el> and <el>wsp:ExactlyOne</el> are associative. For example,</p>
-<eg xml:space="preserve"><wsp:All>
+<eg xml:space="preserve" role="needs-numbering"><wsp:All>
<emph><!-- assertion 1 --></emph>
<emph> </emph><wsp:All> <emph><!-- assertion 2 --> </emph></wsp:All>
</wsp:All></eg>
<p>is equivalent to:</p>
-<eg xml:space="preserve"><wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All></eg>
+<eg xml:space="preserve" role="needs-numbering"><wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All></eg>
<p>and:</p>
-<eg xml:space="preserve"><wsp:ExactlyOne>
+<eg xml:space="preserve" role="needs-numbering"><wsp:ExactlyOne>
<emph><!-- assertion 1 --></emph>
<emph> </emph><wsp:ExactlyOne> <emph><!-- assertion 2 --> </emph></wsp:ExactlyOne>
</wsp:ExactlyOne></eg>
<p>is equivalent to:</p>
-<eg xml:space="preserve"><wsp:ExactlyOne>
+<eg xml:space="preserve" role="needs-numbering"><wsp:ExactlyOne>
<emph><!-- assertion 1 --> <!-- assertion 2 --></emph>
</wsp:ExactlyOne></eg></def>
</gitem>
<gitem>
<label>Idempotent</label>
<def><p><el>wsp:All</el> and <el>wsp:ExactlyOne</el> are idempotent. For example,</p>
-<eg xml:space="preserve"><wsp:All>
+<eg xml:space="preserve" role="needs-numbering" ><wsp:All>
<wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All>
</wsp:All></eg>
<p>is equivalent to:</p>
-<eg xml:space="preserve"><wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All></eg>
+<eg xml:space="preserve" role="needs-numbering"><wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All></eg>
<p>and:</p>
-<eg xml:space="preserve"><wsp:ExactlyOne>
+<eg xml:space="preserve" role="needs-numbering"><wsp:ExactlyOne>
<wsp:ExactlyOne>
<emph><!-- assertion 1 --> <!-- assertion 2 --></emph>
<emph> </emph></wsp:ExactlyOne>
</wsp:ExactlyOne></eg>
<p>is equivalent to:</p>
-<eg xml:space="preserve"><wsp:ExactlyOne>
+<eg xml:space="preserve" role="needs-numbering"><wsp:ExactlyOne>
<emph><!-- assertion 1 --> <!-- assertion 2 --></emph>
</wsp:ExactlyOne></eg></def>
</gitem>
<gitem>
<label>Distributive</label>
<def><p><el>wsp:All</el> distributes over <el>wsp:ExactlyOne</el>. For example,</p>
-<eg xml:space="preserve"><wsp:All>
+<eg xml:space="preserve" role="needs-numbering"><wsp:All>
<wsp:ExactlyOne>
<emph> <!-- assertion 1 --></emph>
<emph> <!-- assertion 2 --></emph>
</wsp:ExactlyOne>
</wsp:All></eg>
<p>is equivalent to:</p>
-<eg xml:space="preserve"><wsp:ExactlyOne>
+<eg xml:space="preserve" role="needs-numbering"><wsp:ExactlyOne>
<wsp:All>
<emph> <!-- assertion 1 --></emph>
</wsp:All>
@@ -1025,7 +1025,7 @@
</wsp:All>
</wsp:ExactlyOne></eg>
<p>Similarly by repeatedly distributing wsp:All over wsp:ExactlyOne,</p>
-<eg xml:space="preserve"><wsp:All>
+<eg xml:space="preserve" role="needs-numbering"><wsp:All>
<wsp:ExactlyOne>
<emph> <!-- assertion 1 --></emph>
<emph> <!-- assertion 2 --></emph>
@@ -1036,14 +1036,14 @@
</wsp:ExactlyOne>
</wsp:All></eg>
<p>is equivalent to:</p>
-<eg xml:space="preserve"><wsp:ExactlyOne>
+<eg xml:space="preserve" role="needs-numbering"><wsp:ExactlyOne>
<wsp:All><emph><!-- assertion 1 --><!-- assertion 3 --></emph></wsp:All>
<wsp:All><emph><!-- assertion 1 --><!-- assertion 4 --></emph></wsp:All>
<wsp:All><emph><!-- assertion 2 --><!-- assertion 3 --></emph></wsp:All>
<wsp:All><emph><!-- assertion 2 --><!-- assertion 4 --></emph></wsp:All>
</wsp:ExactlyOne></eg>
<p>Distributing <el>wsp:All</el> over an empty <el>wsp:ExactlyOne</el> is equivalent to no alternatives. For example,</p>
-<eg xml:space="preserve"><wsp:All>
+<eg xml:space="preserve" role="needs-numbering"><wsp:All>
<wsp:ExactlyOne>
<emph> <!-- assertion 1 --></emph>
<emph> <!-- assertion 2 --></emph>
@@ -1051,7 +1051,7 @@
<wsp:ExactlyOne />
</wsp:All></eg>
<p>is equivalent to:</p>
-<eg xml:space="preserve"><wsp:ExactlyOne /></eg>
+<eg xml:space="preserve" role="needs-numbering"><wsp:ExactlyOne /></eg>
<p>For example, given the following compact policy expression:</p>
<eg xml:space="preserve">(01) <wsp:Policy
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
@@ -1118,13 +1118,12 @@
<head>Policy References</head>
<p>The <el>wsp:PolicyReference</el> element is used to reference <termref def="policy_expression">policy expressions</termref>. The semantics of the <el>wsp:PolicyReference</el> element are determined by the context in which it is used (for an example, see <specref ref="Policy_Inclusion"/>).</p>
<p>The schema outline for the <el>wsp:PolicyReference</el> element is as follows:</p>
-<eg xml:space="preserve"><wsp:PolicyReference
+<eg xml:space="preserve" role="needs-numbering"><wsp:PolicyReference
URI="<emph>xs:anyURI</emph>"
( Digest="<emph>xs:base64Binary</emph>" ( DigestAlgorithm="<emph>xs:anyURI</emph>" )? )?
… >
…
-</wsp:PolicyReference>
-</eg>
+</wsp:PolicyReference></eg>
<p>The following describes the Attribute and Element Information Items defined in the schema outline above:</p>
<glist><gitem>
<label><el>/wsp:PolicyReference</el></label>
@@ -1399,7 +1398,7 @@
expressions, etc.</p>
<example id="ex-chained-policy-reference-elements">
<head>Chained Policy Reference Elements</head>
- <eg xml:space="preserve"><Policy wsu:Id="p1">
+ <eg xml:space="preserve" role="needs-numbering"><Policy wsu:Id="p1">
<PolicyReference URI="#p2"/ >
<PolicyReference URI="#p2"/>
</Policy>
Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -d -r1.49 -r1.50
--- ws-policy-framework.html 7 Oct 2006 22:30:56 -0000 1.49
+++ ws-policy-framework.html 10 Oct 2006 02:02:05 -0000 1.50
@@ -1,5 +1,6 @@
-<!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 - Framework</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 - Framework</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -47,43 +48,24 @@
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
[...2293 lines suppressed...]
- </td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">20061007</td>
- <td rowspan="1" colspan="1">TIB</td>
- <td rowspan="1" colspan="1">Completed action item:
+ </td></tr><tr><td rowspan="1" colspan="1">20061007</td><td rowspan="1" colspan="1">TIB</td><td rowspan="1" colspan="1">Completed action item:
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/19">19</a> Add an intro paragraph that introduces the material in section 4.3.3.
- </td>
- </tr>
- </tbody>
- </table><br>
- </div>
- </div>
-</body></html>
\ No newline at end of file
+ </td></tr><tr><td rowspan="1" colspan="1">20061008</td><td rowspan="1" colspan="1">MH</td><td rowspan="1" colspan="1">Completed action item:
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/45">45</a> Replace security policy example 1.1. as per issue 3753.
+ </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -d -r1.48 -r1.49
--- ws-policy-attachment.xml 9 Oct 2006 03:07:35 -0000 1.48
+++ ws-policy-attachment.xml 10 Oct 2006 02:02:05 -0000 1.49
@@ -509,8 +509,7 @@
<termref def="policy_expression">policy expressions</termref> to be attached to an arbitrary XML
element. The following is the schema definition for the
<att>wsp:PolicyURIs</att> attribute:</p>
-<eg xml:space="preserve">
-<xs:schema>
+<eg xml:space="preserve" role="needs-numbering"><xs:schema>
<xs:attribute name="PolicyURIs">
<xs:simpleType>
<xs:list itemType="xs:anyURI" />
@@ -538,10 +537,9 @@
attribute is given below using the sample policies stated in Section
<specref ref="Example"/>.</p>
<p>If the <termref def="policy">policies</termref> referenced by the following XML element</p>
-<eg xml:space="preserve"><MyElement wsp:PolicyURIs="
+<eg xml:space="preserve" role="needs-numbering"><MyElement wsp:PolicyURIs="
http://www.example.com/policies#RmPolicy
- http://www.example.com/policies#X509EndpointPolicy" />
- </eg>
+ http://www.example.com/policies#X509EndpointPolicy" /></eg>
<p>have been processed and <termref def="merge">merged</termref>,
it would result in an <termref def="element_policy">element policy</termref>
whose XML 1.0 representation is listed in <specref ref="Table4"/>:</p>
@@ -578,7 +576,7 @@
this are the same as for the use of the global attribute. For example,
an alternative way of attaching the policies in the above example,
using child elements, would be as follows: </p>
-<eg xml:space="preserve"><MyElement>
+<eg xml:space="preserve" role="needs-numbering"><MyElement>
<wsp:PolicyReference
URI="http://www.example.com/policies#RmPolicy" />
<wsp:PolicyReference
@@ -610,7 +608,7 @@
but this <termref def="policy_expression">policy expressions</termref> are not considered in scope with respect
to the <el>wsp:PolicyAttachment</el> element using it.</p>
<p>The following is the pseudo-schema for the <el>wsp:PolicyAttachment</el> element:</p>
-<eg xml:space="preserve"><wsp:PolicyAttachment … >
+<eg xml:space="preserve" role="needs-numbering"><wsp:PolicyAttachment … >
<wsp:AppliesTo>
<x:DomainExpression/> +
</wsp:AppliesTo>
@@ -710,7 +708,7 @@
<p>The following example illustrates the use of this mechanism with an
EndpointReference domain expression for a deployed endpoint as defined
in Web Services Addressing [<bibref ref="WS-Addressing"/>]:</p>
-<eg xml:space="preserve"><wsp:PolicyAttachment>
+<eg xml:space="preserve" role="needs-numbering"><wsp:PolicyAttachment>
<wsp:AppliesTo>
<wsa:EndpointReference>
<wsa:Address>http://www.example.com/acct</wsa:Address>
@@ -1955,7 +1953,7 @@
example, associating the <termref def="policy_expression">policy expression</termref> that is identified by the
IRI <code>http://www.example.com/myservice/policy</code> with a <el>businessService</el> is
done as follows: </p>
-<eg xml:space="preserve"><businessService serviceKey="…" >
+<eg xml:space="preserve" role="needs-numbering"><businessService serviceKey="…" >
<name>…</name>
<description>…</description>
<bindingTemplates>…</bindingTemplates>
@@ -1977,7 +1975,7 @@
contain a <el>categoryBag</el> in UDDI Version 2. Therefore, the
<el>bindingTemplate</el>'s <el>tModelInstanceInfo</el> and <el>instanceParms</el>
<rfc2119>MUST</rfc2119> be used as follows: </p>
-<eg xml:space="preserve"><bindingTemplate bindingKey="…" >
+<eg xml:space="preserve" role="needs-numbering"><bindingTemplate bindingKey="…" >
<accessPoint>…</accessPoint>
<tModelInstanceDetails>
<tModelInstanceInfo
@@ -2008,7 +2006,7 @@
<p>The following illustrates a tModel for the <termref def="policy_expression">policy expression</termref>
identified by the IRI
<code>http://www.example.com/myservice/policy</code>.</p>
-<eg xml:space="preserve"><tModel tModelKey="uuid:04cfa…">
+<eg xml:space="preserve" role="needs-numbering"><tModel tModelKey="uuid:04cfa…">
<name>…</name>
<description xml:lang="EN">
Policy Expression for example's Web services
@@ -2069,7 +2067,7 @@
example, associating the <termref def="policy_expression">policy expression</termref> tModel with the <att>tModelKey</att>
<code>"uuid:04cfa…"</code> from above with a <el>businessService</el> is done as
follows: </p>
-<eg xml:space="preserve"><businessService serviceKey="…" >
+<eg xml:space="preserve" role="needs-numbering"><businessService serviceKey="…" >
<name>…</name>
<description>…</description>
<bindingTemplates>…</bindingTemplates>
@@ -2090,7 +2088,7 @@
contain a <el>categoryBag</el> in UDDI Version 2. Therefore, the
<el>bindingTemplate</el>'s <el>tModelInstanceInfo</el> and <el>instanceParms</el>
<rfc2119>MUST</rfc2119> be used as follows: </p>
-<eg xml:space="preserve"><bindingTemplate bindingKey="…" >
+<eg xml:space="preserve" role="needs-numbering"><bindingTemplate bindingKey="…" >
<accessPoint>…</accessPoint>
<tModelInstanceDetails>
<tModelInstanceInfo
@@ -2130,7 +2128,7 @@
for other UDDI entities. For example, the example <el>bindingTemplate</el> from
section <specref ref="CalculatingEffectivePolicyElementPolicyUDDI"/> would be
changed as follows: </p>
-<eg xml:space="preserve"><bindingTemplate bindingKey="…" >
+<eg xml:space="preserve" role="needs-numbering"><bindingTemplate bindingKey="…" >
<accessPoint>…</accessPoint>
<tModelInstanceDetails>…</tModelInstanceDetails>
<categoryBag>
@@ -2148,7 +2146,8 @@
example, searching for all <termref def="policy_expression">policy expression</termref> tModels whose IRI starts
with <code>http://www.example.com/</code>, the following <code>find_tModel</code> API call can
be used: </p>
-<eg xml:space="preserve"><find_tModel xmlns="urn:uddi-org:api_v3" >
+<eg xml:space="preserve" role="needs-numbering"><find_tModel
+ xmlns="urn:uddi-org:api_v3" >
<categoryBag>
<keyedReference
keyValue="http://www.example.com/"
@@ -2480,7 +2479,7 @@
</div3>
<div3 id="ModelStructure1">
<head>tModel Structure</head>
-<eg xml:space="preserve"><tModel tModelKey="uuid:a27078e4-fd38-320a-806f-6749e84f8005" >
+<eg xml:space="preserve" role="needs-numbering"><tModel tModelKey="uuid:a27078e4-fd38-320a-806f-6749e84f8005" >
<name>http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference</name>
<description xml:lang="EN">Category system used for UDDI entities to point to an external Web Services Policy Attachment policy expression that describes their characteristics. See &attachment.title; specification for further details.</description>
<categoryBag>
@@ -2543,7 +2542,7 @@
</div3>
<div3 id="ModelStructure2">
<head>tModel Structure</head>
-<eg xml:space="preserve"><tModel tModelKey="uuid:fa1d77dc-edf0-3a84-a99a-5972e434e993" >
+<eg xml:space="preserve" role="needs-numbering"><tModel tModelKey="uuid:fa1d77dc-edf0-3a84-a99a-5972e434e993" >
<name>http://schemas.xmlsoap.org/ws/2003/03/policytypes</name>
<description xml:lang="EN">Web Services Policy Types category system used for UDDI tModels to characterize them as Web Services Policy – based policy expressions.</description>
<categoryBag>
@@ -2552,7 +2551,7 @@
keyValue="categorization"
tModelKey="uuid:c1acf26d-9672-4404-9d70-39b756e62ab4" />
</categoryBag>
-</tModel> </eg>
+</tModel></eg>
</div3>
</div2>
<div2 id="LocalPolicyReferenceCategorySystem">
@@ -2609,7 +2608,7 @@
</div3>
<div3 id="ModelStructure3">
<head>tModel Structure</head>
-<eg xml:space="preserve"><tModel tModelKey="uuid:a27f7d45-ec90-31f7-a655-efe91433527c" >
+<eg xml:space="preserve" role="needs-numbering"><tModel tModelKey="uuid:a27f7d45-ec90-31f7-a655-efe91433527c" >
<name>http://schemas.xmlsoap.org/ws/2003/03/localpolicyreference</name>
<description xml:lang="en">Category system used for UDDI entities to point to a Web Services Policy policy expression tModel that describes their characteristics. See &attachment.title; specification for further details.</description>
<categoryBag>
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -d -r1.49 -r1.50
--- ws-policy-attachment.html 3 Oct 2006 05:31:05 -0000 1.49
+++ ws-policy-attachment.html 10 Oct 2006 02:02:05 -0000 1.50
@@ -1,5 +1,6 @@
-<!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,
@@ -47,39 +48,24 @@
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
[...3466 lines suppressed...]
-<td rowspan="1" colspan="1">DBO</td>
-<td rowspan="1" colspan="1">Implemented the
+ </td></tr><tr><td rowspan="1" colspan="1">20061002</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Implemented the
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/48">resolution</a>
for issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3712">3712</a>:wsp:PolicyReference can be used in any place where you can use wsp:Policy
- </td>
-</tr>
-</tbody>
-</table><br>
-</div>
-</div>
-</body></html>
\ No newline at end of file
+ </td></tr><tr><td rowspan="1" colspan="1">20061008</td><td rowspan="1" colspan="1">MH</td><td rowspan="1" colspan="1">Implemented the
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/1">resolution</a>
+ for issue
+ <a href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action10">summary of Action 10 from F2F</a> replaced "subject" instances with "policy subject"
+ </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 10 October 2006 02:02:30 UTC