Re: [cti] STIX 2.0 RC1

On 20/08/2016 6:55 AM, "Wunder, John A." <jwunder@mitre.org> wrote:

Hey everyone,

Passing along one suggested change from the MITRE person writing a STIX 2 validator:

Problem: Right now, there’s no normative statement that precludes a Relationship object from pointing to another Relationship object as either the source or target. We said it in the definition of the object, but when writing the validator it seemed like it would be nice to have a normative statement to reference (that could then be listed in the conformance section).

Suggestion: Add the following statement to the source_ref and target_ref property descriptions on the Relationship object: “The value MUST be an ID reference to a STIX Domain Object (i.e., cannot point to an SRO, Bundle, or Marking Definition)”.

Thoughts?

John

From: <cti@lists.oasis-open.org> on behalf of "Wunder, John A." <jwunder@mitre.org>
Date: Thursday, August 18, 2016 at 3:38 PM
To: "cti@lists.oasis-open.org" <cti@lists.oasis-open.org>

Subject: [cti] STIX 2.0 RC1

All,

The STIX editors have worked through all of the recent comments and have wrapped up STIX 2.0 RC1. The document is available:

-          Attached to this e-mail (.doc)

-          Online on Google Docs: https://docs.google.com/document/d/1HJqhvzO35h62gQGPvghVRIAtQrZn3_J__0UcDAj-NXY/edit#.

-          Online on Kavi: https://www.oasis-open.org/apps/org/workgroup/cti/document.php?document_id=58743

At this point, all comment rights have been turned off in Google Docs. Please make any further comments on the specification on the mailing list.

The end of the STIX 2.0 comment period is scheduled for August 19^th, tomorrow. At that point we’ll make a motion to open a ballot and approve the release candidate as a Draft Committee Specification. As I mentioned on the TC call today, we can do this without putting it into the OASIS templates and it only requires a simple majority to approve.

As always, thanks everyone for all of the work,

John & the STIX 2.0 Editors Team

cti message