Core Linked.Archi Ontology

IRI:
https://meta.linked.archi/core#
Current version:
0.1
Authors:
Kalin Maldzhanski
Publisher:
Linked.Archi
https://linked.archi
Other visualisation:
Ontology source

Abstract

Version 0.1: Initial

Table of Content

  1. Introduction
  2. Classes
  3. Object Properties
  4. Annotation Properties
  5. Namespace Declarations

Introduction

Base Ontology EA modeling.

Classes

c back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Concern

is in range of
modelAdressesConcernop, stakeholderHasConcernop, viewpointAdressesConcernop

c back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Environment

is in range of
systemInteractsWithEnvironmentop

c back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Metamodel

A Metamodel in this context is the definition(Model) of the Modeling Language, so that the Model can be expressed in a way that communicates information about a system among involved stakeholders that can be correctly interpreted by the stakeholders and supporting technologies. The Modeling language formalizes the structure, terms, notations, syntax, semantics, integrity rules, inference/derivation rules and also a set of standard Viewpoints. Well-known modeling languages include UML, SQL Schema, BPMN, E/R, OWL, and XML Schema. A model is said to conform to a modeling language.
is in domain of
conceptClassificationop, derivationRulesop, formalRulesop, modelConceptsop
is in range of
modelConformsToMetamodelop

c back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Purpose

is in range of
systemMeetsPurposeop

c back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Stakeholder

is in domain of
stakeholderHasConcernop
is in range of
systemHasStakeholderop, viewpointTargetsStakeholderop

c back to ToC or Class ToC

IRI: https://meta.linked.archi/core#System

The subject of interest of a Model that is a combination of interrelated and interdependent parts organized to achieve one or more stated purposes. As such a system is defined by its structure and purpose. A system is influenced by its environment and may be bounded by space and time. This is inclusive of designs at all levels such as an entire enterprise, a process, information structures or I.T. systems.
is in domain of
systemHasStakeholderop, systemInteractsWithEnvironmentop, systemMeetsPurposeop
is in range of
modelRepresentsSystemop

Catalogc back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Catalog

Catalog is a list of building blocks of a specific type, or of related types, that are used for governance or reference purposes (for example, an organization chart, showing locations and actors). As with building blocks, catalogs carry metadata according to the metamodel, which supports query and analysis.
has super-classes
Viewc

Diagramc back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Diagram

Diagrams are renderings of architectural content in a graphical format to allow stakeholders to retrieve the required information. Diagrams can also be used as a technique for graphically populating architecture content or for checking the completeness of information that has been collected. The TOGAF content framework defines a set of architecture diagrams to be created (e.g., organization chart). Each of these diagrams may be created several times for an architecture with different style or content coverage to suit stakeholder concerns.
has super-classes
Viewc

Elementc back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Element

has super-classes
ModelConceptc

Matrixc back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Matrix

Matrix is a grid that shows relationships between two or more model entities. Matrices are used to represent relationships that are list-based rather than graphical in their usage (for example, a CRUD matrix showing which applications Create, Read, Update, and Delete a particular type of data is difficult to represent visually).
has super-classes
Viewc

Modelc back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Model

A model is a selective representation of some system whose form and content are chosen based on a specific set of concerns. The model is related to the system by an explicit or implicit mapping. The scope and context of a Model is established by analysing the domain subject area and defined by the Metamodel. High-level domains may include: ??? Telecommunications ??? Healthcare ??? Retail ??? Manufacturing ??? Transportation ??? Defense ??? Government More precise domains within a particular organization may be related to the different organizational bodies and depertments such as * Enterprose Architecture * Solution Architecture * Security Architecture, * Software Engineering * Operational Services * Business Departments...
is in domain of
modelAdressesConcernop, modelConformsToMetamodelop, modelRepresentsSystemop
is in range of
conceptContainedInModelop

ModelConceptc back to ToC or Class ToC

IRI: https://meta.linked.archi/core#ModelConcept

has sub-classes
Elementc, Relationshipc, Viewc
is in domain of
alternative Visual Notation, conceptContainedInModelop, conceptExposedInViewop, derivedFrom, preferred Visual Notation

Relationshipc back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Relationship

arch:Relationship is the Class for relationships between Architecture concepts. arch:Relationship is an instance of rdf:Class and subclass of rdf:Property. arch:Relationship instances are to be defined in specific Architecture Model Vocabbularies and used in triples and statements as predicates.
has super-classes
object propertyc
ModelConceptc

Viewc back to ToC or Class ToC

IRI: https://meta.linked.archi/core#View

Architecture View is a representation of a system from the perspective of a related set of concerns. It consists of one or more architecture models of the system
has super-classes
ModelConceptc
has sub-classes
Catalogc, Diagramc, Matrixc
is in domain of
viewConformsToViewpointop
is in range of
conceptExposedInViewop

Viewpointc back to ToC or Class ToC

IRI: https://meta.linked.archi/core#Viewpoint

