Enable support of variety of threat models beyond ATT&CK

[netfl0]

Enable multiple att&ck "matrices".

• Even though ATT&CK for X's share the same technique and tactic names, they have different identifiers for the tactics and techniques.

• We will continue to use the identifiers for the IRI fragment name.

• consider new toplevel organization class above d3f:ATTACKThing such as d3f:ThreatModelThing

• Perhaps something like:

• d3f:ExternalThreatModelThing

  • d3f:ATTACKThing
  • d3f:ATTACKEnterpriseThing
  • d3f:ATTACKICSThing
  • d3f:ATRMThing (thanks @aw350m33d )

This is similar to @aw350m33d 's recommendation of:

This will also require updates to the UI...