[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Outline of proposed 2.0 language specification development process
Great process here! A couple random thoughts: ·
I really like the idea of the use-cases. As someone new to STIX and the industry, this is something that would extremely helpful. ·
I think that the issues worked on in step 2 below should reference back to the use-case in step 1 (or propose a new use-case). This will let us focus
on the issues that have the most meaning, and steer us away from ‘busy work’.
o
I know you have that in step 3 below, but I think it can start earlier, with the items that are already open issues, and after we have identified the
base use-cases. ·
To prioritize the issues we tackle, I would suggest a simple vote where each member of the TC puts a weight on each issue in the list (numbered from N
to 1). Combining the votes, we will have a group priority order. ·
How do we propose settling issues that we as a group can’t come to a consensus on? We should certainly strive for consensus, but my experience with groups
of over 3 or 4 people is that it is tough to always accomplish. Do we need a majority vote to move a proposal forward into the 2.0 spec? ·
My biggest question on all of this is “who is doing what?”. Do we have a way of tracking this sort of thing? I would fear that multiple people would
be working on the same item or worse yet, items get missed. From: cti-stix@lists.oasis-open.org [mailto:cti-stix@lists.oasis-open.org]
On Behalf Of Barnum, Sean D. We have talked a few times now about the desire to move forward as quickly as possible on STIX 2.0 but also of the need to balance this with the requirement of
nailing down STIX 1.2.1 first as an initial OASIS version. We have also talked about the need for a coordinated and deliberative process once we do actually get working officially on 2.0. Unfortunately, we haven’t really given you much detail in what that means beyond the simple principle. In an effort to provide a little more clarity, reduce uncertainty and level set our expectations we have put together an outline of the proposed specification
development process for STIX 2.0 (In reality, this basic process would be the same one followed for pretty much any SC work products). It highlights the important central role of both use cases and the issue trackers to help scope, frame, focus, coordinate,
collaborate, track and record our efforts. There are obviously many other details not represented here but this outline should give a solid feel for the key milestones and dependencies in the process. Outline of proposed 2.0 language specification development process
One key takeaway to highlight is the fact that the set of activities listed under numbers 1 & 2 (the first two blocks in the outline) can be pursued immediately
by the SC members and in parallel with ongoing STIX 1.2.1 activities. In fact, getting this set of activities well along should set us up solidly for the actual formal work on 2.0 including giving us some focus on how we talk about issues rather than bouncing
willy-nilly from issue to issue like pachinko balls. In that light, we encourage everyone to start tackling these steps as soon as you can. The outline will be posted up on the wikis and will be maintained on an ongoing basis. We hope that the outline presented here is clear and helpful in understanding the proposed process going forward. If anyone has any questions or concerns with the process outlined please let us know. Thank you, Sean Barnum CTI STIX SC Co-chair DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]