I think our core objective is that flatter is better than nested
if it makes sense. In this case, our argument is that not all files will have properties relevant to their representation on a file system, which is why this is an optional type. That said, instead of flattening this out, perhaps we should just make
this an extension? Our methodology has been that properties on a base CybOX Object should be relevant for all instances of the Object; if not, they should be represented as extensions.
Regards,
Ivan
From:
<cti-cybox@lists.oasis-open.org> on behalf of Jason Keirstead <Jason.Keirstead@ca.ibm.com>
Date: Tuesday, August 23, 2016 at 1:36 PM
To: Bret Jordan <bret.jordan@bluecoat.com>
Cc: "cti-cybox@lists.oasis-open.org" <cti-cybox@lists.oasis-open.org>
Subject: Re: [cti-cybox] File Object
Are you talking specifically about the file_system_properties construct?
-
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" ---08/23/2016 04:31:05 PM---Right now in the File
Object some of the properties are artificially nested. These properties deal
From: "Jordan, Bret" <bret.jordan@bluecoat.com>
To: "cti-cybox@lists.oasis-open.org" <cti-cybox@lists.oasis-open.org>
Date: 08/23/2016 04:31 PM
Subject: [cti-cybox] File Object
Sent by: <cti-cybox@lists.oasis-open.org>
Right now in the File Object some of the properties are artificially nested. These properties deal with the file system aspects of a file. The argument is that not all files have these and thus it should be nested.
This IMHO, violates one of our core objectives of flatter is better than nested. I feel it would be better to have these fields be flattened and just made optional.
This is something we do throughout STIX and is part of our holistic design principles.
Bret
Sent from my Commodore 64
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php