[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Motion to Approve STIX 2.0 CSD
|
I second this motion. From: cti@lists.oasis-open.org [mailto:cti@lists.oasis-open.org]
On Behalf Of Wunder, John A. All, The STIX editors and co-chairs (Trey Darley, Bret Jordan, Sarah Kelley, Ivan Kirillov, Rich Piazza, and myself) have completed the conversion of the STIX 2.0 documents into the OASIS templates and are ready
for the entire TC to review and vote on them to become a Committee Specification Draft. During conversion, the editors identified a couple issues and made these substantive changes (all very minor): -
Part 1: A non-normative MUST on the list definition was changed to normative (regarding items in the list needing to be of the correct type specified) -
Part 4: The command_line field was promoted from the Windows extension to the Process object to the Process object itself. -
Part 4: A normative SHOULD in the arguments field in the Process object was changed to a MUST given the addition of the command_line field allowed the optionality that used to be required -
Part 4: There was a language field in the software object that was singular (single language per software), was updated to a list (multiple languages per software) -
Part 5: The language used to say that PCRE and PCRE2 were both allowable regular _expression_ formats. This was updated to limit it to just PCRE. Given that the set of changes is relatively small and hopefully non-controversial, we’d like to keep the process moving. Therefore, I move that the TC approve STIX 2.0 Working Draft 01 and all associated artifacts packaged together in
https://www.oasis-open.org/committees/document.php?document_id=59847&wg_abbrev=cti as a Committee Specification Draft and designate the Word version of the specification as authoritative. Thanks everyone, John, Trey, Bret, Sarah, Ivan, Rich |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]