Akoma Ntoso Naming Convention V1.0 OASIS Standard published

OASIS is pleased to announce the publication of its newest OASIS Standard, approved by the members on 21 February 2019:

Akoma Ntoso Naming Convention Version 1.0
OASIS Standard
21 February 2019

The OASIS LegalDocML TC works to advance worldwide best practices for the use of XML within a Parliaments’, Assembly’s or Congress’ document management processes, within courts’ and tribunals’ judgment management systems, and generally in legal documents including contracts. The work is based on the Akoma Ntoso, a project sponsored by the United Nations.

Akoma Ntoso means “linked hearts” in the Akan language of West Africa. For legal publishers and makers of legal information systems, Akoma Ntoso provides a framework for creating machine-readable parliamentary, legislative and judiciary documents such as legislation, debate records, minutes, judgments, etc. In doing so, it helps build a strong foundation for open access to government information.

This Naming Convention provides the rules for defining IRIs and ids used in the Akoma Ntoso XML standard.

The prose specifications and related files are available here:

HTML (Authoritative):
http://docs.oasis-open.org/legaldocml/akn-nc/v1.0/os/akn-nc-v1.0-os.html

Editable source:
http://docs.oasis-open.org/legaldocml/akn-nc/v1.0/os/akn-nc-v1.0-os.doc

PDF:
http://docs.oasis-open.org/legaldocml/akn-nc/v1.0/os/akn-nc-v1.0-os.pdf

Distribution ZIP files

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/legaldocml/akn-nc/v1.0/os/akn-nc-v1.0-os.zip

Our congratulations to the members of the LegalDocML TC on achieving this milestone.

RSA 2019 Features Multi-vendor Key Management Interoperability Protocol (KMIP) Demonstrations

March 5, 2019–At RSA 2019, members of the OASIS international consortium collaborate to provide live multi-vendor interoperability demonstrations featuring one of the industry’s most widely-adopted security standards, the Key Management Interoperability Protocol (KMIP). The demos are being held from 4-7 March, in Booth 543.

“With the latest revision of the KMIP Specification (v2.0) now complete and fully tested, it is great to have six of the Technical Member organizations providing a live demonstration of encryption key management activities to RSA Conference attendees,” said Tony Cox of Cryptsoft, co-chair of the OASIS KMIP Technical Committee and Lead for the KMIP Interop event. “This demonstration is showing the latest features of the KMIP standard including new capabilities, improved performance, scalability, automation and a wide range of security administration capabilities such as Quantum Safe usage and PKCS #11 profiles.”

Six companies collaborate to demonstrate the latest KMIP v2.0 capabilities during the RSA show. The demonstration includes interchange of security objects as well as provision of encryption keys and cryptographic services across a common interface. OASIS KMIP Technical Committee members, Cryptsoft, P6R, QuintessenceLabs, Semper Fortis Solutions, Thales eSecurity, and Utimaco are among the participating companies. The live demonstrations show the full key management lifecycle including creating, registering, locating, retrieving, deleting, and transferring symmetric and asymmetric keys and certificates between vendor systems. RSA visitors to the OASIS booth will witness live demonstrations of interoperable encryption keys and security object management interchange between every member.

For the latest in the KMIP development process, see https://www.oasis-open.org/committees/kmip.

Thoughts from the participants

Cryptsoft CTO, Tim Hudson, said, “Interoperability between key management, hardware security, and encryption systems is no longer ‘nice-to-have’ but essential. The latest OASIS KMIP v2.0 standard provides capabilities to address fundamental interoperability requirements, enabling migration from single point ad-hoc products to full enterprise security solutions. As a major OEM technology supplier, supplying standards-based solutions ensures interoperability is a reality for our customers.”

P6R CEO, Jim Susoy, said, “P6R is strongly committed to standards-based technologies. Our participation in the OASIS interop underscores that commitment and addresses the fundamental requirement of interoperability. As a technology leader, P6R provides conformant KMIP and PKCS#11 technologies that our customers can count on to be interoperable. P6R is committed to promoting and supporting the OASIS KMIP standard.”

