Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

developerWorks Community:

  • Close [x]

Web services specifications

developerWorks staff, Editorial Staff, IBM

Summary:  This is a list of all IBM developerWorks Web services specifications

Date:  09 Feb 2005
Level:  Introductory

Activity:  3511 views
Comments:  

Messaging

Simple Object Access Protocol

8 May 2000
The Simple Object Access Protocol is a W3C Note that describes a lightweight protocol for the exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses. SOAP can potentially be used in combination with a variety of other protocols; however, the only bindings defined in this document describe how to use SOAP in combination with HTTP and HTTP Extension Framework.
This specification is available from the W3C site: http://www.w3.org/TR/SOAP/

Direct Internet Message Encapsulation

17 June 2002
Direct Internet Message Encapsulation is a lightweight binary message format that can be used to encapsulate one or more application-defined payloads of arbitrary type and size into a single message construct. DIME is strictly a message format; it provides no concept of a connection or of a logical circuit. Thus, it can be used to carry SOAP messages with attachments in a binary format as well.
http://www-106.ibm.com/developerworks/library/ws-dime/

Web Services Attachments

17 June 2002
The WS-Attachments draft specification describes an abstract model for SOAP messages to include attachments as well as encapsulating a SOAP message and its attachments within a DIME message.
http://www-106.ibm.com/developerworks/library/ws-attach.html

Web Services for J2EE, Public Final Draft

9 August 2002
This specification defines the Web Services for J2EE architecture. This is a service architecture which leverages the J2EE component architecture to provide a decoupled client and server programming model which is portable across application servers, provides a scalable secure environment, and yet is familiar to J2EE developers.
http://www-106.ibm.com/developerworks/library/ws-jsr109-proposed/


Description

Web Services Description Language

15 March 2001
The Web Services Description Language is a W3C Note that is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what message formats or network protocols are used to communicate, however, the only bindings described in this document describe how to use WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
This specification is available from the W3C: http://www.w3.org/TR/wsdl


Publishing

Universal Description, Discovery and Integration

8 Oct 2002
The Universal Description, Discovery and Integration specification creates a platform-independent, open framework for describing services, discovering businesses, and integrating business services using the Internet, as well as an operational registry that is available today.
This document is available from the Oasis Group: http://www.oasis-open.org/committees/uddi-spec/


Discovery

Web Services Inspection Language (WS-Inspection) 1.0

November 2001
The WS-Inspection specification provides an XML format for assisting in the inspection of a site for available services and a collection of rules for how inspection related information should be made available for consumption. A WS-Inspection document provides a means for aggregating references to pre-existing service description documents which have been authored in any number of formats. These inspection documents are then made available at the point-of-offering of the service as well as through references which may be placed within a content medium such as HTML.
http://www-106.ibm.com/developerworks/library/ws-wsilspec.html


Security

Web services security protocol

05 April 2002
The Web Services Security specification offers a new model for many levels of security needed for services. It includes enhancements to SOAP to provide quality of protection mechanisms; a general-purpose mechanism to associate security-tokens with messages; and describes how to encode binary security tokens in messages.
http://www-106.ibm.com/developerworks/library/ws-secure/

Web Services Security Addendum

18 August 2002
This addendum to the WS-Security specification clarifies elements released in the original document and introduces some new items including timestamps, and passing around passwords and security certificates.
http://www-106.ibm.com/developerworks/library/ws-secureadd.html

WS-Security Profile for XML-based Tokens

28 August 2002
This document describes a general framework to enable XML-based security tokens to be used with WS-Security. Two profiles that use this general framework are provided: one for the Security Assertion Markup Language (SAML) and other for the the eXtensible rights Markup Language (XrML).
http://www-106.ibm.com/developerworks/library/ws-sectoken.html

WS-Security AppNotes

28 August 2002
This paper is provided as guidance to implementers of the WS-Security specification. This application note applies to both WS-Security and the associated addendum. Consequently, the discussions here apply to the schemas identified in both specifications.
http://www-106.ibm.com/developerworks/webservices/library/ws-secapp/

WS-Policy Framework

18 December 2002
The Web Services Policy Framework defines a general purpose model and corresponding syntax to describe and communicate Web services policies so that Service consumers can discover the information they need to know to be able to access services from a Service Provider.
http://www-106.ibm.com/developerworks/webservices/library/ws-polfram/

WS-Policy Attachments

18 December 2002
The Web Services Policy Attachments specification provides a general-purpose mechanism for associating policy assertions with subjects (services). It provides for two approaches for making assertions: policy assertions defined as part of the definition of the subject, or policy assertions defined independently of and associated through an external binding to the subject.
http://www-106.ibm.com/developerworks/webservices/library/ws-polatt/

WS-Policy Assertions

18 December 2002
The goal of WS-PolicyAssertions is to provide basic assertions needed to enable Web Services applications. This document specifies a set of common message policy assertions that can be specified within a policy.
http://www-106.ibm.com/developerworks/webservices/library/ws-polas/

WS-Secure Conversation

18 December 2002
The Web Services Secure Conversation Language is built on top of the WS-Security and WS-Policy models to provide secure communication between services. WS-Security focuses on the message authentication model but not a security context, and thus is subject several forms of security attacks. This specification defines mechanisms for establishing and sharing security contexts, and deriving keys from security contexts, to enable a secure conversation.
http://www-106.ibm.com/developerworks/webservices/library/ws-secon/

WS-Security Policy

18 December 2002
The Web Services Security Policy Language defines a model and syntax to describe and communicate security policy assertions within the larger Policy Framework. It covers assertions for security tokens, data integrity, confidentiality, visibility, security headers and the age of a message.
http://www-106.ibm.com/developerworks/webservices/library/ws-secpol/

WS-Trust

18 December 2002
The Web Services Trust Language uses the secure messaging mechanisms of WS-Security to define additional primitives and extensions for the issuance, exchange and validation of security tokens. WS-Trust also enables the issuance and dissemination of credentials within different trust domains.
http://www-106.ibm.com/developerworks/webservices/library/ws-trust/


Reliability

Reliable HTTP 1.1

1 April 2002
Version 1.1 is an update to the Reliable HTTP (HTTP) protocol released June 2001 that implements guarantees in delivery for Web content. This is can also be used as the transport protocol for higher level messaging protocols like SOAP and MQ.
http://www-106.ibm.com/developerworks/library/ws-httprspec/


Transactions

Web Service Transaction (WS-Transaction)

9 August 2002
This specification describes coordination types that are used with the extensible coordination framework described in the WS-Coordination specification. It defines two coordination types: Atomic Transaction (AT) and Business Activity (BA). Developers can use either or both of these coordination types when building applications that require consistent agreement on the outcome of distributed activities.
http://www-106.ibm.com/developerworks/library/ws-transpec/

Web Services Coordination (WS-Coordination)

9 August 2002
This specification (WS-Coordination) describes an extensible framework for providing protocols that coordinate the actions of distributed applications. Such coordination protocols are used to support a number of applications, including those that need to reach consistent agreement on the outcome of distributed transactions.
http://www-106.ibm.com/developerworks/library/ws-coor/


Business Processes

Business Process Execution Language for Web Services, Version 1.0

31 July 2002
This document defines a notation for specifying business process behavior based on Web services. This notation is called Business Process Execution Language for Web Services (abbreviated to BPEL4WS in the rest of this document). Processes in BPEL4WS export and import functionality by using Web Service interfaces exclusively.
http://www-106.ibm.com/developerworks/library/ws-bpel/


User Interface

Web Services Experience Language -Updated

10 April 2002
WSXL (Web Services Experience Language) is a Web services centric component model for interactive Web applications. WSXL is designed to achieve two main goals: enable businesses to distribute Web applications through multiple revenue channels, and enable new services or applications to be created by leveraging existing applications across the Web.
http://www-106.ibm.com/developerworks/library/ws-wsxl/

Web Services for Remote Portals

21 January 2002
This new specification, Web Services for Remote Portals (WSRP) describes visual, user-facing web services-centric components that plug-n-play with portals or other intermediary web applications that aggregate content or applications from different sources. They are designed to enable businesses to provide content or applications in a form that does not require any manual content- or application-specific adaptation by consuming intermediary applications.
http://www.oasis-open.org/committees/wsrp/#documents


About the author

Report abuse help

Report abuse

Thank you. This entry has been flagged for moderator attention.


Report abuse help

Report abuse

Report abuse submission failed. Please try again later.


developerWorks: Sign in


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

Choose your display name

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


Rate this article

Comments

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=SOA and Web services
ArticleID=32212
ArticleTitle=Web services specifications
publish-date=02092005
author1-email=dwinfo@us.ibm.com
author1-email-cc=