[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti-stix] _ref field suffix
I’m not sure I follow…an ID field identifies the object it’s placed on, not another object.
{
“id”: “this-objects-id”,
“created_by”: “a-different-objects-id”
}
I’m saying that having all of those things that point to a different object have a consistent naming pattern tooling can leverage that and take some actions automatically (I.e., try to resolve it). Semantically, those are different things.
Yes, they both use the identifier data type. But one is identifying something, one is pointing to something else. They do different things.
John
From: Allan Thomson <athomson@lookingglasscyber.com>
Date: Tuesday, May 10, 2016 at 1:41 PM To: "Wunder, John A." <jwunder@mitre.org>, "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org> Subject: Re: [cti-stix] _ref field suffix John – I agree that a _ref is a reference to another object but so is an Id field. That’s my point. Both fields are references to an object that is identified by an identifier.
allan
From: "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org> on behalf of "Wunder, John" <jwunder@mitre.org>
Date: Tuesday, May 10, 2016 at 10:37 AM To: "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org> Subject: Re: [cti-stix] _ref field suffix (Renamed subject line to track this thread)
I’m against dropping it. I have a practical reason and a philosophical reason:
John
From: "Jordan, Bret" <bret.jordan@bluecoat.com>
Date: Tuesday, May 10, 2016 at 1:29 PM To: "Wunder, John A." <jwunder@mitre.org> Cc: "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org> Subject: Re: [cti-stix] STIX, Topics to Review, 10 May
Based on the conversation today on the working call, I would be okay with dropping the "_ref" from the ID reference property names, since that is the only place where we add a field type to a property name.
Where do people stand on this?
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."
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]