QuintessenceLabs CTO, John Leiseboer, said, “QuintessenceLabs has been involved with OASIS and the KMIP Technical Committee since the beginning, enabling our quantum-enhanced technology to be easy to use and integrate. Interoperability benefits customers and empowers them to control their security, which is increasingly important for organizations building quantum resilience.”

Thales eSecurity Sr Dir, Product and Solutions Marketing, Charles Goldberg, said, “Thales is an originating author of KMIP and a dedicated supporter. We are pleased to see our customers and partners leveraging KMIP for far more than tape archives; now big data, flash array storage, hyper-converged infrastructure, and cloud use cases are driving deployments. We are proud to be demonstrating our excellent interoperability results for the KMIP v2.0 working draft and the current v1.4 standard.”

About OASIS

OASIS is a nonprofit consortium that advances open standards and open source development on a global scale. It offers standards and open source projects a path to recognition in international policy and procurement. Any initiative for developing code, APIs, specifications, or reference implementations can find a home at OASIS. Each project operates independently under industry-approved process and IPR policies. Some of the most widely adopted standards are developed at OASIS including: KMIP, STIX, TAXII, OpenC2, and SAML. Many of these have gone on to be published as ISO, IEC, or ITU standards. New work is encouraged, and all are welcome to participate. OASIS members can be found in 100+ countries on virtually every continent. Major multinational companies, SMEs, government agencies, universities, research institutions, consulting groups, and individuals are represented.

Press contact communications@oasis-open.org

Akoma Ntoso Naming Convention V1.0 becomes an OASIS Standard

OASIS is pleased to announce that Akoma Ntoso Naming Convention Version 1.0 has been approved by the membership as an OASIS Standard [1].

The ballot was held under the OASIS call for consent procedure [2]. Under this procedure, consent is assumed unless eligible voters register valid objections. In the ballot, Akoma Ntoso Naming Convention V1.0 received 6 affirmative consents and no objections. Therefore the standard is approved.

To find out more about what Akoma Ntoso Naming Convention V1.0 is and why it might matter to you, see the context discussion in the specification at https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.html#_Toc531692262

TC Administration will now prepare and publish the final OASIS Standard and notify members when it is available.

Our congratulations to the members of the TC and to the community of implementers, developers and users who have brought the work successfully to this milestone

=== Additional information

[1] Ballot:
https://www.oasis-open.org/committees/ballot.php?id=3306

[2] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

[3] Call for consent

https://lists.oasis-open.org/archives/members/201902/msg00002.html

[4] URLs to the latest published version:

Akoma Ntoso Naming Convention Version 1.0
Candidate OASIS Standard 01
03 December 2018

https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.html (Authoritative)

https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.doc

https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.pdf

Call for Consent for MQTT V5.0 as OASIS Standard

The OASIS Message Queuing Telemetry Transport (MQTT) TC members [1] have approved submitting the following Candidate OASIS Standard to the OASIS Membership in a call for consent for OASIS Standard:

MQTT Version 5.0
Candidate OASIS Standard 02
11 February 2019

This is a call to the primary or alternate representatives of OASIS Organizational Members to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however, your consent is assumed unless you register an objection [2]. To register an objection, you must:

1. Indicate your objection on this ballot, and

2. Provide a reason for your objection and/or a proposed remedy to the TC.

You may provide the reason in the comment box or by email to the Technical Committee on its comment mailing list or, if you are a member of the TC, to the TC’s mailing list [2]. If you provide your reason by email, please indicate in the subject line that this is in regard to the Call for Consent.

This Committee Specification was approved by the Technical Committee and was submitted for the required 60-day public review [3]. All requirements of the OASIS TC Process having been met [4][5], the Candidate OASIS Standard is now submitted to the voting representatives of OASIS Organizational Members.

— Details —

The Call for Consent opens on 22 February 2019 at 00:00 UTC and closes on 07 March 2019 at 23:59 pm timezone. You can access the ballot at:

Internal link for voting members: https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=3308

Publicly visible link: https://www.oasis-open.org/committees/ballot.php?id=3308

OASIS members should ensure that their organization’s voting representative responds according to the organization’s wishes. If you do not know the name of your organization’s voting representative is, go to the My Account page at

