OASIS Open

Oracle

Agree a form of EPR comparison

We can always define a restrictive criteria for comparison and state it in a positive way (the comparison criteria will tell you whether two EPRs are the same, not whether they are different). I.e., if certain conditions match then you know that two EPRs are the same. There may be additional out of band information that lets one conclude that two EPRs that are different per our comparison rules are in fact the same. An analogous example is: my employee ID and SS# both point to the same person, but a general comparison algorithm is not going to take that into account.

Furthermore, this only has an impact on an optimization, if the algorithm is overly restrictive then it is not a problem (just send additional messages instead of piggybacking). My fear is that implementations would just compare the value of wsa:Address to figure out piggy-backing.

Since this is not an STV, I cannot state my second preference which is "Add an explicit warning about this to our text".