More than 1 year has passed since last update.

posted at

updated at


OpenChain仕様がISO国際標準になりました! / OpenChain Specification Became an ISO Standard!

*Please scroll down for the English version.


OpenChain Japan Advent Calendar 2020の2日目は、今年のメインテーマであるOpenChain仕様についてお届けします。






2020年12月現在のOpenChain仕様の最新バージョンはversion 2.1で、詳しくはOpenChain仕様バージョン2.1から参照できます。


バージョン名称 改訂時期
version 1.0 2016年10月
version 1.1 2017年4月
version 1.2 2018年4月
version 2.0 2019年4月
version 2.1(最新) 2020年12月

最新版のOpenChain仕様は、下記のような構成になっており、要件は3. Requirementsに記載されています。

1. Scope
2. Terms and definitions
3. Requirements
Appendix A(informative)

明日以降は、OpenChain Japanのメンバーが交代で、個々のRequirementsの解説と関連するトピックスについて投稿します。




Hello. If this is your first visit, nice to meet you. I think it is most likely your second time reading my article this December, right?
As the second day of OpenChain Japan Advent Calendar, today I will write about the OpenChain Specification, which is the main theme of this year.
I would like to skip my self introduction today because of my continuous posts, but if you are interested in that, please do read this.

Background (Issues in Software Supply Chains)

These days, OSS is essential for software development. It is even common to use hundreds to thousands of OSS components in one product or service. To develop software with advanced features by one single company has became very difficult, so a lot of companies have cooperated with each other and built software supply chains.
In a software supply chain, once an inappropriate use of OSS or an insufficient delivery of OSS license information occurs, it affects the entire supply chain. It comes to be claimed by the copyright holder or it is prohibited to distribute products.
In this situation, it is required to take control of problems at the upstream of the supply chain.

About OpenChain

To deal with those issues, the Open Chain Project has built an OSS compliance standard for every organization or company in supply chains to do things that they should do, build trust with each other, and deliver every necessary need (e.g. source code, license or documents).
One of the most important activities of the OpenChain Project is development and promotion of Open Chain Specification. The OpenChain Specification defines inflection points in business workflows where a compliance process, policy or training should exist to minimize the potential for errors and maximize the efficiency of bringing solutions to market. It can be used as a requirement for organizations to do OSS license compliance properly.

About OpenChain Specification

As of December this year, the latest version of OpenChain Specification is version 2.1. It is available at version 2.1.

The updated history of OpenChain Specification is below:

version update date
version 1.0 October 2016
version 1.1 April 2017
version 1.2 April 2018
version 2.0 April 2019
version 2.1(latest) December 2020

The contents of the latest version of OpenChain Specification is below:

1. Scope
2. Terms and definitions
3. Requirements
Appendix A(informative)

The key contents of Specification is written in chapter 3. From tomorrow, OpenChain Japan members will explain the contents of each requirement and related topics in turns.

The Next Topic is...

Osaki-san will explain the topics around OpenChain Specificatoin as an ISO Standard, the biggest news of this year.
See you tomorrow!!!

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
What you can do with signing up