Dave Kemp has been making progress on the JADN spec. You can read his current draft in the working branch of the new JADN repo:
https://github.com/oasis-tcs/openc2-jadn/tree/working A F2F agenda item for a JADN progress report would be quite appropriate. Dave -- David P. Lemire , CISSP G2, Inc. (A Huntington Ingalls company ) OpenC2 Technical Committee Secretary OpenC2 Implementation Considerations SC Co-chair Contractor support to NSA Email:
dave.lemire@g2-inc.com Work ( 301 ) 575-5190 Mobile ( 240 ) 938-9350 On Wed, Apr 3, 2019 at 8:30 AM Considine, Toby <
Toby.Considine@unc.edu > wrote: Oops. Somehow my email fell back to December, and I was being presented with a steady stream of Duncan s comments from December. It surprised me, but I was going with it. Still the issue of how to approach JADN at the F2F remains. tc From:
openc2@lists.oasis-open.org <
openc2@lists.oasis-open.org > On Behalf Of Considine, Toby Sent: Wednesday, April 3, 2019 8:27 AM To: TC OpenC2 <
openc2@lists.oasis-open.org > Subject: [openc2] Lang Spec CSPRD01 and JADN I like each of Duncan s comments so far, but several of them bring up JADN references still in place. As it stands now (likely CS01), there is no JADN specification. It has been removed from the Appendix to the language specification, and appears in no other document. We should not / cannot reference what does not exist. How to proceed with JADN is worthy of a serious but short conversation at the F2F. It seems likely that if we promote it to another Specification, that we should try to recruit some specifically interested in the space of JADN, that is of serious formalization of common semantic interfaces so that they can get wide acceptance and be compatible for inclusion into tooling. I have some ideas on that, but as noted, a good F2F topic. The TC has requested a JADN stub document, but as of yet, we have not seen even WD01. For now, the way to address vague JADN references in the specification(s) is to eliminate them. tc