search

oasis-tcs / cti-stix2

OASIS CTI TC: Provides issue tracking and wiki pages for the STIX 2.x Work Products
https://github.com/oasis-tcs/cti-stix2
Other
24 stars 9 forks source link

Should the versioning of SCOs be revisited because custom properties are deprecated? #239

Closed rpiazza closed 3 years ago

rpiazza commented 3 years ago

Text from the spec:

In STIX 2.1, SCOs do not explicitly have those three versioning properties. Therefore, a SCO cannot be versioned unless custom properties (discussed in section 11.1) are used. Producers who do this SHOULD use the property names created_by_ref, revoked, created, and modified.

A normative statement to use deprecated functionality seems wrong

jordan2175 commented 3 years ago

This is talked about in section 3.6

Original Text

In STIX 2.1, SCOs do not explicitly have those three versioning properties. Therefore, a SCO cannot be versioned unless custom properties (discussed in section 11.1) are used. Producers who do this SHOULD use the property names created_by_ref, revoked, created, and modified.

New Text

In STIX 2.1, SCOs do not explicitly have those three versioning properties. Therefore, a SCO cannot be versioned unless extensions (discussed in section 7.3) are used. Producers who do this SHOULD use the property names created_by_ref, revoked, created, and modified.