cacao — archive

Missing requirements

From: Arnaud Taddei <[email protected]>
To: [email protected]
Date: Tue, 17 Sep 2019 16:56:00 -0000

Thank you Duncan and sorry I was late hour and I couldn t attend the call 2 weeks ago (am WP3 chairman at ITU-T SG17 and it was WP closing plenary!) I think we are going to have to spend quite some time on the gap analysis on point 3 from Duncan below before we can even give feedback. But that will produce a lot of value in itself De : <[email protected]> au nom de "duncan sfractal.com" <[email protected]> Date : mardi, 17 septembre 2019 Ã 18:09 Ã : "[email protected]" <[email protected]> Objet : [EXT] [cacao] Missing requirements This is to document my comments at the meeting. I see 4 requirements missing from the slides that got talked about: Vendor independent interoperability Agile break the CACAO work into phases an get minimum viable product out sooner rather than later, rather than a complete standard taking much more time Use other standards when possible Give feedback to other standards if they are missing something CACAO needs (specifically OpenC2 as the command and control language is new and needs use cases like CACAO to move to it s next phases). Point being (1)use other standard if possible. (2)If it s not possible, see other standard can be changed so it is possible before inventing a new way. I would like to see these included in the meeting notes as brought up as potentially missing from base set of requirements presented. I m not sure process on reaching consensus on the ones presented or on these additions (no objections?). Duncan Sparrell sFractal Consulting LLC iPhone, iTypo, iApologize I welcome VSRE emails. Learn more at http://vsre.info /