- From: Francisco Curbera <curbera@us.ibm.com>
- Date: Thu, 9 Dec 2004 10:01:30 -0500
- To: "Srinivas, Davanum M" <Davanum.Srinivas@ca.com>
- Cc: public-ws-addressing@w3.org, public-ws-addressing-request@w3.org
So I think by now everyone agrees on this: when the address or reference
props. are different then:
- the metadata may or may not be different,
- they EPRs may or may not "point to/reference" different
entities/endpoints/resources/thingies/whatever.
That is, out of a negative byte by byte comparison you cannot infer
anything at all (so you may be better off retrieving fresh copy of the
metadata, for example.) I think we should at least make this crystal clear
in the spec, since it has taken a bunch of smart guys like us a while to
figure it out.
If after this realization the group still wants to call EPRs identifiers
then need to understand we will be endorsing a very ad-hoc notion of
"identifier". This would be a gross mistake IMO: attaching new meaning to
concepts already in use, can only result in confusion - of the general
public as well much as the TAG itself.
Paco
"Srinivas, Davanum M"
<Davanum.Srinivas@ca.com To: <public-ws-addressing@w3.org>
> cc:
Sent by: Subject: Are EPRs identifiers?
public-ws-addressing-req
uest@w3.org
12/08/2004 08:24 PM
End of call today I raised this and someone said, oh we are not discussing
MetadataExchange….
I asked this question since we used WSRF's use of WS-Addressing as a
reference data point, let's use WS-MetadataExchange for another data
point….
Question: I have 2 EPR's, both differ only by a RefProperty, If i use say
MetadataExchange, will i get the same WSDL?
If the answer was "yes, it might be different. E.G. different policies."
it then implies that EPR is an identifier!!!
Thanks,
dims
Davanum Srinivas
Computer Associates
Senior Architect, Web Services Group
Tel: +1 508 628 8251
davanum.srinivas@ca.com
http://ws.apache.org/~dims/
Received on Thursday, 9 December 2004 15:02:04 UTC