Members of the OASIS Open Command and Control (OpenC2) TC create and manage technical content in this TC GitHub repository ( https://github.com/oasis-tcs/openc2-usecases ) as part of the TC's chartered work (i.e., the program of work and deliverables described in its charter).
This repository contains working materials for the OpenC2 TC. The use cases in this repository predate the OpenC2 Language Specification presented by OASIS for public review in October / November 2018. Any implementer of OpenC2 should consider these use cases as illustrative examples that may or may not conform to the current language specification.
OASIS TC GitHub repositories, as described in GitHub Repositories for OASIS TC Members' Chartered Work, are governed by the OASIS TC Process, IPR Policy, and other policies, similar to TC Wikis, TC JIRA issues tracking instances, TC SVN/Subversion repositories, etc. While they make use of public GitHub repositories, these TC GitHub repositories are distinct from OASIS TC Open Repositories, which are used for development of open source licensed content.
Note about GitHub repository name change: This repository was initially created on 2017-09-19 with the repository name change openc2-lsc-usecases but was changed to openc2-usecases on 2018-03-22, per the work order from the Executive Secretary. This change implemented the documented (consensus) proposal "... to rename the use case repo to remove its association with the Language SC and make clear that it is intended for OpenC2 use cases generally"
The purpose of this repository is to support description, elaboration, and review of use cases relevant to the chartered work of the OpenC2 Language Subcommittee.
The OpenC2 language is a standardized language for the command and control of technologies that provide or support cyber defenses. The OpenC2 Language Subcommittee is responsible for the development, maintenance, and resolution of comments to the OpenC2 language documentation, including the language specification documents, use cases, JAEN/JADN specification, JSON specification, glossary, etc.
As stated in this repository's CONTRIBUTING file, contributors to this repository are expected to be Members of the OASIS OpenC2 TC, for any substantive change requests. Anyone wishing to contribute to this GitHub project and participate in the TC's technical activity is invited to join as an OASIS TC Member. Public feedback is also accepted, subject to the terms of the OASIS Feedback License.
Please see the LICENSE file for description of the license terms and OASIS policies applicable to the TC's work in this GitHub project. Content in this repository is intended to be part of the OpenC2 TC's permanent record of activity, visible and freely available for all to use, subject to applicable OASIS policies, as presented in the repository LICENSE file.
This repository is to allow LSC members to contribute usecases in Markdown and use github for change approval and version control, should they desire. The intent is that this is an additonal method for submitting (with OASIS Wiki, documents on OASIS LSC site, and googledocs also being valid submission methods). Members are encouraged to submit use cases in any way they feel comfortable.
The organization is such that each member can contribute in a subdirectory with their company name. Should the LSC reach consensus on a set of use cases, then another directory can be created for the approved usecases. But the main intent is to let members create and share use cases of particular interest to them.
Please send questions or comments about OASIS TC GitHub repositories to Robin Cover and Chet Ensign. For questions about content in this repository, please contact the Co-Chairs as listed on the the OpenC2 TC's home page, or contact the Language Subcommittee Co-Chairs as listed on the OpenC2 Language Subcommittee home page.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent