ditto
From:
OASIS list <cti-cybox@lists.oasis-open.org> on behalf of Jason Keirstead <Jason.Keirstead@ca.ibm.com>
Date: Monday, September 19, 2016 at 10:13 AM
To: "Jordan, Bret" <bret.jordan@bluecoat.com>
Cc: OASIS list <cti-cybox@lists.oasis-open.org>
Subject: Re: [cti-cybox] Email Object
I would get behind this - seems cleaner.
-
Jason Keirstead
STSM, Product Architect, Security Intelligence, IBM Security Systems
www.ibm.com/security | www.securityintelligence.com
Without data, all you are is just another person with an opinion - Unknown
"Jordan, Bret" ---09/15/2016 11:46:05 AM---For the record, I really
dislike it when a property can be one of two types depending on the value o
From: "Jordan, Bret" <bret.jordan@bluecoat.com>
To: "cti-cybox@lists.oasis-open.org" <cti-cybox@lists.oasis-open.org>
Date: 09/15/2016 11:46 AM
Subject: [cti-cybox] Email Object
Sent by: <cti-cybox@lists.oasis-open.org>
For the record, I really dislike it when a property can be one of two types depending on the value of some other property. For example, we have the following two properties:
"is_multipart" boolean
"body" string or list of type mime-part-type
So if "is_multipart" is false then "body" is a [string] however, if "is_multipart" is true then "body" is a [list of type mime-part-type].
It seems like a much simpler way of doing this is to have two properties for the body...
1) body
2) body_multipart
If you still want the boolean property of is_multipart, that is fine. But lets not overload properties based on the value of another property. PLEASE...
Thanks,
Bret
Bret Jordan CISSP
Director of Security Architecture and Standards | Office of the CTO
Symantec
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" deleted by Jason Keirstead/CanEast/IBM]