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] RFI & Motion: JSON MTI & JSON Schemas

Lack of visibility in terms of planning (should it result in best effort) is a real issue.
From discussions with major actors, they don't want to invest in xml based dev and can't start with json. So status quo not benefiting the community.
Personally I had to cancel a talk where a CTI exchange partnership were supposed to be signed between key players of a big energy sector due to lack of visibility. And I will not engage into new loss of credibility.
I hope a new super Mario could help with plumbing

On Sunday, 10 April 2016, Patrick Maroney <Pmaroney@specere.org> wrote:

Many thanks for responding.  I'm not advocating "Focus" on the actual schema implementations.  Intent and requested outcomes are:

(1) Formally establish consensus that JSON Schemas are "Must" deliverables as outlined in the Motion. (I think all we need is for someone to formally second the motion.  Rich can call for objections, and presuming none, we can quickly pass as a resolution.

(2) Estimated target dates for delivery of initial draft JSON schemas by each SC.

(3) Add these schemas as specific deliverables to the STIX and CybOX Road Maps and update going forward as these plans evolve.

Patrick Maroney
Integrated Networking Technologies, Inc.
Desk: (856)983-0001
Cell: (609)841-5104
Email: pmaroney@specere.org

From: Aharon Chernin <achernin@soltra.com>
Sent: Sunday, April 10, 2016 9:35 AM
Subject: Re: [cti] RFI & Motion: JSON MTI & JSON Schemas
To: Patrick Maroney <pmaroney@specere.org>, OASIS CTI TC Discussion List <cti@lists.oasis-open.org>


In my opinion, STIX 2 and CybOX 2 are in too much flux to focus on their schema implementations. However, I would always encourage the community to work on schemas implementations early in the process if the would like to donate the man hours to the group.

More points towards our lack of focus on schema representation at this point:
*) We have not reached consensus on the definition of what an “observation” is, and several other frequently used high level objects, in STIX 2. An email went out from John Wunder on Thursday to the STIX TC asking for comments on both the definition of a few of the STIX high level objects and how they work together in the STIX 2 pre-draft specs. The response to this would be a good gauge to our closeness on consensus. 
*) A word of caution. STIX TC members wishing to invest the hours to build JSON schema implementations at this time risk large changes in the spec until we reach pre-draft consensus.   
*) I think the community is in alignment that a JSON schema should be made based on the agreed STIX 2 specification. I also think it is acceptable to get JSON schema availability timing based on STIX 2 draft specifications when they are available.


From: <cti@lists.oasis-open.org> on behalf of Patrick Maroney <Pmaroney@Specere.org>
Date: Saturday, April 9, 2016 at 4:20 PM
To: OASIS CTI TC Discussion List <cti@lists.oasis-open.org>
Subject: [cti] RFI & Motion: JSON MTI & JSON Schemas

Obviously, the STIX and CybOX specifications are still very much under development.  However, I'm unable to locate any notional/draft JSON Schemas for STIX or CybOX on GitHub, OASIS Document libraries, or Slack Channel. The fact that there are only 6 posts in the 10,000's of Slack Channels/postings that even contain the word "schema" would indicate that there is no current focus on JSON Schemas.

(1) Do these exist anywhere within the known CTI TC document locations? If so, where?
(2) Do these exist anywhere in CTI TC member locations (e.g. GitHub)? If so, where?
(3) If not what is the current road map (with estimated target dates) for their creation as part of the JSON MTI?

Hopefully we have CTI TC consensus that the inclusion of normative JSON Schemas for the OASIS CTI TC Committee Specifications and Standards are critical to our success in many endeavors.  

To quickly and formally establish if this consensus exists, I submit the following motion to the CTI TC:

Motion: "I move that the inclusion of normative JSON Schemas in all OASIS CTI TC Committee Specifications and Standards based on a JSON MTI are critical to our success and are therefore mandatory deliverables".

Of particular immediate concern as one of the CTI TC Interoperability SC cochairs (and basis for formally raising this topic today) relates to the substantive technical body of work that is required to develop normative Interoperability and Conformance Documentation, Use Cases/Scenarios, Test Suites, Test Descriptor, Tools, and CTI Interoperability Testing services.

These CTI Interoperability efforts require a significant amount of planning and coordination.  The road map and target dates for the delivery of the draft JSON Schemas by the STIX and CybOX SCs represent critical dependencies  and potential high risk blocking milestones.

Note:  I created the "json-mti-schema" Slack Channel for advancing the planning and related discourse on the specific topic of CTI TC JSON schemas (and coordination of delivery of same)

Patrick Maroney
Integrated Networking Technologies, Inc.
Desk: (856)983-0001
Cell: (609)841-5104
Email: pmaroney@specere.org

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