OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

openc2-lang message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [openc2-lang] Language Spec open issues

If you think that this new social requirement is a burning issue which makes risking broken links tolerable and you want to fix all the back-links by hand, go ahead.

I note that Github cites numerous problems and recommends waiting.

From: openc2-lang@lists.oasis-open.org <openc2-lang@lists.oasis-open.org> on behalf of David Kemp <dk190a@gmail.com>
Sent: Monday, August 17, 2020 5:49 PM
To: duncan sfractal.com <duncan@sfractal.com>
Cc: openc2-lang@lists.oasis-open.org <openc2-lang@lists.oasis-open.org>; Lemire, Dave (HII-TSD) <david.lemire@hii-tsd.com>
Subject: Re: [openc2-lang] Language Spec open issues
This is more an issue of not wanting to step on the editors' toes.  With your permission I'll ask Dave to proceed with updating the LS repo.

JADN is always updated via PRs, which I submit from my personal fork and approve on OASIS.  I can start suggesting reviewers before I approve them if you'd like to be on the list.  I usually batch up a week's worth of commits for a weekly PR, if software development indicates an update to the spec.


On Mon, Aug 17, 2020 at 4:42 PM duncan sfractal.com <duncan@sfractal.com> wrote:

Wrt getting legacy LS GitHub in sync with our new norms – this is a volunteer organization and relies on volunteers to do the work. Anybody – including yourself – can do the work. I don’t think anyone can task another OASIS member to do the work. It is the editor’s job and I’ll confess It's not highest on my list(I already did it on some of the other artifacts). I’m being a pain in the hope someone else would volunteer to be a co-editor and volunteer to do it.


Wrt JADN – please propose the wording change you’d like to the meeting notes.


Wrt JADN - Are the changes you mention to the working branch being done by PR’s being accepted after being agreed to by the Language SC? I don’t recall any of these PR’s being discussed but maybe I missed it. If we haven’t been reviewing, we might want to start following the process. The editor can make editorial changes willy nilly but even those should be pointed out to LSC, and substantive changes should be reviewed.


I don’t mean to be snippy but my basement flooded yet again, while we were away and after we thought we’d fixed everything, so I had to drive back to VA and spend last several days talking to expensive contractors.



Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

I welcome VSRE emails. Learn more at http://vsre.info/



From: openc2-lang <openc2-lang@lists.oasis-open.org> on behalf of David Kemp <dk190a@gmail.com>
Date: Monday, August 17, 2020 at 4:24 PM
To: openc2-lang <openc2-lang@lists.oasis-open.org>
Cc: David Kemp <dk190a@gmail.com>, "Lemire, Dave (HII-TSD)" <david.lemire@hii-tsd.com>
Subject: [openc2-lang] Language Spec open issues


Hello Co-chairs,

We made good progress discussing open issues at the 3 August meeting https://meet.lucidmeetings.com/meeting/258343.

Under 3.2.2 Pull Requests, there are a number left over from before the release of CS01, with the question of whether they are OBE.  In order to close them out I need to replace them with PRs against the current CS02 spec.  May I request that you task the TC Secretary to update the LS repo to the current CS02 release.

Under 3.3 there's a question in the agenda about the JADN repo not being touched in 2 years. That refers to the master branch dating to creation of the repo. As noted at the meeting the working branch https://github.com/oasis-tcs/openc2-jadn/tree/working is regularly updated, so the meeting minutes should reflect that it is under active development and review and feedback is welcome.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]