Four new Project Specifications approved by the #OSLC Open Project

OASIS is pleased to announce that OSLC Core v3.0, OSLC Query v3.0, OSLC Requirements Management v2.1, and OSLC Change Management v3.0 from the Open Services for Lifecycle Collaboration Open Project [1] have been approved as an OASIS Project Specifications. These join the previously announced OSLC Quality Management v2.1 as the first approved Project Specifications from the Open Projects program.

Managing change and configuration in a complex systems development lifecycle is very difficult, especially in heterogeneous environments that include homegrown tools, open source projects, and commercial tools from different vendors. The OSLC initiative applies World Wide Web and Linked Data principles to enable interoperation of change, configuration, and asset management processes across a product’s entire application and product lifecycle.

OSLC Core defines the overall approach to Open Services for Lifecycle Collaboration based specifications and capabilities that extend and complement the W3C Linked Data Platform.

OSLC Query provides a mechanism for a client to search for RDF resources that match a given criteria.

OSLC Requirements Management support key RESTful web service interfaces for the management of Requirements, Requirements Collections and supporting resources defined in OSLC Core.

OSLC Change Management defines a RESTful web services interface for the management of product change requests, activities, tasks and relationships between those and related resources such as requirements, test cases, or architectural resources.

These Project Specifications are OASIS deliverables, completed and approved by the OP’s Project Governing Board and fully ready for testing and implementation. The applicable open source licenses can be found in the project’s administrative repository at https://github.com/oslc-op/oslc-admin/blob/master/LICENSE.md

The specifications and related files are available at:

* OSLC Core Version 3.0
Project Specification 01
17 September 2020

– OSLC Core Version 3.0. Part 1: Overview
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/oslc-core.html
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/oslc-core.pdf

– OSLC Core Version 3.0. Part 2: Discovery
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/discovery.html
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/discovery.pdf

– OSLC Core Version 3.0. Part 3: Resource Preview
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/resource-preview.html
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/resource-preview.pdf

– OSLC Core Version 3.0. Part 4: Delegated Dialogs
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/dialogs.html
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/dialogs.pdf

– OSLC Core Version 3.0. Part 5: Attachments
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/attachments.html
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/attachments.pdf

– OSLC Core Version 3.0. Part 6: Resource Shape
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/resource-shape.html
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/resource-shape.pdf

– OSLC Core Version 3.0. Part 7: Vocabulary
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/core-vocab.html
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/core-vocab.pdf

– OSLC Core Version 3.0. Part 8: Constraints
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/core-shapes.html
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/core-shapes.pdf

– OSLC Core Vocabulary definitions file:
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/core-vocab.ttl

– OSLC Core Resource Shape Constraints definitions file:
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/core-shapes.ttl

* OSLC Query Version 3.0
Project Specification 01
01 October 2020

https://docs.oasis-open-projects.org/oslc-op/query/v3.0/ps01/oslc-query.html
https://docs.oasis-open-projects.org/oslc-op/query/v3.0/ps01/oslc-query.pdf

* OSLC Requirements Management Version 2.1
Project Specification 01
03 September 2020

– OSLC Requirements Management Version 2.1. Part 1: Specification
https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps01/requirements-management-spec.html
https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps01/requirements-management-spec.pdf

– OSLC Requirements Management Version 2.1. Part 2: Vocabulary
https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps01/requirements-management-vocab.html
https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps01/requirements-management-vocab.pdf

– OSLC Requirements Management Version 2.1. Part 3: Constraints
https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps01/requirements-management-shapes.html
https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps01/requirements-management-shapes.pdf

– Requirements Management Vocabulary definitions file:
https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps01/requirements-management-vocab.ttl

– Requirements Management Resource Shape Constraints definitions file:
https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps01/requirements-management-shapes.ttl

* OSLC Change Management Version 3.0
Project Specification 01
17 September 2020

– OSLC Change Management Version 3.0. Part 1: Specification
https://docs.oasis-open-projects.org/oslc-op/cm/v3.0/ps01/change-mgt-spec.html
https://docs.oasis-open-projects.org/oslc-op/cm/v3.0/ps01/change-mgt-spec.pdf

