"relationship_type": "derived-from", "source_ref": "example--1", "target_ref": "example--2" } Example consumer workflow This section describes an example workflow a consumer receives multiple updates to a particular object. (In this example, the STIX Objects have been truncated for brevity.) Step # STIX Object Recipient Action 1 { Consumer stores example object because this is the first time they "type": "example", have seen the object. "id": "example--1", "created": "2016-05-01T06:13:14.000Z", "modified": "2016-05-01T06:13:14.000Z" } 2 { Consumer updates example object because the received "type": "example", modified property is later than "id": "example--1", the object that is currently stored. "created": "2016-05-01T06:13:14.000Z", "modified": } 3 { Consumer ignores this object because they already have a "type": "example", newer version of the object. "id": "example--1", Note: consumer might choose to "created": "2016-05-01T06:13:14.000Z", store meta-information about "modified": "2016-05-06T06:23:45.000Z" received objects, including } versions that were received The consumer also may choose to store a copy for reference. 4 { Consumer decides to delete example object, but keeps some "type": "example", metadata regarding the object. "id": "example--1", "created": "2016-05-01T06:13:14.000Z", "modified": "2016-05-11T06:41:21.000Z", "revoked": true }
"relationship_type": "derived-from", "source_ref": "example--1", "target_ref": "example--2" } Example consumer workflow This section describes an example workflow a consumer receives multiple updates to a particular object. (In this example, the STIX Objects have been truncated for brevity.) Step # STIX Object Recipient Action 1 { "type": "example", "id": "example--1", "created": "2016-05-01T06:13:14.000Z", "modified": "2016-05-01T06:13:14.000Z" } Consumer stores example object because this is the first time they have seen the object. 2 { "type": "example", "id": "example--1", "created": "2016-05-01T06:13:14.000Z", "modified": } Consumer updates example object because the received modified property is later than the object that is currently stored. 3 { "type": "example", "id": "example--1", "created": "2016-05-01T06:13:14.000Z", "modified": "2016-05-06T06:23:45.000Z" } Consumer ignores this object because they already have a newer version of the object. Note: consumer might choose to store meta-information about received objects, including versions that were received The consumer also may choose to store a copy for reference. 4 { "type": "example", "id": "example--1", "created": "2016-05-01T06:13:14.000Z", "modified": "2016-05-11T06:41:21.000Z", "revoked": true } Consumer decides to delete example object, but keeps some metadata regarding the object.