W3C home > Mailing lists > Public > public-ws-policy@w3.org > March 2007

Re: New Issue: (Bug 4389) WS-Policy 1.5 Attachment UDDI tModel keys and related references outdated

From: Felix Sasaki <fsasaki@w3.org>
Date: Tue, 13 Mar 2007 10:37:53 +0900
Message-ID: <45F60071.40107@w3.org>
To: Prasad Yendluri <prasad.yendluri@webmethods.com>
Cc: public-ws-policy@w3.org

Hi Prasad,

A question below.

Prasad Yendluri wrote:
>
> See bugzilla entry: http://www.w3.org/Bugs/Public/show_bug.cgi?id=4389
>
> _Title_: WS-Policy 1.5 Attachment UDDI tModel keys and related 
> references outdated
>
> _Description_:
>
> The WS-Policy 1.5 Attachment CR specification, UDDI attachment 
> sections use tModel definitions that are outdated. The tModel Keys are 
> based on the http://schemas.xmlsoap.org/ws/2003/03 namespace domain. 
> The definitions need to be changed use the w3.org ws-policy namesapce 
> domain.
>
> _Target_: WS-Policy 1.5 -
>
> _Proposed Resolution_:
>
> The attached word document (also HTML) shows the proposed changed to 
> section 6 and Appendix B of the attachment specification.
>
> Here is a summary of changes:
>
>    1. The tModels definitions in Appendix-B are changed to be as
>       follows (please see full details in the attached document):
>
> *Name: <#policy#policy>__*
>
> 	
>
> http://www.w3.org/ns/ws-policy/remotepolicyreference__
>
> *Description: 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>__*
>
> 	
>
> Category system used for UDDI entities to point to an external Web 
> services policy attachment policy that describes their 
> characteristics. See Web Services Policy 1.5 - Attachment 
> specification for further details. 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>__
>
> *UDDI Key (V3): 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>__*
>
> 	
>
> |uddi:w3c.org:ws-policy:v1.5:attachment:remotepolicyreference|__
>
> *UDDI V1,V2 format key: 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>__*
>
> 	
>
> uuid:c89e98b4-868c-3abf-a683-89071af807c6__
>
> *Categorization: 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>__*
>
> 	
>
> categorization 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>__
>
> *Checked: 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>__*
>
> 	
>
> No <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>__
>
> __
>
> *Name: <#policy_expression#policy_expression>__*
>
> 	
>
> http://www.w3.org/ns/ws-policy/policytypes__
>
> *Description: <#policy_expression#policy_expression>__*
>
> 	
>
> Web services policy types category system used for UDDI tModels to 
> characterize them as Web services policy–based policy expressions. 
> <#policy_expression#policy_expression>__
>
> *UDDI Key (V3): <#policy_expression#policy_expression>__*
>
> 	
>
> |uddi:w3c.org:ws-policy:v1.5:attachment:policytypes|__
>
> *UDDI V1,V2 format key: <#policy_expression#policy_expression>__*
>
> 	
>
> uuid:78003262-1ea8-3ae5-95cb-67cc900b6b59 
> <#policy_expression#policy_expression>__
>
> *Categorization: <#policy_expression#policy_expression>__*
>
> 	
>
> categorization <#policy_expression#policy_expression>__
>
> *Checked: <#policy_expression#policy_expression>__*
>
> 	
>
> No <#policy_expression#policy_expression>__
>
>
>         *_ _*
>
> *Name: <#policy_expression#policy_expression>__*
>
> 	
>
> http://www.w3.org/ns/ws-policy/localpolicyreference__
>
> *Description: 
> <http://schemas.xmlsoap.org/ws/2003/03/localpolicyreference/>__*
>
> 	
>
> Category system used for UDDI entities to point to a Web services 
> policy policy expression tModel that describes their characteristics. 
> See Web Services Policy 1.5 - Attachment specification for further 
> details. <http://schemas.xmlsoap.org/ws/2003/03/localpolicyreference/>__
>
> *UDDI Key (V3): <#policy_expression#policy_expression>__*
>
> 	
>
> |uddi:w3c.org:ws-policy:v1.5:attachment:localpolicyreference|| |__
>
> *UDDI V1,V2 format key: <#policy_expression#policy_expression>__*
>
> 	
>
> uuid:9e9bfbe9-2212-3c9c-a170-381e702a9946 __
>
> *Categorization: <#policy_expression#policy_expression>__*
>
> 	
>
> categorization <#policy_expression#policy_expression>__
>
> *Checked: <#policy_expression#policy_expression>__*
>
> 	
>
> Yes <#policy_expression#policy_expression>__
>
> __
>
>    2. Change all references to the previous tModels in section 6.2 and
>       6.3 to use the new tModels.
>
> 3. we need to provide the tModel description documents that should now 
> go at:
>
> http://www.w3.org/ns/ws-policy/remotepolicyreference 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> http://www.w3.org/ns/ws-policy/policytypes 
> <#policy_expression#policy_expression#pol> and
>
> http://www.w3.org/ns/ws-policy/localpolicyreference 
> <http://schemas.xmlsoap.org/ws/2003/03/localpolicyreference/>
>
> See old ones at:
>
> http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference
>
> http://schemas.xmlsoap.org/ws/2003/03/policytypes
>
> http://schemas.xmlsoap.org/ws/2003/03/localpolicyreference 
> <http://schemas.xmlsoap.org/ws/2003/03/localpolicyreference/>
>

Would it work to construct a "general URI description" for these, 
similar to http://www.w3.org/ns/ws-policy/Sha1Exc ?

Regards, Felix.