– OSLC Change Management Version 3.0. Part 2: Vocabulary
https://docs.oasis-open-projects.org/oslc-op/cm/v3.0/ps01/change-mgt-vocab.html
https://docs.oasis-open-projects.org/oslc-op/cm/v3.0/ps01/change-mgt-vocab.pdf

– OSLC Change Management Version 3.0. Part 3: Constraints
https://docs.oasis-open-projects.org/oslc-op/cm/v3.0/ps01/change-mgt-shapes.html
https://docs.oasis-open-projects.org/oslc-op/cm/v3.0/ps01/change-mgt-shapes.pdf

– Change Management Vocabulary definitions file:
https://docs.oasis-open-projects.org/oslc-op/cm/v3.0/ps01/change-mgt-vocab.ttl

– Change Management Resource Shape Constraints definitions file:
https://docs.oasis-open-projects.org/oslc-op/cm/v3.0/ps01/change-mgt-shapes.ttl

Distribution ZIP file

For your convenience, OASIS provides complete packages of the specifications and related files in ZIP distribution files. You can download the ZIP files at:

OSLC Core: https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/core-v3.0-ps01.zip

OSLC Query: https://docs.oasis-open-projects.org/oslc-op/query/v3.0/ps01/query-v3.0-ps01.zip

OSLC Requirements Management: https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps01/rm-v2.1-ps01.zip

OSLC Change Management: https://docs.oasis-open-projects.org/oslc-op/cm/v3.0/ps01/cm-v3.0-ps01.zip

Members of the OSLC OP Project Governing Board approved these specifications by Special Majority Votes [2] as required by the Open Project rules [3].

Our congratulations to the participants and contributors in the Open Services for Lifecycle Collaboration Open Project on their achieving this milestone.

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

[1] Open Services for Lifecycle Collaboration Open Project
https://open-services.net/

[2] Approval ballots:

– Core Management: https://lists.oasis-open-projects.org/g/oslc-op-pgb/topic/vote_on_oslc_core_v3_0_1/76734933?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,76734933

– Query Management: https://lists.oasis-open-projects.org/g/oslc-op-pgb/topic/vote_on_oslc_query_version/76871816?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,76871816

– Requirements Management: https://lists.oasis-open-projects.org/g/oslc-op-pgb/topic/vote_on_oslc_requirements/76430414?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,76430414

– Change Management: https://lists.oasis-open-projects.org/g/oslc-op-pgb/topic/vote_on_oslc_core_v3_0_1/76734933?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,76734933

Invitation to comment on AMQP Request-Response Messaging with Link Pairing v1.0 – ends October 21

OASIS and the OASIS Advanced Message Queuing Protocol (AMQP) TC are pleased to announce that AMQP Request-Response Messaging with Link Pairing Version 1.0 is now available for public review and comment. This is the first public review for this specification.

AMQP defines links as unidirectional transport for messages between a source and a target. A common messaging pattern is that of “request-response”, that is, two parties partaking in a bidirectional conversation using messages. This document defines a common pattern for pairing two unidirectional links to create a bidirectional message transport between two endpoints.

The documents and related files are available here:

AMQP Request-Response Messaging with Link Pairing Version 1.0
Committee Specification Draft 01
20 August 2020

Editable source (Authoritative):
https://docs.oasis-open.org/amqp/linkpair/v1.0/csd01/linkpair-v1.0-csd01.docx

HTML:
https://docs.oasis-open.org/amqp/linkpair/v1.0/csd01/linkpair-v1.0-csd01.html

PDF:
https://docs.oasis-open.org/amqp/linkpair/v1.0/csd01/linkpair-v1.0-csd01.pdf

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:
https://docs.oasis-open.org/amqp/linkpair/v1.0/csd01/linkpair-v1.0-csd01.zip

How to Provide Feedback

OASIS and the AMQP 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 22 September 2020 at 00:00 UTC and ends 21 October 2020 at 23:59 UTC.

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=amqp).

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/amqp-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 [1] applicable especially [2] 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 AMQP TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/amqp/

Additional information related to this public review can be found in the public review metadata document [3].

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

[1] https://www.oasis-open.org/policies-guidelines/ipr

[2] https://www.oasis-open.org/committees/amqp/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-RAND-Mode
RF on RAND Mode

