I have never looked on XBRL, FIX or LDAP as alternatives specifically
to Web Services. They have much more tightly defined roles and are
not normally viewed as competition to each other or to Web Services.
For example, anyone building a financial trading system will almost
certainly support FIX. This does not mean that they will not
consider using WS or LDAP in their systems somewhere or other
(although for the crucial high-volume, time-critical requirements
right at the core of their systems I doubt they would use WS).
Likewise an XBRL-based reporting system might well use WS to
communicate with other application modules.
As various members of this Group have pointed out many times, SOA
does not necessarily have to be done using WS. Likewise just because
someone implements a WS-based system does not automatically qualify
it as a SOA structure. SOA and its principles precede WS by many
years. What WS has done for SOA is to:
(a) Raise its profile as a strategic architecture to a high level of
recognition
(b) Provide a means, even if only partial, of implementing it which
is ostensibly supported by all the significant vendors
In turn I think SOA has given WS a serious raison d'ĂȘtre at the
strategic architectural level. If you doubt this, in the early days
of WS, when people questioned its purpose or role, this invited such
responses as "it is Microsoft's attempt to take over the middleware
market by redefining it" or "it helps to sell J2EE and EJB/.NET".
Gervas
--- In [email protected], Jerry Zhu <
[EMAIL PROTECTED]> wrote:
>
> Gervas,
>
> Yes, we can use standards and technologies other than
> Web services standards for specific needs. Such as
> Extensible Business Reporting Language for filing
> reports with the SEC; Financial Information eXchange
> Markup Language for exchanging trading instructions
> among financial services organization; Lightweight
> Directory Access Protocal for registering and finding
> resources etc, etc..
>
> You are absolutely right, the key element SOA has and
> the preceding SW architectures do not have is the Web
> Services. Key elements of Web Services standards
> include: XML/XML Schema, SOAP/HTTP, WSDL, UDDI etc.
> Of cause, we can use other standards and technologies
> to define Web Services Platforms.
>
> Jerry
>
> --- Gervas Douglas <[EMAIL PROTECTED]> wrote:
>
> > Jerry,
> >
> > Just because the choices (SGML or HTML if not XML)
> > you have mentioned
> > might be useful choices does not logically exclude
> > all other
> > alternatives any more than the assumption that SOA
> > has to be based on Web Services.
> >
> > Gervas
> >
> > --- In
> > [email protected],
> > Jerry Zhu <
> > jerryyz@> wrote:
> > >
> > >
> > >
> > > --- Gregg Wonderly <gergg@> wrote:
> > >
> > > > I don't believe there is anything in the term
> > > > "Enterprise Service Bus" that says
> > > > XML. Maybe some people want to use it that way,
> > but
> > > > I think that's a short sited view.
> > > >
> > > > Anything that your SOA uses for transfering data
> > > > between services and clients is part of your
> > ESB.
> > >
> > > Maybe SGML or HTML if not XML. I don't think it
> > can
> > > be binary data to achieve service description and
> > > service choregraphy. If one says that it is
> > possible
> > > to implement polymorphism using assembly language,
> > I
> > > won't argue.
> > >
> > > Jerry
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam? Yahoo! Mail has the best spam
> > protection around
> > > http://mail.yahoo.com
> > >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