> Couple of points with the above proposal:
>
>    1. The UDDI v3 keys are now defined to use the
>       “|uddi:w3c.org:ws-policy:v1.5:attachment:” domain / preamble.|
>    2. |The V2 keys (UUIDs) are not derived from V2 keys. Should they be?|
>   3.
>
> Regards,
>
> Prasad
>
>
> ------------------------------------------------------------------------
>
> *Web Services Policy 1.5 - Attachment*
>
>
>     Editors' copy $Date: 2007/02/22 21:50:02 $ @@ @@@@ @@@@
>
> *This version:*
>
> ws-policy-attachment.html 
> <http://dev.w3.org/cvsweb/%7Echeckout%7E/2006/ws/policy/ws-policy-attachment.html> 
>
>
> *Latest version:*
>
> http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-attachment.html?content-type=text/html;charset=utf-8 
> <http://dev.w3.org/cvsweb/%7Echeckout%7E/2006/ws/policy/ws-policy-attachment.html?content-type=text/html;charset=utf-8>
>
> *Previous version:*
>
> http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117
>
> *Editors:*
>
> Asir S Vedamuthu, Microsoft Corporation
>
> David Orchard, BEA Systems, Inc.
>
> Frederick Hirsch, Nokia
>
> Maryann Hondo, IBM Corporation
>
> Prasad Yendluri, webMethods, Inc.
>
> Toufic Boubez, Layer 7 Technologies
>
> Ümit Yalçinalp, SAP AG.
>
> Copyright <http://www.w3.org/Consortium/Legal/ipr-notice#Copyright> © 
> @@@@ _W3C_ <http://www.w3.org/>^® (_MIT_ <http://www.csail.mit.edu/>, 
> _ERCIM_ <http://www.ercim.org/>, Keio <http://www.keio.ac.jp/>), All 
> Rights Reserved. W3C liability 
> <http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer>, 
> trademark 
> <http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks> and 
> document use <http://www.w3.org/Consortium/Legal/copyright-documents> 
> rules apply.
>
> ------------------------------------------------------------------------
>
>
>     Abstract
>
> This specification, Web Services Policy 1.5 - Attachment, defines two 
> general-purpose mechanisms for associating policies, as defined in Web 
> Services Policy 1.5 - Framework, with the subjects to which they 
> apply. This specification also defines how these general-purpose 
> mechanisms may be used to associate policies with WSDL and UDDI 
> descriptions.
>
>
>     Status of this Document
>
> *This document is an editors' copy that has no official standing.*
>
>
>     Table of Contents
>
> 1. Introduction <#tocRange>
> 2. Notations and Terminology <#NotationsTerminology>
> 2.1 Notational Conventions <#NotationalConventions>
> 2.2 XML Namespaces <#XMLNamespaces>
> 2.3 Terminology <#Glossary>
> 2.4 Example <#Example>
> 3. Policy Attachment <#rPolicyAttachment>
> 3.1 Effective Policy <#rEffectivePolicy>
> 3.2 Policy Attachment Mechanisms <#PolicyAttachmentMechanisms>
> 3.3 XML Element Attachment <#XMLElementAttachement>
> 3.4 External Policy Attachment <#ExternalPolicyAttachment>
> 3.4.1 URI Domain Expression <#uri-domain-expression>
> 3.5 Use of IRIs in Policy Attachment <#IRI_Policy_Attachment>
> 4. Attaching Policies Using WSDL 1.1 <#AttachingPolicyUsingWSDL1.1>
> 4.1 Calculating Effective Policy in WSDL 1.1 
> <#CalculatingEffectivyPolicywithWSDL1.1>
> 4.1.1 Service Policy Subject <#ServicePolicySubject>
> 4.1.2 Endpoint Policy Subject <#EndpointPolicySubject>
> 4.1.3 Operation Policy Subject <#OperationPolicySubject>
> 4.1.4 Message Policy Subject <#MessagePolicySubject>
> 4.1.5 Example <#Example2>
> 5. WS-Policy Attachment for WSDL 2.0 <#ws-policy-attachment-for-wsdl20>
> 5.1 Example <#wsdl20-example>
> 5.2 Attaching Policy Expressions <#attaching-policy-expressions>
> 5.3 Extension to WSDL Component Model <#extension-to-wsdl-component-model>
> 5.4 Effective Policy <#effective-policy>
> 5.4.1 Service Policy Subject <#service-policy-subject>
> 5.4.2 Endpoint Policy Subject <#endpoint-policy-subject>
> 5.4.3 Operation Policy Subject <#operation-policy-subject>
> 5.4.4 Message Policy Subject (input message) 
> <#message-policy-subject-input>
> 5.4.5 Message Policy Subject (output message) 
> <#message-policy-subject-output>
> 5.4.6 Message Policy Subject (input fault message) 
> <#message-policy-subject-input-fault>
> 5.4.7 Message Policy Subject (output fault message) 
> <#message-policy-subject-output-fault>
> 6. Attaching Policies Using UDDI <#AttachingPoliciesUsingUDDI>
> 6.1 Calculating Effective Policy and Element Policy in UDDI 
> <#CalculatingEffectivePolicyElementPolicy>
> 6.1.1 Service Provider Policy Subject <#ServiceProviderPolicySubjectUDDI>
> 6.1.2 Service Policy Subject <#ServicePolicySubjectUDDI>
> 6.1.3 Endpoint Policy Subject <#EndpointPolicySubjectUDDI>
> 6.2 Referencing Remote Policy Expressions 
> <#ReferencingRemotePolicyExpressions>
> 6.3 Registering Reusable Policy Expressions 
> <#RegisteringReusablePolicyExpressions>
> 6.4 Registering Policies in UDDI Version 3 
> <#RegisteringPoliciesUDDIVersion3>
> 7. Security Considerations <#SecurityConsiderations>
> 8. Conformance <#Conformance>
> 8.1 External Policy Attachment Conformance <#d3e3991>
> 8.2 WSDL 1.1 Attachment Conformance <#d3e4003>
> 8.3 WSDL 2.0 Attachment Conformance <#d3e4012>
>
>
>       Appendices
>
> A. References <#References>
> A.1 Normative References <#Normative-References>
> A.2 Other References <#Informative-References>
> B. UDDI tModel Definitions <#AppendixA>
> B.1 Remote Policy Reference Category System 
> <#RemotePolicyReferenceCategorySystem>
> B.1.1 Design Goals <#DesigGoals1>
> B.1.2 tModel Definition <#tModelDefinition1>
> B.1.3 tModel Structure <#ModelStructure1>
> B.2 Web Services Policy Types Category System 
> <#WS-PolicyTypesCategorySystem>
> B.2.1 Design Goals <#DesignGoals2>
> B.2.2 tModel Definition <#tModelDefinition2>
> B.2.3 tModel Structure <#ModelStructure2>
> B.3 Local Policy Reference Category System 
> <#LocalPolicyReferenceCategorySystem>
> B.3.1 Design Goals <#DesignGoals3>
> B.3.2 tModel Definition <#tModelDefinition3>
> B.3.3 tModel Structure <#ModelStructure3>
> C. Acknowledgements <#acknowledgments> (Non-Normative)
>
> ------------------------------------------------------------------------
>
>
>     1. Introduction
>
> The Web Services Policy 1.5 - Framework [Web Services Policy Framework 
> <#WS-Policy>] specification defines an abstract model and an XML-based 
> language for expressing policies <#policy> of entities in a Web 
> services-based system. This specification, Web Services Policy 1.5 - 
> Attachment, defines two general-purpose mechanisms for associating 
> policies with the subjects <#policy_subject> to which they apply; the 
> policies may be defined as part of existing metadata about the subject 
> or the policies may be defined independently and associated through an 
> external binding to the subject.
>
> To enable Web Services Policy to be used with existing Web service 
> technologies, this specification describes the use of these 
> general-purpose mechanisms with WSDL [WSDL 1.1 <#WSDL11>, WSDL 2.0 
> Core Language <#WSDL20>] definitions and UDDI [UDDI API 2.0 
> <#UDDIAPI20>, UDDI Data Structure 2.0 <#UDDIDataStructure20>, UDDI 3.0 
> <#UDDI30>].
>
>
>     2. Notations and Terminology
>
> This section specifies the notations, namespaces, and terminology used 
> in this specification.
>
> 2.1 Notational Conventions
>
> 2.2 XML Namespaces
>
>
>     3. Policy Attachment
>
> This section defines two general-purpose mechanisms for associating 
> policies <#policy> with one or more policy subjects <#policy_subject>.
>
>
>     _4. Attaching Policies Using WSDL 1.1_ <#AttachingPolicyUsingWSDL1.1>
>
>
> _ _
>
>
>     _5. WS-Policy Attachment for WSDL 2.0_ <#Table6>
>
> · _ _
>
>
>     _6. Attaching Policies Using UDDI_ <#policy>
>
> _This section defines a mechanism for associating policies with policy 
> subjects through the use of UDDI. It defines a minimum level of 
> support for associating policy expressions with entities in a UDDI 
> registry. The calculation of effective policy for UDDI entities is 
> described in Section *6.1 Calculating Effective Policy and Element 
> Policy in UDDI*. While the general concept for associating policy 
> expressions with UDDI entities, which is specified in Sections *6.2 
> Referencing Remote Policy Expressions* and *6.3 Registering Reusable 
> Policy Expressions*, is based on UDDI Version 2 [UDDI API 2.0, UDDI 
> Data Structure 2.0], the necessary changes with respect to UDDI 
> Version 3 [UDDI 3.0] are explained in Section *6.4 Registering 
> Policies in UDDI Version 3*._ <#policy>
>
> _There are essentially two approaches for registering policies in 
> UDDI. One approach is to directly reference remotely accessible policy 
> expressions in UDDI entities, the other is to register policy 
> expressions as distinct tModels and then reference these tModels in 
> each UDDI entity that is using the policy expression. While the former 
> approach (see Section *6.2 Referencing Remote Policy Expressions*) is 
> expected to be used for policy expressions that are mainly unique for 
> a given Web service, the latter approach (see Section *6.3 Registering 
> Reusable Policy Expressions*) is expected to be used for more modular 
> and reusable policy expressions._ <#policy>
>
>
>       _6.1 Calculating Effective Policy and Element Policy in UDDI_
>       <#RegisteringPoliciesUDDIVersion3>
>
> _When attaching a policy to a UDDI entity a policy scope is implied 
> for that attachment. The policy scope only contains the policy 
> subjects associated with that entity, and not those associated with 
> the children of that entity. This policy is the entity's element 
> policy._ <#policy_expression>
>
> _Each policy assertion contained within a UDDI entity's element policy 
> should have the correct semantic such that the policy subject for that 
> assertion is that UDDI entity. For example, assertions that describe 
> behaviours regarding a service provider should only be contained 
> within policies attached to a businessEntity structure._ 
> <#policy_expression>
>
> _For UDDI tModels that represent Web service types, the element policy 
> is considered an intrinsic part of the tModel and applies to all uses 
> of that tModel. In particular, it MUST be merged into the effective 
> policy of every bindingTemplate that references that tModel._ 
> <#element_policy>
>
> _Policies that apply to deployed Web services (bindingTemplates) are 
> only considered in the effective policy of that deployed resource 
> itself._ <#element_policy>
>
> _Each of these entities MAY have an element policy per Section *3. 
> Policy Attachment*. The remainder of this section defines how that 
> element policy is interpreted to calculate the effective policy._ 
> <#effective_policy>
>
>
>         _6.1.1 Service Provider Policy Subject_ <#effective_policy>
>
> _The following UDDI element is considered as the service provider 
> policy subject:_ <#effective_policy>
>
> · |_uddi:businessEntity _ <#effective_policy>|
>
> _This element MAY have element policy as per Section *3. Policy 
> Attachment*, and if present MUST be merged into the effective policy 
> of the UDDI businessEntity Subject._ <#effective_policy>
>
> _Policy attached to the service provider policy subject applies to 
> behaviors or aspects of the service provider as a whole, irrespective 
> of interactions over any particular service. This includes — but is 
> not limited to — acting as a service consumer or a service provider in 
> general. _ <#effective_policy>
>
>
>         _6.1.2 Service Policy Subject_ <#effective_policy>
>
> _The following UDDI element is considered as the service policy 
> subject:_ <#effective_policy>
>
> · |_uddi:businessService _ <#effective_policy>|
>
> _This element MAY have element policy as per Section *3. Policy 
> Attachment*, and if present MUST be merged into the effective policy 
> of the UDDI businessService Subject._ <#effective_policy>
>
> _Policy attached to the service policy subject applies to behaviors or 
> aspects of the service as a whole, irrespective of interactions over 
> any particular endpoint. This includes — but is not limited to — 
> acting as a consumer or a provider of the service._ <#effective_policy>
>
>
>         _6.1.3 Endpoint Policy Subject_ <#effective_policy>
>
> _The following UDDI elements collectively describe an endpoint:_ 
> <#effective_policy>
>
> · |_uddi:bindingTemplate _ <#effective_policy>|
>
> · |_uddi:tModel _ <#effective_policy>|
>
> _These elements MAY have element policy as per Section *3. Policy 
> Attachment*. The policy scope implied by each of these elements 
> contains the endpoint policy subject representing the deployed 
> endpoint._ <#effective_policy>
>
> _An endpoint policy subject applies to behaviours associated with an 
> entire endpoint of the service, irrespective of any message exchange 
> made. This includes — but is not limited to — aspects of communicating 
> with or instantiating the endpoint._ <#effective_policy>
>
> _The effective policy for a UDDI endpoint includes the element policy 
> of the |uddi:bindingTemplate| element that defines the endpoint merged 
> with the element policy of those |uddi:tModel| elements that are 
> referenced in contained |uddi:tModelInstanceInfo| elements._ 
> <#policy_scope>
>
>
>       _6.2 Referencing Remote Policy Expressions_ <#policy_scope>
>
> _UDDI tModels provide a generic mechanism for associating arbitrary 
> metadata with services and other entities in a UDDI registry. To 
> properly integrate Web Services Policy into the UDDI model, Web 
> Services Policy 1.5 - Attachment pre-defines one tModel that is used 
> to associate a remotely accessible policy with an entity in a UDDI 
> registry._ <#element_policy>
>
> _This new tModel is called the remote policy reference category system 
> and is defined in Appendix *B.1 Remote Policy Reference Category 
> System*._ <#element_policy>
>
> _UDDI registries MUST use the (UDDI V2 [UDDI Data Structure 2.0]) 
> _|_tModelKey_|_ 
> _|_uuid:c89e98b4-868c-3abf-a683-89071af807c6_||_uuid:a27078e4-fd38-320a-806f-6749e84f8005_|_ 
> to uniquely identify this tModel so that UDDI registry users can 
> expect the same behavior across different UDDI registries._ <#policy>
>
> _The tModel's valid values are those IRIs that identify external 
> policy expressions; that is, when referencing this category system in 
> a |categoryBag|, the corresponding |keyValue| of the |keyedReference| 
> is the IRI of the policy expression._ 
> <#RemotePolicyReferenceCategorySystem>
>
> _Using the remote policy reference category system, one can then 
> associate a policy expression with a |businessEntity|, a 
> |businessService|, and a tModel using the entity's |categoryBag|. For 
> example, associating the policy expression that is identified by the 
> IRI |http://www.example.com/myservice/policy| with a |businessService| 
> is done as follows: _ <#UDDIDataStructure20>
>
> _(01) <businessService serviceKey="…" >_ <#policy_expression>
>
> _(02) <name>…</name>_ <#policy_expression>
>
> _(03) <description>…</description>_ <#policy_expression>
>
> _(04) <bindingTemplates>…</bindingTemplates>_ <#policy_expression>
>
> _(05) <categoryBag>_ <#policy_expression>
>
> _(06) <keyedReference_ <#policy_expression>
>
> _(07) keyName="Policy Expression for example's Web services"_ 
> <#policy_expression>
>
> _(08) keyValue="http://www.example.com/myservice/policy"_ 
> <#policy_expression>
>
> (09) 
> tModelKey="uuid:c89e98b4-868c-3abf-a683-89071af807c6uuid:a27078e4-fd38-320a-806f-6749e84f8005" 
> />
>
> _(10) </categoryBag>_ <#policy_expression>
>
> _(11) </businessService>_ <#policy_expression>
>
> _The |tModelKey| of the |keyedReference| MUST match the fixed 
> |tModelKey| from the remote policy reference category system. The 
> |keyValue| MUST be the IRI that identifies the policy expression._ 
> <#policy_expression>
>
> _A different approach has to be taken to associate a policy expression 
> with a |bindingTemplate|, since bindingTemplates do not contain a 
> |categoryBag| in UDDI Version 2. Therefore, the |bindingTemplate|'s 
> |tModelInstanceInfo| and |instanceParms| MUST be used as follows: _ 
> <#policy_expression>
>
> _(01) <bindingTemplate bindingKey="…" >_ <#policy_expression>
>
> _(02) <accessPoint>…</accessPoint>_ <#policy_expression>
>
> _(03) <tModelInstanceDetails>_ <#policy_expression>
>
> _(04) <tModelInstanceInfo_ <#policy_expression>
>
> (05) 
> tModelKey="uuid:c89e98b4-868c-3abf-a683-89071af807c6uuid:a27078e4-fd38-320a-806f-6749e84f8005" 
> >
>
> _(06) <instanceDetails>_ <#policy_expression>
>
> _(07) <instanceParms>_ <#policy_expression>
>
> _(08) http://www.example.com/myservice/policy_ <#policy_expression>
>
> _(09) </instanceParms>_ <#policy_expression>
>
> _(10) </instanceDetails>_ <#policy_expression>
>
> _(11) </tModelInstanceInfo>_ <#policy_expression>
>
> _(12) </tModelInstanceDetails>_ <#policy_expression>
>
> _(13) </bindingTemplate>_ <#policy_expression>
>
> _The |tModelKey| of the |tModelInstanceInfo| MUST match the fixed 
> |tModelKey| from the remote policy reference category system as 
> defined above. The |instanceParms| MUST be the IRI that identifies the 
> policy expression._ <#policy_expression>
>
>
>       _6.3 Registering Reusable Policy Expressions_ <#policy_expression>
>
> _In addition to using the approach outlined in the section above, 
> publishers may register a specific policy expression in a UDDI 
> registry as a distinct tModel. To properly categorize tModels as 
> policy expressions, Web Services Policy 1.5 - Attachment pre-defines 
> the Web Services Policy Types category system as a tModel. This tModel 
> is defined in Appendix *B.2 Web Services Policy Types Category 
> System*._ <#policy_expression>
>
> _The following illustrates a tModel for the policy expression 
> identified by the IRI |http://www.example.com/myservice/policy|._ 
> <#policy_expression>
>
> _(01) <tModel tModelKey="uuid:04cfa…">_ <#WS-PolicyTypesCategorySystem>
>
> _(02) <name>…</name>_ <#policy_expression>
>
> _(03) <description xml:lang="EN">_ <#policy_expression>
>
> _(04) Policy Expression for example's Web services_ <#policy_expression>
>
> _(05) </description>_ <#policy_expression>
>
> _(06) <overviewDoc>_ <#policy_expression>
>
> _(07) <description xml:lang="EN">Web Services Policy 
> Expression</description>_ <#policy_expression>
>
> _(08) 
> <overviewURL>http://www.example.com/myservice/policy</overviewURL>_ 
> <#policy_expression>
>
> _(09) </overviewDoc>_ <#policy_expression>
>
> _(10) <categoryBag>_ <#policy_expression>
>
> _(11) <keyedReference_ <#policy_expression>
>
> _(12) keyName="Reusable policy Expression"_ <#policy_expression>
>
> _(13) keyValue="policy"_ <#policy_expression>
>
> (14) 
> tModelKey="uuid:78003262-1ea8-3ae5-95cb-67cc900b6b59uuid:fa1d77dc-edf0-3a84-a99a-5972e434e993" 
> />
>
> _(15) <keyedReference_ <#policy_expression>
>
> _(16) keyName="Policy Expression for example's Web services"_ 
> <#policy_expression>
>
> _(17) keyValue="http://www.example.com/myservice/policy"_ 
> <#policy_expression>
>
> (18) 
> tModelKey="uuid:c89e98b4-868c-3abf-a683-89071af807c6uuid:a27078e4-fd38-320a-806f-6749e84f8005" 
> />
>
> _(19) </categoryBag>_ <#policy_expression>
>
> _(20) </tModel>_ <#policy_expression>
>
> _The first |keyedReference| specifies that the tModel represents a 
> policy expression — rather than only being associated with one — by 
> using the Web Services Policy Types category system's built-in 
> category |"policy"|, which is its single valid value. This is 
> necessary in order to enable UDDI inquiries for policy expressions in 
> general. The second |keyedReference| designates the policy expression 
> the tModel represents by using the approach from the section above. 
> This is necessary in order to enable UDDI inquiries for particular 
> policy expressions based on their IRI._ <#policy_expression>
>
> _Note that the policy expression IRI is also specified in the tModel's 
> overview URL to indicate that it is a resolvable URL to actually 
> retrieve the policy expression._ <#policy_expression>
>
> _Web Services Policy 1.5 - Attachment pre-defines another tModel that 
> is used to associate such a pre-registered, locally available policy 
> expressions with an entity in a UDDI registry_ <#policy_expression>
>
> _This new tModel is called the local policy reference category system 
> and is defined in Appendix *B.3 Local Policy Reference Category 
> System*._ <#policy_expression>
>
> _UDDI registries MUST use the |tModelKey| 
> uuid:9e9bfbe9-2212-3c9c-a170-381e702a9946|uuid:a27f7d45-ec90-31f7-a655-efe91433527c| 
> to uniquely identify this tModel so that UDDI registry users can 
> expect the same behavior across different UDDI registries._ 
> <#policy_expression>
>
> _The local policy reference category system is based on tModelKeys. 
> The valid values of this category system are those tModelKeys 
> identifying tModels that_ <#LocalPolicyReferenceCategorySystem>
>
> · _exist in the same UDDI registry_ <#LocalPolicyReferenceCategorySystem>
>
> · _and are categorized as |"policy"| using the Web Services Policy 
> Types category system._ <#LocalPolicyReferenceCategorySystem>
>
> _That is, when referencing this category system in a category bag, the 
> corresponding |keyValue| of the |keyedReference| is the |tModelKey| of 
> the tModel that represents the policy expression._ 
> <#LocalPolicyReferenceCategorySystem>
>
> _Given the local policy reference category system, one can then 
> associate a policy expression tModel with a |businessEntity|, a 
> |businessService|, and a tModel using the entity's |categoryBag|. For 
> example, associating the policy expression tModel with the |tModelKey| 
> |"uuid:04cfa…"| from above with a |businessService| is done as 
> follows: _ <#LocalPolicyReferenceCategorySystem>
>
> _(01) <businessService serviceKey="…" >_ <#policy_expression>
>
> _(02) <name>…</name>_ <#policy_expression>
>
> _(03) <description>…</description>_ <#policy_expression>
>
> _(04) <bindingTemplates>…</bindingTemplates>_ <#policy_expression>
>
> _(05) <categoryBag>_ <#policy_expression>
>
> _(06) <keyedReference_ <#policy_expression>
>
> _(07) keyName="Policy Expression for example's Web services"_ 
> <#policy_expression>
>
> _(08) keyValue="uuid:04cfa…"_ <#policy_expression>
>
> (09) 
> tModelKey="uuid:9e9bfbe9-2212-3c9c-a170-381e702a9946uuid:a27f7d45-ec90-31f7-a655-efe91433527c" 
> />
>
> _(10) </categoryBag>_ <#policy_expression>
>
> _(11) </businessService>_ <#policy_expression>
>
> _The |tModelKey| of the |keyedReference| MUST match the fixed 
> |tModelKey| from the local policy reference category system. The 
> keyValue MUST be the |tModelKey| of the policy expression that is 
> registered with the UDDI registry._ <#policy_expression>
>
> _A different approach has to be taken to associate a policy expression 
> with a |bindingTemplate|, since bindingTemplates do not contain a 
> |categoryBag| in UDDI Version 2. Therefore, the |bindingTemplate|'s 
> |tModelInstanceInfo| and |instanceParms| MUST be used as follows: _ 
> <#policy_expression>
>
> _(01) <bindingTemplate bindingKey="…" >_ <#policy_expression>
>
> _(02) <accessPoint>…</accessPoint>_ <#policy_expression>
>
> _(03) <tModelInstanceDetails>_ <#policy_expression>
>
> _(04) <tModelInstanceInfo_ <#policy_expression>
>
> (05) 
> tModelKey="uuid:9e9bfbe9-2212-3c9c-a170-381e702a9946uuid:a27f7d45-ec90-31f7-a655-efe91433527c" 
> >
>
> _(06) <instanceDetails>_ <#policy_expression>
>
> _(07) <instanceParms>uuid:04cfa…</instanceParms>_ <#policy_expression>
>
> _(08) </instanceDetails>_ <#policy_expression>
>
> _(09) </tModelInstanceInfo>_ <#policy_expression>
>
> _(10) </tModelInstanceDetails>_ <#policy_expression>
>
> _(11) </bindingTemplate>_ <#policy_expression>
>
> _The tModelKey of the |tModelInstanceInfo| MUST match the fixed 
> |tModelKey| from the local policy reference category system. The 
> |instanceParms| MUST be the |tModelKey| of the policy expression that 
> is registered with the UDDI registry._ <#policy_expression>
>
>
>       _6.4 Registering Policies in UDDI Version 3_ <#policy_expression>
>
> _UDDI Version 3 [UDDI 3.0] provides a number of enhancements in the 
> areas of modeling and entity keying. Special considerations for UDDI 
> multi-version support are outlined in chapter 10 of [UDDI 3.0]. The 
> changes with respect to the previous sections are as follows._ 
> <#policy_expression>
>
> _First, the tModelKeys of the pre-defined tModels are migrated to 
> domain-based keys. The migration is unique since the Version 2 keys 
> introduced in this specification are already programmatically derived 
> from the Version 3 keys given below._ <#policy_expression>
>
> _The |tModelKey| for the remote policy reference tModel changes from 
> |"|_ 
> _|_uuid:c89e98b4-868c-3abf-a683-89071af807c6_uuid:a27078e4-fd38-320a-806f-6749e84f8005"| 
> to |"uddi:w3c.org:ws-policy:v1.5:attachment:remotepolicyreference|_ 
> _|uddi:schemas.xmlsoap.org:remotepolicyreference:2003_03"|._ <#UDDI30>
>
> _The |tModelKey| for the Web Services Policy Types tModel changes from 
> |"|_ 
> _|_uuid:78003262-1ea8-3ae5-95cb-67cc900b6b59_uuid:fa1d77dc-edf0-3a84-a99a-5972e434e993"| 
> to 
> |"_uddi:w3c.org:ws-policy:v1.5:attachment:policytypes_uddi:schemas.xmlsoap.org:policytypes:2003_03"|._ 
> <#UDDI30>
>
> _The |tModelKey| for the local policy reference tModel changes from 
> |"|uuid:9e9bfbe9-2212-3c9c-a170-381e702a9946|uuid:a27f7d45-ec90-31f7-a655-efe91433527c"| 
> to |"_uddi:w3c.org:ws-policy:v1.5:attachment:localpolicyreference 
> _uddi:schemas.xmlsoap.org:localpolicyreference:2003_03"|._ <#UDDI30>
>
> _Second, rather than putting policy expression references in a 
> |bindingTemplate|'s |tModelInstanceInfo|, they are added to the 
> |bindingTemplate|'s |categoryBag|, analogous to the mechanism 
> described for other UDDI entities. For example, the example 
> |bindingTemplate| from section *6.1 Calculating Effective Policy and 
> Element Policy in UDDI* would be changed as follows: _ <#UDDI30>
>
> _(01) <bindingTemplate bindingKey="…" >_ <#UDDI30>
>
> _(02) <accessPoint>…</accessPoint>_ 
> <#CalculatingEffectivePolicyElementPolicy>
>
> _(03) <tModelInstanceDetails>…</tModelInstanceDetails>_ 
> <#CalculatingEffectivePolicyElementPolicy>
>
> _(04) <categoryBag>_ <#CalculatingEffectivePolicyElementPolicy>
>
> _(05) <keyedReference_ <#CalculatingEffectivePolicyElementPolicy>
>
> _(06) keyName="Policy Expression for example's Web services"_ 
> <#CalculatingEffectivePolicyElementPolicy>
>
> _(07) keyValue="http://www.example.com/myservice/policy"_ 
> <#CalculatingEffectivePolicyElementPolicy>
>
> (08) 
> tModelKey="uddi:w3c.org:ws-policy:v1.5:attachment:remotepolicyreference 
> uddi:schemas.xmlsoap.org:remotepolicyreference:2003_03"
>
> _(09) />_ <#CalculatingEffectivePolicyElementPolicy>
>
> _(10) </categoryBag>_ <#CalculatingEffectivePolicyElementPolicy>
>
> _(11) </bindingTemplate>_ <#CalculatingEffectivePolicyElementPolicy>
>
> _Third, inquiries for reusable policy expression tModels described in 
> Section *6.3 Registering Reusable Policy Expressions* and UDDI tModel 
> entities that are associated with remote policy expression is enhanced 
> by the wildcard mechanism for keyValues in keyedReferences. For 
> example, searching for all policy expression tModels whose IRI starts 
> with |http://www.example.com/|, the following |find_tModel| API call 
> can be used: _ <#CalculatingEffectivePolicyElementPolicy>
>
> _(01) <find_tModel _ <#CalculatingEffectivePolicyElementPolicy>
>
> _ xmlns="urn:uddi-org:api_v3" >_ <#policy_expression>
>
> _(02) <categoryBag>_ <#policy_expression>
>
> _(03) <keyedReference_ <#policy_expression>
>
> _(04) keyValue="http://www.example.com/"_ <#policy_expression>
>
> (05) 
> tModelKey="uddi:w3c.org:ws-policy:v1.5:attachment:remotepolicyreference 
> uddi:schemas.xmlsoap.org:remotepolicyreference:2003_03"
>
> _(06) />_ <#policy_expression>
>
> _(07) </categoryBag>_ <#policy_expression>
>
> _(08) <findQualifiers>_ <#policy_expression>
>
> _(09) <findQualifier>approximateMatch</findQualifier>_ 
> <#policy_expression>
>
> _(10) </findQualifiers>_ <#policy_expression>
>
> _(11) </find_tModel>_ <#policy_expression>
>
> _Fourth, all UDDI entities may be digitally signed using XML digital 
> signatures [XML-Signature]. Publishers who want to digitally sign 
> their policy expression tModels or policy expression references in 
> UDDI MUST use the Schema-centric canonicalization algorithm [SCC14N]._ 
> <#policy_expression>
>
>
>     _7. Security Considerations_ <#policy_expression>
>
> _It is RECOMMENDED that policy attachments be integrity protected to 
> permit the detection of tampering. This can be done using a technology 
> such as XML DSig [XML-Signature], SSL/TLS [IETF RFC 2246], or 
> WS-Security 2004 [WS-Security 2004]. This also provides a mechanism 
> for authenticating policy attachments by determining if the signer has 
> the right to "speak for" the scope of the policy attachment._ <#SCC14N>
>
> _Policies SHOULD NOT be accepted unless they are signed and have an 
> associated security token to specify the signer has the right to 
> "speak for" the scope containing the policy._ <#SCC14N>
>
> _A more complete discussion of security considerations can be found in 
> the Security Considerations section of the Web Services Policy 1.5 - 
> Framework document [Web Services Policy Framework]. _ <#policy_attachment>
>
>
>     _8. Conformance_ <#policy>
>
>
>       _8.1 External Policy Attachment Conformance_ <#WS-Policy>
>
> _An element information item whose namespace name is 
> "http://www.w3.org/ns/ws-policy" and whose local part is 
> PolicyAttachment conforms to this specification if it is valid 
> according to the XML Schema [XML Schema Structures] for that element 
> as defined by this specification 
> (http://www.w3.org/2007/02/ws-policy.xsd) and additionally adheres to 
> all the constraints contained in Section *3.4 External Policy 
> Attachment* of this specification. Such a conformant element 
> information item constitutes an external policy attachment. _ <#WS-Policy>
>
>
>       _8.2 WSDL 1.1 Attachment Conformance_ <#WS-Policy>
>
> _A WSDL 1.1 [WSDL 1.1] description conforms to this specification when 
> it incorporates one or more element policies and additionally adheres 
> to all the constraints contained in section *4. Attaching Policies 
> Using WSDL 1.1* _ <#ExternalPolicyAttachment>
>
>
>       _8.3 WSDL 2.0 Attachment Conformance_ <#ExternalPolicyAttachment>
>
> _A WSDL 2.0 [WSDL 2.0 Core Language] description conforms to this 
> specification when it incorporates one or more element policies and 
> additionally adheres to all the constraints contained in section *5. 
> WS-Policy Attachment for WSDL 2.0* _ <#AttachingPolicyUsingWSDL1.1>
>
>
>     _A. References_ <#AttachingPolicyUsingWSDL1.1>
>
>
>       _A.1 Normative References_ <#ws-policy-attachment-for-wsdl20>
>
> *_[BP 1.1] _ <#ws-policy-attachment-for-wsdl20>*
>
> _Basic Profile Version 1.1, K. Ballinger, et al, Editors. The Web 
> Services-Interoperability Organization, 10 June 2006. This version of 
> the Basic Profile Version 1.1 is 
> http://www.ws-i.org/Profiles/BasicProfile-1.1-2006-04-10.html. The 
> latest version of the Basic Profile Version 1.1 is available at 
> http://www.ws-i.org/Profiles/BasicProfile-1.1.html _ 
> <#ws-policy-attachment-for-wsdl20>
>
> *_[IETF RFC 3023] _ <#ws-policy-attachment-for-wsdl20>*
>
>
>     _B. UDDI tModel Definitions_
>     <http://www.ws-i.org/Profiles/BasicProfile-1.1.html>
>
> _This section contains the UDDI tModel definitions for the canonical 
> tModels used in Section *6. Attaching Policies Using UDDI*. The 
> tModelKeys shown in the tModel structure sections are valid UDDI 
> Version 2 keys. When using UDDI Version 3, the corresponding derived 
> UDDI Version 2 keys must be used._ <http://www.w3.org/TR/xptr-framework/>
>
>
>       _B.1 Remote Policy Reference Category System_
>       <http://www.w3.org/TR/xptr-framework/>
>
>
>         _B.1.1 Design Goals_ <#AttachingPoliciesUsingUDDI>
>
> _This tModel is used to attach a policy to a UDDI entity by 
> referencing the policy's IRI._ <#AttachingPoliciesUsingUDDI>
>
>
>         _B.1.2 tModel Definition_ <#AttachingPoliciesUsingUDDI>
>
> *_Name:_ <#policy>*
>
> 	
>
> _http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference _ <#policy>
>
> _http://www.w3.org/ns/ws-policy/remotepolicyreference_
>
> *_Description:_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>*
>
> 	
>
> _Category system used for UDDI entities to point to an external Web 
> services policy attachment policy that describes their 
> characteristics. See Web Services Policy 1.5 - Attachment 
> specification for further details._ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> *_UDDI Key (V3):_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>*
>
> 	
>
> |_uddi:schemas.xmlsoap.org:remotepolicyreference:2003_03_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>|
>
> |____uddi:w3c.org:ws-policy:v1.5:attachment:remotepolicyreference____ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>|
>
> *_UDDI V1,V2 format key:_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>*
>
> 	
>
> |_uuid:a27078e4-fd38-320a-806f-6749e84f8005 _ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>|
>
> ____u____uid____:c89e98b4-868c-3abf-a683-89071af807c6____ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> *_Categorization:_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>*
>
> 	
>
> _categorization_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> *_Checked:_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>*
>
> 	
>
> _No_ <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
>
>         _B.1.3 tModel Structure_
>         <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(01) <tModel 
> tModelKey="uuid:_c89e98b4-868c-3abf-a683-89071af807c6_a27078e4-fd38-320a-806f-6749e84f8005" 
> >_ <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(02) <name>_ http://www.w3.org/ns/ws-policy/remotepolicyreference__ 
> _http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference</name>_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(03) <description xml:lang="EN">Category system used for UDDI 
> entities to point to an external_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(04) Web Services Policy Attachment policy expression that describes 
> their characteristics._ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(05) See Web Services Policy 1.5 - Attachment specification for 
> further details.</description>_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(06) <categoryBag>_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(07) <keyedReference_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(08) keyName="uddi-org:types:categorization"_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(09) keyValue="categorization"_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(10) tModelKey="uuid:c1acf26d-9672-4404-9d70-39b756e62ab4" />_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(11) </categoryBag>_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _(12) </tModel>_ 
> <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
>
>       _B.2 Web Services Policy Types Category System_
>       <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
>
>         _B.2.1 Design Goals_
>         <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> _This tModel is used to categorize tModels as representing policy 
> expressions. There is only one valid value, namely |"policy"|, that 
> indicates this very fact. It is RECOMMENDED that tModels categorized 
> as representing policy expressions reference no more and no less than 
> this very policy expression using the remote policy reference category 
> system._ <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
>
>         _B.2.2 tModel Definition_
>         <http://schemas.xmlsoap.org/ws/2003/03/remotepolicyreference/>
>
> *_Name:_ <#policy_expression>*
>
> 	
>
> _http://schemas.xmlsoap.org/ws/2003/03/policytypes _ <#policy_expression>
>
> ____h_ttp://www.w3.org/ns/ws-policy/policytypes_____ <#policy_expression>
>
> *_Description:_ <#policy_expression>*
>
> 	
>
> _Web services policy types category system used for UDDI tModels to 
> characterize them as Web services policy–based policy expressions._ 
> <#policy_expression>
>
> *_UDDI Key (V3):_ <#policy_expression>*
>
> 	
>
> |_uddi:schemas.xmlsoap.org:policytypes:2003_03_ <#policy_expression>|
>
> |____uddi:w3c.org:ws-policy:v1.5:attachment:policytypes____ ____ 
> <#policy_expression>|
>
> *_UDDI V1,V2 format key:_ <#policy_expression>*
>
> 	
>
> |_uuid:fa1d77dc-edf0-3a84-a99a-5972e434e993 _ <#policy_expression>|
>
> ____u____u____id____:78003262-1ea8-3ae5-95cb-67cc900b6b59____ 
> <#policy_expression>
>
> *_Categorization:_ <#policy_expression>*
>
> 	
>
> _categorization_ <#policy_expression>
>
> *_Checked:_ <#policy_expression>*
>
> 	
>
> _No_ <#policy_expression>
>
>
>         _B.2.3 tModel Structure_ <#policy_expression>
>
> _(01) <tModel 
> tModelKey="_u__uid__:78003262-1ea8-3ae5-95cb-67cc900b6b59_uuid:fa1d77dc-edf0-3a84-a99a-5972e434e993" 
> >_ <#policy_expression>
>
> _(02) <name>_ 
> http://www.w3.org/ns/ws-policy/policytypes_http://schemas.xmlsoap.org/ws/2003/03/policytypes</name>_ 
> <#policy_expression>
>
> _(03) <description xml:lang="EN">Web Services Policy Types category 
> system used for UDDI tModels_ <#policy_expression>
>
> _(04) to characterize them as Web Services Policy – based policy 
> expressions.</description>_ <#policy_expression>
>
> _(05) <categoryBag>_ <#policy_expression>
>
> _(06) <keyedReference_ <#policy_expression>
>
> _(07) keyName="uddi-org:types:categorization"_ <#policy_expression>
>
> _(08) keyValue="categorization"_ <#policy_expression>
>
> _(09) tModelKey="uuid:c1acf26d-9672-4404-9d70-39b756e62ab4" />_ 
> <#policy_expression>
>
> _(10) </categoryBag>_ <#policy_expression>
>
> _(11) </tModel>_ <#policy_expression>
>
>
>       _B.3 Local Policy Reference Category System_ <#policy_expression>
>
>
>         _B.3.1 Design Goals_ <#policy_expression>
>
> _This tModel is used to attach a policy expression to a UDDI entity by 
> referencing the UDDI entity that represents this policy expression. 
> The local policy reference category system is based on tModelKeys. It 
> is expected that referenced tModels are registered with the same UDDI 
> registry and are categorized as representing policy expressions using 
> the Web services policy types category system._ <#policy_expression>
>
>
>         _B.3.2 tModel Definition_ <#policy_expression>
>
> *_Name:_ <#policy_expression>*
>
> 	
>
> _http://schemas.xmlsoap.org/ws/2003/03/localpolicyreference _ 
> <#policy_expression>
>
> ____http://www.w3.org/ns/ws-policy/localpolicyreference____ 
> <#policy_expression>
>
> *_Description:_ 
> <http://schemas.xmlsoap.org/ws/2003/03/localpolicyreference/>*
>
> 	
>
> _Category system used for UDDI entities to point to a Web services 
> policy policy expression tModel that describes their characteristics. 
> See Web Services Policy 1.5 - Attachment specification for further 
> details._ <http://schemas.xmlsoap.org/ws/2003/03/localpolicyreference/>
>
> *_UDDI Key (V3):_ 
> <http://schemas.xmlsoap.org/ws/2003/03/localpolicyreference/>*
>
> 	
>
> |_uddi:schemas.xmlsoap.org:localpolicyreference:2003_03_ 
> <#policy_expression>|
>
> |____uddi:w3c.org:ws-policy:v1.5:attachment:localpolicyreference____ 
> ____ <#policy_expression>|
>
> *_UDDI V1,V2 format key:_ <#policy_expression>*
>
> 	
>
> |_uuid:a27f7d45-ec90-31f7-a655-efe91433527c_ <#policy_expression>|
>
> ____uuid____:____9e9_bfbe9-2212-3c9c-a170-381e702a9946_____ ____ 
> <#policy_expression>
>
> *_Categorization:_ <#policy_expression>*
>
> 	
>
> _categorization_ <#policy_expression>
>
> *_Checked:_ <#policy_expression>*
>
> 	
>
> _Yes_ <#policy_expression>
>
>
>         _B.3.3 tModel Structure_ <#policy_expression>
>
> _(01) <tModel 
> tModelKey="_u__uid__:9e9bfbe9-2212-3c9c-a170-381e702a9946_uuid:a27f7d45-ec90-31f7-a655-efe91433527c" 
> >_ <#policy_expression>
>
> _(02) 
> <name>http://schemas.xmlsoap.org/ws/2003/03/localpolicyreference</name>_ 
> <#policy_expression>
>
> _(03) <description xml:lang="en">Category system used for UDDI 
> entities to point to a_ <#policy_expression>
>
> _(04) Web Services Policy policy expression tModel that describes 
> their characteristics._ <#policy_expression>
>
> _(05) See Web Services Policy 1.5 - Attachment specification for 
> further details.</description>_ <#policy_expression>
>
> _(06) <categoryBag>_ <#policy_expression>
>
> _(07) <keyedReference_ <#policy_expression>
>
> _(08) keyName="uddi-org:types:categorization"_ <#policy_expression>
>
> _(09) keyValue="categorization"_ <#policy_expression>
>
> _(10) tModelKey="uuid:c1acf26d-9672-4404-9d70-39b756e62aB4" />_ 
> <#policy_expression>
>
> _(11) <keyedReference_ <#policy_expression>
>
> _(12) keyName="uddi-org:types:checked"_ <#policy_expression>
>
> _(13) keyValue="checked"_ <#policy_expression>
>
> _(14) tModelKey="uuid:c1acf26d-9672-4404-9d70-39b756e62aB4" />_ 
> <#policy_expression>
>
> _(15) <keyedReference_ <#policy_expression>
>
> _(16) keyName="uddi-org:entityKeyValues"_ <#policy_expression>
>
> _(17) keyValue="tModelKey"_ <#policy_expression>
>
> _(18) tModelKey="uuid:916b87bf-0756-3919-8eae-97dfa325e5a4" />_ 
> <#policy_expression>
>
> _(19) </categoryBag>_ <#policy_expression>
>
> _(20) </tModel> _ <#policy_expression>
>
>
>     _C. Acknowledgements (Non-Normative)_ <#policy_expression>
>
> _This document is the work of the W3C Web Services Policy Working 
> Group._ <#policy_expression>
>
> _Members of the Working Group are (at the time of writing, and by 
> alphabetical order): Dimitar Angelov (SAP AG), Abbie Barbir (Nortel 
> Networks), Charlton Barreto (Adobe Systems Inc.), Sergey Beryozkin 
> (IONA Technologies, Inc.), Vladislav Bezrukov (SAP AG), Toufic Boubez 
> (Layer 7 Technologies), Symon Chang (BEA Systems, Inc.), Paul Cotton 
> (Microsoft Corporation), Jeffrey Crump (Sonic Software), Glen Daniels 
> (Sonic Software), Jacques Durand (Fujitsu Limited), Ruchith Fernando 
> (WSO2), Christopher Ferris (IBM Corporation), William Henry (IONA 
> Technologies, Inc.), Frederick Hirsch (Nokia), Maryann Hondo (IBM 
> Corporation), Tom Jordahl (Adobe Systems Inc.), Paul Knight (Nortel 
> Networks), Philippe Le Hégaret (W3C/MIT), Mark Little (JBoss Inc.), 
> Ashok Malhotra (Oracle Corporation), Monica Martin (Sun Microsystems, 
> Inc.), Arnaud Meyniel (Axway Software), Jeff Mischkinsky (Oracle 
> Corporation), Dale Moberg (Axway Software), Anthony Nadalin (IBM 
> Corporation), Bob Natale (MITRE Corporation), David Orchard (BEA 
> Systems, Inc.), Fabian Ritzmann (Sun Microsystems, Inc.), Daniel Roth 
> (Microsoft Corporation), Tom Rutt (Fujitsu Limited), Sanka 
> Samaranayake (WSO2), Felix Sasaki (W3C/Keio), Skip Snow (Citigroup), 
> Yakov Sverdlov (CA Inc.), Mark Temple-Raston (Citigroup), Asir 
> Vedamuthu (Microsoft Corporation), Sanjiva Weerawarana (WSO2), Ümit 
> Yalçinalp (SAP AG), Prasad Yendluri (webMethods, Inc.). _ 
> <#policy_expression>
>
> _Previous members of the Working Group were: Jong Lee (BEA Systems, 
> Inc.), Bijan Parsia (University of Manchester), Seumas Soltysik (IONA 
> Technologies, Inc.). _ <http://www.w3.org/2002/ws/policy/>
>
> _The people who have contributed to discussions on 
> public-ws-policy@w3.org are also gratefully acknowledged. ___ __ 
> <http://www.w3.org/2002/ws/policy/>
>
Received on Tuesday, 13 March 2007 01:38:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:48 GMT