[3] Public review metadata document:
– https://docs.oasis-open.org/amqp/linkpair/v1.0/csd01/linkpair-v1.0-csd01-public-review-metadata.html

OpenTeams Podcast features OASIS

Guy Martin on measuring ROI of contributions and similarities between open standards and OSS.

Invitation to comment on Security Playbooks v1.0 – ends Sept. 30th

OASIS and the OASIS Collaborative Automated Course of Action Operations (CACAO) for Cyber Security TC are pleased to announce that Security Playbooks v1.0 is now available for public review and comment.

To defend against threat actors and their tactics, techniques, and procedures, organizations need to identify, create, document, and test detection, investigation, prevention, mitigation, and remediation steps. These steps, when grouped together, form a cyber security playbook that can be used to protect organizational systems, networks, data, and users.

This specification defines the schema and taxonomy for cybersecurity playbooks and how cybersecurity playbooks can be created, documented, and shared in a structured and standardized way across organizational boundaries and technological solutions.

The documents and related files are available here:

Security Playbooks Version 1.0
Committee Specification Draft 01
11 August 2020

Editable source (Authoritative):
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/csd01/security-playbooks-v1.0-csd01.docx
HTML:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/csd01/security-playbooks-v1.0-csd01.html
PDF:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/csd01/security-playbooks-v1.0-csd01.pdf

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:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/csd01/security-playbooks-v1.0-csd01.zip

How to Provide Feedback

OASIS and the CACAO 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 our technical work.

The public review starts 01 September 2020 at 00:00 UTC and ends 30 September 2020 at 23:59 UTC.

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=cacao).

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/cacao-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 [1] applicable especially [2] 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 CACAO TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/cacao/

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

[1] https://www.oasis-open.org/policies-guidelines/ipr

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

Invitation to comment on KMIP Specification v2.1 and KMIP Profiles v2.1 – ends Oct. 26th

OASIS and the OASIS Key Management Interoperability Protocol (KMIP) TC [1] are pleased to announce that KMIP Specification v2.1 Committee Specification 01 and KMIP Profiles v2.1 Committee Specification 01 are now available for public review and comment.

The TC members approved submitting these Committee Specifications to the OASIS membership for consideration as Candidate OASIS Standards, as described in the OASIS TC Process [6]. This is a 60-day public review, after which they may be submitted to a membership-wide call for consent to promote the specifications to OASIS Standards.

The Key Management Interoperability Protocol (KMIP) is a single, comprehensive protocol for communication between clients that request any of a wide range of encryption keys and servers that store and manage those keys. By replacing redundant, incompatible key management protocols, KMIP provides better data security while at the same time reducing expenditures on multiple products.

The KMIP Specification v2.1 is intended for developers and architects who wish to design systems and applications that interoperate using the Key Management Interoperability Protocol Specification.

KMIP Profiles v2.1 specifies conformance clauses that define the use of objects, attributes, operations, message elements and authentication methods within specific contexts of KMIP server and client interaction.

The TC has received 3 Statements of Use. They are from Cryptsoft, Primekey, and Utimaco [3].

The candidate specifications and related files are available here:

Key Management Interoperability Protocol Specification Version 2.1
Committee Specification 01
07 May 2020

Editable source (Authoritative):
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs01/kmip-spec-v2.1-cs01.docx
HTML:
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs01/kmip-spec-v2.1-cs01.html
PDF:
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs01/kmip-spec-v2.1-cs01.pdf
For your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:
https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs01/kmip-spec-v2.1-cs01.zip

Key Management Interoperability Protocol Profiles Version 2.1
Committee Specification 01
07 May 2020

Editable source (Authoritative):
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01.docx
HTML:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01.html
PDF:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01.pdf
Test cases:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/test-cases/
ZIP file:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01.zip

Public Review Period:

The 60-day public review starts immediately and ends 26 October 2020 at 23:59 UTC.

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility as explained in the instructions located via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:
https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
http://lists.oasis-open.org/archives/kmip-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 of KMIP Specification v2.1 and KMIP Profiles v2.1, 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 specifications, so that notice of them may be posted to the notice page for this TC’s work.

