[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: STIX 2.1 CSD01
Hi everyone, As you probably know, one thing we as a TC are working as fast as we can towards is the release of our first CSD (Committee Specification Draft) of STIX 2.1. As you may recall, we plan on issuing
a series of CSDs until such point we are ready to release a CS (Committee Specification). A CSD is basically the first step towards the TC formalizing normative text for the things included in a release of STIX, and is also the start of our recently-balloted
TC process that includes sponsorship, implementation, and interoperability text. At the same time, as we discuss the malware object, itâs becoming clear that we still have some work to do on it. We want to make sure we get it right, and in particular to consider how it relates
to the Infrastructure object and other new SDOs planned for CSD02 and beyond.
This would do two things:
If this sounds good, we would immediately begin work to finalize the drafts to get us to a CSD01 ballot:
Based on maybe 2 iterations of the working drafts, that would mean opening a CSD ballot in the August timeframe. Once that happens and the CSD is approved we can continue our work to get sponsors,
validate implementations, and write interoperability text. In order to do this, I move that the TC approve by unanimous consent deferring Malware to a subsequent STIX 2.1 CSD and continuing with our CSD01 release process. Thanks all, John |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]