[ogsa-naming-wg] WS-Names and WS-Addressing WSDL Binding

[David Snelling]

Tom,

A couple of questions for you.

It appears that in the example that either the was:Address and the  
soap:address must be the same or that the wsa:Addess is irrelevant. I  
can't really believe the former so let's assume the later.

With a wsdl11:definitions section present, the wsa:Address field must  
be superseded by the soap:address chosen by the client. I assume that  
the soap:address gets copied to the was:To field in the soap header.  
There is no linkage in the wsdl11:definitions to connect the  
wsa:Address to it.

Q1) What happens with more than one wsdl11:definitions section in the  
was:Metadata?

Q2) In this case can we put any old junk in the wsa:Address? i.e. leave  
it out (except that the scheme saus [1..].

Q3) If we use the wsa:Address as an Abstract Name, how do we know that  
is what we are doing? We could  subtype the EPR to create a WS-Name as  
we do now, and bind the usage of the was:Address to type of the  
WS-Name.

Q4) I thought WS-Addressing was NOT about naming or identity. How will  
this use (abuse) of the wsa:Address go down with the W3C folks?

Thoughts?

On 7 Oct 2005, at 12:41, Maguire_Tom at emc.com wrote:

> This will be a fairly long note to discuss the current incarnation of
> WS-Naming Abstract Names.  An Abstract Name has the following  
> properties:
>
> *	The name MUST be globally unique in both space and time.
> *	The name conforms to URI syntax ("Uniform Resource Identifiers
> (IRI): Generic Syntax", RFC 3987).
>
> Let's leave aside the first point, for the time being, and focus on the
> second point.  The abstract name is an IRI which is an  
> internationalized
> URI.  Currently this means that a WS-Name abstract name would look like
> this:
>
> <wsa:EndpointReference
>     xmlns:wsa="http://www.w3.org/2005/03/addressing"
>     xmlns:name="http://ggf.org/name">
>         <wsa:Address>http://tempuri.org/example</wsa:Address>
>
> <name:AbstractName>urn:guid:B94C4186-0923-4dbb-AD9C-39DFB8B54388</ 
> name:Abstr
> actName>
> </wsa:EndpointReference>
>
> There are several built in assumptions in this particular rendering of  
> an
> abstract name.   First, there is an assumption that the <wsa:Address>  
> is the
> [destination] MAP of the EPR.  Second, the AbstractName does not need  
> to
> flow on the wire when 'dereferencing' this EPR.
>
> It may be ok for the AbstractName to not flow on the wire.  I will  
> leave
> that discussion to others.  Let's focus on the first assumption...
> If you assume that the <wsa:Address> is NOT necessarily a physical  
> address
> (URL) then it is essentially the same as an AbstractName minus the  
> "MUST be
> globally unique in both space and time" property described above.
>
> This is essentially how 'Web Services Addressing 1.0 - WSDL Binding'  
> defines
> a <wsa:Address>.  An example from that specfication:
>
> <wsa:EndpointReference
>     xmlns:wsa="http://www.w3.org/2005/03/addressing">
>   <wsa:Address>http://example.com/fabrikam/acct</wsa:Address>
>   <wsa:Metadata>
>     <wsdl11:definitions targetNamespace="http://example.com/fabrikam"
>         xmlns:fabrikam="http://example.com/fabrikam"
>         xmlns:abc="http://www.abccorp.com/"
>         xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>         xmlns:iiop="http://www.iiop.org/"
>         xmlns:wsdl11="http://schemas.xmlsoap.org/wsdl/">
>       <wsdl11:import namespace="http://example.com/fabrikam"
>           location="http://example.com/fabrikam/fabrikam.wsdl"/>
>       <wsdl11:import namespace="http://www.abccorp.com/"
>           location="http://www.abccorp.com/abc.wsdl"/>
>       <wsdl11:service name="InventoryService">
>         <wsdl11:port name="ep1" binding="abc:soap-http-binding">
>           <soap:address location="http://example.com/fabrikam/acct"/>
>         </wsdl11:port>
>         <wsdl11:port name="ep2" binding="abc:iiop">
>           <iiop:address location="..."/>
>         </wsdl11:port>
>       </wsdl11:service>
>     </wsdl11:definitions>
>   </wsa:Metadata>
> </wsd:EndpointReference>
>
> And also from 'Web Services Addressing 1.0 - WSDL Binding'
>
> 	In particular, embedding a WSDL service component description MAY be
> used by EPR issuers to indicate the presence of alternative addresses  
> and
> protocol bindings to access the referenced endpoint. The alternatives  
> are
> provided by the different endpoints of the embedded service.
>
> It is interesting to note that in the above example that the  
> <wsa:address>
> matches the soap:address location.
> So this says to me that the <wsa:address> is essentially equivalent  
> (or at
> least could be) to an abstract name.
>
> Thoughts?
>
>
> Thanks,
> Tom
>
> Senior Technologist, CTO Office
> EMC²|SMARTS
> 44 South Broadway
> 7th Floor
> White Plains, NY 10601
> Office: +1-914-508-3477
> Mobile: +1-845-729-4806
> Email: maguire_tom at emc.com <mailto:maguire_tom at emc.com>
>
> If you want to build a ship, don't drum up people to collect wood and  
> don't
> assign them tasks and work, but rather teach them to long for the  
> endless
> immensity of the sea.
>
> Antoine de Saint-Exupery
>
>
-- 

Take care:

     Dr. David Snelling < David . Snelling . UK . Fujitsu . com >
     Fujitsu Laboratories of Europe
     Hayes Park Central
     Hayes End Road
     Hayes, Middlesex  UB4 8FE

     +44-208-606-4649 (Office)
     +44-208-606-4539 (Fax)
     +44-7768-807526  (Mobile)