http://www.oasis-open.org/members/user_tools

then click the link for your Company (at the top of the page) and review the list of users for the name designated as “Primary”.

— Information about the Candidate OASIS Standard and the MQTT TC —

MQTT is a client/server publish/subscribe messaging transport protocol. It is lightweight, 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 where a small code footprint is required and/or network bandwidth is at a premium.

The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections.

The TC received 4 Statements of Use from HiveMQ, IBM, the Eclipse Paho Project, and VerneMQ [2].

URIs
The prose specification document and related files are available here:

Editable Source (Authoritative):
https://docs.oasis-open.org/mqtt/mqtt/v5.0/cos02/mqtt-v5.0-cos02.docx

HTML:
https://docs.oasis-open.org/mqtt/mqtt/v5.0/cos02/mqtt-v5.0-cos02.html

PDF:
https://docs.oasis-open.org/mqtt/mqtt/v5.0/cos02/mqtt-v5.0-cos02.pdf

Distribution ZIP files:

For your convenience, OASIS provides a complete package of the prose specifications and related files in a ZIP distribution file. You can download the ZIP file here:

https://docs.oasis-open.org/mqtt/mqtt/v5.0/cos02/mqtt-v5.0-cos02.zip

— Additional information —

[1] OASIS Message Queuing Telemetry Transport (MQTT) TC
https://www.oasis-open.org/committees/mqtt/

TC IPR page
https://www.oasis-open.org/committees/mqtt/ipr.php

https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

[2] MQTT TC comment mailing list: mqtt-comment@lists.oasis-open.org
(You must be subscribed to send to this list. To subscribe, see https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=mqtt.)

MQTT main mailing list: mqtt@lists.oasis-open.org

[3] Candidate OASIS Standard Special Majority Vote:
https://www.oasis-open.org/committees/ballot.php?id=3264

Candidate OASIS Standard Special Majority Vote 02:
https://www.oasis-open.org/committees/ballot.php?id=3300

[4] Public reviews:

– 30-day public review, 10 August 2017:
https://lists.oasis-open.org/archives/members/201708/msg00004.html
– Comment resolution log:
http://docs.oasis-open.org/mqtt/mqtt/v5.0/csprd01/mqtt-v5.0-csprd01-comment-resolution-log.doc

– 15-day public review, 17 November 2017:
https://lists.oasis-open.org/archives/members/201711/msg00005.html
– Comment resolution log:
http://docs.oasis-open.org/mqtt/mqtt/v5.0/csprd02/mqtt-v5.0-csprd02-comment-resolution-log.docx

– 60-day public review, 16 November 2018:
https://lists.oasis-open.org/archives/members/201811/msg00003.html
– Comment resolution log:
http://docs.oasis-open.org/mqtt/mqtt/v5.0/cos01/mqtt-v5.0-cos01-comment-resolution-log.txt

[5] Statements of Use:

HiveMQ:
https://www.oasis-open.org/apps/org/workgroup/mqtt/email/archives/201807/msg00001.html

IBM:
https://www.oasis-open.org/apps/org/workgroup/mqtt/email/archives/201807/msg00002.html

Eclipse Paho Project:
https://lists.oasis-open.org/archives/mqtt-comment/201808/msg00000.html

VerneMQ:
https://lists.oasis-open.org/archives/mqtt-comment/201807/msg00000.html

Invitation to comment on Service Metadata Publishing (SMP) Version 2.0 – ends March 12th

We are pleased to announce that Service Metadata Publishing (SMP) Version 2.0 from the BDXR TC [1] is now available for public review and comment. This is the second public review for SMP v2.0.

SMP v2.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 (endpoint) of the business document, such as types of documents the endpoint 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.

The documents and related files are available here:

Service Metadata Publishing (SMP) Version 2.0
Committee Specification Draft 02 / Public Review Draft 02
30 January 2019

Editable source (Authoritative):
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd02/bdx-smp-v2.0-csprd02.docx
HTML:
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd02/bdx-smp-v2.0-csprd02.html
PDF:
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd02/bdx-smp-v2.0-csprd02.pdf

