Agree with Duncan in this matter. Suggest we keep the OpenC2.org page static and have a link to the OASIS open repo
From: firstname.lastname@example.org [mailto:email@example.com]
On Behalf Of firstname.lastname@example.org
Sent: Monday, January 22, 2018 2:15 PM
To: dave.lemire <email@example.com>
Cc: firstname.lastname@example.org; Chet Ensign <email@example.com>; Robin Cover <firstname.lastname@example.org>
Subject: [Non-DoD Source] RE: [openc2-imple] Proposal for an open repository for "general info"
I'd propose we 'develop' the webpages under OASIS in an OASIS repo following their rules.
Where we get the content from is up to us (so using previous
openc2.org is one potential and valuable source - albeit it needs updating).
Unless the owner of the domain (which btw is G2 so you get a say in it) gives
openc2.org to OASIS, then I propose
openc2.org be the one linked to OASIS not vice versa. Ie if we maintain repos under OASIS rules and develop the content, then owner of
openc2.org can link to or be a copy of the OASIS content. This gets around the issue if the owner of
openc2.org stops paying their fees to own the domain as well as solves the membership rules differences between Forum and OASIS.
In other words, I still think we need the OASIS open repo.
iPhone, iTypo, iApologize
-------- Original Message --------
Subject: Re: [openc2-imple] Proposal for an open repository for "general
From: Dave Lemire <email@example.com>
Date: Mon, January 22, 2018 1:46 pm
To: Duncan <firstname.lastname@example.org>
Cc: email@example.com, Chet Ensign
<firstname.lastname@example.org>, Robin Cover <email@example.com>
Duncan: thanks for putting the idea forward, and especially for volunteering to help.
Initial thoughts (subject to revision if I manage deeper thoughts):
I agree that the CTI page is a great resource.
We currently have something similar at
http://openc2.org ; source at https://github.com/OpenC2-org/openc2-org.github.io;
If I Google "openc2", the
openc2.org link is the very first thing that appears (I realize other people's Google results may vary), and
openc2.org seems a very obvious domain name (vice the complicated URL for the CTI page)
Similar Googling for CTI, STIX, or TAXII doesn't yield an obvious connection to the CTI documentation page.
Wouldn't it make more sense to focus on improving the
openc2.org page? If OASIS really prefers that we manage that content under an OASIS open repo, then we could create the repo, port the current
openc2.org content to it, and adjust DNS so that
openc2.org points to the
github.io page that presents the OpenC2 documentation. It could then evolve from there as needed.
At the risk of sounding argumentative, if the problem is a lack of "other non-normative products to increase adoption and improve the ease of use", maybe the front
end web page isn't the real issue.
 Side note: it would be good to upgrade the
OpenC2.org page to be HTTPS.
OpenC2 Implementation Considerations SC Co-chair
Contractor support to NSA
On Sat, Jan 20, 2018 at 10:47 AM, <firstname.lastname@example.org> wrote:
The Implementation Considerations Subcommittee has the open repo's within it's charter as well as under deliverables it has the statement "Other non-normative work
products to increase adoption and improve the ease of use of the OpenC2 language". Based on comments made at the F2F I believe we are lacking in this area and would benefit from something like CTI's
https://oasis-open.github.io/cti-documentation/. Note the webpages you render when you click on that link are in an OASIS open repo at
https://github.com/oasis-open/cti-documentation. I recently noticed an error on that site and put in a change to fix it which reinforced by belief that github is the way to do this
kind of thing. It also reminded me what a wonderful site CTI put together for those interested in STIX or TAXII. I think OpenC2 needs an equivalent site and I think it falls within the IC-SC charter. I would be willing to lead an effort (and be the github
maintainer) to do so under the IC-SC.
Since the IC-SC does not meet, I would propose to gain consensus via email to get it going and then use github itself (in combination with email to IC-SC) for reaching
consensus on content. Since an open repo requires TC agreement, I intend to make a motion at the February meeting for the creation of an open repo
https://github.com/oasis-open/openc2 to instantiate at
https://oasis-open.github.io/openc2. I can discuss at next TC working meeting and send an email to TC prior to Feb meeting with the motion, but since it's within IC-SC charter, I thought I'd
start the discussion here.
Thoughts (and help) welcomed.
iPhone, iTypo, iApologize
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.
Follow this link to all your TCs in OASIS at:
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php