SoftwareApplication table is confusing - says MUST then SHOULD

[ptsefton]

The requirements for @type on SoftwareApplication.

Suggest showing these as three separate tables, one per type (which will be easier when you can generate from linkML) I would also suggest making this table more informative, like:

[simleo]

The second column says whether the property must/should/may be present in the entity, while the third one describes the requirements of the property's value.

[stain]

Could be "MUST be either SoftwareApplication or SoftwareSourceCode, MAY additionally be ComputationalWorkflow or other types."