The document discusses the BPMN 2.0 metamodel and schema. It explains that all valid BPMN models must conform to the specifications of the metamodel, which defines elements as object classes with required and optional attributes. It also summarizes that the BPMN XSD schema separates the graphical and semantic models, defines elements and their attributes, and that IDs must follow certain naming conventions. Import and targetNamespace attributes allow modularization and reuse across multiple BPMN files that constitute a single model.

1. Chapter 12
BPMN 2.0
Metamodel
and Schema
By: Maram A. Fadel

2. Introduction
01
MetaModel
XSD Basics
02
BPMN Schema
Fundamentals
03
XSD Files, Semantic and
Graphical Models, IDs and
ID References, Import,
targetNamespace, and
Remote ID References
Table of
Contents

3. All valid BPMN models must conform to the
specifications of the metamodel.
Metamodel elements are defined as object classes
with defined required and optional attributes.
Some classes are subtypes of other classes and
inherit their attributes, while adding more of
their own.
Introduction

5. An XML schema is itself an XML document. You can
view or edit it as tagged text, but many
XML tools also provide a graphical view that is more
helpful for understanding the schema
structure.
XSD Basics

6. An XML schema is itself an XML document. You can
view or edit it as tagged text, but many
XML tools also provide a graphical view that is more
helpful for understanding the schema
structure.
XSD Basics
The XSD defines the element names and datatypes,
their attributes and child elements. A
BPMN 2.0 model is, by definition, incorrect unless it
is a valid instance of the schema.

8. XSD Files
The BPMN 2.0 schema is distributed as a set of five XSD files:
BPMN20.xsd, Semantic.xsd,BPMNDI.xsd, DI.xsd, and DC.xsd.
Implementers should store them locally in the same folder.
BPMN20.xsd is the top level. It includes Semantic.xsd and
imports BPMNDI.xsd, which in turn imports DI.xsd and
DC.xsd.
BPMN Schema
Fundamentals
By itself, BPMN20.xsd represents the Infrastructure package
of the BPMN metamodel Core. It contains just two elements,
definitions and import.

9. Semantic and Graphical Models:
In the BPMN XSD, the graphical model – information
concerning the graphical layout of shapes, such as position,
size, and connection points – is entirely separate from the
semantic model.
BPMN Schema
Fundamentals
By itself, BPMN20.xsd represents the Infrastructure package
of the BPMN metamodel Core. It contains just two elements,
definitions and import.

10. IDs and ID References:
Most elements in the BPMN 2.0 XSD have an id attribute of
type xsd:ID, a type defined by the XSD language for use in
attributes only. ID types have special requirements. Their
values must start with either a letter or underscore, and can
contain only letters, digits, underscores,hyphens, and
periods.
BPMN Schema
Fundamentals

11. Import, targetNamespace, and Remote ID References:
Recall that a BPMN instance document may import other
BPMN instance documents. This is not the same as an XSD
file importing another XSD file, but it works in a similar
manner. One of the documents represents the top level or
root of the BPMN model, but all the documents together
constitute a single BPMN model. This import feature is the
key to BPMN modularity and reuse.
BPMN Schema
Fundamentals

12. CREDITS: This presentation template was
created by Slidesgo, including icons by Flaticon,
and infographics & images by Freepik
Thanks