|
Expertise
Research
|
Web Services Easily
the most analyzed and misunderstood of the tools in the SOA
kit is the Web Services set of standards and techniques. In
the interest of clarity, OpenWare Technologies suggests that
RPC patterns should be avoided and document-centric,
loosely-coupled patterns should be enforced. The
development of loosely-coupled web services is a challenge
that OpenWare Technologies has successfully achieved time
and again in multiple verticals and environments. If you're
not viewing the Web Services standards in their entirety,
you'll create brittle components that result in unmanageable
service invocations. Take a moment and observe the Web
Services standards family provided by CBDI at
http://roadmap.cbdiforum.com/reports/protocols/summary.php
|
Protocol or Initiative
|
Domain
|
Description
|
Standards or Admin Body
|
Initially Proposed by
|
Current Status
|
|
SOAP
|
Messaging
|
Simple
Object Access Protocol
Provides the definition of the XML-based
information which can be used for exchanging
structured and typed information between peers
in a decentralized, distributed environment.
Part of W3C XML Protocol Group.
|
W3C
|
DevelopMentor,
IBM, Microsoft, Lotus, UserLand Software
|
Version
1.2 Recommendation
|
|
UDDI
|
Metadata
|
Universal
Description, Discovery, and Integration
Defines a SOAP-based Web service for locating
WSDL-formatted protocol descriptions of Web
services. UDDI provides a foundation for
developers and administrators to readily share
information about internal Web services across
the enterprise and public Web services across
the Internet.
|
OASIS
|
Ariba,
IBM, Microsoft
|
V2
- OASIS Standard, V3 - OASIS Committee Draft
|
|
WS-Addressing
|
Messaging
|
This
specification enables messaging systems to
support message transmission in a
transport-neutral manner through networks that
include processing nodes such as endpoint
managers, firewalls, and gateways. Previously
known as WS-Routing, WS-Referral and SOAP
Routing Protocol (SOAP-RP).
|
Submitted
to W3C
|
BEA,
IBM, Microsoft, TIBCO (now joined by Sun)
|
Specification
published
|
|
WS-AtomicTransaction
|
Transactions
|
This
specification provides the definition of the
atomic transaction coordination type that is
to be used with the extensible coordination
framework described in the WS-Coordination
specification. The specification defines three
specific agreement coordination protocols for
the atomic transaction coordination type:
completion, volatile two-phase commit, and
durable two-phase commit. Developers can use
any or all of these protocols when building
applications that require consistent agreement
on the outcome of short-lived distributed
activities that have all-or-nothing semantics.
WS-AtomicTransaction replaces Part I of the
WS-Transaction
|
|
BEA,
Microsoft, IBM
|
Specification
published
|
|
WS-Attachments
|
Messaging
|
Superseded
by SOAP MTOM
|
|
|
Superseded
|
|
WSBPEL
|
Business
Process
|
Business
Process Execution Language
The purpose of the BPEL TC is to continue work
on the business process language published in
BPEL4WS
|
OASIS
|
BEA,
IBM, Microsoft, others
|
TC
formed
|
|
WS-CAF
|
Transactions
|
WS
Composite Application Framework
Proposes standard, interoperable mechanisms
for managing shared context and ensuring
business processes achieve predictable results
and recovery from failure.
WS-CAF is divided into three parts:
- Web
Service Context (WS-CTX), a lightweight
framework for simple context management
- Web
Service Coordination Framework (WS-CF), a
sharable mechanism to manage context
augmentation and lifecycle, and guarantee
message delivery
- Web
Services Transaction Management (WS-TXM),
comprising three distinct protocols for
interoperability across multiple
transaction managers and supporting
multiple transaction models (two phase
commit, long running actions, and business
process flows)
|
OASIS
|
Arjuna
Technologies, Fujitsu, IONA, Oracle, Sun
|
TC
formed
WS-Context is committee Draft
|
|
WS-CF
|
Transactions
|
WS
Coordination Framework
Defines a software agent to handle context
management. Web services in a composite
application register with a coordinator to
ensure messages and results are correctly
communicated and allow, e.g. the success or
failure of an individual service to be tied to
the success or failure of the larger unit of
work comprising multiple Web services.. See
WS-CAF
|
|
|
|
|
WS-Choreography
|
Business
Process
|
Working
Group created to address the ability to
compose and describe the relationships between
Web services.
|
W3C
|
Various
inc., EDS, HP, Oracle, Sun, Tibco
|
Working
Group formed
|
|
WS-CDL
|
Business
Process
|
Web
Services Choreography Description Language
Describes peer-to-peer collaborations of
parties by defining, from a global viewpoint,
their common and complementary observable
behavior; where ordered message exchanges
result in accomplishing a common business
goal.
See WS-Choreography
|
W3C
|
Commerce
One, Oracle, Novell
|
Working
draft published
|
|
WS-Coordination
|
Transactions
|
Describes
an extensible framework for providing
protocols that coordinate the actions of
distributed applications. See also
WS-AtomicTransaction
|
Not
yet submitted
|
BEA,
IBM, Microsoft
|
Specification
published
|
|
WS-CTX
|
Transactions
|
WS
Context
Provides an open, common, interoperable
runtime mechanism to manage, share, and access
context information among related Web
services. See WS-CAF
|
|
|
|
|
WS-Discovery
|
Metadata
|
Web
Services Dynamic Discovery
Defines a multicast discovery protocol to
locate services. By default, probes are sent
to a multicast group, and target services that
match return a response directly to the
requestor. To scale to a large number of
endpoints, the protocol defines the multicast
suppression behavior if a discovery proxy is
available on the network. To minimize the need
for polling, target services that wish to be
discovered send an announcement when they join
and leave the network.
|
none
|
BEA,
Canon, Intel, Microsoft
|
Specification
published
|
|
WSDL
|
Metadata
|
WS
Description Language
Web Services Description Language (WSDL)
provides a model and an XML format for
describing Web services. WSDL enables one to
separate the description of the abstract
functionality offered by a service from
concrete details of a service description such
as "how" and "where" that
functionality is offered.
|
W3C
|
Ariba,
IBM, Microsoft
|
version
2.0
Working Draft
|
|
WSDM
|
Management
|
WS
Distributed Management
The purpose of this TC is to define web
services management, including using web
services architecture and technology to manage
distributed resources. This TC will also
develop the model of a web service as a
manageable resource
|
OASIS
|
Various
inc.,
BMC, CA, Cisco, IBM, HP, Novell, Tibco
|
Committee
Draft
|
|
WS-Enumeration
|
Messaging
|
WS-Enumeration
describes a SOAP-based protocol for
enumerating a sequence of XML elements that is
suitable for traversing logs, message queues,
or other linear information models.
WS-Enumeration enables an application to ask
for items from a list of data that is held by
a Web service. In this way, WS-Enumeration is
useful for reading event logs, message queues,
streaming, or other applications for which a
simple single-request/single-reply metaphor is
insufficient for transferring large data sets
over SOAP.
|
Not
yet submitted
|
BEA,
CA, Microsoft, Sonic Software, Systinet.
|
Specification
Published
|
|
WS-Eventing
|
Messaging
|
WS-Eventing
describes how to construct an event-oriented
message exchange pattern using WS-Addressing
concepts, allowing Web services to act as
event sources for subscribers. It defines the
operations required to manage subscriptions to
event sources, as well as how the actual event
messages are constructed.
|
Not
yet submitted
|
Microsoft,
BEA, Tibco (now joined by CA, IBM, Sun)
|
Specification
published
|
|
WS-Federation
|
Security
|
Web
Services Federation Language
This specification defines mechanisms to allow
different security realms to federate by
allowing and brokering trust of identities,
attributes, authentication between
participating Web services. The Web Services
Federation specification is another component
of the Web Services Security model that
defines mechanisms to allow different security
realms to federate by allowing and brokering
trust of identities, attributes,
authentication between participating Web
services. The mechanisms defined in this
specification can be used by passive and
active requestors. The Web service requestors
are assumed to understand the new security
mechanisms and be capable of interacting with
Web service providers.
|
Not
yet submitted
|
IBM,
Microsoft, BEA, RSA Security, Verisign
|
Specification
published
|
|
WSIL
|
Metadata
|
WS
Inspection Language - WS-Inspection
Provides an XML format for assisting in the
inspection of a site for available services
and a set of rules for how inspection related
information should be made available for
consumption. Consolidates earlier ADS (IBM)
and DISCO (Microsoft).
|
Not
yet submitted
|
IBM,
Microsoft
|
Specification
published
|
|
WS-Manageability
|
Management
|
Web
services manageability is defined as a set of
capabilities for discovering the existence,
availability, health, performance, and usage,
as well as the control and configuration of a
Web service within the Web services
architecture. See WSDM
|
OASIS
|
CA,
IBM, Talking Blocks
|
Specification
published
|
|
WS-MetadataExchange
|
Metadata
|
Web
Services Metadata Exchange
To bootstrap communication with a Web service,
this specification defines three
request-response message pairs to retrieve
three types of metadata: one retrieves the
WS-Policy associated with the receiving
endpoint or with a given target namespace,
another retrieves either the WSDL associated
with the receiving endpoint or with a given
target namespace, and a third retrieves the
XML Schema with a given target namespace.
Together these messages allow efficient,
incremental retrieval of a Web service's
metadata.
|
none
|
BEA,
IBM, Microsoft, SAP (now joined by CA, Sun and
webMethods)
|
Specification
published
|
|
WS-MessageDelivery
|
Messaging
|
Specifies
an abstract set of message delivery properties
that enable message delivery for Web services
that utilize Message Exchange Patterns
associated with WSDL documents.
Should be superseded by WS-Addressing
|
W3C
|
Oracle,
Arjuna, Cyclone Commerce, Enigmatec, IONA,
Nokia, SeeBeyond, Sun
|
Submission
to W3C
Should be superseded
|
|
WS-Notification
|
Messaging
|
Web
Services Notification, which includes the
WS-BaseNotification, WS-BrokeredNotification,
and WS-Topics specifications, implements the
Notification pattern, where a service
provider, or other entity, initiates messages
based on a subscription or registration of
interest from a service requestor. It defines
how the publish/subscribe (pub sub) pattern
commonly used in Message-Oriented middleware
products can be realized using Web services.
This includes brokered as well as direct pub
sub which allows the publisher/subscribers to
be decoupled and provides greater scalability.
|
Not
yet submitted
|
IBM,
Akamai, HP, SAP, Sonic Software, The Globus
Alliance, TIBCO
|
Specification
published
|
|
WS-Policy
|
Metadata
|
Provides
a general-purpose model and corresponding
syntax to describe and communicate the
policies of a Web service.
|
Not
yet submitted
|
BEA,
IBM, Microsoft, SAP
|
Specification
published
|
|
WS-Provisioning
|
Management
|
WS-Provisioning
describes the APIs and schemas necessary to
facilitate interoperability between
provisioning systems and to allow software
vendors to provide provisioning facilities in
a consistent way. The specification addresses
many of the problems faced by provisioning
vendors in their use of existing protocols,
commonly based on directory concepts, and
confronts the challenges involved in
provisioning Web Services described using WSDL
and XML Schema. The specification defines a
model for the primary entities and operations
common to provisioning systems including the
provisioning and de-provisioning of resources,
retrieval of target data and target schema
information, and provides a mechanism to
describe and control the lifecycle of
provisioned state.
|
OASIS
|
IBM
|
Specification
published Passed to OASIS Provisioning
Services TC
|
|
WS-Reliability
|
Messaging
|
Specification
for open, reliable Web services messaging
including guaranteed delivery, duplicate
message elimination and message ordering,
enabling reliable communication between Web
services.
|
OASIS
|
|
V1.1
OASIS Standard
|
|
WS
Reliable Messaging
|
Messaging
|
The
purpose of this TC is to create a generic and
open model for ensuring reliable message
delivery for Web services. Reliable message
delivery is the ability to guarantee message
delivery to software applications - Web
services or Web service client applications -
with a chosen level of quality of service
(QoS).
|
OASIS
|
Various
inc.,
Fujitsu, Hitachi, IONA,, NEC, Nokia, Oracle,
SAP, Sonic, Sun
|
Specification
Published
WS-Reliability V1.1 OASIS Standard
|
|
WS-RF
|
Metadata
|
WS-Resource
Framework
Defines a generic and open framework for
modeling and accessing stateful resources
using Web services. This includes mechanisms
to describe views on the state, to support
management of the state through properties
associated with the Web service, and to
describe how these mechanisms are extensible
to groups of Web services.
|
OASIS
|
IBM,
Akamai, HP, SAP, Sonic Software, The Globus
Alliance, TIBCO
|
TC
Formed Working Drafts
|
|
WS-Routing
|
Messaging
|
See
WS-Addressing
|
|
|
Superseded
|
|
WSRP
|
Portal
and Presentation
|
WS
Remote Portals
The purpose of this TC is to develop a web
services standard that will allow for the
"plug-n-play" of portals, other
intermediary web applications that aggregate
content, and applications from disparate
sources.
|
OASIS
|
Various
inc.,
BEA, Bowstreet, IBM, Novell, Oracle, Plumtree,
SAP, Sun
|
Approved
|
|
WS-Security
|
Security
|
Describes
enhancements to SOAP messaging to provide
quality of protection through message
integrity, message confidentiality, and single
message authentication. See WS Security
Services
|
OASIS
Standard
|
IBM,
Microsoft, Verisign
|
OASIS
Standard
|
|
WS-SecureConversation
|
Security
|
Defines
extensions that build on WS-Security to
provide secure communication. Specifically, it
defines mechanisms for establishing and
sharing security contexts, and deriving
session keys from security contexts.
|
Not
yet submitted
|
IBM,
Microsoft, RSA, Verisign
|
Specification
published
|
|
WS-SecurityPolicy
|
Security
|
An
addendum to WS-Security. Indicates the policy
assertions for WS-Policy which apply to
WS-Security.
|
Not
yet submitted
|
IBM,
Microsoft, RSA, Verisign
|
Specification
published
|
|
WS
Security Services TC
|
Security
|
The
purpose of the Web Services Security TC is to
continue work on the Web Services security
foundations as described in the WS-Security
specification
|
OASIS
|
Various
inc.,
Baltimore, BEA, HP, IBM, Microsoft, RSA, SAP,
Sun
|
Technical
Committee
|
|
WS-TM
|
Transactions
|
WS
Transaction Management
Defines three distinct transaction protocols
that can be plugged into the coordination
framework for interoperability across existing
transaction managers, long running
compensations, and asynchronous business
process flows. It also includes an innovative
solution to bridge different transaction
models (e.g. MQ Series, JMS). See WS-CAF
|
|
|
|
|
WS-Transaction
|
Transactions
|
Superseded
by WS-AtomicTransaction
|
|
|
|
|
WS-Transfer
|
Messaging
|
Describes
a general SOAP-based protocol for accessing
XML representations of Web service-based
resources.
WS-Transfer defines how to invoke a simple set
of familiar verbs (Get, Post, Put, and Delete)
using SOAP. An application protocol may be
constructed to perform these operations over
resources.
|
Not
yet submitted
|
BEA,
CA, Microsoft, Sonic Software, Systinet.
|
Specification
Published
|
|
WS-Trust
|
Security
|
Defines
extensions that build on WS-Security to
request and issue security tokens and to
manage trust relationships.
|
Not
yet submitted
|
IBM,
Microsoft, RSA, Verisign
|
Specification
published
|
|
|
