OASIS Committee/Project Specification
Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0
Defines JSON and XML based request/response protocols for signing and verifying documents and other data. It also defines a timestamp format, and a signature property for use with these protocols. Finally, it defines transport and security bindings for the protocols.
Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0
Defines JSON and XML based request/response protocols for signing and verifying documents and other data. It also defines a timestamp format, and a signature property for use with these protocols. Finally, it defines transport and security bindings for the protocols.
Produced by:
OASIS Digital Signature Services eXtended (DSS-X) TCVoting history:
July 2019
OASIS Standard:
Cite as:
Cite as:
[DSS-v2.0]
Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0. Edited by Andreas Kuehne and Stefan Hagen. 04 July 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/dss-x/dss-core/v2.0/cs01/dss-core-v2.0-cs01.html. Latest version: https://docs.oasis-open.org/dss-x/dss-core/v2.0/dss-core-v2.0.html.
Digital Signature Service Metadata Version 1.0
Defines JSON and XML structures and discovery mechanisms for metadata related to digital signature services.
Digital Signature Service Metadata Version 1.0
Defines JSON and XML structures and discovery mechanisms for metadata related to digital signature services.
Produced by:
OASIS Digital Signature Services eXtended (DSS-X) TCVoting history:
July 2019
OASIS Standard:
Cite as:
Cite as:
[DSS-MD-v1.0]
Digital Signature Service Metadata Version 1.0. Edited by Detlef Hühnlein and Andreas Kuehne. 04 July 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/dss-x/dss-md/v1.0/cs01/dss-md-cs01.html. Latest version: https://docs.oasis-open.org/dss-x/dss-md/v1.0/dss-md-v1.0.html.
Service Metadata Publishing (SMP) Version 2.0
Describes a protocol for publishing service metadata within a 4-corner network. In a 4-corner network, entities are exchanging business documents through intermediary gateway services (sometimes called Access Points). To successfully send a business document in a 4-corner network, an entity must be able to discover critical metadata about the recipient of the business document, such as types of documents the recipient is capable of receiving and methods of transport supported. The recipient makes this metadata available to other entities in the network through a Service Metadata Publisher service. This specification describes the request/response exchanges between a Service Metadata Publisher and a client wishing to discover endpoint information. A client can either be an end-user business application or a gateway/access point in the 4-corner network. It also defines the request processing that must happen at the client.
Service Metadata Publishing (SMP) Version 2.0
Describes a protocol for publishing service metadata within a 4-corner network. In a 4-corner network, entities are exchanging business documents through intermediary gateway services (sometimes called Access Points). To successfully send a business document in a 4-corner network, an entity must be able to discover critical metadata about the recipient of the business document, such as types of documents the recipient is capable of receiving and methods of transport supported. The recipient makes this metadata available to other entities in the network through a Service Metadata Publisher service. This specification describes the request/response exchanges between a Service Metadata Publisher and a client wishing to discover endpoint information. A client can either be an end-user business application or a gateway/access point in the 4-corner network. It also defines the request processing that must happen at the client.
Produced by:
OASIS Business Document Exchange (BDXR) TCVoting history:
May 2019
OASIS Standard:
Committee Specification 01
XML schema
XML schema
Model documentation
Namespaces:
http://docs.oasis-open.org/bdxr/ns/SMP/2/ServiceGroup
http://docs.oasis-open.org/bdxr/ns/SMP/2/ServiceMetadata
http://docs.oasis-open.org/bdxr/ns/SMP/2/AggregateComponents
http://docs.oasis-open.org/bdxr/ns/SMP/2/BasicComponents
http://docs.oasis-open.org/bdxr/ns/SMP/2/ExtensionComponents
http://docs.oasis-open.org/bdxr/ns/SMP/2/QualifiedDataTypes
http://docs.oasis-open.org/bdxr/ns/SMP/2/UnqualifiedDataTypes
Cite as:
Cite as:
[BDX-SMP-v2.0] Service Metadata Publishing (SMP) Version 2.0. Edited by Kenneth Bengtsson, Erlend Klakegg Bergheim, Sander Fieten, and G. Ken Holman. 20 May 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs01/bdx-smp-v2.0-cs01.html. Latest version: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/bdx-smp-v2.0.html.
Electronic Court Filing Web Services Service Interaction Profile Version 5.0
Defines a Service Interaction Profile, as defined in section 6 of the LegalXML Electronic Court Filing Version 5.0 (ECF 5.0) specification. The Web Services Service Interaction Profile may be used to transmit ECF 5.0 messages between Internet-connected systems.
Electronic Court Filing Web Services Service Interaction Profile Version 5.0
Defines a Service Interaction Profile, as defined in section 6 of the LegalXML Electronic Court Filing Version 5.0 (ECF 5.0) specification. The Web Services Service Interaction Profile may be used to transmit ECF 5.0 messages between Internet-connected systems.
Produced by:
OASIS LegalXML Electronic Court Filing TCVoting history:
April 2019
OASIS Standard:
Cite as:
[ECF-WS-SIP-v5.0] Electronic Court Filing Web Services Service Interaction Profile Version 5.0. Edited by James Cabral, Gary Graham, and Philip Baughman. 24 April 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.0/cs01/ecf-webservices-v5.0-cs01.html. Latest version: https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.0/ecf-webservices-v5.0.html.
Cross-Enterprise Security and Privacy Authorization (XSPA) Profile of SAML v2.0 for Healthcare Version 2.0
Defines a set of SAML attributes and corresponding vocabularies for healthcare information exchange applications.
Cross-Enterprise Security and Privacy Authorization (XSPA) Profile of SAML v2.0 for Healthcare Version 2.0
Defines a set of SAML attributes and corresponding vocabularies for healthcare information exchange applications.
Produced by:
OASIS Cross-Enterprise Security and Privacy Authorization (XSPA) TCVoting history:
April 2019
OASIS Standard:
Cite as:
Cite as:
[SAML-XSPA-v2.0] Cross-Enterprise Security and Privacy Authorization (XSPA) Profile of SAML v2.0 for Healthcare Version 2.0. Edited by John M. Davis, Duane DeCouteau, and Mohammad Jafari. 23 April 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/xspa/saml-xspa/v2.0/cs01/saml-xspa-v2.0-cs01.html. Latest version: https://docs.oasis-open.org/xspa/saml-xspa/v2.0/saml-xspa-v2.0.html.
Electronic Court Filing Version 5.0
Consists of a set of non-proprietary XML and Web services specifications developed to promote interoperability among electronic court filing vendors and systems. ECF v5.0 is a major release that adds new functionality and capabilities beyond the scope of the ECF 4.0 and 4.01 specifications that it supersedes.
Electronic Court Filing Version 5.0
Consists of a set of non-proprietary XML and Web services specifications developed to promote interoperability among electronic court filing vendors and systems. ECF v5.0 is a major release that adds new functionality and capabilities beyond the scope of the ECF 4.0 and 4.01 specifications that it supersedes.
Produced by:
OASIS LegalXML Electronic Court Filing TCVoting history:
April 2019
OASIS Standard:
Committee Specification 01
XML schemas and Genericode code lists
XML example messages
Model and documentation
UML model artifacts
Cite as:
[ECF-v5.0] Electronic Court Filing Version 5.0. Edited by James Cabral, Gary Graham, and Philip Baughman. 18 April 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/cs01/ecf-v5.0-cs01.html. Latest version: https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/ecf-v5.0.html.
Virtual I/O Device (VIRTIO) Version 1.1
Describes the specifications of the “virtio” family of devices. These devices are found in virtual environments, yet by design they look like physical devices to the guest within the virtual machine – and this document treats them as such. This similarity allows the guest to use standard drivers and discovery mechanisms.
The purpose of virtio and this specification is that virtual environments and guests should have a straightforward, efficient, standard and extensible mechanism for virtual devices, rather than boutique per-environment or per-OS mechanisms.
Virtual I/O Device (VIRTIO) Version 1.1
Describes the specifications of the “virtio” family of devices. These devices are found in virtual environments, yet by design they look like physical devices to the guest within the virtual machine – and this document treats them as such. This similarity allows the guest to use standard drivers and discovery mechanisms.
The purpose of virtio and this specification is that virtual environments and guests should have a straightforward, efficient, standard and extensible mechanism for virtual devices, rather than boutique per-environment or per-OS mechanisms.
Produced by:
OASIS Virtual I/O Device (VIRTIO) TCVoting history:
April 2019
OASIS Standard:
Cite as:
Cite as:
[VIRTIO-v1.1]
Virtual I/O Device (VIRTIO) Version 1.1. Edited by Michael S. Tsirkin and Cornelia Huck. 11 April 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/virtio/virtio/v1.1/cs01/virtio-v1.1-cs01.html. Latest version: https://docs.oasis-open.org/virtio/virtio/v1.1/virtio-v1.1.html.
Exchange Header Envelope (XHE) Version 1.0
Defines a business-oriented artefact either referencing (as a header) or containing (as an envelope) 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 header or envelope that may be required to propagate documents from one system to another. An exchange header envelope describes contextual information important to the sender and receiver about the payloads, without having to modify the payloads in any fashion.
Exchange Header Envelope (XHE) Version 1.0
Defines a business-oriented artefact either referencing (as a header) or containing (as an envelope) 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 header or envelope that may be required to propagate documents from one system to another. An exchange header envelope describes contextual information important to the sender and receiver about the payloads, without having to modify the payloads in any fashion.
Produced by:
OASIS Business Document Exchange (BDXR) TCVoting history:
March 2019
OASIS Standard:
Cite as:
Cite as:
[XHE-V1.0] Exchange Header Envelope (XHE) Version 1.0. Edited by G. Ken Holman. 21 March 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/bdxr/xhe/v1.0/cs01/xhe-v1.0-cs01-oasis.html. Latest version: https://docs.oasis-open.org/bdxr/xhe/v1.0/xhe-v1.0-oasis.html.
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.
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.
SAML V2.0 Subject Identifier Attributes Profile Version 1.0
Standardizes two new SAML Attributes to identify security subjects, as a replacement for long-standing inconsistent practice with the and constructs, and to address recognized deficiencies with the SAML V2.0 urn:oasis:names:tc:SAML:2.0:nameid-format:persistent Name Identifier format.
SAML V2.0 Subject Identifier Attributes Profile Version 1.0
Standardizes two new SAML Attributes to identify security subjects, as a replacement for long-standing inconsistent practice with the
Produced by:
Security Services (SAML) TCVoting history:
January 2019
OASIS Standard:
Cite as:
Cite as:
[SAML-SubjectID-v1.0] SAML V2.0 Subject Identifier Attributes Profile Version 1.0. Edited by Scott Cantor.
16 January 2019. OASIS Committee Specification 01.
https://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/cs01/saml-subject-id-attr-v1.0-cs01.html.
Latest version: https://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/saml-subject-id-attr-v1.0.html.
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.
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.
JSON Profile of XACML 3.0 Version 1.1
Define a standardized interface between a policy enforcement point and a policy decision point using JSON. The decision request and response structure is specified in the core XACML specification. This profile leverages it.
JSON Profile of XACML 3.0 Version 1.1
Define a standardized interface between a policy enforcement point and a policy decision point using JSON. The decision request and response structure is specified in the core XACML specification. This profile leverages it.
Produced by:
OASIS eXtensible Access Control Markup Language (XACML) TCVoting history:
December 2018
OASIS Standard:
Cite as:
Cite as:
[xacml-json-v1.1]
JSON Profile of XACML 3.0 Version 1.1. Edited by David Brossard and Steven Legg. 05 December 2018. OASIS Committee Specification 01.
https://docs.oasis-open.org/xacml/xacml-json-http/v1.1/cs01/xacml-json-http-v1.1-cs01.html.
Latest version: https://docs.oasis-open.org/xacml/xacml-json-http/v1.1/xacml-json-http-v1.1.html.
No results with the selected filters