Changes

m
Added reference links/citations.
Line 1: Line 1: −
A content metamodel defines a set of entities that allow architectural concepts to be captured, stored, filtered, queried, and represented in a way that supports consistency, completeness, and traceability. (TOGAF 9: 30.2.2)
+
A content metamodel defines a set of entities that allow architectural concepts to be captured, stored, filtered, queried, and represented in a way that supports consistency, completeness, and traceability <small>([https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap30.html#tag_30_02 TOGAF 9: 30.2.2])</small>
   −
Our content metamodel is based largely on the TOGAF 9.2 and (primarily) on the ArchiMate 3.0.1 specification, with some specific adaptations and alignment for SSC.  In general, unless specified, any relationship permitted in ArchiMate 3.0.1 is permitted.
+
Our content metamodel is based largely on the [https://pubs.opengroup.org/architecture/togaf9-doc/arch/index.html TOGAF 9.2] and (primarily) on the [https://pubs.opengroup.org/architecture/archimate3-doc/ ArchiMate 3.0.1 specification], with some specific adaptations and alignment for SSC.  In general, unless specified, any relationship permitted in ArchiMate is permitted.
    
=== Content Metamodel Diagrams ===
 
=== Content Metamodel Diagrams ===