Additional information related to this public review can be found at:
– https://docs.oasis-open.org/kmip/kmip-spec/v2.1/cs01/kmip-spec-v2.1-cs01-public-review-metadata.html
– https://docs.oasis-open.org/kmip/kmip-profiles/v2.1/cs01/kmip-profiles-v2.1-cs01-public-review-metadata.html

==============

[1] OASIS Key Management Interoperability Protocol (KMIP) TC
https://www.oasis-open.org/committees/kmip/

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

[3] Statements of Use:
– Cryptsoft: https://lists.oasis-open.org/archives/kmip/202008/msg00004.html
– PrimeKey: https://lists.oasis-open.org/archives/kmip/202007/msg00000.html
– Utimaco: https://lists.oasis-open.org/archives/kmip/202008/msg00005.html

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

[5] http://www.oasis-open.org/committees/kmip/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-RAND-Mode
RF on RAND Terms Mode

[6] TC Process for OASIS Standard
https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OASISstandard

OASIS launches new ‘Open Matters Forum’

Check out episode 1 on YouTube.

Baseline Protocol Achieves Key Milestone with Release of v0.1 Implementation for Enterprise IT and the Ethereum Public Blockchain

BOSTON, MA, USA, August 26, 2020 — Today, the Baseline Protocol, an OASIS open source initiative, published the first major dot-release of its reference implementation, clearing the way for standards development.

Launched in March of this year, the Baseline Protocol uses advances in peer-to-peer messaging, zero-knowledge cryptography and blockchain technology to coordinate complex, confidential workflows between enterprises without moving company data out of traditional systems of record. Today, over 600 companies and individuals are actively participating in the initiative, which coordinates with the Enterprise Ethereum Alliance’s Mainnet Working Group.

Several proofs of concept have been released to showcase how to ‘baseline’ systems such as SAP, Microsoft Dynamics and Google Sheets. Recently, major brands have announced projects using the protocol, and more are known to be in private development.

Today’s release of Baseline Protocol v0.1 represents a significant milestone, because it provides a set of standard interfaces for developers to implement solutions easily and for vendors to provide their own modules that comply with the specification. Official OASIS standards development based on the v0.1 reference implementation will commence in September.

Today at 12pm US-ET, the development team will host an open walk-through of the system.

For more information go to https://www.baseline-protocol.org/releases/v01/

SUPPORT FOR BASELINE PROTOCOL v0.1

Ethereum OASIS is sponsored by the Enterprise Ethereum Alliance, Ethereum Foundation, ConsenSys, Chainlink, Nethermind, Provide, and Unibright.

Stefan Schmidt, CTO and Co-Founder of Unibright:

“Congratulations to all the contributors of release v.01, especially Kyle Thomas of Provide, Kartheek Solipuram of EY and Tomasz Stanczak of Nethermind. V.01 is defining a milestone for all those who aim to build products around the Baseline Protocol, as we at Unibright do. V0.1 will drive adoption for enterprise blockchain use cases on Ethereum.”

Kyle Thomas, CEO and Founder of Provide:

“Building v0.1 of the Baseline Protocol with the community has been a humbling experience. As of today’s release, contributing to this initiative means contributing to a new set of state-of-the-art business process automation standards that have the attention of some of the biggest brands in the world! I am looking forward to continued collaboration with all the talented individuals and organizations working on the Baseline Protocol and OASIS standard.”

Thomasz Stanczak, CTO and Founder of Nethermind:

“Baseline v0.1 is a big milestone – it combines great tools and guidance for data reconciliation in the world of integrated enterprise systems. At Nethermind we are excited that our solutions support the baseline protocol specification and help companies prevent delays and outages caused by mismatched data.”

Johann Eid, Chainlink Product Manager:

“Congratulations to Baseline for completing a major milestone by launching v0.1, showcasing that blockchain can serve as a valuable way of keeping systems of record in sync without the common concerns around data and business logic privacy. We look forward to helping Baseline continue to expand its capabilities by providing a framework for Baseline contracts to maintain synchronization when obtaining external data.”

Andrei Semenov, Coke One North America Services, Director of Innovation – Supply Chain:

“The release v0.1 is a great achievement for the Baseline community and a step towards building a steady foundation for the enterprise application on mainnet. My sincere congratulations to Provide, Unibright and other teams who contributed to the protocol.”

Paul Brody, EY Global Blockchain Leader:

