1 / 43

Integrating Data or Ontologies - A look at the ISO 18876 Architecture

Integrating Data or Ontologies - A look at the ISO 18876 Architecture. Matthew West. Requirements. Support Data Integration & Sharing Consolidation of different data sets Integration of different data models (ontologies) Use of different languages. IM 1. M 1. M 2. Integration models.

beatrizw
Download Presentation

Integrating Data or Ontologies - A look at the ISO 18876 Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integrating Data or Ontologies - A look at the ISO 18876 Architecture Matthew West ISO TC184/SC4/WG10

  2. Requirements • Support Data Integration & Sharing • Consolidation of different data sets • Integration of different data models (ontologies) • Use of different languages ISO TC184/SC4/WG10

  3. IM1 M1 M2 Integration models ISO TC184/SC4/WG10

  4. IM1 IM2 M1 M2 M3 M4 M5 Integration models ISO TC184/SC4/WG10

  5. IM3 IM1 IM2 M1 M2 M3 M4 M5 Integration models M6 ISO TC184/SC4/WG10

  6. What you really want ... C C++ Integration Model Mapping A B D External Model ISO TC184/SC4/WG10

  7. Context and Scope Context Scope The scope of a model must fit within a defined context for internal consistency. ISO TC184/SC4/WG10

  8. Context and Scope Outside Context Models which are developed in different contexts, will be incompatible. ISO TC184/SC4/WG10

  9. Context and Scope Data models must have the same context in order to fit together. ISO TC184/SC4/WG10

  10. Mapping to a Conceptual Model C Conceptual Model 1' 2' Mapping A B 1 2 External Model ISO TC184/SC4/WG10

  11. Mapping to a Conceptual Model 3 Consolidate C Conceptual Model 1' 2' Mapping A B 1 2 External Model ISO TC184/SC4/WG10

  12. IntegrationArchitecture • IntegrationModel • ISO 15926-2 • “STEP IM” • “SC4 IM” Parts 1 & 2of ISO18876. • EXPRESS • EXPRESS-X • EXPRESS-2 • EXIST • Languages Integration &MappingMethodology Standards ISO TC184/SC4/WG10

  13. 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 ISO TC184/SC4/WG10

  14. Integration Model Subset Foundation Concepts Subset Selection Mapping General Concepts Derived concepts Discipline-specific Concepts Application Model Integration model Integration Architecture ISO TC184/SC4/WG10

  15. Mapping • Specification of the transformations between a “subset” of the IM and an external/application data model • Includes: • structural changes • terminology changes ISO TC184/SC4/WG10

  16. Analysis AM Integration vs. Mapping IM

  17. Integration Analysis AM Integration vs. Mapping IM IM’

  18. Integration Analysis AM Integration Model Subset Sub-setting Integration vs. Mapping IM IM’

  19. Integration Analysis AM Mapping Integration Model Subset Sub-setting Integration vs. Mapping IM IM’

  20. Organisation Integration Model Application Model Mapping Specification Integration Model Model Specification Language Model Specification Language Mapping Specification Language Integration Model Subset Model Model Constraint Specification Reference Classes Reference Classes Structure Transformation Reference Individuals Reference Individuals Terminology Translation ISO TC184/SC4/WG10

  21. Basic Elements Virtual Schema persistent schema ConstrainedSub-Schema UnconstrainedSub-Schema UnconstrainedSub-Schema IntegratedSchema IntegratedSchema Synchronous Two way mapping Synchronous (only master held) server client Asynchronous (copy at each end) server client ISO TC184/SC4/WG10

  22. Integrated System ConstrainedSub-Schema F ConstrainedSub-Schema B IntegratedSystemSchema UnconstrainedSub-Schema A ConstrainedSub-Schema G ConstrainedSub-Schema C UnconstrainedSub-Schema E ConstrainedSub-Schema D ISO TC184/SC4/WG10

  23. 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 ISO TC184/SC4/WG10

  24. Tightly Coupled - Type 1 System 1Schema System 2Schema Sub-Schema A Sub-Schema A ISO TC184/SC4/WG10

  25. Notes • This is essentially the “wrappering” of one application for some of its data. • The access is synchronous ISO TC184/SC4/WG10

  26. Loosely Coupled - Type 1 System 1Schema System 2Schema Sub-Schema A Sub-Schema A ISO TC184/SC4/WG10

  27. 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. ISO TC184/SC4/WG10

  28. Tightly Coupled - Type 2 System 1Schema Sub-Schema A Sub-Schema A System 2Schema ISO TC184/SC4/WG10

  29. Notes • A sub-schema of one application is defined as a view on another • Point to point interface • Synchronous access • A form of Federation ISO TC184/SC4/WG10

  30. Loosely Coupled - Type 2 System 1Schema Sub-Schema A Sub-Schema A System 2Schema ISO TC184/SC4/WG10

  31. Notes • Point to point interface • Asynchronous communication • A form of Federation ISO TC184/SC4/WG10

  32. Synchronous Messaging B 1 MessagingSystem A A C B C A B C 2 3 C ISO TC184/SC4/WG10

  33. Notes • Communication is synchronous • The messaging system makes a connection on demand • This is a form of Federation ISO TC184/SC4/WG10

  34. Asynchronous Messaging B 1 MessagingSystem A A C B C A B C 2 3 C ISO TC184/SC4/WG10

  35. 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 ISO TC184/SC4/WG10

  36. Centrally managed messaging B 1 B A A Messaging System C’ C’ B’ A’ 3 B’ 2 A’ C’’ C C C’’ ISO TC184/SC4/WG10

  37. 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 ISO TC184/SC4/WG10

  38. Shared Database Shared Database 1 Z X X Y 3 Z 2 Y ISO TC184/SC4/WG10

  39. 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 ISO TC184/SC4/WG10

  40. Loosely Integrating Database IntegratingSystem 1 Z X X Y 3 Z 2 Y ISO TC184/SC4/WG10

  41. Notes • Integration through controlled data duplication • Mapping is done dynamically on demand for a data set • Mappings managed centrally • Asynchronous ISO TC184/SC4/WG10

  42. 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 ISO TC184/SC4/WG10

  43. Questions? ISO TC184/SC4/WG10

More Related