XML schemas and documentation:
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd02/xsd/
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd02/xsdrt/
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd02/mod/

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd02/bdx-smp-v2.0-csprd02.zip

How to Provide Feedback

OASIS and the OASIS Business Document Exchange (BDXR) TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

The public review starts February 12 at 00:00 UTC and ends March 12, 2019 at 23:59 UTC.

This specification was previously submitted for public review [2]. This 30-day review is limited in scope to changes made from the previous review. Changes are highlighted in red-lined file included in the package [3].

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=bdxr).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:

https://lists.oasis-open.org/archives/bdxr-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

Additional information about the specification and the BDXR TC can be found at the TC’s public home page [1].

========== Additional references:
[1] OASIS Business Document Exchange (BDXR) TC
http://www.oasis-open.org/committees/bdxr/

[2] Previous public review:
– 30-day public review, 25 July 2018:
https://lists.oasis-open.org/archives/bdxr/201807/msg00008.html
– Comment resolution log:
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd01/bdx-smp-v2.0-csprd01-comment-resolution-log.xlsx

[3] Red-lined version:
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd02/bdx-smp-v2.0-csprd02-DIFF.pdf

[4] http://www.oasis-open.org/policies-guidelines/ipr

[5] http://www.oasis-open.org/committees/bdxr/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode

Call for Consent for Akoma Ntoso Naming Convention V1.0 as OASIS Standard

The OASIS LegalDocumentML (LegalDocML) TC members [1] have approved submitting the following Candidate OASIS Standard to the OASIS Membership in a call for consent for OASIS Standard:

Akoma Ntoso Naming Convention Version 1.0
Candidate OASIS Standard 01
03 December 2018

This is a call to the primary or alternate representatives of OASIS Organizational Members to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however, your consent is assumed unless you register an objection [2]. To register an objection, you must:

1. Indicate your objection on this ballot, and

2. Provide a reason for your objection and/or a proposed remedy to the TC.

You may provide the reason in the comment box or by email to the Technical Committee on its comment mailing list or, if you are a member of the TC, to the TC’s mailing list [3]. If you provide your reason by email, please indicate in the subject line that this is in regard to the Call for Consent.

This Committee Specification was approved by the Technical Committee and was submitted for the required 60-day public review [4]. All requirements of the OASIS TC Process having been met [5][6], the Candidate OASIS Standard is now submitted to the voting representatives of OASIS Organizational Members.

— Details —

The Call for Consent opens on 08 February 2019 00:00 UTC and closes on 21 February 2019 23:59 pm timezone. You can access the ballot at:

Internal link for voting members: https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=3306

Publicly visible link: https://www.oasis-open.org/committees/ballot.php?id=3306

OASIS members should ensure that their organization’s voting representative responds according to the organization’s wishes. If you do not know the name of your organization’s voting representative is, go to the My Account page at

http://www.oasis-open.org/members/user_tools

then click the link for your Company (at the top of the page) and review the list of users for the name designated as “Primary”.

— Information about the Candidate OASIS Standard and the LegalDocML TC —

The OASIS LegalDocML TC works to advance worldwide best practices for the use of XML within a Parliaments’, Assembly’s or Congress’ document management processes, within courts’ and tribunals’ judgment management systems, and generally in legal documents including contracts. The work is based on the Akoma Ntoso, a project sponsored by the United Nations.

Akoma Ntoso means “linked hearts” in the Akan language of West Africa. For legal publishers and makers of legal information systems, Akoma Ntoso provides a framework for creating machine-readable parliamentary, legislative and judiciary documents such as legislation, debate records, minutes, judgments, etc. In doing so, it helps build a strong foundation for open access to government information.

URIs
The prose specification document and related files are available here:

HTML (Authoritative):
https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.html

PDF:
https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.pdf

Editable source:
https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.doc

Distribution ZIP files:

For your convenience, OASIS provides a complete package of the prose specifications and related files in a ZIP distribution file. You can download the ZIP file here:

https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.zip

— Additional information —

[1] OASIS LegalDocumentML (LegalDocML) TC
https://www.oasis-open.org/committees/legaldocml/

