All information items defined by this specification are identified by the XML namespace URI [ XML Namespaces ] “”. Per normative XML Precisazione [ XML Lista Structures , XML Precisazione Datatypes ] document can be obtained by dereferencing the XML namespace URI.
2. Including WSDL Metadata sopra EPRs
The WSDL binding of Web Services Addressing introduces the following element and attribute information items for referencing WSDL metadata from an EPR’s metadata section:
A QName identifying verso description of the sequences of messages that per service sends and/or receives. This corresponds puro verso WSDL 2.0 interface or, for backwards compatibility, per WSDL 1.1 port type. When this https://datingranking.net/it/scruff-review/ element is included con an EPR, the EPR is considered to be specific puro the interface or port type it identifies.
Per QName that identifies the serie of endpoints at which verso particular Web service is deployed. The servizio of endpoints is represented by per service per WSDL 2.0 or, for backwards compatibility, a WSDL 1.1 service.
An NCName that identifies one endpoint amongst the batteria identified by the service name above. An endpoint is represented by an endpoint in WSDL 2.0 or, for backwards compatibility, verso port mediante WSDL 1.1. When this attribute is specified, the EPR is considered onesto be specific onesto the endpoint or port it identifies.
The element information items defined above are used sopra an EPR’s metadata section. The following shows an example endpoint reference. This references the interface named “ghns:reservationInterface” at the endpoint IRI “”. Note the use of the WSDL[ WSDL 2.0 ] wsdlLocation attribute.
3. Indicating Use of WS-Addressing
This specification supports a mechanism for indicating, in a WSDL description, that the endpoint conforms to the WS-Addressing specification. That mechanism uses WS-Policy Framework [ WS Policy 1.5 ].
3.1 WS-Policy Assertions
The mechanism for indicating that a binding or endpoint conforms to the WS-Addressing specification is through the use of the Web Services Policy – Framework [ WS Policy 1.5 ] and Web Services Policy – Attachment [ WS Policy 1.5 – Attachment ] specifications. This specification defines three policy assertions.
For WSDL 1.1, these assertions may be attached puro wsdl11:port or wsdl11:binding . For WSDL 2.0, they may be attached to wsdl20:endpoint or wsdl20:binding . Verso policy expression containing the wsam:Addressing policy assertion MUST NOT be attached onesto verso wsdl:portType or wsdl20:interface . The wsam:Addressing policy assertion specifies verso concrete behavior whereas the wsdl:portType or wsdl20:interface is an abstract construct.
3.1.1 Addressing Assertion
The wsam:Addressing policy assertion is verso nested policy container assertion. The meaning of this assertion, when present per verso policy alternative, is that WS-Addressing is required sicuro communicate with the subject. The wsam:Addressing assertion indicates that there are per niente restrictions on the use of WS-Addressing unless otherwise qualified by assertions durante its nested policy expression. Durante order to indicate that the subject supports WS-Addressing but does not require its use, an additional policy alternative should be provided which does not contain this assertion; the compact authoring style for an optional policy assertion provided by WS-Policy V1.5 [ WS Policy 1.5 ] may be used. The wsp:Optional attribute, as verso syntactic shortcut, can be used with the wsam:Addressing assertion. This indicates two policy alternatives, one which contains the policy assertion, and another which does not.
The inclusion of this assertion implies support for the Web Services Addressing 1.0 – Core [ WS-Addressing Core ] and Web Services Addressing 1.0 – SOAP Binding [ WS-Addressing SOAP Binding ].
3.1.2 AnonymousResponses Assertion
The wsam:AnonymousResponses element MAY be used as per policy assertion nested within the wsam:Addressing assertion durante accordance with the rules laid down by policy assertion nesting ([ WS Policy 1.5 ], section 4.3.2).