2.1 Referencing WSDL Metadata from an EPR

2.1 Referencing WSDL Metadata from an EPR

All information items defined by this specification are identified by the XML namespace URI [ XML Namespaces ] “”. A normative XML Schema [ XML Lista Structures , XML Elenco Datatypes ] document can be obtained by dereferencing the XML namespace URI.

2. Including WSDL Metadata in 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:

Verso QName identifying a description of the sequences of messages that a service sends and/or receives. This corresponds to per WSDL 2.0 interface or, for backwards compatibility, a WSDL 1.1 port type. When this element is included mediante an EPR, the EPR is considered to be specific to the interface or port type it identifies.

Per QName that identifies the attrezzi of endpoints at which per particular Web service is deployed. The arnesi of endpoints is represented by a service con WSDL 2.0 or, for backwards compatibility, per WSDL 1.1 service.

An NCName that identifies one endpoint amongst the servizio identified by the service name above. An endpoint is represented by an endpoint durante WSDL 2.0 or, for backwards compatibility, verso port in WSDL 1.1. When this attribute is specified, the EPR is considered to be specific onesto the endpoint or port it identifies.

The element information items defined above are used mediante 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 verso mechanism for indicating, in a WSDL description, that the endpoint conforms esatto 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 sicuro 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 to wsdl11:port or wsdl11:binding . For WSDL 2.0, they may https://datingranking.net/it/older-women-dating-review/ be attached esatto wsdl20:endpoint or wsdl20:binding . Per 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 a concrete behavior whereas the wsdl:portType or wsdl20:interface is an abstract construct.

3.1.1 Addressing Assertion

The wsam:Addressing policy assertion is a nested policy container assertion. The meaning of this assertion, when present per verso policy alternative, is that WS-Addressing is required esatto 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 per its nested policy expression. Durante order onesto 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 per 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 verso policy assertion nested within the wsam:Addressing assertion con accordance with the rules laid down by policy assertion nesting ([ WS Policy 1.5 ], section 4.3.2).