Re: [cti] Agenda for Tuesday's Call

[Bret Jordan <bj@ctin.us>]

Thanks. That will really help. 

Bret


> On Apr 30, 2021, at 3:29 PM, aa tt <atcyber1000@gmail.com> wrote:
> 
> Bret - I wonât make the call but I have commented on all these issues in GitHub and provided my input to the discussion.
> 
> Allan
> 
>> On Apr 30, 2021, at 1:20 PM, Bret Jordan <bj@ctin.us> wrote:
>> 
>> All,
>> 
>> Here is the list of Github Issues that we are going to hopefully address on Tuesdayâs call, and the ORDER in which we will address them:
>> 
>> 267 - UUIDv5 issue w/SHA-1 - This would be a material change.
>> 235 - Issue with patterning
>> 266 - Add entries to infrastructure open-vocab
>> 259 - Extension proporties
>> 260 - SCO versioning
>> 261 - Extensions should be a contributing property to ID gen - This would be a material change
>> 262 - Dealing with Optional Properties - This would be a material change
>> 263 - Dealing with the term parsing - This would be a material change
>> 
>> 
>> It is important to note that the Editors have flagged the following as deferred to a future release since they represent new features would be a material change. Now, like all of these, if we decide we must do a material change, then these would be come open for discussion on inclusion.
>> 
>> 
>> 264 - Add properties to Incident
>> 265 - CVSS scoring to Vulnerability
>> 
>> 
>> While the TC can disagree, the editors believe that the material change of 267 is the only issue that might warrant doing another CSD/CS. It is important to note that the editors do not believe 267 is a problem that we need to address at this time. However, if the TC decides it needs to be solved then this is the only issue that by itself could warrant a new version. The others just do not seem significant enough. This is why we will address it first as the decision of this issue will impact our later decisions.
>> 
>> We really hope that we do not need to do another CSD/CS. But if we do, we will look back through the issues and pick up any and all of the low hanging fruit. Also, as I said via slack, if we have to do another CSD/CS (which I hope we do not), then it would result in about a 3-4 week delay. It would also require organizations to update their Statements of Use.
>> 
>> Letâs work together as a team on Tuesday and try and finish resolving these last few issues. Please read up on the issues BEFORE the call. If we can resolve them all on Tuesday, then the editors can finish prepping the new version with non-material changes.
>> 
>> Bret
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  Follow this link to all your TCs in OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>> 
>