language en

Linked.Archi BPMN Cross-Language Mappings

Modified on: 2026-09-05
Revision:
0.1.0
Issued on:
2026-09-05
Authors:
Kalin Maldzhanski
Source:
https://pubs.opengroup.org/architecture/archimate3-doc/
https://pubs.opengroup.org/architecture/archimate4-doc/
https://www.omg.org/spec/BPMN/2.0.2/
See also:
https://www.omg.org/spec/BPMN/2.0.2/
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://creativecommons.org/licenses/by/4.0/
Visualization:
Visualize with WebVowl
Cite as:
Kalin Maldzhanski. Linked.Archi BPMN Cross-Language Mappings. Revision: 0.1.0.
Provenance of this page
Ontology Specification Draft

Linked.Archi BPMN Cross-Language Mappings: Overview back to ToC

This ontology has the following classes and properties.

Annotation Properties

Linked.Archi BPMN Cross-Language Mappings: Description back to ToC

Cross-language SKOS mappings between BPMN 2.0.2 concepts and ArchiMate modeling language concepts, for both ArchiMate 3.2 and ArchiMate 4.0. These mappings are editorial. No official document maps BPMN to ArchiMate: the ArchiMate specification notes that BPMN can be used to detail business processes but defines no element-level correspondence, and the OMG BPMN specification does not mention ArchiMate. The assertions here express semantic proximity based on the concept definitions in the two specifications. The dominant predicate is deliberately skos:relatedMatch rather than skos:closeMatch, because the two notations model behaviour at different granularities and for different purposes. BPMN describes executable control flow — order, gateways, message exchange, exception paths. ArchiMate describes architectural behaviour and its relationship to structure, and its finest behavioural grain is coarser than a BPMN task. A mapping that claimed these coincide would overstate what a cross-notation query can conclude. BPMN Lite reaches these mappings through its own concept-level assertions: each bpmnl: class carries skos:exactMatch to its bpmn: counterpart, so a query that follows both hops resolves a BPMN Lite type onto the ArchiMate correspondences below. Not mapped, deliberately: bpmn:EventBasedGateway and bpmn:ComplexGateway (no ArchiMate construct expresses event-driven or condition-driven routing); bpmn:Gateway itself (abstract, with the routing semantics carried by its subclasses); and the BPMN serialization and extension machinery, which describes documents rather than architecture.

Cross-reference for Linked.Archi BPMN Cross-Language Mappings classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi BPMN Cross-Language Mappings.

Annotation Properties

close matchap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#closeMatch

creatorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/creator

descriptionap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/description

issuedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/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/terms/modified

preferred namespace prefixap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespacePrefix

preferred namespace uriap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespaceUri

related matchap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#relatedMatch

sourceap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/source

titleap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/title

Legend back to ToC

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.