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


Help: OASIS Mailing Lists Help | MarkMail Help

openc2 message

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

Subject: Re: [openc2] Language Specification Issue Clean-Up

Count me in. Either way works for me. 

iPhone, iTypo, iApologize

From: openc2@lists.oasis-open.org <openc2@lists.oasis-open.org> on behalf of Vasileios Mavroeidis <vasileim@ifi.uio.no>
Sent: Friday, March 11, 2022 6:10:40 AM
To: Lemire, Dave (HII-TSD) <david.lemire@hii-tsd.com>
Cc: TC OpenC2 <openc2@lists.oasis-open.org>
Subject: Re: [openc2] Language Specification Issue Clean-Up
Count me in Dave. 

I can go both ways but a dedicated session and a  prepared group would allow us to resolve those issues faster.

Vasileios Mavroeidis
University of Oslo

On Mar 10, 2022, at 3:54 PM, Lemire, Dave (HII-TSD) <david.lemire@hii-tsd.com> wrote:

TC Members: as discussed during the 9 March 2022 working meeting, our on-going work on actuator profiles and transfer specifications has clearly indicated a need for an update to the currentv1.0 CS02 OpenC2 Language Specification.  The LS repository currently has 30 open issues, some of which have been open (and not updated) for a considerable period of time. I propose that we organize a focused work session to review the existing LS issues, identify ones that can be closed as no longer valid, and prioritize which of the remaining should be resolved as part of a v1.1 update to the LS. This could be done either during one of our weekly Wednesday working meeting, or as a one-off special work session, depending on the availability of interested parties to commit to one or the other.
If you are interested in contributing to this issue screening effort, please reply here with your interest and your preference for using working meeting time or for scheduling a separate focused work session. If the majority preference is for a separate session I will undertake to coordinate scheduling that meeting.  In the interim, there would be value in our members taking a fresh look at the issues on GH and adding their opinions there regarding any / all of the currently open issues; having that input prior to a work session may significantly improve the efficiency of the meeting.
As an FYI, my software team has identified some concerns with the LS (and to a lesser degree the architecture spec) that I plan to being recording as new issues in the appropriate repositories.
David Lemire
IA Systems Engineer
Technical Solutions
302 Sentinel Drive | Annapolis Junction, MD 20701
Work (301) 575-5190 | Mobile (240) 938-9350

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