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

[Maguire_Tom at emc.com]

Mark, 
I'm going to chime in on a few points you make...

Your question number 3...

3) wsa:address identifies a resource, it has a IRI, but is that the same
thing that the AbstractName is meant to identify?

The suggestion that I was making is that the wsa:address CAN be the abstract
name.  Especially given that in the presence of wsdl port bindings there is
no need for it to be the URL (and I mean Locator here) of the resource.  I
expect that the WS Addressing WSDL Binding will address this issue.  Think
of the wsa:address as a 'logical' address.

Your statement 4...

4) A WSRF WS-Resource has this concept of being composed of two things, a
Web Service and a resource -
http://docs.oasis-open.org/wsrf/wsrf-ws_resource-1.2-spec-pr-02.pdf
(personally I prefer to thing of a WS-Resource as a single thing)- so is the
AbstractName ment to identify the resource or the Web Service. (Of course
according to W3C Web Services Architecture the Web service is a resource as
well)

I prefer to think of a WS-Resource as a Resource that happens to have a Web
Service interface.  And yes the AbstractName is meant to identify the
resource which is why I want to use the <wsa:address> (IRI) for that.

Your question 5....

5) A scenario from RealityGrid (http://www.realitygrid.org)- I am working in
collaboration with others, I have a job running on resource provider A's
machine, the job has an EPR and the A gives it an AbstractName, I migrate
the job to another machine provided by B, it has a new EPR and B gives it a
different AbstractName. This is not what I want - I want the job to have the
same AbstractName
after I migrate it so that my fellow collaborators can find it. Can a client
add an AbstractName to an EPR, or is only the EPR minter allowed to do that?

The AbstractName is immutable (based on the rules defined thus far).  Btw, I
don't think this is a problem if you view the <wsa:address> (IRI) as logical
and the addresses (protocol bound) as the wsdl port binding addresses which
is what (I believe) the WS-Addressing WSDL Binding will contemplate.  

Your question 6... 

6) Can I use the AbstractName to identify a particular conversation I am
having with a Web service?

I guess you could but I would use reference parameters for this..... 

Tom