Feature/4.2.0 rc.2

[andreea-pasare]

• Fixed the following GitHub issues:
  • eforms BT-730 Subcontracting Value Known. There does not seem to be a mapping in ePO to this #624
  • Remove predicate epo-sub:refersToOtherESPDResponse #688
  • Remove epo-con:ContractModificationInformation from core module diagram in ePO 4.2.0 #689
  • Revert predicate epo-ful:refersToOrderLine cardinality to [0..1] #703
  • Remove Predicates from ePO 4.2.0 that were not forseen for 4.2.0 release #705
• Modifications done at the level of the Enterprise Architect file:
  • Conventions used for both internal and external concepts (stored as tags in the CM):
    • skos:historyNote: Contains the date that the concept was approved by the Working Group as a rdf:plainLiteral datatype using the following notation: “WG Approval DD/MM/YYYY”. For example, “WG Approval 28/04/20.”
    • skos:editorialNote: Contains the business term used by a specific data model that can be mapped to the concept. Its value is a rdf:plainLiteral datatype using the following notation: “Used by X BT/BG-Y, Z BT/BG-H..” where X and Z are the data models, and Y and H the number of the Business Term (BT) or Business Group (BG) that this concept represents. For example, “Used by eForms BT-724".
    • dct:source: Contains the reference from where this definition was taken.
  • Conventions used for external concepts.
    • For each external concept, the ‘Notes’ section of the Conceptual Model contains a hyperlink to a human-readable website that provides the original definition of the concept.