Messaging
StandardEmergency Data Exchange Language (EDXL) Tracking of Emergency Patients (TEP) Version 1.1
An XML messaging standard primarily for exchange of emergency patient and tracking information from the point of patient encounter through definitive care admission or field release. TEP supports patient tracking across the Emergency Medical Services (EMS) care continuum, as well as hospital evacuations and patient transfers, providing real-time information to responders, Emergency Management, coordinating organizations and care facilities in the chain of care and transport.
Emergency Data Exchange Language (EDXL) Tracking of Emergency Patients (TEP) Version 1.1
An XML messaging standard primarily for exchange of emergency patient and tracking information from the point of patient encounter through definitive care admission or field release. TEP supports patient tracking across the Emergency Medical Services (EMS) care continuum, as well as hospital evacuations and patient transfers, providing real-time information to responders, Emergency Management, coordinating organizations and care facilities in the chain of care and transport.
Produced by:
OASIS Emergency Management TCVoting history:
January 2016
OASIS Standard:
Cite as:
Cite as:
[EDXL-TEP-v1.1] Emergency Data Exchange Language (EDXL) Tracking of Emergency Patients (TEP) Version 1.1. Edited by Werner Joerg and Patti Lles Aymond. 20 January 2016. OASIS Committee Specification 01. http://docs.oasis-open.org/emergency/edxl-tep/v1.1/cs01/edxl-tep-v1.1-cs01.html. Latest version: http://docs.oasis-open.org/emergency/edxl-tep/v1.1/edxl-tep-v1.1.html.
Produced by:
OASIS Open Data Protocol (OData) TCVoting history:
November 2015
OASIS Standard:
Committee Specification 02
OData Aggregation ABNF Construction Rules
OData Aggregation ABNF Test Cases
OData Aggregation Vocabulary
Cite as:
Cite as:
[OData-Data-Agg-v4.0] OData Extension for Data Aggregation Version 4.0. Edited by Ralf Handl, Hubert Heijkers, Gerald Krause, Michael Pizzo, and Martin Zurmuehl. 04 November 2015. OASIS Committee Specification 02. http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs02/odata-data-aggregation-ext-v4.0-cs02.html. Latest version: http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/odata-data-aggregation-ext-v4.0.html.
StandardBusiness Document Envelope Version 1.0
Defining a business-oriented artefact enveloping a payload of one or more business documents or other artefacts with supplemental semantic information about the collection of payloads as a whole. This is distinct from any transport-layer infrastructure envelope that may be required.
Business Document Envelope Version 1.0
Defining a business-oriented artefact enveloping a payload of one or more business documents or other artefacts with supplemental semantic information about the collection of payloads as a whole. This is distinct from any transport-layer infrastructure envelope that may be required.
Produced by:
OASIS Business Document Exchange (BDXR) TCVoting history:
August 2015
OASIS Standard:
Cite as:
Cite as:
[BDX-BDE-V1.0] Business Document Envelope Version 1.0. Edited by G. Ken Holman and Kenneth Bengtsson. 02 August 2015. OASIS Committee Specification 01. http://docs.oasis-open.org/bdxr/bdx-bde/v1.0/cs01/bdx-bde-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/bdxr/bdx-bde/v1.0/bdx-bde-v1.0.html.
StandardMQTT v3.1.1
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts.
MQTT v3.1.1
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts.
Produced by:
OASIS Message Queuing Telemetry Transport (MQTT) TCVoting history:
Voting History for OASIS Standard, October 2014
Voting History for Approved Errata 01, December 2015
Additional approvals
OASIS Standard:
OASIS Standard:
HTML
Approved Errata 01:
HTML
PDF
DOC
Cite as:
Cite as:
[mqtt-v3.1.1]MQTT Version 3.1.1. Edited by Andrew Banks and Rahul Gupta. 29 October 2014. OASIS Standard. http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html. Latest version: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html.
[mqtt-v3.1.1-errata01]MQTT Version 3.1.1 Errata 01. Edited by Andrew Banks and Rahul Gupta. 10 December 2015. OASIS Approved Errata. http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/errata01/os/mqtt-v3.1.1-errata01-os.html. Latest version: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/errata01/mqtt-v3.1.1-errata01.html.
[mqtt-v3.1.1-plus-errata01]MQTT Version 3.1.1 Plus Errata 01. Edited by Andrew Banks and Rahul Gupta. 10 December 2015. OASIS Standard Incorporating Approved Errata 01. http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/errata01/os/mqtt-v3.1.1-errata01-os-complete.html. Latest version: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html.
StandardOData v4.0
OData enables the creation and consumption of REST-based data services which allow resources, identified using Uniform Resource Locators (URLs) and defined in a data model, to be published and edited by Web clients using simple HTTP messages. OData helps create a more open, programmable Web, and simplifies the querying and sharing of data across applications for re-use in the enterprise, cloud, and mobile devices.
OData v4.0
OData enables the creation and consumption of REST-based data services which allow resources, identified using Uniform Resource Locators (URLs) and defined in a data model, to be published and edited by Web clients using simple HTTP messages. OData helps create a more open, programmable Web, and simplifies the querying and sharing of data across applications for re-use in the enterprise, cloud, and mobile devices.
Produced by:
OASIS Open Data Protocol (OData) TCVoting history:
Voting History for OASIS Standard, February 2014
Voting History for Approved Errata 01, September 2014
Voting History for Approved Errata 02, October 2014
Voting History for Approved Errata 03, June 2016
Additional approvals
OASIS Standard:
ABNF components
Vocabulary components
XML schemas
OData Metadata Service Entity Model
Approved Errata 01:
DOC
HTML
PDF
OASIS Standard incorporating Approved Errata 01:
DOC
HTML
PDF
ABNF components
Vocabulary components
XML schemas
OData Metadata Service Entity Model
Approved Errata 02:
DOC
HTML
PDF
OASIS Standard incorporating Approved Errata 02:
DOC
HTML
PDF
ABNF components
Vocabulary components
XML schemas
OData Metadata Service Entity Model
Approved Errata 03:
DOC
HTML
PDF
OASIS Standard incorporating Approved Errata 03:
DOC
HTML
PDF
ABNF components
Vocabulary components
XML schemas
OData Metadata Service Entity Model
Cite as:
StandardOData JSON Format v4.0
OData enables the creation and consumption of REST-based data services which allow resources, identified using Uniform Resource Locators (URLs) and defined in a data model, to be published and edited by Web clients using simple HTTP messages. This document extends the core specification by defining representations for OData requests and responses using a JSON format.
OData JSON Format v4.0
OData enables the creation and consumption of REST-based data services which allow resources, identified using Uniform Resource Locators (URLs) and defined in a data model, to be published and edited by Web clients using simple HTTP messages. This document extends the core specification by defining representations for OData requests and responses using a JSON format.
Produced by:
OASIS Open Data Protocol (OData) TCVoting history:
Voting History for OASIS Standard, February 2014
Voting History for Approved Errata 01, September 2014
Voting History for Approved Errata 02, October 2014
Voting History for Approved Errata 03, June 2016
Additional approvals
OASIS Standard:
Approved Errata 01:
DOC
HTML
PDF
OASIS Standard incorporating Approved Errata 01:
DOC
HTML
PDF
Approved Errata 02:
DOC
HTML
PDF
OASIS Standard incorporating Approved Errata 02:
DOC
HTML
PDF
Approved Errata 03:
DOC
HTML
PDF
OASIS Standard incorporating Approved Errata 03:
DOC
HTML
PDF
Cite as:
Cite as:
[OData-JSON-Format-v4.0]
OData JSON Format Version 4.0. Edited by Ralf Handl, Michael Pizzo, and Mark Biamonte. 24 February 2014. OASIS Standard. http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.html. Latest version: http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.html.
[OData-JSON-Format-v4.0]OData JSON Format Version 4.0 Plus Errata 01. Edited by Ralf Handl, Michael Pizzo, Martin Zurmuehl, and Mark Biamonte. 04 September 2014. OASIS Standard incorporating Approved Errata 01. http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata01/os/odata-json-format-v4.0-errata01-os-complete.html. Latest version: http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.html.
[OData-JSON-Format-v4.0-plus-Errata02]OData JSON Format Version 4.0 Plus Errata 02. Edited by Ralf Handl, Michael Pizzo, Martin Zurmuehl, and Mark Biamonte. 30 October 2014. OASIS Standard incorporating Approved Errata 02. http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata02/os/odata-json-format-v4.0-errata02-os-complete.html. Latest version: http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.html.
[OData-JSON-Format-v4.0-errata03]OData JSON Format Version 4.0 Errata 03. Edited by Ralf Handl, Michael Pizzo, and Martin Zurmuehl. 02 June 2016. OASIS Approved Errata. http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata03/os/odata-json-format-v4.0-errata03-os.html. Latest version: http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata03/odata-json-format-v4.0-errata03.html.
[OData-JSON-Format-v4.0]OData JSON Format Version 4.0 Plus Errata 03. Edited by Ralf Handl, Michael Pizzo, and Mark Biamonte. 02 June 2016. OASIS Standard incorporating Approved Errata 03. http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata03/os/odata-json-format-v4.0-errata03-os-complete.html. Latest version: http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.html.
StandardOData Atom Format Version 4.0
The Open Data Protocol (OData) for representing and interacting with structured content is comprised of a set of specifications. The core specification for the protocol is in OData Version 4.0 Part 1: Protocol. This document extends the core specification by defining representations for OData requests and responses using an Atom format.
OData Atom Format Version 4.0
The Open Data Protocol (OData) for representing and interacting with structured content is comprised of a set of specifications. The core specification for the protocol is in OData Version 4.0 Part 1: Protocol. This document extends the core specification by defining representations for OData requests and responses using an Atom format.
Produced by:
OASIS Open Data Protocol (OData) TCVoting history:
November 2013
OASIS Standard:
Cite as:
Cite as:
[OData-Atom-Format-v4.0] OData Atom Format Version 4.0. Edited by Martin Zurmuehl, Michael Pizzo, and Ralf Handl. 17 November 2013. OASIS Committee Specification 02. http://docs.oasis-open.org/odata/odata-atom-format/v4.0/cs02/odata-atom-format-v4.0-cs02.html. Latest version: http://docs.oasis-open.org/odata/odata-atom-format/v4.0/odata-atom-format-v4.0.html.
StandardEmergency Data Exchange Language (EDXL) Distribution Element Version 2.0
Describes a standard message distribution format for data sharing among emergency information systems. The DE 2.0 serves two important purposes:
(1) The DE 2.0 allows an organization to wrap separate but related pieces of emergency information, including any of the EDXL message types, into a single “package” for easier and more useful distribution;
(2) The DE 2.0 allows an organization to “address” the package to organizations or individuals with specified roles, located in specified locations or those interested in specified keywords.
This version of the DE expands the ability to use local community-defined terms, uses a profile of the Geographic Markup Language (GML) , follows best practices for naming conventions, provides the capability to link content objects, supports extensions, and is reorganized for increased flexibility and reuse of common types. The DE 2.0 packages and addresses emergency information for effective distribution with improved standardization and ability to be tailored for user needs.
Emergency Data Exchange Language (EDXL) Distribution Element Version 2.0
Describes a standard message distribution format for data sharing among emergency information systems. The DE 2.0 serves two important purposes:
(1) The DE 2.0 allows an organization to wrap separate but related pieces of emergency information, including any of the EDXL message types, into a single “package” for easier and more useful distribution;
(2) The DE 2.0 allows an organization to “address” the package to organizations or individuals with specified roles, located in specified locations or those interested in specified keywords.
This version of the DE expands the ability to use local community-defined terms, uses a profile of the Geographic Markup Language (GML) , follows best practices for naming conventions, provides the capability to link content objects, supports extensions, and is reorganized for increased flexibility and reuse of common types. The DE 2.0 packages and addresses emergency information for effective distribution with improved standardization and ability to be tailored for user needs.
Produced by:
OASIS Emergency Management TCVoting history:
September 2013
OASIS Standard:
Cite as:
Cite as:
[EDXL-DE-v2.0] Emergency Data Exchange Language (EDXL) Distribution Element Version 2.0. Edited by Jeff Waters. 19 September 2013. OASIS Committee Specification 02. http://docs.oasis-open.org/emergency/edxl-de/v2.0/cs02/edxl-de-v2.0-cs02.html. Latest version: http://docs.oasis-open.org/emergency/edxl-de/v2.0/edxl-de-v2.0.html.
StandardEmergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) v1.2 Australia (AU) Profile Version 1.0
Describes an interpretation of the OASIS CAP v1.2 standard necessary to meet the needs of the Australian Government.
Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) v1.2 Australia (AU) Profile Version 1.0
Describes an interpretation of the OASIS CAP v1.2 standard necessary to meet the needs of the Australian Government.
Produced by:
OASIS Emergency Management TCVoting history:
September 2013
OASIS Standard:
Cite as:
Cite as:
[EDXL-CAP-AU] Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) v1.2 Australia (AU) Profile Version 1.0. Edited by Gret Trott and Elysa Jones. 05 September 2013. OASIS Committee Specification 02. http://docs.oasis-open.org/emergency/edxl-cap1.2-au/v1.0/cs02/edxl-cap1.2-au-v1.0-cs02.html. Latest version: http://docs.oasis-open.org/emergency/edxl-cap1.2-au/v1.0/edxl-cap1.2-au-v1.0.html.
StandardAS4 Profile of ebMS 3.0 v1.0
The OASIS ebMS 3.0 Standard combined multiple Web Service standards to create a single comprehensive specification for defining the secure and reliable exchange of documents using Web Services. The AS4 profile of the ebMS 3.0 specification was developed in order to bring continuity to the principles and simplicity that made AS2 successful, while adding better compliance to Web Services standards, and features such as message pulling capability and a built-in Receipt mechanism.
AS4 Profile of ebMS 3.0 v1.0
The OASIS ebMS 3.0 Standard combined multiple Web Service standards to create a single comprehensive specification for defining the secure and reliable exchange of documents using Web Services. The AS4 profile of the ebMS 3.0 specification was developed in order to bring continuity to the principles and simplicity that made AS2 successful, while adding better compliance to Web Services standards, and features such as message pulling capability and a built-in Receipt mechanism.
Produced by:
OASIS ebXML Messaging Services TCVoting history:
January 2013
Additional approvals:
OASIS Standard:
Cite as:
Cite as:
[AS4-Profile ]
AS4 Profile of ebMS 3.0 Version 1.0. Edited by Jacques Durand and Pim van der Eijk. 23 January 2013. OASIS Standard. http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/os/AS4-profile-v1.0-os.html. Latest version: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html.
Produced by:
OASIS Advanced Message Queuing Protocol (AMQP) TCVoting history:
Voting History for OASIS Standard, October 2012
Additional approvals
OASIS Standard:
XML Document Type Definition (DTD)
The work is covered by the RF on RAND Mode of the OASIS IPR Policy.
Cite as:
Cite as:
[amqp-core-overview-v1.0]
OASIS Advanced Message Queuing Protocol (AMQP) Version 1.0 Part 0: Overview. Edited by Robert Godfrey, David Ingham, and Rafael Schloming. 29 October 2012. OASIS Standard. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-overview-v1.0-os.html. Latest version: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-overview-v1.0.html.
[amqp-core-types-v1.0]OASIS Advanced Message Queuing Protocol (AMQP) Version 1.0 Part 1: Types. Edited by Robert Godfrey, David Ingham, and Rafael Schloming. 29 October 2012. OASIS Standard. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-types-v1.0-os.html. Latest version: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-types-v1.0.html.
[amqp-core-transport-v1.0]OASIS Advanced Message Queuing Protocol (AMQP) Version 1.0 Part 2: Transport. Edited by Robert Godfrey, David Ingham, and Rafael Schloming. 29 October 2012. OASIS Standard. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html Latest version: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-transport-v1.0.html.
[amqp-core-messaging-v1.0]OASIS Advanced Message Queuing Protocol (AMQP) Version 1.0 Part 3: Messaging. Edited by Robert Godfrey, David Ingham, and Rafael Schloming. 29 October 2012. OASIS Standard. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html. Latest version: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-messaging-v1.0.html.
[amqp-core-transactions-v1.0]OASIS Advanced Message Queuing Protocol (AMQP) Version 1.0 Part 4: Transactions. Edited by Robert Godfrey, David Ingham, and Rafael Schloming. 29 October 2012. OASIS Standard. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transactions-v1.0-os.html. Latest version: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-transactions-v1.0.html.
[amqp-core-security-v1.0]OASIS Advanced Message Queuing Protocol (AMQP) Version 1.0 Part 5: Security. Edited by Robert Godfrey, David Ingham, and Rafael Schloming. 29 October 2012. OASIS Standard. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-security-v1.0-os.html. Latest version: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-security-v1.0.html.
StandardebXML RegRep v4.0
A a standard defining the service interfaces, protocols and information model for an integrated registry and repository. The repository stores digital content while the registry stores metadata that describes the content in the repository.
ebXML RegRep v4.0
A a standard defining the service interfaces, protocols and information model for an integrated registry and repository. The repository stores digital content while the registry stores metadata that describes the content in the repository.
Produced by:
OASIS ebXML Registry TCVoting history:
January 2012
Additional approvals:
OASIS Standard:
This OASIS Standard is composed of the following files:
- Part 0: Overview Document
HTML
PDF
ODT - Part 1: Registry Information Model (ebRIM)
HTML
PDF
ODT - Part 2: Services and Protocols (ebRS)
HTML
PDF
ODT - Part 3: XML Schema
- Part 4: WSDL
- Part 5: XML Definitions
- Distribution ZIP file containing the complete package of the prose specification and related files
Cite as:
No results with the selected filters