[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti] Documents
I agree. In reality there are lots of interdependencies and they almost always version in sync anyway, so we might as well formalize that. It also simplifies how we talk about things…how many times have you said “well that’s not really STIX, it’s CybOX,
so XYZ rather than ABC”? This way we get rid of that issue.
I do agree with Paul’s (separate) concerns about references in, but I think by following what Allan and Bret mentioned we can avoid that and ensure that people only deal with what they have to.
One symptom of the split that I really don’t like is that certain TLOs will have a CTI Common spec version (relationship), others have a STIX one (Indicator), and others have a CybOX one (Observation). That seems very confusing to me…one version to rule
them all!
John
From: <cti@lists.oasis-open.org> on behalf of Allan Thomson <athomson@lgscout.com>
Date: Monday, March 7, 2016 at 1:45 PM To: "Jordan, Bret" <bret.jordan@BLUECOAT.COM> Cc: "cti@lists.oasis-open.org" <cti@lists.oasis-open.org> Subject: Re: [cti] Documents Having a single version of the content is preferred from my perspective.
You can still have normative text that describes each module separately.
But having ONE version to track for the related content is preferred.
allan
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]