[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Competing Specifications - A Good or Bad Thing?


competing good or bad
I have a theory on the subject of "competing specifications" that I'd
like to present, in hopes of getting some good feedback. I'm thinking
mostly in terms of Web Services specifications - or specifications that
are not intended strictly for Web Services by nature, but have
applicability to Web Services. 

By "competing", I mean 2 or more specifications that cover the same
"functional area" (e.g. reliable messaging, context, transactions, etc.)
and most/all of the same general actions that are applicable to that
functional area (e.g. for reliable messaging, "notify a sender reliable
messaging processor that a message was received out-of-order"). Some
examples of such overlapping specifications (both "open" and emerging)
would be:

* Reliable Messaging: OASIS WS-Reliability, WS-ReliableMessaging
* Transaction/Coordination: WS-Transaction (WS-AT and WS-BA), OASIS
WS-CAF
* Identity Management: Liberty Alliance, OASIS SAML 2.0

My theory: Competing specifications are not necessarily a bad thing, as
long as:

(1) The cost to an organization to interoperate with another
organization (or another system within the organization) that implements
a competing specification in a given functional area is either minimal
or 0, and 
(2) The risk is either minimal or 0

One case in which the risk would (in my opinion) be more than minimal,
and possibly quite high, would be in reliable messaging: WS-Reliability,
for example, considers a message ID to be a unique combination of [a
Group ID + a Sequence ID]; if an organization that implemented
WS-Reliability were, for example, to interoperate with an organization
that implemented a reliable messaging standard that did not group
message IDs together (but instead used unique message IDs for each
message), a middle process would be required to pack/unpack groups of
messages between the installations as required. If this "translation"
were to be faulty (due to a software or configuration bug), the whole
messaging interaction could be - pardon the pun - unreliable.

Thoughts? Comments?
-- 
Kind Regards,
Joseph Chiusano
Associate
Booz | Allen | Hamilton

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.