Semantische Interoperabiliteit binnen het bedrijf
Voor Nederlands Genootschap voor Informatica Afdeling architectuur 12 juni 2008 Spreker Bedrijf Afdeling Functie
: Ing. Richard Claassens MIM : SNS Bank : SNS IT - Architectuur : Informatie Architect
Probleemstelling Focus : semantische interoperabiliteit/integratie binnen het bedrijf Purchased Packages
Legacy Applications E-Marketplaces HTTP/XML
“Jaguar”
Autonomous Divisions Message queue
Download file
FTP Download file
Screen scrape
CICS gateway Gateway
Transaction file
Sockets
Screen scrape
RPC
Transaction file ORB
E-mail Applications in Trading Partners
SMTP
Message queue
Transaction file
CICS gateway
Transaction file
Message queue XML/ HTTP
Browser End-User Development Message
Download file
APPC
Outsourced and ASP Applications
Applications From Mergers and Acquisitions
Jaguar?
“Geautomatiseerde systemen worden steeds meer samengesteld uit delen gedistribueerde functionaliteit die vaak onafhankelijk van elkaar ontwikkeld zijn, die zich op verschillende platforms bevinden en die zich in principe overal kunnen bevinden.
De lezing is gebaseerd op Paper: Semantische interoperabiliteit met behulp van een bedrijfsbrede taxonomie, Richard Claassens, februari 2007 http://www.via-novaarchitectura.org/magazine/reviewed/semantischeinteroperabiliteit-met-behulp-van-een-bedrijfsbrede-taxo.html
Verkenning op het gebied van Web2.0 en Enterprise2.0 http://architectureren.wetpaint.com/
Agenda Probleemstelling Wat is semantische interoperabiliteit ? Hulpmiddelen om semantiek te beschrijven en structuren Ontologie Tagging Classificatieschema|Taxonomie Faceted Approach
Bedrijfsbrede hulpmiddelen Enterprise ontologie Zachman framework IBM IFW
Semantische Interoperabiliteit Twee componenten Interoperabiliteit wisselwerking met één of meer andere autonome operatoren
Semantiek speelt pas wanneer er bij die wisselwerking tekens betrokken zijn.
Gebaseerd op : Pieter Wisse, Semantiek, interoperabiliteit en infrastructuur, http://www.informationdynamics.nl/pwisse/htm/semantiek_interoperabiliteit_infrastructuur.htm
Een basismodel van semantiek: “The Meaning Triangle” (Odgen, Richards, 1923) before: Frege, Peirce; see (Sowa 2000)
Concept(s) –or •Thought •idea •intension
(in mind)
Symbolize
Symbol(s) –or •term •label •code
Stands for
“Jaguar”
2) Example of the ambiguity of symbols (Based on Ogden & Richards, 1923)
Refers to
Referent(s) -or •thing •object •extension
Semantische stromen in bedrijfssystemen Een bedrijfssysteem bestaat uit mensen, applicaties, verschillende typen van interactie en de bijbehorende semantische stromen
Semantic
interpretation
Human
Semantic
Application
H2H
H2A
A2H
A2A
Human
origination
Application
Gebaseerd op : Dave McComb, Semantics in Business systems, The savvy manager’s guide, 2004, p. 23.
“The Meaning Triangle” afgebeeld op een bedrijfssysteem The Meaning Triangle
• ... Human Agent 1 (HA1)
Human Agent 2 (HA2)
Concept
Machine Agent 1 (MA1)
Machine Agent 2 (MA2)
Symbolize
Symbol
Refers to
Referent Stands for
exchange signs, e.g. protocols
exchange signs, e.g. nat. language
Symbols / Syntactic structures
‘‘JAGUAR“ (H2H)
(H2A),(H2A2H),(A2H)
(A2A)
Formal models
Internal models MA1
HA2
HA1
MA2
Things in the real world
a specific domain, e.g. animals
(H2H) Human to human (Based on Maedche, 2002)
(H2A),(H2A2H),(A2H) Human to application
&
Application to human
Concepts / Semantic structures
(A2A)
= flow of communication and also the flow of semantics
Application to application
Oplossingsrichting : ontologie The Meaning Triangle
• ... Human Agent 1 (HA1)
Human Agent 2 (HA2)
Concept
Machine Agent 1 (MA1)
Machine Agent 2 (MA2)
Symbolize
Symbol
Refers to
Referent Stands for
exchange signs, e.g. nat. language
exchange signs, e.g. protocols
Ontology Description
‘‘JAGUAR“
Symbols / Syntactic structures
Formal Semantics
Internal models
commit
commit
MA1
HA2
HA1 commit
Ontology
a specific domain, e.g. animals
commit
(Based on Maedche, 2002)
Formal models
Concepts / Semantic structures MA2
commit
Things in the real world
=The ontological commitment refers to agreements on the use of the shared vocabulary by the agents committed to the ontology
Welke Ontologie ? a philosophical discipline The Science of Being Comes from
Aristotle, Metaphysics. •Immanuel Kant, Charles Sanders Pierce
Ontology
Borrowed by
Research fields
Used in
Information systems
Knowledge engineering
Enterprise integration
Knowledge representation
Natural language translation
Qualitative modeling
Medicine
Language engineering
Mechanical engineering
Database design
Standardization of product knowledge
Information modeling
Electronic commerce
Information integration
Geographic information systems
Knowledge management and organization
Legal information systems
Agent based system design
Biological information systems
(Based on Guarino, 1998)
Welke Ontologie ? twee uiterste invalshoeken 2) Utmost views on ontology
1)The Meaning Triangle
Computer science viewpoint Concept
Symbolize
Symbol
An ontology is an explicit specification of a shared conceptualisation (Gruber 1995)
Refers to
Referent
An ontology is a shared understanding of some domain of interest. (Uschold et al. 1996)
Stands for
Philosophical viewpoint ... philosophical discipline, branch of philosophy that deals with the nature and the organisation of reality.” (Guarino 1998)
Welke Ontologie ? ontology
VIEW
philosophical ontology
pragmatic ontology
LEVEL
SUBJECT
PURPOSE
LANGUAGE
FORMALIZING
domain general task task specific ontology specific indeuniversal ontology ontology pendant ontology ontology language dependant ontology application specific top level specific ontology ontology ontology
formal not ontology formal ontology language independant ontology
Bodil Nistrup Madsen (2002), based on a.o.: Guarino, Nicola (1998). Formal Ontology and Information Systems,. In: Formal Ontology in Information Systems, Proceedings of the First International Conference (FOIS'98), June 6-8, Trento, Italy, 3-15. Ed. Nicola Guarino. Amsterdam: IOS Press.
Weakly structured
Strongly structured
Technieken voor het beschrijven van semantiek (op een logaritmische schaal)
Ontologies
Full topic maps
(associative)
Classification and categorization
TAO topics maps Thesauri
Faceted classification (hierarchical) Mind Maps Taxonomies Classification schemes Term Subjects headings Lists Synonym rings (flat) Authority List Controlled Vocabulary Natural language
position paper by Tore Hoel, Oslo University College, 2007
Formal, standardized language
Weakly structured
Strongly structured
..verschillende bedrijfsbrede hulpmiddelen er op afgebeeld
1) Enterprise ontology
Ontologies
Full topic maps
(associative)
Classification and categorization
TAO topics maps Thesauri
Faceted classification 4) IBM IFW (hierarchical) Mind Maps Taxonomies 3)Zachman Framework Classification schemes Term Subjects headings Lists Synonym rings (flat) Authority List Controlled Vocabulary 2) Tag Cloud Natural language
Formal, standardized language
(1) Voorbeeld: topniveau van een enterprise ontologie Enterprise
Inter-context relationship
Context
Purpose Time
Actor Action
Location
Facility Object
Somebody (actor) does Something (action), for Some reasons (purpose), for Someone (object), with the help of Something (facility), Somewhere (location) and Sometimes (time) Mauri Leppänen, A Contextual-Based Enterprise Ontology, 2007
Communities of interests and boundary objects 1) A community of practice is a group of people who do a certain type of work, talk to each other about their work, and derive some measure of their identity from that work.
2) 1)
2) A community of interest involves members of distinct communities of practice coming together to solve a particular problem of common concern (Arias and Fischer 2000). 3) 3) Boundary objects Artifacts, documents and perhaps even vocabulary that can help people from different communities build a shared understanding. Boundary objects will be interpreted differently by the different communities, and it is an acknowledgement and discussion of these differences that enables a shared understanding to be formed.
Distributed Intelligence: From Reflective Practitioners to Reflective Communities, Gerhard Fischer.Center for LifeLong Learning & Design (L3D) Department of Computer Science and Institute of Cognitive Science, University of Colorado, Boulder, http://l3d.cs.colorado.edu/~gerhard/, may 2005.
(2) Van persoonlijke tagging naar sociale tagging
Publiekelijk toegankelijk
Match?
Persoonlijke tags een gebruiker organiseert eigen data en data van anderen
Informatie objecten
Tag Cloud: A visual representation of social tags, organized into paragraph-style layout, usually in alphabetical
Tekstueel & Niet- tekstueel
Gebaseerd op presentatie: Digital categorization , 2005, Rashmi Sinha
order, where the
relative
and weight of the font for each tag to the relative frequency of its use.
size
corresponds
= voorbeeld van een boundary object
Het cognitieve proces achter digitale categorisatie (1) en tagging (2) 1) Categorisatie
Fase 0
Een informatie(object) dat de moeite waard is om terug te halen: een artikel, afbeelding, enz.
Fase 1
Meerdere concepten worden geactiveerd
Fase 2
Een van de concepten wordt gekozen
2) Tagging
Fase 0
Een informatie(object) dat de moeite waard is om terug te halen: een artikel, afbeelding, enz.
Fase 1
Meerdere concepten worden geactiveerd
Gebaseerd op presentatie: Digital categorization , 2005, Rashmi Sinha
Tagging
Registreer alle geactiveerde concepten
Categoriseer
Registreer het gekozen concept
(3)
ENTERPRISE ARCHITECTURE - A FRAMEWORK 1 DATA
2 What
FUNCTION
3 How
NETWORK
Where
4
PEOPLE
5 Who
TIME
When
TM
MOTIVATION
6 Why
SCOPE (CONTEXTUAL)
List of Things Important to the Business
List of Processes the Business Performs
List of Locations in which the Business Operates
Planner
ENTITY = Class of Business Thing
Function = Class of Business Process
Node = Major Business Location
People = Major Organizations
Time = Major Business Event
Ends/Means=Major Bus. Goal/ Critical Success Factor
e.g. Semantic Model
e.g. Business Process Model
e.g. Logistics Network
e.g. Work Flow Model
e.g. Master Schedule
e.g. Business Plan
Ent = Business Entity Reln = Business Relationship
Proc. = Business Process I/O = Business Resources
Node = Business Location Link = Business Linkage
People = Organization Unit Work = Work Product
Time = Business Event Cycle = Business Cycle
End = Business Objective Means = Business Strategy
e.g. Logical Data Model
e.g. "Application Architecture"
e.g. "Distributed System Architecture"
e.g. Human Interface Architecture
e.g. Processing Structure
Ent = Data Entity Reln = Data Relationship
Proc .= Application Function I/O = User Views
Node = I/S Function (Processor, Storage, etc) Link = Line Characteristics
People = Role Work = Deliverable
Time = System Event Cycle = Processing Cycle
End = Structural Assertion Means =Action Assertion
TECHNOLOGY MODEL (PHYSICAL)
e.g. Physical Data Model
e.g. "System Design"
e.g. "System Architecture"
e.g. Presentation Architecture
e.g. Control Structure
e.g. Rule Design
Builder
Ent = Segment/Table/etc. Reln = Pointer/Key/etc.
Proc.= Computer Function I/O = Screen/Device Formats
Node = Hardware/System Software Link = Line Specifications
Cycle = Component Cycle
e.g. Data Definition
e.g. "Program"
e.g. "Network Architecture"
People = User Work = Screen Format e.g. Security Architecture
Ent = Field Reln = Address
Proc.= Language Stmt I/O = Control Block
Node = Addresses Link = Protocols
e.g. DATA
e.g. FUNCTION
e.g. NETWORK
List of Organizations Important to the Business
List of Events Significant to the Business
List of Business Goals/Strat
SCOPE (CONTEXTUAL)
1
ENTERPRISE MODEL (CONCEPTUAL)
Planner ENTERPRISE MODEL (CONCEPTUAL)
2 Owner
SYSTEM MODEL (LOGICAL)
3 Designer
e.g., Business Rule Model
Owner
SYSTEM MODEL (LOGICAL)
Designer TECHNOLOGY CONSTRAINED MODEL (PHYSICAL)
4
5
DETAILED REPRESENTATIONS (OUT-OFCONTEXT)
SubContractor FUNCTIONING ENTERPRISE
Zachman Institute for Framework Advancement - (810) 231-0531
People = Identity Work = Job e.g. ORGANIZATION
Time = Execute
End = Condition
e.g. Timing Definition
e.g. Rule Specification
Time = Interrupt Cycle = Machine Cycle
End = Sub-condition Means = Step
e.g. SCHEDULE
Builder
Means = Action
e.g. STRATEGY
DETAILED REPRESENTATIONS (OUT-OF CONTEXT)
Sub-
Contractor FUNCTIONING ENTERPRISE
Copyright - John A. Zachman, Zachman International
(4) The Information Framework -Three views -Three levels Types of infomation
I) Organisation View
-Ten columns -Five rows II) Business View
-Fifty cells
III) Technical View
Level of constraint Deconstruction level
Structure
Strategy
Domain Concept (A-level) Domain Classification (B-level)
Composition level
Generic Template (C-level) Design Context (C’-level)
Implementation level
Operational Bound (D-level)
Business Data Concepts Classification =
(Modelware International, 1999)
Skills
Data
Functions
Workflow
Solutions
Interface
Networks
Platform
Faceted classification a Library discipline
Ranganathan 1939
To illustrate the differences between faceted and enumerative classifications, consider the class Literature. In an enumerative scheme we might have the following subclasses:
In a faceted scheme we might have the following instructions and subclasses: Citation order:
English
Language facet is cited before form facet
Prose Poetry Sonnet Ballad German Prose Poetry Sonnet Ballad French Prose Poetry Sonnet Ballad
Language facet : English German French Form facet : Prose Poetry Sonnet Ballad
Explanation of the B-level -Concept
Involved party (IP) scheme
Individual
=
Question
+
INDIVIDUAL GENDER
Answer(s) Female Male
Involved Party(IP)
INVOLVED PARTY TYPE Organization
1. Fundamental hierarchy
IP Descriptor
IP DESCRIPTOR TYPE
INDIVIDUAL EMPLOYMENT STATUS
Working Individual
ORGANIZATION LEGAL STRUCTURE TYPE
Corporation
IP IPName component NAME COMPONENT TYPE
IP RELATIONSHIP TYPE
3. Relationship hierarchy
(Modelware International, 1999)
Partnership Given Name Name Initial Family name
2. Descriptive hierarchy IP Relationship
Not Employed Individual
IP/IP-relationship
IP/IP RELATIONSHIP TYPE
IP is spouse of IP IP is employee of IP IP is customer of IP
IFW Framework B-level
-3 Layers of the data column A-level Deconstruction level
Involved Party (IP)
Arrangement (AR)
Location (LO) Event (EV)
Conceptual
Conditions (CN)
Classification (CL)
Business Direction Item (BD)
Resource Item (RI)
9 data concepts Logical
Composition level
Physical
Implementation level
(Modelware International, 1999)
Product (PD)
27 classification hierarchies C-level & C’-level
54 business objects D-level
Semantische Interoperabiliteit binnen het bedrijf
Bedrijfsbrede taxonomieën met de volgende karakteristieken: Een ‘boundary object’ voor de diverse ‘communities’, die met het bedrijfsinformatiesysteem te maken hebben als communicatiemiddel dat effectieve en efficiënte samenwerking ondersteunt
Een middel om standaardisatieprocessen te ondersteunen Voor efficiënte ontwikkeling van applicaties en koppelingen tussen geautomatiseerde systemen Vermindering van fouten in de gegevensverwerking
Initieel ontwikkeld op basis van ontologieën, die het relevante deel van de realiteit zo goed mogelijk beschrijven Om te komen tot een stabiele basisstructuur, die met minimale impact aanpasbaar en uitbreidbaar is
