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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

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

Subject: Re: FW: Proposal: A Registry Browser GUI tool

Message text written by Martin W Sachs/Watson/IBM
I'm not sure I agree with your first paragraph.  If UDDI had not specified
a particular binding (SOAP messages), there would be the potential for
interoperability nightmares if each registry operator were to pick a
different binding.  I think you actually say this in your second paragraph
("the spec still needs to say what is the required binding for
interoperability") but while a standard cannot prevent someone from using a
proprietary binding, it shouldn't encourage it.


Thanks for being a beacon of light here.  The key is to ensure
AND also ensuring we do not re-invent the wheel.

I have been looking at WebDav DASL for RegRep exactly because it
is already available, it is simple, it includes a neutral query syntax, it 
includes an error protocol and it is widely deployed on WinXX and UNIX.

However - having said all that - I'm also focusing on the Query/Response
payload (that which actually gets the job done) as being very neutral too.
So if you did want to send these Querey/Response pairs over some
other protocol - then that would be emminently doable.   MQ-Series 
would be an obvious one for IBM foreinstance.

Never forget it was IBM that emulated TCP/IP over SNA, which is like
putting a RollsRoyce engine in a VW Beetle.

What it demonstrates though is that if you build simple it can be
deployed and interfaced everywhere.


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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC