Web Services
StandardWeb Services Transaction v1.1
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 activities.
Web Services Transaction v1.1
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 activities.
Produced by:
OASIS Web Services Transaction (WS-TX) TCVoting history:
March 2007
OASIS Standard:
This specification consists of three documents available as follows:
Web Services Coordination (WS-Coordination) v1.1 incorporating Approved Errata HTMLDOC
Schema
WSDL
Web Services Atomic Transaction (WS-AtomicTransaction) v1.1 incorporating Approved Errata HTML
DOC
Schema
WSDL
Web Services Business Activity (WS-BusinessActivity) v1.1 incorporating Approved Errata HTML
DOC
Schema
WSDL
Cite as:
StandardWS-SecureConversation v1.3
Defines extensions that build on [WS-Security] to provide a framework for requesting and issuing security tokens, and to broker trust relationships.
WS-SecureConversation v1.3
Defines extensions that build on [WS-Security] to provide a framework for requesting and issuing security tokens, and to broker trust relationships.
StandardWebCGM v2.0
Computer Graphics Metafile (CGM) is an ISO standard, defined by ISO/IEC 8632:1999, for the interchange of 2D vector and mixed vector/raster graphics. WebCGM is a profile of CGM, which adds Web linking and is optimized for Web applications in technical illustration, electronic documentation, geophysical data visualization, and similar fields. First published (1.0) in 1999 and followed by a second (errata) release in 2001, WebCGM unifies potentially diverse approaches to CGM utilization in Web document applications. It therefore represents a significant interoperability agreement amongst major users and implementers of the ISO CGM standard.
WebCGM 2.0 adds a DOM (API) specification for programmatic access to WebCGM objects, and a specification of an XML Companion File (XCF) architecture, for externalization of non-graphical metadata. WebCGM 2.0, in addition, builds upon and extends the graphical and intelligent content of WebCGM 1.0, delivering functionality that was forecast for WebCGM 1.0, but was postponed in order to get the standard and its implementations to users expeditiously.
The design criteria for WebCGM aim at a balance between graphical expressive power on the one hand, and simplicity and implementability on the other. A small but powerful set of standardized metadata elements supports the functionalities of hyperlinking and document navigation, picture structuring and layering, and enabling search and query of WebCGM picture content.
WebCGM v2.0
Computer Graphics Metafile (CGM) is an ISO standard, defined by ISO/IEC 8632:1999, for the interchange of 2D vector and mixed vector/raster graphics. WebCGM is a profile of CGM, which adds Web linking and is optimized for Web applications in technical illustration, electronic documentation, geophysical data visualization, and similar fields. First published (1.0) in 1999 and followed by a second (errata) release in 2001, WebCGM unifies potentially diverse approaches to CGM utilization in Web document applications. It therefore represents a significant interoperability agreement amongst major users and implementers of the ISO CGM standard.
WebCGM 2.0 adds a DOM (API) specification for programmatic access to WebCGM objects, and a specification of an XML Companion File (XCF) architecture, for externalization of non-graphical metadata. WebCGM 2.0, in addition, builds upon and extends the graphical and intelligent content of WebCGM 1.0, delivering functionality that was forecast for WebCGM 1.0, but was postponed in order to get the standard and its implementations to users expeditiously.
The design criteria for WebCGM aim at a balance between graphical expressive power on the one hand, and simplicity and implementability on the other. A small but powerful set of standardized metadata elements supports the functionalities of hyperlinking and document navigation, picture structuring and layering, and enabling search and query of WebCGM picture content.
Produced by:
OASIS CGM Open WebCGM TCVoting history:
Voting History for OASIS Standard, January 2007
Additional approvals:
W3C WebCGM 2.0
StandardWeb Services Resource Metadata 1.0
The components introduced by the WS Resource Framework (WSRF) address functional aspects of modeling stateful resources (such as systems resources) using Web services. WSRF uses WSDL (currently WSDL 1.1) as the form of service description. There is a need to be able to supplement the descriptive information available about a WS-Resource. The format of the information about the components of a WS-Resource is standardized by WSRF, most notably in the resource properties document [WS-ResourceProperties].
In the realm of resource properties, the loosely coupled operations for reading and writing of properties [WS-ResourceProperties] would benefit from metadata. An example of this type of metadata is the mutability constraints and an enumeration of possible values for resource property elements. This document explains the need for such metadata and proposes an information model representing it that would be applicable to Manageable Resources and WS-Resources in general.
Web Services Resource Metadata 1.0
The components introduced by the WS Resource Framework (WSRF) address functional aspects of modeling stateful resources (such as systems resources) using Web services. WSRF uses WSDL (currently WSDL 1.1) as the form of service description. There is a need to be able to supplement the descriptive information available about a WS-Resource. The format of the information about the components of a WS-Resource is standardized by WSRF, most notably in the resource properties document [WS-ResourceProperties].
In the realm of resource properties, the loosely coupled operations for reading and writing of properties [WS-ResourceProperties] would benefit from metadata. An example of this type of metadata is the mutability constraints and an enumeration of possible values for resource property elements. This document explains the need for such metadata and proposes an information model representing it that would be applicable to Manageable Resources and WS-Resources in general.
Produced by:
OASIS Web Services Resource Framework (WSRF) TCVoting history:
November 2006
OASIS Standard:
Cite as:
Cite as:
[WS-Resource-Metadata]
Web Services Resource Metadata 1.0. Edited by Dan Jemiolo. November 9, 2006. OASIS Committee Specification 01. http://docs.oasis-open.org/wsrf/wsrf-ws_resource_metadata_descriptor-1.0-spec-cs-01.htm.
StandardWSN v1.3
The Event-driven, or Notification-based, interaction pattern is a commonly used pattern for inter-object communications. Examples exist in many domains, for example in publish/subscribe systems provided by Message Oriented Middleware vendors, or in system and device management domains. This notification pattern is increasingly being used in a Web services context.
WS-Notification is a family of related specifications that define a standard Web services approach to notification using a topic-based publish/subscribe pattern. It includes: standard message exchanges to be implemented by service providers that wish to participate in Notifications, standard message exchanges for a notification broker service provider (allowing publication of messages from entities that are not themselves service providers), operational requirements expected of service providers and requestors that participate in notifications, and an XML model that describes topics. The WS-Notification family of documents includes three normative specifications: WS-BaseNotification, [WS-BrokeredNotification], and [WS-Topics].
WSN v1.3
The Event-driven, or Notification-based, interaction pattern is a commonly used pattern for inter-object communications. Examples exist in many domains, for example in publish/subscribe systems provided by Message Oriented Middleware vendors, or in system and device management domains. This notification pattern is increasingly being used in a Web services context.
WS-Notification is a family of related specifications that define a standard Web services approach to notification using a topic-based publish/subscribe pattern. It includes: standard message exchanges to be implemented by service providers that wish to participate in Notifications, standard message exchanges for a notification broker service provider (allowing publication of messages from entities that are not themselves service providers), operational requirements expected of service providers and requestors that participate in notifications, and an XML model that describes topics. The WS-Notification family of documents includes three normative specifications: WS-BaseNotification, [WS-BrokeredNotification], and [WS-Topics].
Produced by:
OASIS Web Services Notification (WSN) TCVoting history:
October 2006
OASIS Standard:
The WS-Notification family consists of three OASIS Standards available as follows:
Web Services Base Notification v1.3
Web Services Brokered Notification v1.3
Web Services Topics v1.3
The complete package, including schemas and wsdl files is also available for
download.
Cite as:
StandardWSDM v1.1
There are two specifications produced by the Web Services Distributed Management technical committee: Management Using Web services (MUWS) and Management Of Web Services (MOWS, see [[MOWS]]). This document is part of MUWS.
MUWS defines how an Information Technology resource connected to a network provides manageability interfaces such that the IT resource can be managed locally and from remote locations using Web services technologies.
MUWS is composed of two parts. This document is MUWS part 1 and provides the fundamental concepts for management using Web services. MUWS part 2 [MUWS Part 2] provides specific messaging formats used to enable the interoperability of MUWS implementations. MUWS part 2 depends on MUWS part 1, while part 1 is independent from part 2.
WSDM v1.1
There are two specifications produced by the Web Services Distributed Management technical committee: Management Using Web services (MUWS) and Management Of Web Services (MOWS, see [[MOWS]]). This document is part of MUWS.
MUWS defines how an Information Technology resource connected to a network provides manageability interfaces such that the IT resource can be managed locally and from remote locations using Web services technologies.
MUWS is composed of two parts. This document is MUWS part 1 and provides the fundamental concepts for management using Web services. MUWS part 2 [MUWS Part 2] provides specific messaging formats used to enable the interoperability of MUWS implementations. MUWS part 2 depends on MUWS part 1, while part 1 is independent from part 2.
Produced by:
OASIS Web Services Distributed Management (WSDM) TCVoting history:
August 2006
OASIS Standard:
Web Services Distributed Management: Management Using Web Services (WSDM-MUWS) v1.1
HTML / PDF
Web Services Distributed Management: Management Using Web Services (WSDM-MUWS)
v1.1, Part 2
HTML /
PDF
Web Services Distributed Management: Management of Web Services (WSDM-MOWS) v1.1
HTML /
PDF
The Schema and WSDL files are available as follows:
WSDM MUWS 1.1 Part 1 XML Schema
http://docs.oasis-open.org/wsdm/muws1-2.xsd
WSDM MUWS 1.1 Part 2 XML Schema
http://docs.oasis-open.org/wsdm/muws2-2.xsd
WSDM MUWS 1.1 Part 2 WSDL
http://docs.oasis-open.org/wsdm/muws2-2.wsdl
WSDM MUWS 1.1 Part 2 Topics Document
http://docs.oasis-open.org/wsdm/muwse2-2.xml
WSDM MUWS 1.1 Part 2 PBM Schema
http://docs.oasis-open.org/wsdm/pbm.xsd
WSDM MOWS 1.1 XML Schema
http://docs.oasis-open.org/wsdm/mows-2.xsd
WSDM MOWS 1.1 WSDL
http://docs.oasis-open.org/wsdm/mows-2.wsdl
WSDM MOWS 1.1 Topics Document
http://docs.oasis-open.org/wsdm/mowse-2.xml
Available as a .ZIP file
http://docs.oasis-open.org/wsdm/wsdm-1.1-os-01.zip
Cite as:
StandardWeb Services Resource Framework (WSRF) v1.2
A family of OASIS-published specifications for web services. Web Services Resource Framework provides a set of operations that web services can use to implement stateful interactions.
Web Services Resource Framework (WSRF) v1.2
A family of OASIS-published specifications for web services. Web Services Resource Framework provides a set of operations that web services can use to implement stateful interactions.
Produced by:
OASIS Web Services Resource Framework TCVoting history:
April 2006
OASIS Standard:
The specification set, including schema and wsdl files, can be downloaded as a zip archive and includes the following documents:
Web Services Resource Framework (WSRF) v1.2
WS-Resource v1.2
WS-ResourceProperties v1.2
WS-ResourceLifetime v1.2
WS-ServiceGroup v1.2
WS-BaseFaults v1.2
Cite as:
StandardWeb Services Security v1.1
Proposing a standard set of SOAP extensions that can be used when building secure Web services to implement message content integrity and confidentiality.
Web Services Security v1.1
Proposing a standard set of SOAP extensions that can be used when building secure Web services to implement message content integrity and confidentiality.
Produced by:
OASIS Web Services Security TCVoting history:
February 2006
OASIS Standard:
This OASIS Standard is composed of the following files:
- WS-Security Core Specification 1.1
- WS-Security SOAP Message Security 1.1 Errata (only)
- WS-Security SOAP Message Security 1.1 Errata (merged)
- Username Token Profile 1.1
- SAML Token Profile 1.1
- SAML Token Profile 1.1 Errata (only)
- SAML Token Profile 1.1 Errata (merged)
- X.509 Token Profile 1.1
- X.509 Token Profile 1.1 Errata (only)
- X.509 Token Profile 1.1 Errata (merged)
- Kerberos Token Profile 1.1
- Kerberos Token Profile 1.1 Errata (only)
- Kerberos Token Profile 1.1 Errata (merged)
- Rights Expression Language (REL) Token Profile 1.1
- SOAP with Attachments (SWA) Profile 1.1
- SOAP with Attachments (SWA) Profile 1.1 Errata (only)
- SOAP with Attachments (SWA) Profile 1.1 Errata (merged)
and schemas:
- secext-1.1.xsd
- secext-1.0.xsd
- utility-1.0.xsd
Cite as:
StandardWSDM Management Using Web Services v1.0 (WSDM-MOWS)
Defines A) how management of any resource can be accessed via
15 Web services protocols – Management Using Web Services, or MUWS, and B)
16 management of the Web services resources via the former – Management Of Web
17 Services, or MOWS. This document is the WSDM specification defining MOWS.
WSDM Management Using Web Services v1.0 (WSDM-MOWS)
Defines A) how management of any resource can be accessed via
15 Web services protocols – Management Using Web Services, or MUWS, and B)
16 management of the Web services resources via the former – Management Of Web
17 Services, or MOWS. This document is the WSDM specification defining MOWS.
StandardWSDM Management Using Web Services v1.0 (WSDM-MUWS)
Defines A) how management of any resource can be accessed via
15 Web services protocols – Management Using Web Services, or MUWS, and B)
16 management of the Web services resources via the former – Management Of Web
17 Services, or MOWS. This document is the WSDM specification defining MOWS.
WSDM Management Using Web Services v1.0 (WSDM-MUWS)
Defines A) how management of any resource can be accessed via
15 Web services protocols – Management Using Web Services, or MUWS, and B)
16 management of the Web services resources via the former – Management Of Web
17 Services, or MOWS. This document is the WSDM specification defining MOWS.
StandardUniversal Description, Discovery and Integration v3.0.2 (UDDI)
Universal Description Discovery & Integration (UDDI) is the definition of a set of services supporting the description and discovery of businesses, organizations, and other Web services providers, the Web services they make available, and the technical interfaces which may be used to access those services.
Universal Description, Discovery and Integration v3.0.2 (UDDI)
Universal Description Discovery & Integration (UDDI) is the definition of a set of services supporting the description and discovery of businesses, organizations, and other Web services providers, the Web services they make available, and the technical interfaces which may be used to access those services.
StandardWeb Services Security
Describes how to use Security Assertions Markup Language (SAML) V1.1 assertions and ISO/IEC 21000-5 Rights Expressions with the Web Services Security (WSS): SOAP Message Security [WS-Security] specification.
Web Services Security
Describes how to use Security Assertions Markup Language (SAML) V1.1 assertions and ISO/IEC 21000-5 Rights Expressions with the Web Services Security (WSS): SOAP Message Security [WS-Security] specification.
Produced by:
OASIS Web Services Security TCVoting history:
December 2004
OASIS Standard:
SAML Token Profile 1.0 and REL Token Profile 1.0
SAML Token profile:
oasis-wss-saml-token-profile-1.0.pdf
REL Token profile:
oasis-wss-rel-token-profile-1.0.pdf
Cite as:
No results with the selected filters