Known Issues After Schema Change

[wrbrant]

Known issues after 6e732b3:

• Improper relationships can be made. there is no active validation. this is a pre-existing bug
• In open-vocab enum selection, only the first value will show up. Any others will be in the json, but won't show up in the gui. this is a pre-existing bug
• Some optional properties show up as default. They can be removed. This is a pre-existing bug
• The new schema contained some specifications that the STIG code could not parse, so some changes to this schema were made. The schema was changed in the following ways:

object	titles added for	other changes for proper parsing
campaign	first_seen, last_seen
indicator	valid_from, valid_until
infrastructure	first_seen, last_seen
intrusion-set	first_seen, last_seen
language-content	contents, object_ref, object_modified
location		all conditionally required properties removed
malware-analysis	submitted, analysis_started, analysis_ended, host_vm_ref, operating_system_ref, sample_ref	pattern of sample_ref was combined ; conditional requirement of either result or analysis_sco_refs was removed
malware	first_seen, last_seen	required property was reduced to just is_family, ignoring conditional requirement for name
observed-data	first_observed, last_observed	conditional requirement of either objects or object_refs was removed
report	published
sighting*	sighting_of_ref
threat-actor	first_seen, last_seen

* sighting isn't actually included as an option in STIG, but was edited for the sake of compatibility