[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Scope of OpenC2
As stated, the question is ill-formed. The OpenC2 TC has three subcommittees – Language, Profiles, and Implementation. Each of those SCs has a set of documents on their roadmap. There shouldn’t be much disagreement on “what should and should not be done/defined in OpenC2”. The lively discussion on Slack concerns “what should be defined
in the OpenC2 Language Spec” and “what should be defined in the Implementation specifications”. When the question is framed in terms of scope of the subcommittee specifications, it will be ready to be debated and voted. Dave From: openc2@lists.oasis-open.org [mailto:openc2@lists.oasis-open.org]
On Behalf Of Bret Jordan TC, Over the past few weeks we have had some lively discussions on Slack. A lot of the debates come down to scope of what should and should not be done / defined in OpenC2. Some of this relates to interoperability,
some of it relates to functionality. I MOTION that we have a discussion at the TC level about scope and functionality and then have a ballot on it to decide. Areas I would like discussed:
If the OpenC2 TC decides that most of this is out of scope after a ballot then I will propose that a new TC be formed to tackle this higher level stuff. Bret |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]