Linked.Archi ArchiMate 3.2 Viewpoint Conformance Shapes

Linked.Archi ArchiMate 3.2 Viewpoint Conformance Shapes: Overview back to ToC

This ontology has the following classes and properties.

Linked.Archi ArchiMate 3.2 Viewpoint Conformance Shapes: Description back to ToC

Viewpoint conformance for ArchiMate 3.2 models. The rules are in the core shapes, which this document imports, and it adds none of its own: 1. Viewpoint declaration — every View declares exactly one viewpoint, as an arch:Viewpoint individual rather than a literal. 2. View type conformance — a View's rdf:type must match one of the viewpoint's arch:viewType values (Diagram, Catalog, Matrix). 3. Element conformance — elements presented in a View, linked by arch:inView, must be instances of types the viewpoint's arch:includesConcept allows. 4. Relationship endpoint conformance — the endpoints of a relationship drawn on a View should themselves be in the viewpoint's palette. 5. Viewpoint completeness — a viewpoint should declare what it admits, the concerns it frames and which kinds of view realise it. They read the viewpoint definitions from the loaded graph rather than naming any viewpoint, and use no ArchiMate term, so core states them once for every language: ArchiMate example viewpoints, custom viewpoints and other frameworks' alike. A rule that only ArchiMate 3.2 viewpoints need would go here. Usage: load the core shapes with the 3.2 viewpoint catalogue and the model. core-onto.ttl and the 3.2 ontology go in the shapes graph and the data: the shapes target arch:View and arch:Viewpoint, and their SPARQL walks rdfs:subClassOf* in the data.

Cross-reference for Linked.Archi ArchiMate 3.2 Viewpoint Conformance Shapes classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi ArchiMate 3.2 Viewpoint Conformance Shapes.

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.