“As a founding contributor to this program, EY is very pleased to see continued progress. EY teams will be implementing and tracking Baseline Protocol through the EY OpsChain and EY Blockchain Analyzer solutions as it evolves. We see this as critical infrastructure to enable secure, private, enterprise transactions going forward.”

About Ethereum OASIS

Founded by the Ethereum Foundation, the Enterprise Ethereum Alliance, and ConsenSys, Ethereum OASIS is an OASIS Open Project that provides a neutral forum for supporting open source projects and specifications that advance interoperability for blockchain applications worldwide. The Ethereum OASIS community works to develop clear, open standards, first-rate documentation, and shared test suites that facilitate new features and enhancements for Ethereum. Everyone is welcome to contribute to the Baseline Protocol, and suggestions for new Ethereum OASIS projects are encouraged.

For more information go to: https://github.com/ethereum-oasis/


Media inquiries: communications@oasis-open.org; +1.941.284.0403

Invitation to comment on five UBL Committee Note Drafts – ends Sept. 17th

OASIS members and other interested parties,

We are pleased to announce that five Committee Note Drafts are now available for public review and comment.

“UBL 2.1 JSON Alternative Representation Version 2.0” supplements the OASIS Universal Business Language version 2.1 release with an alternative expression of the UBL sample XML documents in JSON syntax, and a JSON schema expression of all 65 XSD schemas in conformance to the OASIS Business Document Naming and Design Rules Version 1.1.

“UBL 2.2 JSON Alternative Representation Version 1.0” supplements UBL 2.2 with a JSON schema expression of all 81 XSD schemas.

“UBL 2.3 JSON Alternative Representation Version 1.0” supplements UBL 2.3 with a JSON schema expression of all 81 XSD schemas.

“UBL Maintenance Governance Procedures Version 1.1” describes the governance of the process to propose, accept and incorporate changes to the OASIS Universal Business Language (UBL) 2 specifications.

“UBL Naming and Design Rules Version 3.1” describes the application of the OASIS Business Document Naming and Design Rules (NDR) to the OASIS UBL 2.3 specification.

The documents and related files are available here:

UBL 2.1 JSON Alternative Representation Version 2.0
Committee Note Draft 01
29 July 2020

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cnd01/UBL-2.1-JSON-v2.0-cnd01.xml
HTML:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cnd01/UBL-2.1-JSON-v2.0-cnd01.html
PDF:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cnd01/UBL-2.1-JSON-v2.0-cnd01.pdf
JSON examples:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cnd01/json/
JSON schemas:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cnd01/json-schema/
Validation test environment:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cnd01/val/
For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files.
ZIP file:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cnd01/UBL-2.1-JSON-v2.0-cnd01.zip
*********************

UBL 2.2 JSON Alternative Representation Version 1.0
Committee Note Draft 01
29 July 2020

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cnd01/UBL-2.2-JSON-v1.0-cnd01.xml
HTML:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cnd01/UBL-2.2-JSON-v1.0-cnd01.html
PDF:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cnd01/UBL-2.2-JSON-v1.0-cnd01.pdf
JSON examples:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cnd01/json/
JSON schemas:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cnd01/json-schema/
Validation test environment:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cnd01/val/
ZIP file:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cnd01/UBL-2.2-JSON-v1.0-cnd01.zip
*********************

UBL 2.3 JSON Alternative Representation Version 1.0
Committee Note Draft 01
29 July 2020

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cnd01/UBL-2.3-JSON-v1.0-cnd01.xml
HTML:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cnd01/UBL-2.3-JSON-v1.0-cnd01.html
PDF:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cnd01/UBL-2.3-JSON-v1.0-cnd01.pdf
JSON examples:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cnd01/json/
JSON schemas:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cnd01/json-schema/
Validation test environment:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cnd01/val/
ZIP file:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cnd01/UBL-2.3-JSON-v1.0-cnd01.zip
*********************

UBL Maintenance Governance Procedures Version 1.1
Committee Note Draft 01
29 July 2020

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/UBL-Governance/v1.1/cnd01/UBL-Governance-v1.1-cnd01.xml
HTML:
https://docs.oasis-open.org/ubl/UBL-Governance/v1.1/cnd01/UBL-Governance-v1.1-cnd01.html
PDF:
https://docs.oasis-open.org/ubl/UBL-Governance/v1.1/cnd01/UBL-Governance-v1.1-cnd01.pdf
ZIP file:
https://docs.oasis-open.org/ubl/UBL-Governance/v1.1/cnd01/UBL-Governance-v1.1-cnd01.zip
*********************

