>** I WOULD GREATLY APPRECIATE YOUR DIRECT COMMENTS on this question,
or links to further research! COARSE OR FINE, guys. What is the
answer. What are the reasons?
Black and white are not useful colours to obtain the whole picture - you need
something in between to convey detail. Think on the following scenarios:
1) Thin documents, where most of the information is "pre-agreed" and only changes are
transmitted
2) Fat RPC, where you try to activate as many processes as possible in a single
transmission
3) Using SOAP to manage the interchange of thin documents
4) Moving intelligence from the server to the client using XSLT and related techniques
(not Java)
>Question: what XML standard should these hundreds of dotcoms adopt,
considering their own self interest, to establish interoperability
between and among themselves?
No XML "standard" (except the "XML standard") will ever meet all the needs of all
users. First define the needs of the specific business process you want to undertake.
Then identify how the process can be modularized. Then look for the closest existing
matching structure to your needs. Then be prepared to extend/restrict your use of that
to meet the needs of the trading partners you need to interoperate with.
>Is it even possible, today, for BSPs to pursue interoperability?
Individual BSPs can interoperate today using tools/mehtodologies of the type you list,
but a generalized mechnaism will have to await the outcome of the ebXML initiative.
Martin Bryan
==========================================
XML/EDI Group members-only discussion list
Homepage = http://www.xmledi.org
Brought to you by: Online Technologies Corporation
Home of BizServe - www.bizserve.com
TO UNSUBSCRIBE: Send email to <[EMAIL PROTECTED]>
Leave the subject blank, and
In the body of the message, enter ONLY: unsubscribe
Questions/requests should be sent to: [EMAIL PROTECTED]
To join the XML/EDI Group complete the form located at:
http://www.geocities.com/WallStreet/Floor/5815/mail1.htm