TC IPR page
https://www.oasis-open.org/committees/legaldocml/ipr.php

[2] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

[3] LegalDocML TC comment mailing list: legaldocml-comment@lists.oasis-open.org (You must be subscribed to send to this list. To subscribe, see https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=legaldocml .)

LegalDocML TC main mailing list: legaldocml@lists.oasis-open.org

[4] Candidate OASIS Standard Special Majority Vote:
https://www.oasis-open.org/committees/ballot.php?id=3272

[5] Public reviews:

60-day public review, 07 December 2018:
https://lists.oasis-open.org/archives/members/201812/msg00002.html
– Comment resolution log:
https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01-comment-resolution-log.txt

15-day public review, 25 April 2017:
https://lists.oasis-open.org/archives/legaldocml/201704/msg00011.html
– Comment resolution log:
http://docs.oasis-open.org/legaldocml/akn-nc/v1.0/csprd03/akn-nc-v1.0-csprd03-comment-resolution-log.txt

15-day public review, 10 June 2016:
https://lists.oasis-open.org/archives/legaldocml/201606/msg00002.html
– Comment resolution log:
http://docs.oasis-open.org/legaldocml/akn-nc/v1.0/csprd02/akn-v1.0-csprd02-comment-resolution-log.xls

30-day public review, 07 May 2015:
https://lists.oasis-open.org/archives/legaldocml/201505/msg00004.html
– Comment resolution logs:
http://docs.oasis-open.org/legaldocml/akn-nc/v1.0/csprd01/akn-v1.0-csprd01-comment-resolution-log.xls
http://docs.oasis-open.org/legaldocml/akn-nc/v1.0/csprd01/akn-v1.0-csprd01-TAB-comment-resolution-log.xlsx

[6] Statements of Use:

– Food and Agriculture Organization of the United Nations (FAO): https://www.oasis-open.org/apps/org/workgroup/legaldocml/download.php/64234/latest/1.Statement%20of%20use%20-%20FAO_letter_20180

– Xcential Corporation: https://www.oasis-open.org/apps/org/workgroup/legaldocml/download.php/64235/latest/2.StatementOfUse-Xcential-nc.pdf

– CIRSFID, University of Bologna: https://www.oasis-open.org/apps/org/workgroup/legaldocml/download.php/64236/latest/3.StatementOfUse-CIRSFID-UNIBO-nc.pdf

Classification of Everyday Living v1.0 OASIS Standard published

OASIS is pleased to announce the publication of its newest OASIS Standard, approved by the members on 23 January 2019:

Classification of Everyday Living Version 1.0
OASIS Standard
23 January 2019

The OASIS COEL specification provides a privacy-by-design framework for the collection and processing of behavioural data. It is uniquely suited to the transparent use of dynamic data for personalised digital services, IoT applications where devices are collecting information about identifiable individuals, and the coding of behavioural data in identity solutions. The specification pseudonymises personal data at the source and maintains a separation of different data types with clearly defined roles and responsibilities for all actors. All behavioural data are defined as event-based packets. Every packet is connected directly to an individual and can contain a summary of the consent they provided for the processing of the data. A combination of a taxonomy of all human behaviours (the COEL model) and the event-based protocol provide a universal template for data portability. Simple interface specifications enforce the separation of roles and provide system-level interoperability.

The prose specifications and related files are available here:

Editable source (Authoritative):
https://docs.oasis-open.org/coel/COEL/v1.0/os/COEL-v1.0-os.docx
HTML:
https://docs.oasis-open.org/coel/COEL/v1.0/os/COEL-v1.0-os.html
PDF:
https://docs.oasis-open.org/coel/COEL/v1.0/os/COEL-v1.0-os.pdf
COEL JSON model:
https://docs.oasis-open.org/coel/COEL/v1.0/os/model/
JSON schemas:
https://docs.oasis-open.org/coel/COEL/v1.0/os/schemas/

Distribution ZIP files

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:
https://docs.oasis-open.org/coel/COEL/v1.0/os/COEL-v1.0-os.zip

Our congratulations to the members of the OASIS Classification of Everyday Living (COEL) TC on achieving this milestone.

