SourceForge : Post

Project: OGSA-WG Discussion > Architecture Notes > Policy regarding EPRs, WS-Names, etc. > List of Posts

Forum Topic - Policy regarding EPRs, WS-Names, etc.: (2 Items)

View: as

12/16/2005 4:11 AM

post5618

Policy regarding EPRs, WS-Names, etc.

- An OGSA compliant service when returning a reference MUST use a WS-Addressing EndpointReference (EPR).

- An OGSA compliant service MAY return a profiled usage of a WS-Addressing EndpointReference (EPR).

- An OGSA compliant service SHOULD return a WS-Naming profiled WS-Addressing EndpointReference (EPR) where appropriate.

- An OGSA compliant service MUST NOT require that a specific profiled usage of a WS-Addressing EndpointReference (EPR) 
be returned.

Therefore an OGSA compliant service MUST NOT require that a WS-Naming profiled WS-Addressing EndpointReference (EPR) be 
returned.

Andreas Savva

12/16/2005 4:14 AM

post5619

Rationale for policy statement

The reasoning for this is quite simple.  The architectural construct for OGSA is a WS-Addressing EndpointReference.  WS-
Naming presupposes a particular client interaction.  Clients may or may not use this particular interaction style (
equivalence checking).  In particular, placing the requirement that all implementations of a particular portType must 
return a WS-Naming profiled EPR may be onerous, especially considering that the interaction being fulfilled by the 
service might never be exercised by the consumer.  In general, OGSA would be better served if clients that required such
 profiled use selected only services that can provide that information. This area, metadata discovery and exchange, is 
something that OGSA should be
addressing.

[From Tom Maguire's post to the list]

Return