UBL Naming and Design Rules Version 3.1
Committee Note Draft 01
29 July 2020

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/UBL-NDR/v3.1/cnd01/UBL-NDR-v3.1-cnd01.xml
HTML:
https://docs.oasis-open.org/ubl/UBL-NDR/v3.1/cnd01/UBL-NDR-v3.1-cnd01.html
PDF:
https://docs.oasis-open.org/ubl/UBL-NDR/v3.1/cnd01/UBL-NDR-v3.1-cnd01.pdf
ZIP file:
https://docs.oasis-open.org/ubl/UBL-NDR/v3.1/cnd01/UBL-NDR-v3.1-cnd01.zip
*********************

How to Provide Feedback

OASIS and the UBL 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 our technical work.

The public review starts 19 August 2020 at 00:00 UTC and ends 17 September 2020 at 23:59 UTC.

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=ubl).

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/ubl-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 [1] applicable especially [2] 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 specifications and the UBL TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/ubl/

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

[1] https://www.oasis-open.org/policies-guidelines/ipr

[2] https://www.oasis-open.org/committees/ubl/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode
RF on Limited Terms Mode

Invitation to comment on Business Document Naming and Design Rules (BDNDR) v1.1 from the UBL TC – ends September 2nd

We are pleased to announce that Business Document Naming and Design Rules (BDNDR) Version 1.1 from the UBL TC [1] is now available for public review and comment. This is the second public review for BDNDR v1.1.

Overview:

An important and powerful method to design interoperable business documents is to construct logical semantic models using concepts described in the UN/CEFACT Core Components Technical Specification (CCTS) Version 2.01. From these semantic models one can create physical syntax models with which to express the content constraints of actual business documents to be interchanged.

The OASIS Business Document Naming and Design Rules (BDNDR) Version 1.1 Draft Specification prescribes a set of naming and design rules used to create complete CCTS models of interoperable business documents. It also includes the rules needed to create validation artefacts corresponding to them. For XML syntax, the rules govern creating W3C Schema (XSD) and OASIS Context/value Association (CVA) validation artefacts. For JSON syntax, the rules govern creating JSON Schema validation artefacts.

JSON is the _javascript_ Object Notation described by ISO/IEC 21778 Information technology — The JSON data interchange format, initially published at https://www.ecma-international.org/publications/standards/Ecma-404.htm as ECMA 404 The JSON data interchange format. JSON Schema is the vocabulary described at http://json-schema.org for annotating and validating JSON documents.

BDNDR Version 1.1 changes no rules for XML syntax from BDNDR Version 1.0 and only adds the new rules prescribed for JSON syntax.

The specification documents and related files are available here:

Business Document Naming and Design Rules (BDNDR) Version 1.1
Committee Specification Draft 03
29 July 2020

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/csd03/Business-Document-NDR-v1.1-csd03.xml
HTML:
https://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/csd03/Business-Document-NDR-v1.1-csd03.html
PDF:
https://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/csd03/Business-Document-NDR-v1.1-csd03.pdf

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 at:
https://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/csd03/Business-Document-NDR-v1.1-csd03.zip

How to Provide Feedback

OASIS and the UBL TC value your feedback. We solicit feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

This public review starts 19 August 2020 at 00:00 UTC and ends 02 September 2020 at 11:59 UTC.

This specification was previously submitted for public review [2]. This 15-day review may be limited in scope to changes made from the previous review. Changes are described in the previous comment resolution log [2] and highlighted in a 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=ubl).

Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/ubl-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 the public review of this work, 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 this specification and the UBL TC may be found on the TC’s public home page [1].

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

[1] OASIS Universal Business Language (UBL) TC
https://www.oasis-open.org/committees/ubl/

[2] Previous public reviews and comment resolution logs:
– Please see the “Timeline Summary” in the public review metadata document at:
https://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/csd03/Business-Document-NDR-v1.1-csd03-public-review-metadata.html