TOSCA Simple Profile in YAML v1.2 OASIS Standard published

OASIS is pleased to announce the publication of its newest OASIS Standard, approved by the members on 17 January 2019:

TOSCA Simple Profile in YAML Version 1.2
OASIS Standard
17 January 2019

The TOSCA TC works to enhance the portability and operational management of cloud applications and services across their entire lifecycle.

YAML is a human friendly data serialization standard with a syntax much easier to read and edit than XML. The TOSCA Simple Profile in YAML specifies a rendering of TOSCA which aims to provide a more accessible syntax as well as a more concise and incremental expressiveness of the TOSCA DSL (Domain Specific Language) in order to minimize the learning curve and speed the adoption of the use of TOSCA to portably describe cloud applications.

The prose specifications and related files are available here:

PDF (Authoritative):
https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/os/TOSCA-Simple-Profile-YAML-v1.2-os.pdf

HTML:
https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/os/TOSCA-Simple-Profile-YAML-v1.2-os.html

Editable source:
https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/os/TOSCA-Simple-Profile-YAML-v1.2-os.docx

Distribution ZIP files

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/os/TOSCA-Simple-Profile-YAML-v1.2-os.zip

Our congratulations to the members of the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC on achieving this milestone.

Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0 from Emergency TC approved as a Committee Specification

OASIS is pleased to announce that Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0 from the OASIS Emergency Management TC [1] has been approved as an OASIS Committee Specification.

EDXL-HAVE (HAVE) is 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.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 2.0
Committee Specification 01
Proposed HL7® Informative Document
13 December 2018

Editable source (Authoritative):
https://docs.oasis-open.org/emergency/edxl-have/v2.0/cs01/edxl-have-v2.0-cs01.doc
HTML:
https://docs.oasis-open.org/emergency/edxl-have/v2.0/cs01/edxl-have-v2.0-cs01.html
PDF:
https://docs.oasis-open.org/emergency/edxl-have/v2.0/cs01/edxl-have-v2.0-cs01.pdf
XML schemas:
https://docs.oasis-open.org/emergency/edxl-have/v2.0/cs01/schema/

Distribution ZIP file
For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:
https://docs.oasis-open.org/emergency/edxl-have/v2.0/cs01/edxl-have-v2.0-cs01.zip

Members of the Emergency Management TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

========== Additional references:

[1] OASIS Emergency Management TC
https://www.oasis-open.org/committees/emergency/

[2] Public reviews:
* 60-day public review, 16 March 2015:
https://lists.oasis-open.org/archives/emergency/201503/msg00011.html
* 30-day public review, 11 September 2017:
https://lists.oasis-open.org/archives/emergency/201709/msg00004.html
– Comment resolution log:
https://docs.oasis-open.org/emergency/edxl-have/v2.0/csprd02/edxl-have-v2.0-csprd02-comment-resolution-log.docx
* 15-day public review, 16 August 2018:
https://lists.oasis-open.org/archives/emergency/201808/msg00014.html
– Comment resolution log:
https://docs.oasis-open.org/emergency/edxl-have/v2.0/csprd03/edxl-have-v2.0-csprd03-comment-resolution-log.txt

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3284

SAML V2.0 Subject Identifier Attributes Profile v1.0 from SAML TC approved as a Committee Specification

OASIS is pleased to announce that SAML V2.0 Subject Identifier Attributes Profile Version 1.0 from the OASIS Security Services (SAML) TC [1] has been approved as an OASIS Committee Specification.

Security Assertion Markup Language (SAML), developed by the Security Services Technical Committee of OASIS, is an XML-based framework for communicating user authentication, entitlement and attribute information. As its name suggests, SAML allows business entities to make assertions regarding the identity, attributes, and entitlements of a subject to other entities, such as a partner company or another enterprise application.

The SAML V2.0 Subject Identifier Attributes Profile specification standardizes two new SAML Attributes to identify security subjects, as a replacement for long-standing inconsistent practice with the and constructs. It also addresses recognized deficiencies with the SAML V2.0 urn:oasis:names:tc:SAML:2.0:nameid-format:persistent Name Identifier format.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

