OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cti message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [cti] Sponsor Template Link & Tracking Matrix


Just to be clear about Attestation, what we are looking for is
organizations saying they have implemented feature X and declare either
everything went well and all of the text is good, or provide a list of
issues or text problems they ran in to. We understand that most
commercial providers can not release or share their source code and may
not even be able to release and share their use cases. The key is to
make sure it was implemented in code and it works. If it does not work,
we need to know sooner rather than later so we can fix it. It is also
important to call out how one might test this feature for interoperability.

I've had a comment that the Template seems a little complex and scary...
Note that I built this from a Committee Note framework with the
expectation that even in draft form, it will go into the official
record. Most of the fluff in the intro is boiler plate. The main
sections you would need to concentrate on for the Sponsor Documents are
sections 3 (Attestation and/or POC code) & 4 (Interoperability).Â

All for now,

Jane Ginn

On 9/25/2019 1:21 PM, JG wrote:
> During the September meeting we discussed the need for Sponsors to come
> forward to develop POC code for SDO & feature completeness and
> interoperability. I mentioned that I'd put together a Template for you
> all to use for publishing those POC code snippets. Richard also noted
> that in lieu of published code snippets an Attestation of functionality
> would be sufficient to meet the "Sponsorship" demonstration.Â
> Here is a link to the Template:
> https://docs.google.com/document/d/16bgE5dPgujpXlsK7eGfW-rhMw-2MBmrnkMc2r-tfRbg/edit?usp=sharing
> Note that I developed it for the Course of Action SDO, but that it can
> easily be copied and modified for any of the SDOs and/or Features. Once
> you establish a new Google Document, please send me the link so I can
> put it up on the CTI TC Cover Page (scroll down to page 2). Also note
> that there is a placeholder for an Attestation of functionality also in
> the Template.Â
> I've also put together a matrix for Bret & Emily, Co-Chairs of the STIX
> Subcommittee, for tracking the volunteers that step forward to "Sponsor"
> an SDO or Feature. If you were not on the September meeting, we need
> Sponsors to come forward before the specified date to either Attest to,
> or document the completeness, functionality and interoperability of key
> SDOs and Features.Â
> The time is passing us by...... Please reach out to them directly to let
> them know which of the items you will take responsibility for.
> Here is the link to the Google Doc.Â
> https://docs.google.com/spreadsheets/d/1knWwGSN5SilYMQMYXw8D_Xa6MRLM7-Lypig-A0VH_dw/edit#gid=472317016
> Also, a quick reminder on TAXII 2.1 - We have a Ballot waiting to be
> issued as soon as there is one more demonstration of functionality of
> the Pagination refactoring.Â
> Help us get that moving!!!
Jane Ginn, MSIA, MRP
Secretary, OASIS CTI TC
001 (928) 399-0509

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]