ISOTC184/SC4
ISO TC184/SC4/WG10 1
IIDEAS
Integrating Data or Ontologies - A look at the ISO 18876 Architecture
Matthew West
ISOTC184/SC4
ISO TC184/SC4/WG10 2
IIDEAS
Requirements
• Support Data Integration & Sharing– Consolidation of different data sets– Integration of different data models (ontologies)– Use of different languages
ISOTC184/SC4
ISO TC184/SC4/WG10 3
IIDEAS
Integration models
M1 M2
IM1
ISOTC184/SC4
ISO TC184/SC4/WG10 4
IIDEAS
Integration models
M1 M2 M3 M4 M5
IM1 IM2
ISOTC184/SC4
ISO TC184/SC4/WG10 5
IIDEAS
Integration models
M1 M2 M3 M4 M5
IM1 IM2
M6
IM3
ISOTC184/SC4
ISO TC184/SC4/WG10 6
IIDEAS
Integration Model
External Model
Mapping
What you really want ...
A B D
C++C
ISOTC184/SC4
ISO TC184/SC4/WG10 7
IIDEAS
The scope of a model must fit within a defined context for internal consistency.
Context
Scope
Context and Scope
ISOTC184/SC4
ISO TC184/SC4/WG10 8
IIDEAS
Models which are developed in different contexts, will be incompatible.
Outside Context
Context and Scope
ISOTC184/SC4
ISO TC184/SC4/WG10 9
IIDEAS
Data models must have the same context in order to fit together.
Context and Scope
ISOTC184/SC4
ISO TC184/SC4/WG10 10
IIDEAS
Conceptual Model
External Model
Mapping
Mapping to a Conceptual Model
A B
C
1 2
1' 2'
ISOTC184/SC4
ISO TC184/SC4/WG10 11
IIDEAS
Conceptual Model
External Model
Mapping
Mapping to a Conceptual Model
A B
C
1 2
1' 2'
3Consolidate
ISOTC184/SC4
ISO TC184/SC4/WG10 12
IIDEAS
IntegrationArchitecture
IntegrationModel
• ISO 15926-2• “STEP IM”• “SC4 IM”
• EXPRESS• EXPRESS-X• EXPRESS-2• EXIST
Languages
Integration &Mapping
Methodology
Parts 1 & 2of ISO18876.
Standards
ISOTC184/SC4
ISO TC184/SC4/WG10 13
IIDEAS
Mapping and integration methodology - requirements
• Methods describing the following processes:– extending an integration model to meet new
requirements– selecting a “subset” of the integration model that
satisfies the semantics of a particular external/application model
– defining the mapping(s) between the selected subset and the structure of the external/application model
ISOTC184/SC4
ISO TC184/SC4/WG10 14
IIDEAS
FoundationConcepts
GeneralConcepts
Discipline-specificConceptsD
eriv
ed c
once
pts
Integration model
Integration Architecture
ApplicationModel
ApplicationModel
Mapping
Integration Model Subset
Integration Model Subset
Subset
Selection
ISOTC184/SC4
ISO TC184/SC4/WG10 15
IIDEAS
Mapping
• Specification of the transformations between a “subset” of the IM and an external/application data model
• Includes:– structural changes– terminology changes
IMIMAMAM
Analysis
Integration vs. Mapping
IMIMIM’IM’AMAM
IntegrationAnalysis
Integration vs. Mapping
IMIMIM’IM’
Integration Model Subset
Integration Model Subset
AMAM
IntegrationAnalysis
Sub-setting
Integration vs. Mapping
Mapping
IMIMIM’IM’
Integration Model Subset
Integration Model Subset
AMAM
IntegrationAnalysis
Sub-setting
Integration vs. Mapping
ISOTC184/SC4
ISO TC184/SC4/WG10 20
IIDEAS
Organisation
Integration ModelIntegration Model Mapping Specification
Model
Reference Classes
Reference Individuals
Integration Model Subset
Constraint Specification
Model Specification
Language
Mapping Specification
Language
Structure Transformation
Application Model
Model
Reference Classes
Reference Individuals
Model Specification
Language
Terminology Translation
ISOTC184/SC4
ISO TC184/SC4/WG10 21
IIDEAS
Basic Elements
IntegratedSchema
UnconstrainedSub-Schema
ConstrainedSub-Schema
IntegratedSchema
UnconstrainedSub-Schema
Synchronous (only master held)
Asynchronous (copy at each end)
Synchronous Two way mapping
server client
server client
Virtual Schema
persistent schema
ISOTC184/SC4
ISO TC184/SC4/WG10 22
IIDEAS
Integrated System
IntegratedSystemSchema
UnconstrainedSub-Schema A
ConstrainedSub-Schema B
ConstrainedSub-Schema C
ConstrainedSub-Schema D
UnconstrainedSub-Schema E
ConstrainedSub-Schema F
ConstrainedSub-Schema G
ISOTC184/SC4
ISO TC184/SC4/WG10 23
IIDEAS
Notes
• The previous slide represents a traditional integrated system.
• Sub-schemas can be seen as like SQL views for particular functions.
• This represents Full Integration
ISOTC184/SC4
ISO TC184/SC4/WG10 24
IIDEAS
Tightly Coupled - Type 1
System 1Schema
System 2Schema
Sub-Schema A Sub-Schema A
ISOTC184/SC4
ISO TC184/SC4/WG10 25
IIDEAS
Notes
• This is essentially the “wrappering” of one application for some of its data.
• The access is synchronous
ISOTC184/SC4
ISO TC184/SC4/WG10 26
IIDEAS
Loosely Coupled - Type 1
System 1Schema
System 2Schema
Sub-Schema A Sub-Schema A
ISOTC184/SC4
ISO TC184/SC4/WG10 27
IIDEAS
Notes
• Here asynchronous data exchange is used with controlled data duplication
• An unlikely case (except by design) when the two data models happen to match where they overlap.
ISOTC184/SC4
ISO TC184/SC4/WG10 28
IIDEAS
Tightly Coupled - Type 2
System 1Schema
System 2Schema
Sub-Schema A Sub-Schema A
ISOTC184/SC4
ISO TC184/SC4/WG10 29
IIDEAS
Notes
• A sub-schema of one application is defined as a view on another
• Point to point interface• Synchronous access• A form of Federation
ISOTC184/SC4
ISO TC184/SC4/WG10 30
IIDEAS
Loosely Coupled - Type 2
System 1Schema
System 2Schema
Sub-Schema A Sub-Schema A
ISOTC184/SC4
ISO TC184/SC4/WG10 31
IIDEAS
Notes
• Point to point interface• Asynchronous communication• A form of Federation
ISOTC184/SC4
ISO TC184/SC4/WG10 32
IIDEAS
Synchronous Messaging
MessagingSystem
1
32
A
A
C
B
A
C
C
C
B
B
ISOTC184/SC4
ISO TC184/SC4/WG10 33
IIDEAS
Notes
• Communication is synchronous• The messaging system makes a connection
on demand• This is a form of Federation
ISOTC184/SC4
ISO TC184/SC4/WG10 34
IIDEAS
Asynchronous Messaging
MessagingSystem
1
32
A
A
C
B
A
C
C
C
B
B
ISOTC184/SC4
ISO TC184/SC4/WG10 35
IIDEAS
Notes
• This messaging system puts most of the intelligence with the applications
• Communication is asynchronous• Publish and Subscribe is a version of this• This is a form of Federation
ISOTC184/SC4
ISO TC184/SC4/WG10 36
IIDEAS
Centrally managed messaging
Messaging System
1
32
A
A’
C
B
A’
C’
C C’’
B’
B
B’
C’
C’’
A
ISOTC184/SC4
ISO TC184/SC4/WG10 37
IIDEAS
Notes
• This messaging system has a central model and external mappings to each system
• The complexity is managed centrally, rather than being replicated for each application
• A form of Federation
ISOTC184/SC4
ISO TC184/SC4/WG10 38
IIDEAS
Shared Database
Shared Database1
32
X
X
Y
YZ
Z
ISOTC184/SC4
ISO TC184/SC4/WG10 39
IIDEAS
Notes
• This option shows a simple shared database as the master for shared data.
• Data is made available through application specific views
• Access is synchonous
ISOTC184/SC4
ISO TC184/SC4/WG10 40
IIDEAS
Loosely Integrating Database
IntegratingSystem
1
32
X
X
Y
YZ
Z
ISOTC184/SC4
ISO TC184/SC4/WG10 41
IIDEAS
Notes
• Integration through controlled data duplication• Mapping is done dynamically on demand for
a data set• Mappings managed centrally• Asynchronous
ISOTC184/SC4
ISO TC184/SC4/WG10 42
IIDEAS
Conclusions
• The IIDEAS Architecture describes what is necessary to achieve integration
• Mapping is fundamental to the whole architecture
• Integration of all shared concepts into the integration model is also critical
ISOTC184/SC4
ISO TC184/SC4/WG10 43
IIDEAS
Questions?