Messaging
StandardEmergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0
An XML messaging standard primarily for exchange of information related to health facilities in the context of emergency management. HAVE supports sharing information about facility services, bed counts, operations, capacities, and resource needs so first responders, emergency managers, coordinating organizations, hospitals, care facilities, and the health community can provide each other with a coherent view of the health system.
Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0
An XML messaging standard primarily for exchange of information related to health facilities in the context of emergency management. HAVE supports sharing information about facility services, bed counts, operations, capacities, and resource needs so first responders, emergency managers, coordinating organizations, hospitals, care facilities, and the health community can provide each other with a coherent view of the health system.
Produced by:
OASIS Emergency Management TCVoting history:
March 2019
OASIS Standard:
Cite as:
Cite as:
[EDXL-HAVE-v2.0] Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0.
Edited by Darrell O’Donnell, Brian Wilkins, Rex Brooks, and Scott M. Robertson. 18 March 2019.
OASIS Committee Specification 02. HL7 Informative Document.
https://docs.oasis-open.org/emergency/edxl-have/v2.0/cs02/edxl-have-v2.0-cs02.html.
Latest version: https://docs.oasis-open.org/emergency/edxl-have/v2.0/edxl-have-v2.0.html.
StandardMQTT Version 5.0
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed 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 Version 5.0
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed 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:
March 2019
OASIS Standard:
Cite as:
Cite as:
[mqtt-v5.0]
MQTT Version 5.0. Edited by Andrew Banks, Ed Briggs, Ken Borgendale, and Rahul Gupta. 07 March 2019.
OASIS Standard. http://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html.
Latest version: http://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html.
StandardEmergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0
An XML messaging standard primarily for exchange of information related to health facilities in the context of emergency management. HAVE supports sharing information about facility services, bed counts, operations, capacities, and resource needs so first responders, emergency managers, coordinating organizations, hospitals, care facilities, and the health community can provide each other with a coherent view of the health system.
Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0
An XML messaging standard primarily for exchange of information related to health facilities in the context of emergency management. HAVE supports sharing information about facility services, bed counts, operations, capacities, and resource needs so first responders, emergency managers, coordinating organizations, hospitals, care facilities, and the health community can provide each other with a coherent view of the health system.
Produced by:
OASIS Emergency Management TCVoting history:
December 2018
OASIS Standard:
Cite as:
Cite as:
[EDXL-HAVE-v2.0] Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0.
Edited by Darrell O’Donnell, Brian Wilkins, Rex Brooks, and Scott M. Robertson. 13 December 2018.
OASIS Committee Specification 01. HL7 Informative Document.
https://docs.oasis-open.org/emergency/edxl-have/v2.0/cs01/edxl-have-v2.0-cs01.html.
Latest version: https://docs.oasis-open.org/emergency/edxl-have/v2.0/edxl-have-v2.0.html.
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:
September 2018
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 Iles Aymond. 21 September 2018. OASIS Committee Specification 02. http://docs.oasis-open.org/emergency/edxl-tep/v1.1/cs02/edxl-tep-v1.1-cs02.html. Latest version: http://docs.oasis-open.org/emergency/edxl-tep/v1.1/edxl-tep-v1.1.html.
Produced by:
OASIS Advanced Message Queuing Protocol (AMQP) TCVoting history:
September 2018
OASIS Standard:
Committee Specification 01
The work is covered by the RF on RAND Mode of the OASIS IPR Policy.
Cite as:
Cite as:
[soleconn-v1.0]
Advanced Message Queuing Protocol (AMQP) Enforcing Connection Uniqueness Version 1.0. Edited by Robert Godfrey. 17 September 2018. OASIS Committee Specification 01. http://docs.oasis-open.org/amqp/soleconn/v1.0/cs01/soleconn-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/amqp/soleconn/v1.0/soleconn-v1.0.html.
StandardUsing the AMQP Anonymous Terminus for Message Routing Version 1.0
An open internet protocol for business messaging. AMQP defines links as a unidirectional transport for messages between a source and a target. The target of a link identifies the node to which messages are to be sent to. If a large number of distinct destinations are in use, or if the destinations to be sent to are not known ahead of time (for example, they are provided as a reply-to in incoming messages) then creating a link per destination can be burdensome. This document defines a mechanism whereby a single outgoing link can be used to transfer messages which are then routed using the address carried in their “to” field.
Using the AMQP Anonymous Terminus for Message Routing Version 1.0
An open internet protocol for business messaging. AMQP defines links as a unidirectional transport for messages between a source and a target. The target of a link identifies the node to which messages are to be sent to. If a large number of distinct destinations are in use, or if the destinations to be sent to are not known ahead of time (for example, they are provided as a reply-to in incoming messages) then creating a link per destination can be burdensome. This document defines a mechanism whereby a single outgoing link can be used to transfer messages which are then routed using the address carried in their “to” field.
Produced by:
OASIS Advanced Message Queuing Protocol (AMQP) TCVoting history:
September 2018
OASIS Standard:
Cite as:
Cite as:
[anonterm-v1.0]
Using the AMQP Anonymous Terminus for Message Routing Version 1.0. Edited by Robert Godfrey. 17 September 2018. OASIS Committee Specification 01. http://docs.oasis-open.org/amqp/anonterm/v1.0/cs01/anonterm-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/amqp/anonterm/v1.0/anonterm-v1.0.html.
StandardMQTT Version 5.0
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed 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 Version 5.0
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed 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:
May 2018
OASIS Standard:
Cite as:
Cite as:
[mqtt-v5.0]
MQTT Version 5.0. Edited by Andrew Banks, Ed Briggs, Ken Borgendale, and Rahul Gupta. 15 May 2018.
OASIS Committee Specification 02. http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs02/mqtt-v5.0-cs02.html.
Latest version: http://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html.
StandardMQTT Version 5.0
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed 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 Version 5.0
A Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed 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:
December 2017
OASIS Standard:
Cite as:
Cite as:
[mqtt-v5.0]
MQTT Version 5.0. Edited by Andrew Banks, Ed Briggs, Ken Borgendale, and Rahul Gupta. 25 December 2017.
OASIS Committee Specification 01. http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs01/mqtt-v5.0-cs01.html.
Latest version: http://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html.
StandardBusiness Document Envelope Version 1.1
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.1
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:
December 2016
OASIS Standard:
Cite as:
Cite as:
[BDX-BDE-V1.1] Business Document Envelope Version 1.1. Edited by G. Ken Holman and Kenneth Bengtsson. 05 December 2016. OASIS Committee Specification 01. http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/cs01/bdx-bde-v1.1-cs01.html. Latest version: http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/bdx-bde-v1.1.html.
StandardEmergency Data Exchange Language Situation Reporting (EDXL-SitRep) Version 1.0
Describes a set of standard reports and elements that can be used for data sharing among emergency information systems, and that provide incident information for situation awareness on which incident command can base decisions.
Emergency Data Exchange Language Situation Reporting (EDXL-SitRep) Version 1.0
Describes a set of standard reports and elements that can be used for data sharing among emergency information systems, and that provide incident information for situation awareness on which incident command can base decisions.
Produced by:
OASIS Emergency Management TCVoting history:
October 2016
OASIS Standard:
Cite as:
Cite as:
[EDXL-SitRep]
Emergency Data Exchange Language Situation Reporting (EDXL-SitRep) Version 1.0. Edited by Rex Brooks, Timothy Grapes, Werner Joerg, and Jeff Waters. 06 October 2016. OASIS Committee Specification 02. http://docs.oasis-open.org/emergency/edxl-sitrep/v1.0/cs02/edxl-sitrep-v1.0-cs02.html. Latest version: http://docs.oasis-open.org/emergency/edxl-sitrep/v1.0/edxl-sitrep-v1.0.html.
StandardebCore Agreement Update Specification Version 1.0
Defines message exchanges and an XML schema to support the exchange of messaging service communication agreement update requests and the associated responses to such requests. The schema offers extensibility for various types of updates. The main initial application of the specification is the exchange of X.509 certificates for certificate rollover, for which a separate extension schema is provided. The specification is based on the concept of messaging service communication agreements and the creation of new agreements as independently identified updated copies of existing agreements. The specification also provides an Agreement Termination feature. The specification supports ebMS2, ebMS3 and AS4 but can also be used with other protocols that have a concept of communication agreement. The specification is independent of storage or interchange formats for configuration information.
ebCore Agreement Update Specification Version 1.0
Defines message exchanges and an XML schema to support the exchange of messaging service communication agreement update requests and the associated responses to such requests. The schema offers extensibility for various types of updates. The main initial application of the specification is the exchange of X.509 certificates for certificate rollover, for which a separate extension schema is provided. The specification is based on the concept of messaging service communication agreements and the creation of new agreements as independently identified updated copies of existing agreements. The specification also provides an Agreement Termination feature. The specification supports ebMS2, ebMS3 and AS4 but can also be used with other protocols that have a concept of communication agreement. The specification is independent of storage or interchange formats for configuration information.
Produced by:
OASIS ebXML Core (ebCore) TCVoting history:
September 2016
OASIS Standard:
Committee Specification 01
Agreement Update XML schema
Certificate Update XML schema
Schema Data Dictionaries
XML Signature 1.1 schema driver
XML document samples
Cite as:
Cite as:
[ebcore-au-v1.0]
ebCore Agreement Update Specification Version 1.0. Edited by Pim van der Eijk and Theo Kramer. 18 September 2016. OASIS Committee Specification 01.
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/ebcore-au-v1.0-cs01.html.
Latest version: http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/ebcore-au-v1.0.html.
Produced by:
OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TCVoting history:
August 2016
OASIS Standard:
Cite as:
Cite as:
[amqp-wsb-v1.0]
Advanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB) Version 1.0. Edited by John Fallows, David Ingham, and Robert Godfrey. 16 August 2016. OASIS Committee Specification 01. http://docs.oasis-open.org/amqp-bindmap/amqp-wsb/v1.0/cs01/amqp-wsb-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/amqp-bindmap/amqp-wsb/v1.0/amqp-wsb-v1.0.html.
No results with the selected filters