[3] Red-lined version:
https://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/csd03/Business-Document-NDR-v1.1-csd03-DIFF.pdf

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

[5] https://www.oasis-open.org/committees/ubl/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode
RF on Limited Terms Mode

Invitation to comment on Universal Business Language v2.3 from the UBL TC – ends September 2nd

We are pleased to announce that Universal Business Language Version 2.3 from the UBL TC [1] is now available for public review and comment. This is the third public review for Universal Business Language v2.3.

UBL is the leading interchange format for business documents. It is designed to operate within a standard business framework such as ISO/IEC 15000 (ebXML) to provide a complete, standards-based infrastructure that can extend the benefits of existing EDI systems to businesses of all sizes. The European Commission has declared UBL officially eligible for referencing in tenders from public administrations, and in 2015 UBL was approved as ISO/IEC 19845:2015.

Specifically, UBL provides:
– A suite of structured business objects and their associated semantics expressed as reusable data components and common business documents.
– A library of schemas for reusable data components such as Address, Item, and Payment, the common data elements of everyday business documents.
– A set of schemas for common business documents such as Order, Despatch Advice, and Invoice that are constructed from the UBL library components and can be used in generic procurement and transportation contexts.

UBL v2.3 is a minor revision to v2.2 that preserves backwards compatibility with previous v2.# versions. It adds five new document types, bringing the total number of UBL business documents to 86.

The specification documents and related files are available here:

Universal Business Language Version 2.3
Committee Specification Draft 03
29 July 2020

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/UBL-2.3.xml
HTML:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/UBL-2.3.html
PDF:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/UBL-2.3.pdf
Code lists for constraint validation:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/cl/
Context/value Association files for constraint validation:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/cva/
Document models of information bundles:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/mod/
Default validation test environment:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/val/
XML examples:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/xml/
Annotated XSD schemas:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/xsd/
Runtime XSD schemas:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/xsdrt/

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 at:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/UBL-2.3.zip

How to Provide Feedback

OASIS and the UBL TC value your feedback. We solicit feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

This public review starts 19 August 2020 at 00:00 UTC and ends 02 September 2020 at 11:59 UTC.

This specification was previously submitted for public review [2]. This 15-day review may be limited in scope to changes made from the previous review. Changes are described in the previous comment resolution log [2] and highlighted in a 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=ubl).

Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/ubl-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 the public review of this work, 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 this specification and the UBL TC may be found on the TC’s public home page [1].

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

[1] OASIS Universal Business Language (UBL) TC
https://www.oasis-open.org/committees/ubl/

[2] Previous public reviews and comment resolution logs:
– Please see the “Timeline Summary” in the public review metadata document at:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/UBL-2.3-csd03-public-review-metadata.html

[3] Red-lined version:
https://docs.oasis-open.org/ubl/csd03-UBL-2.3/csd03-UBL-2.3-DIFF.pdf

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

[5] https://www.oasis-open.org/committees/ubl/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode
RF on Limited Terms Mode

ISO Approves OASIS ebMS3 and AS4 as International Standards for Messaging

News Item – 28 July 2020 — Two OASIS Standards have been published as ISO international standards: ebXML Messaging version 3.0 (ebMS3) and Applicability Statement 4 (AS4). They will now become part 1 (ISO 15000-1) and part 2 (ISO 15000-2) of ISO 15000. While approved by ISO’s Technical Committee 154 (TC154) “Processes, data elements and documents in commerce, industry and administration,” the standards will continue to be maintained by OASIS.

ISO’s recognition allows ebMS3 and AS4 to be used in confidence as core elements of the digital infrastructure for the European Union’s future plans, and may be authorized for use in international legislation and public policy initiatives. Many governments and industries around the world rely on and trust standards published by ISO. This recognition is important for worldwide adoption and provides more confidence among users that the standards are safe and developed through a respected process.

The OASIS Technical Committee (TC) that maintains ebXML Messaging is one of the consortium’s longest running TCs. In 2016, ebMS3 and AS4 were included in a Commission Implementing Decision (EU) that enables governments in the European Union to reference the specifications in tenders for public procurement. AS4, the message exchange protocol, is part of Connecting Europe Facility (CEF) eDelivery Building Blocks to facilitate message transmission in an interoperable, secure way.

About OASIS

