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
On Mar 7, 2016, at 9:14 AM, Jordan, Bret <> wrote:
Right now, we have three documents for STIX & CybOX, aka CTI. We have:
CTI Common 1.0
STIX 2.0
CybOX 3.0
I would like to challenge this design. It seems like we are opening ourselves to document versioning and compliance / interoperability nightmares.
1) Does it really make sense, other than for historical reasons, to keep these documents separate?
2) If they were merged, then could not things like MAEC and other standards (that are NOT part of OASIS) just reference the sections that were of interest to them?
Thanks,
Bret
Bret Jordan CISSP
Director of Security Architecture and Standards | Office of the CTO
Blue Coat Systems
PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
