Messaging
StandardElection Markup Language (EML) Specification Version 7.0
Describes the background and purpose of the Election Markup Language, the electoral processes from which it derives its structure and the security and audit mechanisms it is designed to support. It also provides an explanation of the core schemas used throughout, definitions of the simple and complex datatypes, plus the EML schemas themselves. It also covers the conventions used in the specification and the use of namespaces, as well as guidance on the constraints, extensibility, and splitting of messages.
Election Markup Language (EML) Specification Version 7.0
Describes the background and purpose of the Election Markup Language, the electoral processes from which it derives its structure and the security and audit mechanisms it is designed to support. It also provides an explanation of the core schemas used throughout, definitions of the simple and complex datatypes, plus the EML schemas themselves. It also covers the conventions used in the specification and the use of namespaces, as well as guidance on the constraints, extensibility, and splitting of messages.
Produced by:
OASIS Election and Voter Services TCVoting history:
October 2011
OASIS Standard:
Cite as:
Cite as:
[EML-v7.0] Election Markup Language (EML) Specification Version 7.0. Edited by John Borras and David Webber. 27 October 2011. OASIS Committee Specification 01. http://docs.oasis-open.org/election/eml/v7.0/cs01/eml-v7.0-cs01.html. Latest version: http://docs.oasis-open.org/election/eml/v7.0/eml-v7.0.html.
StandardOASIS ebXML Messaging Services Version 3.0: Part 2, Advanced Features
Complements the ebMS 3.0 Core Specification by specifying advanced messaging functionality for message service configuration, message bundling, messaging across intermediaries (multi-hop) and transfer of (compressed) messages as series of smaller message fragments.
OASIS ebXML Messaging Services Version 3.0: Part 2, Advanced Features
Complements the ebMS 3.0 Core Specification by specifying advanced messaging functionality for message service configuration, message bundling, messaging across intermediaries (multi-hop) and transfer of (compressed) messages as series of smaller message fragments.
Produced by:
OASIS ebXML Messaging Services TCVoting history:
May 2011
OASIS Standard:
Cite as:
Cite as:
[ebxml-msg-srv-part2-v3.0] OASIS ebXML Messaging Services Version 3.0: Part 2, Advanced Features. Edited by Jacques Durand, Sander Fieten, and Pim van der Eijk. 19 May 2011. OASIS Committee Specification 01. http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/cs01/ebms-v3.0-part2-cs01.html. Latest version: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/part2/201004/ebms-v3-part2.html.
StandardSymmetric Key Services Markup Language (SKSML) Version 1.0
Defines the first (1.0) version of the Symmetric Key Services Markup Language (SKSML), an XML-based messaging protocol, by which applications executing on computing devices may request and receive symmetric key-management services from centralized key-management servers, securely, over networks. Applications using SKSML are expected to either implement the SKSML protocol, or use a software library – called the Symmetric Key Client Library (SKCL) – that implements this protocol. SKSML messages are transported securely over standard HTTP using XML Security (XML Signature and XML Encryption).
Symmetric Key Services Markup Language (SKSML) Version 1.0
Defines the first (1.0) version of the Symmetric Key Services Markup Language (SKSML), an XML-based messaging protocol, by which applications executing on computing devices may request and receive symmetric key-management services from centralized key-management servers, securely, over networks. Applications using SKSML are expected to either implement the SKSML protocol, or use a software library – called the Symmetric Key Client Library (SKCL) – that implements this protocol. SKSML messages are transported securely over standard HTTP using XML Security (XML Signature and XML Encryption).
Produced by:
OASIS Enterprise Key Management Infrastructure (EKMI) TCVoting history:
January 2011
OASIS Standard:
Cite as:
Cite as:
[sksml-v1.0]
Symmetric Key Services Markup Language (SKSML) Version 1.0. Edited by Allen Schaaf, Anil Saldhana, and Tomas Gustavsson. 10 January 2011. OASIS Committee Specification 02. http://docs.oasis-open.org/ekmi/sksml/v1.0/cs02/SKSML-1.0-Specification.html. Latest version: http://docs.oasis-open.org/ekmi/sksml/v1.0/SKSML-1.0-Specification.html.
StandardElection Markup Language (EML) Specification Version 6.0
Describes the background and purpose of the Election Markup Language, the electoral processes from which it derives its structure and the security and audit mechanisms it is designed to support. It also provides an explanation of the core schemas used throughout, definitions of the simple and complex datatypes, plus the EML schemas themselves. It also covers the conventions used in the specification and the use of namespaces, as well as the guidance on the constraints, extendibility, and splitting of messages.
Election Markup Language (EML) Specification Version 6.0
Describes the background and purpose of the Election Markup Language, the electoral processes from which it derives its structure and the security and audit mechanisms it is designed to support. It also provides an explanation of the core schemas used throughout, definitions of the simple and complex datatypes, plus the EML schemas themselves. It also covers the conventions used in the specification and the use of namespaces, as well as the guidance on the constraints, extendibility, and splitting of messages.
Produced by:
OASIS Election and Voter Services TCVoting history:
August 2010
OASIS Standard:
Cite as:
Cite as:
[EML-v6.0] Election Markup Language (EML) Specification Version 6.0. Edited by John Borras and David Webber. 19 August 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/election/eml/v6.0/cs01/EML-Specification-v6.0-cs01.html. Latest version: http://docs.oasis-open.org/election/eml/v6.0/EML-Specification-v6.0.html.
StandardCommon Alerting Protocol v1.2
General format for exchanging all-hazard emergency alerts and public warnings over all kinds of networks. CAP allows a consistent warning message to be disseminated simultaneously over many different warning systems, thus increasing warning effectiveness while simplifying the warning task. CAP also facilitates the detection of emerging patterns in local warnings of various kinds, such as might indicate an undetected hazard or hostile act. And CAP provides a template for effective warning messages based on best practices identified in academic research and real-world experience.
Common Alerting Protocol v1.2
General format for exchanging all-hazard emergency alerts and public warnings over all kinds of networks. CAP allows a consistent warning message to be disseminated simultaneously over many different warning systems, thus increasing warning effectiveness while simplifying the warning task. CAP also facilitates the detection of emerging patterns in local warnings of various kinds, such as might indicate an undetected hazard or hostile act. And CAP provides a template for effective warning messages based on best practices identified in academic research and real-world experience.
Produced by:
OASIS Emergency Management TCVoting history:
Voting History for OASIS Standard, July 2010
Additional approvals:
ITU-T X.1303 bis
StandardOASIS ebXML Messaging Services 3.0 Conformance Profiles
A supplement to the ebMS-3 specification [ebMS3]. It defines some conformance profiles that support specific messaging styles or context of use. Future releases of this document are likely to be augmented with additional conformance profiles that reflect the choices or needs of user communities. As a pre-condition to interoperability it is necessary for two implementations to agree on which common conformance profile, or which compatible conformance profiles, they will comply with. This document and its future releases is intended as a medium to publish conformance profiles that users and products will claim compliance with.
OASIS ebXML Messaging Services 3.0 Conformance Profiles
A supplement to the ebMS-3 specification [ebMS3]. It defines some conformance profiles that support specific messaging styles or context of use. Future releases of this document are likely to be augmented with additional conformance profiles that reflect the choices or needs of user communities. As a pre-condition to interoperability it is necessary for two implementations to agree on which common conformance profile, or which compatible conformance profiles, they will comply with. This document and its future releases is intended as a medium to publish conformance profiles that users and products will claim compliance with.
Produced by:
OASIS ebXML Messaging Services TCVoting history:
April 2010
OASIS Standard:
Cite as:
Cite as:
[ebxml-msg-srv-3.0-conf] OASIS ebXML Messaging Services 3.0 Conformance Profiles. Edited by Jacques Durand. 24 April 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/200707/ebms3-confprofiles-cs-01.html. Latest version: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/200707/ebms3-confprofiles.html.
StandardEmergency Data Exchange Language (EDXL) Hospital AVailability Exchange
Describes a standard message for data sharing among emergency information systems using the XML-based Emergency Data Exchange Language (EDXL). This format may be used over any data transmission system, including but not limited to the SOAP HTTP binding.
Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange
Describes a standard message for data sharing among emergency information systems using the XML-based Emergency Data Exchange Language (EDXL). This format may be used over any data transmission system, including but not limited to the SOAP HTTP binding.
StandardEmergency Data Exchange Language Resource Messaging (EDXL-RM) v1.0 incorporating Approved Errata
Describes a suite of standard messages for data sharing among emergency and other information systems that deal in requesting and providing emergency equipment, supplies, people and teams. This format may be used over any data transmission system, including but not limited to the SOAP HTTP binding.
Emergency Data Exchange Language Resource Messaging (EDXL-RM) v1.0 incorporating Approved Errata
Describes a suite of standard messages for data sharing among emergency and other information systems that deal in requesting and providing emergency equipment, supplies, people and teams. This format may be used over any data transmission system, including but not limited to the SOAP HTTP binding.
StandardOASIS ebXML Messaging Transport Binding for Digital Signature Services Version 1.0
Mappings from DSS messages into standard communication protocols are called DSS bindings. A transport binding specifies how DSS messages are encoded and carried using a transport protocol. The DSS Core standard [DSS Core] specifies two transport bindings. This document specifies an alternative transport binding that uses the OASIS ebXML Messaging Service. This profile supports is compatible with both the version 2.0 [ebMS 2.0] and version 3.0 [ebMS 3.0] ebXML Messaging OASIS standards.
OASIS ebXML Messaging Transport Binding for Digital Signature Services Version 1.0
Mappings from DSS messages into standard communication protocols are called DSS bindings. A transport binding specifies how DSS messages are encoded and carried using a transport protocol. The DSS Core standard [DSS Core] specifies two transport bindings. This document specifies an alternative transport binding that uses the OASIS ebXML Messaging Service. This profile supports is compatible with both the version 2.0 [ebMS 2.0] and version 3.0 [ebMS 3.0] ebXML Messaging OASIS standards.
Produced by:
OASIS Digital Signature Services eXtended (DSS-X) TCVoting history:
October 2008
OASIS Standard:
Cite as:
Cite as:
[dss-profiles-ebxml-v1.0] OASIS ebXML Messaging Transport Binding for Digital Signature Services Version 1.0. Edited by Pim van der Eijk and Ernst Jan van Nigtevecht. 31 October 2008. OASIS Committee Specification 01. http://docs.oasis-open.org/dss-x/profiles/ebxml/v1.0/cs01/oasis-dss-1.0-profiles-ebxml-cs01.html. Latest version: http://docs.oasis-open.org/dss-x/profiles/ebxml/v1.0/oasis-dss-1.0-profiles-ebxml.html.
StandardElection Markup Language (EML) v5.0
Describes the background and purpose of the Election Markup Language, the electoral processes from which it derives its structure and the security and audit mechanisms it is designed to support. It also provides an explanation of the core schemas used throughout, definitions of the simple and complex datatypes, plus the EML schemas themselves. It also covers the conventions used in the specification and the use of namespaces, as well as the guidance on the constraints, extendibility, and splitting of messages.
Election Markup Language (EML) v5.0
Describes the background and purpose of the Election Markup Language, the electoral processes from which it derives its structure and the security and audit mechanisms it is designed to support. It also provides an explanation of the core schemas used throughout, definitions of the simple and complex datatypes, plus the EML schemas themselves. It also covers the conventions used in the specification and the use of namespaces, as well as the guidance on the constraints, extendibility, and splitting of messages.
StandardebXML Messaging Services v3.0: Part 1, Core Features
Defines a communications-protocol neutral method for exchanging electronic business messages. It defines specific Web Services-based enveloping constructs supporting reliable, secure delivery of business information. Furthermore, the specification defines a flexible enveloping technique, permitting messages to contain payloads of any format type. This versatility ensures legacy electronic business systems employing traditional syntaxes (i.e. UN/EDIFACT, ASC X12, or HL7) can leverage the advantages of the ebXML infrastructure along with users of emerging technologies.
ebXML Messaging Services v3.0: Part 1, Core Features
Defines a communications-protocol neutral method for exchanging electronic business messages. It defines specific Web Services-based enveloping constructs supporting reliable, secure delivery of business information. Furthermore, the specification defines a flexible enveloping technique, permitting messages to contain payloads of any format type. This versatility ensures legacy electronic business systems employing traditional syntaxes (i.e. UN/EDIFACT, ASC X12, or HL7) can leverage the advantages of the ebXML infrastructure along with users of emerging technologies.
Produced by:
OASIS ebXML Messaging Services TCVoting history:
Produced by:
OASIS ebXML Business Process TCVoting history:
December 2006
No results with the selected filters