[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti-cybox] CybOX 3.0: Address Object Refactoring
I agree.
While the format could be distinguished from the string without explicit labeling this puts the onus on the consumer to do that analysis on the data field. This seems like an unnecessary burden for use cases where the field may be used in processing, orchestration
or workflow routing decisions.
sean
From: <cti-cybox@lists.oasis-open.org> on behalf of John Wunder <jwunder@mitre.org>
Date: Thursday, October 29, 2015 at 9:58 AM To: John Anderson <janderson@soltra.com> Cc: Mark Davidson <mdavidson@mitre.org>, Trey Darley <trey@soltra.com>, Terry MacDonald <terry@soltra.com>, "Jordan, Bret" <bret.jordan@bluecoat.com>, Steve Cell <ikirillov@mitre.org>, "cti-cybox@lists.oasis-open.org" <cti-cybox@lists.oasis-open.org> Subject: Re: [cti-cybox] CybOX 3.0: Address Object Refactoring What’s the upside of not requiring the producer to specify the version? If it’s distinguishable by format, coudn’t the producer just do that and always provide the format?
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]