This GitHub public repository ( https://github.com/oasis-open/openc2-compatibility ) was created at the request of the OASIS Open Command and Control (OpenC2) TC as an OASIS TC Open Repository to support development of open source resources related to Technical Committee work.
While this TC Open Repository remains associated with the sponsor TC, its development priorities, leadership, intellectual property terms, participation rules, and other matters of governance are separate and distinct from the OASIS TC Process and related policies.
All contributions made to this TC Open Repository are subject to open source license terms expressed in the CC-BY 4.0 license. That license was selected as the declared "Applicable License" when the TC Open Repository was created.
As documented in "Public Participation Invited", contributions to this OASIS TC Open Repository are invited from all parties, whether affiliated with OASIS or not. Participants must have a GitHub account, but no fees or OASIS membership obligations are required. Participation is expected to be consistent with the OASIS TC Open Repository Guidelines and Procedures, the open source LICENSE designated for this particular repository, and the requirement for an Individual Contributor License Agreement that governs intellectual property.
The purpose of this public GitHub repository is to capture OpenC2 core design principles and develop implementation guidelines for interoperable systems. OpenC2 is an evolving standard for computer and network security with continued refinement over language semantics. Development and adoption is hampered by the following "chicken and egg problem": The OpenC2 community will converge on language and protocols that work well in practice, but implementers need to agree on language and protocols to build interoperable systems.
This repository supports an attempt to bootstrap the process by capturing core design principles and suggesting implementation guidelines. In the short term, it is meant to act as an evolving reference guide to OpenC2 prototype implementers and provide a feedback mechanism to the OASIS OpenC2 Technical Committee and its Subcommittees.
This repository work is chartered as an open source effort in accordance with the Creative Commons Attribution 4.0 International License. The initial content will be imported from the JTC GitHub repository.
The OASIS OpenC2 Technical Committee was chartered to address matters as they pertain to command and control of cyber defense technologies, and to maintain a library of prototype implementations. The TC charter further specifies that the TC shall provide implementation guidance, as supported by assets in this GitHub reporitory.
Repository Maintainers may include here any clarifications — any additional sections, subsections, and paragraphs that the Maintainer(s) wish to add as descriptive text, reflecting (sub-) project status, milestones, releases, modifications to statement of purpose, etc. The project Maintainers will create and maintain this content on behalf of the participants.
TC Open Repository Maintainers are responsible for oversight of this project's community development activities, including evaluation of GitHub pull requests and preserving open source principles of openness and fairness. Maintainers are recognized and trusted experts who serve to implement community goals and consensus design preferences.
Initially, the associated TC members have designated one or more persons to serve as Maintainer(s); subsequently, participating community members may select additional or substitute Maintainers, per consensus agreements.
Questions or comments about this TC Open Repository's activities should be composed as GitHub issues or comments. If use of an issue/comment is not possible or appropriate, questions may be directed by email to the Maintainer(s) listed above. Please send general questions about TC Open Repository participation to OASIS Staff at firstname.lastname@example.org and any specific CLA-related questions to email@example.com.