OpenC2 Language Subcommittee

SC Page     Send a comment to this SC

Developing, maintaining, and resolving comments to the OpenC2 language documentation.

Completed

The OpenC2 Language Subcommittee operated from the TC’s founding in June 2017 through its charter revision in March 2021. Following the charter revision, subcommittee operations were suspended and a consolidated working meeting process adopted to manage the development of the TC’s work products. The information on these subcommittee pages is retained for historical purposes.

Statement of Purpose

This OpenC2 Language SC is responsible for the development, maintenance, and resolution of comments to the OpenC2 language documentation, including the language specification documents, use cases, JAEN specification, JSON specification, glossary, etc.

Background

The OpenC2 language is a standardized language for the command and control of technologies that provide or support cyber defenses. Future defense will require the integration of new functional blocks, coordination of responses between domains, synchronization of cyber defense mechanisms, and automated actions at machine speed against current and pending attacks. Standard interfaces and protocols are needed to facilitate the integration of components resulting in a more flexible and interoperable cyber defense system. A defined, standardized, and unambiguous machine-to-machine command and control language will help realize this vision.

All interested parties are welcome to participate in evolving the OpenC2 language as part of the Language SC under the main OASIS OpenC2 Technical Committee.

List of Deliverables

  • OpenC2 Language Specification
  • JSON Abstract Encoding Notation (JAEN) Specification
  • OpenC2 JAEN Schema
  • OpenC2 JSON Schema
  • OpenC2 Glossary
  • Other non-normative work products to increase adoption and improve the ease of use of the specification

Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.