4045 2006-12-08 14:04:56 +0000 scoping of wsdl1.1 identifiers spec 2007-03-07 18:54:37 +0000 1 1 1 Unclassified WS-Policy WSDL1.1-Element-Identifiers FPWD PC All RESOLVED FIXED P2 normal --- 1 chrisfer chrisfer public-ws-policy-qa oldest_to_newest 13095 0 chrisfer 2006-12-08 14:04:56 +0000 I believe that it would be most appropriate if the WG scoped its work on the WSDL1.1 element identifiers working group note to the specific set of WSDL1.1 policy attachment points defined in the WS-Policy 1.5 - Attachments specification. Going further than that would IMO be of marginal value to the WG and would potentially add to the amount of effort needed to complete the work. Our primary concern is with using these identifiers in the context of policy attachments. 13668 1 orchard 2007-01-17 19:02:22 +0000 I'll note that I think the same problem applies to WSDL 2.0, that is there are components that have designators that are not policy subjects listed in the attachments doc. How about the following new paragraph for 3.4.1: The scope of URI domain expressions for WSDL 2.0 components or WSDL 1.1 elements is limited to the subjects defined in this specification at (ref to Attaching Policies Using WSDL 1.1 and WS-Policy Attachment for WSDL 2.0). (note, what happens if somebody puts a URI with an out-of-scope subject, does it fail) 13672 2 orchard 2007-01-17 19:32:38 +0000 Combining 4045 with 4127 with Editors action 112 (http://www.w3.org/2005/06/tracker/wspolicyeds/actions/112) ( add WSDL 1.1 reference) could yield: URI domain expressions are used to identify resources that are identified using IRI or IRI References (such as endpoint, message or operation definitions) with which policies can be associated. For example, URI domain expressions can be used to identify WSDL 1.1 definitions, WSDL 2.0 components, etc. When a URI domain expression identifies multiple resources, ie WSDL 1.1 supports multiple operations with the same name (sometimes called operation name overloading), the Policy applies to all the resources that are identified. IRI References for WSDL 2.0 components are defined in Appendix C of the Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language [WSDL 2.0 Core Language]. The following example illustrates the use of URI domain expression with a WSDL 2.0 IRI Reference: (01) <wsp:PolicyAttachment> (02) <wsp:AppliesTo> (03) <wsp:URI>http://example.org/TicketAgent.wsdl20#wsdl.endpoint(TicketAgentService/Endpoint)</wsp:URI> (04) </wsp:AppliesTo> (05) <wsp:PolicyReference URI="http://www.example.com/policies#RmPolicy" /> (06) </wsp:PolicyAttachment> In this example, the policy expression at http://www.example.com/policies#RmPolicy applies to all interactions with the endpoint at http://example.org/TicketAgent.wsdl20#wsdl.endpoint(TicketAgentService/Endpoint). IRI References for WSDL 1.1 elements are defined in WSDL 1.1 Element Identifiers [ref]. The scope of URI domain expressions for WSDL 2.0 components or WSDL 1.1 elements is limited to the subjects defined in this specification at (ref to Attaching Policies Using WSDL 1.1 and WS-Policy Attachment for WSDL 2.0). 13677 3 Paul.Cotton 2007-01-17 22:27:01 +0000 In addition Change the Section 4 as follows: This section describes a mechanism for associating policy expressions with Web service constructs in WSDL 1.1. The mechanism consists of: - A model for attaching policies to WSDL 1.1 constructs. The model defines: - A partitioning of WSDL constructs into service, endpoint, operation and message policy subjects. - The semantics of attaching a policy to each policy subject. - How to combine policies attached to more than one WSDL construct within a single policy subject. - An XML representation of policy expressions attached to WSDL 1.1 constructs. - The annotation of such policy expressions as required extensions using the WSDL-defined extensibility flag @wsdl:required. <fix above sentence is the WSDL 2.0 section> WSDL 1.1 disallows the use of extensibility elements on certain elements and the use of extensibility attributes on others. However, the WS-I Basic Profile 1.1 [BP 1.1] overrules this restriction and allows element extensibility everywhere. Therefore, when attaching a reference directly to the WSDL element the policy reference SHOULD be attached using wsp:PolicyReference as child element unless it is absolutely necessary to maintain the original WSDL 1.1 restriction, in which case the @wsp:PolicyURIs attribute MAY be used for the following WSDL elements: wsdl11:portType wsdl11:portType/wsdl11:operation/wsdl11:input wsdl11:portType/wsdl11:operation/wsdl11:output wsdl11:portType/wsdl11:operation/wsdl11:fault /paulc 13678 4 chrisfer 2007-01-17 22:52:10 +0000 See http://www.w3.org/2007/01/17-ws-policy-irc#T22-50-02 RESOLUTION: Close 4045 and 4127 closed with text as provided in http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c2 and http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c3 respectively 14344 5 chrisfer 2007-03-07 18:54:37 +0000 Note that the resolution to 4332 reverses part of this decision. http://www.w3.org/Bugs/Public/show_bug.cgi?id=4332