On mySimon: Holiday Gifts For Mom And Dad
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 6 of 9:
Next »
« Previous
Interoperability Seems to Remain Elusive
"As a result, while the XML schema instance describing the service seems to describe an XML element, what is actually presented is a (.NET+XML) service or a (Java +XML) service--a hybrid containing information that ties the service to its originating platform, which can create costly interoperability issues."

While this sort of thing is not encouraging, (XML and Schema are suppose to supply a common carrier understood unambiguously by any back-end programming system), maybe it is a minor 'fly in the ointment', a political football that just will not go away.( C# <--/--> Java.) Makes for a niche market for companies willing to serve as translators and 'referees'.

In the big picture, interoperability problems may be over emphasized. There are many interesting XML applications that have evolved based on centralized models that use well defined and unambiguous XML types that are not susceptible to interoperability issues.
Posted by: Peter Komisar   Posted on: 03/07/05 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

Next Generation?  Roger Ramjet | 03/07/05
Complexity inherent in XML  jorwell | 03/07/05
A small but important correction  jorwell | 03/07/05
Deja Vu All Over Again  psomerset@... | 03/07/05
It's more than that  seosamh_z | 03/07/05
Interoperability Seems to Remain Elusive  Peter Komisar | 03/07/05
You have a valid point.  htotten | 03/07/05
Interop is getting there  seosamh_z | 03/07/05
Great discussion!  glebleu | 03/08/05

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

Meet Doc