An architecture Viewpoint is a specification of the conventions for a particular kind of architecture view. It can also be called the definition or schema for that kind of architecture view. It establishes the conventions for constructing, interpreting, and using an architecture view to address a specific concern (or set of concerns) about a system-of-interest. A viewpoint can be seen as a diferent perspective of the subject area that shapes the Metamodel, which defines the Model. Viewpoints may look quite different so as to be meaningful to different stakeholders
is in domain of
purpose, technique, viewpointAdressesConcernop, viewpointTargetsStakeholderop
is in range of
viewConformsToViewpointop

Object Properties

conceptClassificationop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#conceptClassification

ConceptClassification property specifies the document that defines the classification of the Elements, Relationships and Viewpoints defined within a Metamodel. One way to express those is SKOS.
has domain
c

conceptContainedInModelop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#conceptContainedInModel

Concepts property that specifies the Model that contains that Concept such as Elements, Relationships or other Views. In the case of a relationshipRDF* or statement can be used to link the triple with the View. Note that Model propery of a concept can be expressed via quads.
has domain
ModelConceptc
has range
Modelc

conceptExposedInViewop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#conceptExposedInView

Concepts property that specifies the individual Views that exposes that Concept such as Elements, Relationships or other Views. In the case of a relationshipRDF* or statement can be used to link the triple with the View.
has domain
ModelConceptc
has range
Viewc

derivationRulesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#derivationRules

DerivationRules property specifies the document that defines the possible derivation rules. A way to express those rules could be N3 notation.
has domain
c

formalRulesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#formalRules

FormalRules property specifies all the rules that a Model needs to conform to. This include Element structure, relationships, properties even naming conventions. A way to represent those rules can be SHACL.
has domain
c

modelAdressesConcernop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#modelAdressesConcern

has domain
Modelc
has range
c

modelConceptsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#modelConcepts

ModelConcepts property specifies the document that defines the structure, terms, notations, semantics and basic syntax of the modeling language.
has domain
c

modelConformsToMetamodelop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#modelConformsToMetamodel

has domain
Modelc
has range
c

modelRepresentsSystemop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#modelRepresentsSystem

has domain
Modelc
has range
c

specURLop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#specURL

has super-properties
urlop
is also defined as
annotation property

stakeholderHasConcernop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#stakeholderHasConcern

has domain
c
has range
c

systemHasStakeholderop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#systemHasStakeholder

has domain
c
has range
c

systemInteractsWithEnvironmentop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#systemInteractsWithEnvironment

has domain
c
has range
c

systemMeetsPurposeop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#systemMeetsPurpose

has domain
c
has range
c

viewConformsToViewpointop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#viewConformsToViewpoint

viewpoint property specifies the Viewpoint individual of a particular View instance
has domain
Viewc
has range
Viewpointc

viewpointAdressesConcernop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#viewpointAdressesConcern

has domain
Viewpointc
has range
c

viewpointTargetsStakeholderop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/core#viewpointTargetsStakeholder

Viewpoint property that relates targeted stakeholders. While this relationship can be infered from arch:viewpointAdressesConcern and arch:stakeholderHasConcern it ia not always the case when concerns overlap or there are different visula notations and representation preferences form the side of the stakeholders. In other words this is explicitly defined by the designer of the particular viewpoint and can match all or a subsets of the stakeholders. In some case it
has domain
Viewpointc
has range
c

Annotation Properties

alternative Visual Notationap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#altVisNotation

A resource can have more than one value of arch:altVisNotation
has super-properties
imageap
has domain
ModelConceptc

creatorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/creator

derivedFromap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#derivedFrom

DerivedFrom property specifies if the specific concept is derived and what is the derivation rule, facts related to the derivation or any other related information. As within the context of Linkeed.Archi derivation is considered as one of the main aspects and feaatures of a Linked Architecture we encourage its usage. Note that this generic concept of derivation can be futher extended using prov-o ontology specificaally using prov:wasGeneratedBy, prov:wasDerivedFrom or other related propeerties. For complex tracking of derivations a specific Indidual may be used to contain that information similarly as prov:Derivation, prov:Generation, prov:Activity, etc.
has domain
ModelConceptc

descriptionap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/description

imageap back to ToC or Annotation Property ToC

IRI: http://schema.org/image

has sub-properties
alternative Visual Notationap, preferred Visual Notationap

issuedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/issued

licenseap back to ToC or Annotation Property ToC

IRI: http://creativecommons.org/ns#license

modifiedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/modified

preferred Visual Notationap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#prefVisNotation

A resource has no more than one value of arch:prefVisNotation
has super-properties
imageap
has domain
ModelConceptc

publisherap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/publisher

purposeap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#viewpointHasPurpose

has domain
Viewpointc

specURLap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#specURL

is also defined as
object property

techniqueap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#technique

has domain
Viewpointc

titleap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/title

Namespace Declarations back to ToC

default namespace
https://meta.linked.archi/core#
core
https://meta.linked.archi/core#
dc
http://purl.org/dc/elements/1.1/
ns
http://creativecommons.org/ns#
owl
http://www.w3.org/2002/07/owl#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
schema
http://schema.org/
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.