OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [uddi-spec-comment] Public Comment

Hello Ben,

Thanks for your question.
You are right that the use of a UDDI V2 hostingRedirector does not conform to the WS-I Basic Profile 1.0.

As far as UDDI V3 in general is concerned, there is no conformance to any WS-I Profile since WS-I has not chartered a Working Group to cover UDDI V3, yet. It is certainly conceivable that this will be covered in the future, especially when considering the planned ratification of UDDI V3 as an OASIS Open Standard.

As far as the hostingRedirector in particular is concerned, the reason why this is disallowed in UDDI V2 by the Basic Profile 1.0 is mainly its incompatibility with the "Using WSDL in a UDDI Registry, Version 1.08" Best Practice, which has been published by the OASIS UDDI TC. This Best Practice requires that "A bindingTemplate is created for each service access endpoint. The network address of the
access point is encoded in the accessPoint element."

Thus, from my point of view, I would assume that the hostingRedirector would still be disallowed in a WS-I profile that adopts UDDI V3 as one of its base specification.

Best regards,
 Claus von Riegen, SAP AG

-----Original Message-----
From: comment-form@oasis-open.org [mailto:comment-form@oasis-open.org] 
Sent: Friday, May 14, 2004 9:06 PM
To: uddi-spec-comment@lists.oasis-open.org
Subject: [uddi-spec-comment] Public Comment

Comment from: ben.bloch@systinet.com


I hope this is the right place to send the mail.  If not, I apopologize.  The UDDI dev and spec mailing lists kicked me back.  I am an OASIS memmber but am not on UDDI TC.

In any event, here is my question:
Iam trying to figure out whether the use of hostingDirector in UDDI V3 is compliant with Ws-I Basic Profile 1.0.

R3100 of Ws-I Basic Profile basically the prohibits the use of hostingRedirector in V2 because it is used instead of accessPoint:


REGDATA of type uddi:bindingTemplate representing a conformant INSTANCE MUST contain the uddi:accessPoint element."

However, because V3 makes hostingRedirector a valid useType for an accessPoint rather than an OPTION  to accessPoint, it is not "explicitly" in violation of BasicProfile.  V3 hostingRedirector still seems to violate the spirit of it however which is that  "the network address of the instance be directly specified."

Overall, I am putting together whether some Best Practices and see the use of hostingRedirector and Ws-I compliance in potential conflict.

Anyone know if V3 hostingRedirector violates Ws-I BasicProfile or have an opinion?  Or if in conflict, who trumps whom, from a Best Practices perspective. Or any thoughts on Best Practices in this area?  

The use case is primarily one of trust and how to allow requests from Client X to Service Y while X may not be trusted by Y but is trusted by intermediary Z  who is in turn trusted by Y.   X can leverage Z (who trusts X) to provide access to Y (who trusts Z).

Thanks in advance. Any comments appreciated.




Ben Bloch

To unsubscribe from this list, send a post to uddi-spec-comment-unsubscribe@lists.oasis-open.org, or visit http://www.oasis-open.org/mlmanage/.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]