One of the most respected, member-driven standards bodies in the world, OASIS offers projects—including open source projects—a path to standardization and de jure approval for reference in international policy and procurement. OASIS members include major multinational companies, SMEs, government agencies, universities, research institutions, consulting groups, and individuals are represented.

Media inquiries
Carol Geyer
communications@oasis-open.org
+1.941.284.0403

OASIS Approves Four Public-Key Cryptography (PKCS) #11 Standards

Boston, MA, USA; 30 July 2020 – The OASIS international open standards consortium today announced that its members have approved four standards to enhance Public-Key Cryptography Standard (PKCS) #11, one of the most widely implemented cryptography standards in the world. The PKCS #11 standards are Version 3.0, and are now official OASIS Standards, a status that signifies the highest level of ratification.

PKCS #11, part of the PKCS family of standards, specifies a platform-independent application programming interface (API) for cryptographic tokens, such as hardware security modules and smart cards, which store and control authentication information, including personal identity, cryptographic keys, certificates, digital signatures, and biometric data. The API itself is named “Cryptoki” (from “cryptographic token interface” and pronounced as “crypto-key”).

The four approved PKCS #11 standards include:

● PKCS #11 Cryptographic Token Interface Base Specification Version 3.0, known as “Base Specification,” defines data types, functions, and other basic components of the PKCS #11 Cryptoki interface.

● PKCS #11 Cryptographic Token Interface Profiles Version 3.0, known as “Profiles,” is intended for developers and architects who wish to design systems and applications that conform to the PKCS #11 Cryptographic Token Interface standard.

● PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 3.0, known as “Current Mechanisms,” defines mechanisms that are anticipated for use with the current version of PKCS #11.

● PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 3.0, known as “Historical Mechanisms,” defines mechanisms for PKCS #11 that are no longer in general use.

“The approved PKCS #11 standards address the advances in cryptography by including new functions and mechanisms to protect data in the mobile and cloud space,” said Robert Relyea of Red Hat, co-chair of the OASIS PKCS #11 Technical Committee. “The standard is valued for helping keep transactions and data secure and has adapted to the latest IT deployment strategies.”

“We are pleased that the PKCS #11 standard continues to evolve, strengthening support for additional cryptographic algorithms and cryptographic technologies industry-wide,” added OASIS PKCS #11 co-chair, Tony Cox of Cryptsoft. “PKCS #11 is a versatile, interoperable standard that enables the secure and seamless integration of critical cybersecurity tools into the enterprise.”

Support for PKCS #11

Cryptsoft

“Cryptsoft has been a long-term supplier of cryptographic toolkits for many years and our commitment to the standardization of cryptographic technologies remains resolute. As our society continues to increase its use of cryptographic capabilities, the need to ensure cleaner, more consistent integrations also increases. The release of v3.0 of the PKCS #11 specification raises the bar further and is the culmination of years of hard work by the Technical Committee members towards ensuring that the standard continues to meet today’s requirements.”

— Tony Cox, VP Partners Alliances & Standards, Cryptsoft

nCipher

“In our hyper-connected world, standards-based access to secure cryptography has never been more important. nCipher, an Entrust Datacard company, is a strong advocate of open standards and has continued to support PKCS#11 since 1998 with the first release of its nShield HSM. We value the out-of-the-box integration it brings between our HSMs and vendor applications and are excited by the ratification of PKCS#11 v3.0. We look forward to enabling application vendors to take advantage of the new mechanisms and functions.”

— Kevin McKeogh, Vice President Product Management, nCipher, an Entrust Datacard Company

P6R

“P6R believes in standards and will continue to support the PKCS#11 standard in our PKCS#11 SDK’s, KMIP token and AWS CloudHSM products.”

— Jim Susoy, CEO, P6R Inc.


Additional Information

OASIS PKCS #11 Technical Committee: https://www.oasis-open.org/committees/pkcs11


About OASIS

One of the most respected, member-driven standards bodies in the world, OASIS offers projects—including open source projects—a path to standardization and de jure approval for reference in international policy and procurement. OASIS members include major multinational companies, SMEs, government agencies, universities, research institutions, consulting groups, and individuals are represented.


Media inquiries: communications@oasis-open.org; +1.941.284.0403

No results with the selected filters