NOTE: This wiki is provided by the OASIS standards consortium as a collaborative tool for members of the OASIS Open Command and Control (OpenC2) Technical Committee, who are permited to post to these pages. As this is an official workspace of the TC, the OASIS IPR Policy and other OASIS rules apply to its use. To learn more about the work of the TC, send a comment, or join this effort, visit the OASIS OpenC2 TC homepage.

Wiki pages are transient documents, so intermediate edits may not be saved. TC members should move all permanent work and stable artifacts to the TC's document repository, where the archival work product of the TC also can be viewed by the public.

OASIS Open Command and Control (OpenC2) TC Wiki

Why a wiki?

What is this wiki about? - It's for members of OpenC2 TC to share ideas as part of the creation of OpenC2 documents for standardization. Note the standards documents do not reside here on this wiki - they reside outside the wiki and are accessed thru normal OASIS web links. This wiki for for discussion, ideas, history, and information ancillary to the standards making process.

What is OpenC2?

For more info on openc2 - put some stuff here. Preferably link to a home page (we haven't made yet)

Many of draft documents are worked on in google docs. This is a summary google docs page that may be useful.

OpenC2 Face2Face Meetings

Sub Committees

The home pages for the Openc2 subcommittees are:

Products and Users

Use Cases

All of the work is driven by real needs, generally best expressed as use cases. All of the subcommittees probably will develop use cases specific to their needs, but the thought was to develop them visible to everyone. Use cases are documented in a TC GitHub repositority: OpenC2UseCases

Standing Rules

The OASIS OpenC2 Technical Committee has adopted the following standing rules to aid in the execution of the business of the Technical Committee. In particular, the standing rules are intended to ensure sufficient deliberation, prioritize the business brought before the committee, and aid in the progress of the effort. To the greatest extent practical, the subcommittees are operated at the discretion of subcommittee chairs, therefore these standing rules do not apply to the subcommittees.

SR-1: Suspension Of Standing Rules For The Duration Of The Meeting

  1. The rules of OASIS or Roberts Rule of Order cannot be suspended as they are not standing rules and always apply.
  2. During the course of a meeting, a standing rule may be suspended for the duration of a meeting. A motion to suspend a standing rule is not debatable and must be called to question immediately.
  3. The rule will be suspended if any of the following criteria are met:
    1. By a vote of 2/3 majority of the voting members present without prior notice
    2. By a simple majority vote of the voting members present with prior notice

SR-2: Consideration Of Artifacts Presented By A Subcommittee To The Committee As A Whole

  1. All artifacts must be provided to the Executive Secretary no later than seven business days prior to the meeting of the technical committee. The topic may be added to the agenda upon approval of the co-chairs or by proposal by members of the TC as described in Rule Three of these standing rules. If approved as an agenda item, the executive secretary will provide the artifacts to the members of the TC no later than three business days prior to the meeting of the technical committee.
  2. Prior to consideration, the chair will call for objections.
  3. Any member present may object. An objection must include a brief reason for the objection.
  4. Any other member present may support one or more objections.
  5. If a threshold of 25% or more of the members present object, then the committee will take it as sufficient cause to send the artifact back to the subcommittee for further deliberation.
  6. If the threshold is not met, then a motion to consider the artifact may proceed.
  7. If the artifact is called to question, then the voting members present may accept, reject or send the artifact back to the subcommittee for further deliberation.

SR-3: Consideration Of Agenda Items For Committee Meetings

  1. For items that are not artifacts as referenced in rule two, all members may propose agenda items to the technical committee by providing a summary of the item to the executive secretary no later than five days prior to the meeting.
  2. All agenda items are subject to the approval of the co-chairs.

SR-4: Election and Term of OpenC2 Co-chairs

  1. The Technical Committee (TC) and each subcommittee shall elect two co-chairs for a 24 month term.
  2. The period of each co-chair shall be offset by 12 months.
  3. The TC shall hold open elections in the month of March during the during the regular business meeting.
  4. All TC members (to include the incumbent co-chairs whose terms are up) are eligible for nomination for an office.
  5. In the event of a vacancy (such as a co-chair stepping down prior to the conclusion of their term), a replacement will be elected to complete the term.

Getting Started on Wiki

Interesting starting points:

How to use this site

A Wiki is a collaborative site, anyone can contribute and share:

To learn more about what a WikiWikiWeb is, read about MoinMoin:WhyWikiWorks and the MoinMoin:WikiNature. Also, consult the HelpMiscellaneous/FrequentlyAskedQuestions page.

This wiki is powered by MoinMoin.

FrontPage (last edited 2019-01-29 18:04:35 by dave.lemire)