Linked.Archi ArchiMate 4.0 Relationship Tables

Linked.Archi ArchiMate 4.0 Relationship Tables: Overview back to ToC

This ontology has the following classes and properties.

Annotation Properties

• permits access
• permits access directly
• permits aggregation
• permits aggregation directly
• permits assignment
• permits assignment directly
• permits association
• permits association directly
• permits composition
• permits composition directly
• permits flow
• permits flow directly
• permits influence
• permits influence directly
• permits realization
• permits realization directly
• permits serving
• permits serving directly
• permits specialization
• permits specialization directly
• permits triggering
• permits triggering directly
• permitted by
• permitted directly by

Linked.Archi ArchiMate 4.0 Relationship Tables: Description back to ToC

The relationship tables of ArchiMate 4.0 (Appendix B.5) as lookups: for each element type, the types each relationship may go to — directly, or as the result of a derivation — as annotations on the element type (am4:Artifact :permitsRealization am4:BusinessObject), and for each relationship the annotation that holds its permissions (am4:realizes :permittedBy :permitsRealization). A relationship permitted to every element type lists arch:Element, and to every element and relationship arch:ModelConcept: association, which the tables permit between any two. Each permission also says whether it is direct: :permitsDirectRealization, a subproperty of :permitsRealization (am4:realizes :permittedDirectlyBy :permitsDirectRealization), lists the types the tables print in upper case — a relationship a modeller may draw. A type :permits… but not :permitsDirect… is one the specification sanctions only as the conclusion of a derivation. The relationships between relationships of Table B-1 are direct. The same tables as the relationship shapes (archimate4-relationship-shapes.ttl), generated from the same matrix, in a form for another use. The shapes validate: SHACL Core, which any SHACL engine runs and which reports a relationship the tables forbid. These answer a lookup — may this relationship go from this type to that one, and may a modeller draw it? — with one triple pattern. A tool may use either: the shapes to validate, and to read the table back out of their sh:or lists; these to look a relationship up, and to tell one a modeller may draw from one only a derivation gives. The derivation rules (archimate4-derivation-rules.ttl) use these: a SHACL rule queries the data graph, where the shapes are not, and reading the shapes' lists in SPARQL is slow. A potential rule derives only what these permit from the one element type to the other, so load this file with the model to run them: without it, the potential rules derive nothing. This is not an official Open Group document.

Cross-reference for Linked.Archi ArchiMate 4.0 Relationship Tables classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi ArchiMate 4.0 Relationship Tables.

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.