Lists Home |
Date Index |
> 3/11/2002 3:22:56 AM, Mozhgan Moussavi
> <Mozhgan.Moussavi@tribon.com> wrote:
> >I'm wondering if anybody perhaps could help me to make right
> decision, i.e.
> >choose the right
> >standard for the company's messaging system. Which aspects are most
> >important to take into considerations?
What are the business drivers? If there is not a clear business driver to
support one or the other standard, maybe you shouldn't be trying to
standardize on any of them right now.
> From: Mike Champion [mailto:firstname.lastname@example.org]
> Another consideration is the technological sophistication of the IT
> people at the company. If they are capable of building the messaging
> infrastructure themselves using "raw" Web and XML technologies,
> many possibilities are available. If they need an "out of the box"
> solution, the choice will (for the time being) come down to
> finding the least limiting of the unappealing alternatives, at
> least for now, or unless they have extremely generic needs.
You also need to consider the IT people at the companies with which you will
be integrating (if that is the goal, here). Are you simply raising the bar
for them by adopting one of these standards, or are you facilitating
integrations? Many IT departments are still new to XML messaging and have
not yet achieved a very high degree of sophistication with XML and related
> Another consideration is whether the industry the company is in has a
> reasonably mature data exchange standard. As I understand it,
> the electronics industry has RosettaNet and would be a fairly obvious
> choice; on the other hand, the financial industry has a great
> variety of more or less competing "standards" and deciding on one
> depends on a lot of detailed knowledge of the particular nich the
> company is in, who it exchanges messages with, etc.
> Of course, the most important consideration is that you have
> skill in fortunetelling to predict which standards will ultimately
> predominate! And not to mention that it takes advanced training in
> anthropology, political science, group psychology, AND business
> AND technology to make any sense out of how all the various standards
> effort you mention compete and/or complement one another <grin>
All excellent points. And I think if there is not a clear compelling
business reason to support a particular standard (such as being in an
industry with a broadly supported data exchange standard), then keeping your
options open for the future may be wiser than rushing to standardize on one
of these standards. All of these standards share certain things in common,
though, so moving toward deploying a flexible enabling infrastructure for
XML messaging (if you haven't already) can help keep your options open for
the future while providing something useful for the short term.