On Mon, 26 Apr 2004, David Forslund wrote:
> At 03:48 PM 4/26/2004, Andrew Ho wrote:
> > "General interfacing" must to be evaluated by cost and performance of
> >specific interface implementations. Somehow and somewhere, the general
> >interface must be customized to fit specific use-case requirements.
> >
> > Is it possible that previous interfacing efforts have failed because
> >they have tried to be too general?
>
> I'm not sure what you mean by "general interfacing" vs "specific
> interface implementations". XML-RPC is about as general as it gets with
> no structure except that imposed by the XML.
Dave,
The concept of "general interface" was raised by Tim Churches. XML-RPC
is quite general but hxp provides very specific interface to concepts in
healthcare information systems. Tim pointed out that hxp may fail as a
"general" inter-connect solution.
Aren't the concepts that HXP has an interface for already defined by others?
Why not simply use those concepts in HXP and use XML-RPC (or whatever)
to move those "concepts" around
...
> Adopting XML-RPC is not going to lead to wide adoption, also in my
> opinion.
This question is subject to empirical testing. :-)
Of course, that is why I said that it is was in my opinion. The big question
is what you add to XML-RPC. XML-RPC was bypassed by much of industry
in its movement to SOAP/WSDL. This, I believe, was to get a handle on
what it is that is going to be send over the RPC call in a standard way.
It would be best if we reliably invent the right technology at the right
time. Since this is often not possible, the second best thing is to keep
trying different technologies until something works.
Unfortunately, today, there are too many technologies to try for this
to be successful (except in the lottery sense). We must be smarter than
simply trying different technologies until we find one that works. I've never
understood what is the "right time". I don't think anyone does.
Dave
Best regards,
Andrew
---
Andrew P. Ho, M.D.
OIO: Open Infrastructure for Outcomes
www.TxOutcome.Org
