The syntax means that those fields are a sub-object nested under the parent. So that would be one of the keys within the objects in the external_ids array.
From: "Jordan, Bret" <>
Date: Wednesday, February 3, 2016 at 10:00 AM
To: "Wunder, John A." <>
Cc: "" <>
Subject: Re: [cti] Top-Level Object Properties
I do not believe we have consensus on all of the items in the consensus section. Namely, what are the "----" field all about?
Example
----id (required)
IDFormat
The external ID itself
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."
On Feb 3, 2016, at 05:53, Wunder, John A. <> wrote:
All,
There’s a new topic to think about! As discussed at the face to face, each top-level object in STIX and CybOX will inherit from a core set of properties…things like ID, etc. We haven’t quite agreed on what all of those fields are, though.
Take a look at this writeup: https://github.com/STIXProject/specifications/wiki/Active-Issue:-IDable-Construct-Properties. It has
a set of fields that we have general agreement on, a list of fields we haven’t really discussed, and then a couple proposals (from Sean and from the twigs team). Feel free to either add your own proposal to that wiki page or discuss on the mailing lists and
slack. The key question to consider: what fields should be available on *all* top-level objects?
John
PS: The twigs team added our proposal to the writeup on source references. You can see it on the issue page (https://github.com/STIXProject/specifications/wiki/Active-Issue:-Relating-Source)
by scrolling down to Proposal 2. If you want to respond to that one via e-mail, make sure to make a separate thread.