SAML V2.0 Subject Identifier Attributes Profile Version 1.0
Committee Specification 01
16 January 2019

Editable source (Authoritative):
https://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/cs01/saml-subject-id-attr-v1.0-cs01.odt
HTML:
https://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/cs01/saml-subject-id-attr-v1.0-cs01.html
PDF:
https://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/cs01/saml-subject-id-attr-v1.0-cs01.pdf
XML schema:
https://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/cs01/schema/saml-subject-id-attr-v1.0.xsd

Distribution ZIP file
For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:
https://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/cs01/saml-subject-id-attr-v1.0-cs01.zip

Members of the SAML TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

========== Additional references:

[1] OASIS Security Services (SAML) TC
https://www.oasis-open.org/committees/security/

[2] Public reviews:
* 30-day public review, 13 November 2017:
https://lists.oasis-open.org/archives/security-services/201711/msg00004.html
– Comment resolution log:
http://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/csprd01/saml-subject-id-attr-v1.0-csprd01-comment-resolution-log.txt
* 15-day public review, 20 April 2018:
https://lists.oasis-open.org/archives/security-services/201804/msg00006.html
– Comment resolution log:
http://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/csprd02/saml-subject-id-attr-v1.0-csprd02-comment-resolution-log.txt
* 15-day public review, 18 October 2018:
https://lists.oasis-open.org/archives/security-services/201810/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/csprd03/saml-subject-id-attr-v1.0-csprd03-comment-resolution-log.txt

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3293

Learn about the U.S. TAG to ISO/PC 317 – Consumer protection

See who is involved and find out more about the U.S. Technical Advisory Group (TAG) to ISO Project Committee 317 – Consumer protection: privacy by design for consumer goods and services.

Classification of Everyday Living V1.0 (#COEL) becomes an OASIS Standard

OASIS is pleased to announce that Classification of Everyday Living Version 1.0 has been approved by the membership as an OASIS Standard [1].

The ballot was held under the OASIS call for consent procedure [2]. Under this procedure, consent is assumed unless eligible voters register valid objections. In the ballot, Classification of Everyday Living V1.0 received 12 affirmative consents and no objections. Therefore the standard is approved.

Digital technologies are becoming integral to our daily lives. They promise
huge benefits to society, but the data they create carries the potential for
abuse.

COEL is a hierarchical taxonomy of everyday human life events. It provides a privacy-by-design framework for collecting and processing behavioral data that is uniquely suited to the transparent use of dynamic data for personalized digital services, IoT
applications where devices are collecting information about identifiable
individuals, and the coding of behavioral data in identity solutions.

COEL aims to be a roadmap for collecting and handling personal data that protects the interests of both individuals and businesses.

To find out more, see the TC’s home page at https://www.oasis-open.org/committees/coel/.

TC Administration will now prepare and publish the final OASIS Standard and notify members when it is available.

Our congratulations to the members of the TC and to the community of implementers, developers, and users who have brought the work successfully to this milestone

=== Additional information

[1] Ballot:
https://www.oasis-open.org/committees/ballot.php?id=3292

[2] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

[3] Call for consent

https://lists.oasis-open.org/archives/members/201901/msg00003.html

[4] URLs to the latest published version:

Classification of Everyday Living Version 1.0
Candidate OASIS Standard 01
18 October 2018

Editable source (Authoritative):
http://docs.oasis-open.org/coel/COEL/v1.0/cos01/COEL-v1.0-cos01.docx

HTML:
http://docs.oasis-open.org/coel/COEL/v1.0/cos01/COEL-v1.0-cos01.html

PDF:
http://docs.oasis-open.org/coel/COEL/v1.0/cos01/COEL-v1.0-cos01.pdf

COEL model v1.0:
http://docs.oasis-open.org/coel/COEL/v1.0/cos01/model/coel.json

Schemas for Behavioural Atom Specification and Public Query Interface (PQI):
http://docs.oasis-open.org/coel/COEL/v1.0/cos01/schemas/

Distribution ZIP files:

For your convenience, OASIS provides a complete package of the prose specifications and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/coel/COEL/v1.0/cos01/COEL-v1.0-cos01.zip

No results with the selected filters