This is version 2.0.0 of the TOGAF Content Metamodel ontology. It is based on the Content Metamodel of the TOGAF Version 9.2 standard. See TOGAF 9.2 Content Metamodel for the complete set of entities, attributes and relationships.
- Uses the name
Business Service
instead ofService
to stay consistent with the original ontology and TOGAF 9.2 Metamodel Figure 30-7. - Adds decomposition and relevant inverse properties that were missing in the version 1 of the metamodel ontology.
- Adds
Business Capability
decomposition and inverse properties that are absent in TOGAF 9.2 to make this ontology more practical. In most cases, people are interested in business capabilities breakdown and impact assessment. - Adds inverse property flag for
communicates with
andrelated to
properties forLogical Application Component
,Function
andPhysical Application Component
. - Collapses multiple properties from TOGAF 9.2 using
AndOr
convention to improve the usability of the ontology. Properties can be sub-classed later if needed. - Keeps
precedes of follows
as a single property ofProcess
as per TOGAF 9.2 section 30.7. Properties can be sub-classed later if needed. - Fixes inconsistent property naming in TOGAF 9.2 section 30.7 to create
togaf:informationSystemServiceIsUsedByDataEntity
,togaf:logicalApplicationComponentIsUsedByLogicalDataComponent
andtogaf:physicalApplicationComponentIsUsedByPhysicalDataComponent
to improve usability of the ontology. - Fixed inconsistent property naming for
Business Capability
in TOGAF 9.2 by usingtogaf:businessCapabilityIsUsedByOrganizationUnit
- Removes duplicate
togaf:logicalTechnologyComponentServesLogicalApplicationComponent
found in TOGAF 9.2 section 30.7. - Adds
hasCategory
property with no domain or range specified. Updates restrictions ontogaf:ArchitectureComponent
andtogaf:AssociationObjects
. Although linking toskos:Concept
is preferred, there are no limitations as to what resource can be used to specify the category of an entity.
Given low prior adoption of the ontology and disruptive changes to many classes disjoint statements due to Location moving to General Entities, the decision is to adopt entirely new Ontology URI for TOGAF 9.2. For earlier discussion on ontology versioning see Ontology Design Patterns Versioning and URIs and OWL Guide Ontology Versioning.
Both JSON-LD and Turtle serializations are provided out of the box to improve adoption.
Original from https://sites.google.com/site/ontologyprojects/home/togaf-core-content-metamodel is used with permission from Aurona Gerber.
Based on the paper Towards the Formalisation of the TOGAF Content Metamodel using Ontologies by Aurona Gerber, Paula Kotze and Alta van der Merwe which is using TOGAF 9.1 Content Metamodel.
A regulatory impact analysis solution based on the ontology was presented at the Semantic Web London meetup. Source code is available on https://github.com/cadmiumkitty/ontologies-for-enterprise-architecture, and the slides are on https://www.slideshare.net/EugeneMorozov/documenting-enterprise-architectures-using-ontologies.
Taxonomy mapping and transformation is based on MoneyAggVoc.
Ontology can be viewed in TopBraid EDG and WebProtege once you create an account.
Taxonomy import and visualization have been tested with VocBench 3 and TopBraid EDG. For more tools see Software for Controlled Vocabularies list maintained by BARTOC.
Taxonomies for Confluence can be used to index Confluence pages and use Confluence as an architecture repository.
TOGAF is a registered trademark of The Open Group.