The Data Interoperability Dilemma. ISO 15000-5 Core Components. Process
Models, CCTS, and Syntax. CCTS and The Semantic Web. CCTS in SAP ...
Semantic Data Modeling Within and Across The Firewall
Mark Crawford Standards Architect SAP Labs
[email protected]
The Data Interoperability Dilemma ISO 15000-5 Core Components Process Models, CCTS, and Syntax CCTS and The Semantic Web CCTS in SAP
The Data Interoperability Dilemma Users Higher Education & Research
! Integrate with multiple processes and industries
Healthcare
! Do not want to learn, deploy and maintain different integration approaches
Financial Service Provider
Industry Communities ! Want complete, interoperable specifications ! Want to avoid endless reinvention
High Tech
Internal Applications
Telco
! Support data across multiple business functional areas
Chemicals
! Support interfaces with different databases and systems
Automotive Mill Products Engineering & Construction SAP 2006, EcoSystem Industry Standards / 3
Application Providors
Mining Pharma Oil & Gas Insurance Aerospace & Defense
Media Consumer Products
! Support every industry and process ! Want easier, cheaper interoperability approaches to reduce TCO
Retail Banking
How Serious is the Problem?
Internal Data Modeling relies on the experiences and vocabularies of the modeler Common Understanding and Naming is syntax and context specific Little agreement across business functions and systems
External More than 2000 different Business Standards dialects! Gartner: Only 5% of the interface is a function of the middleware choice 95% is a function of application semantics and logic
SAP 2006, EcoSystem Industry Standards / 4
The Data Interoperability Dilemma ISO 15000-5 Core Components Process Models, CCTS, and Syntax CCTS and The Semantic Web CCTS in SAP
Semantic Data Modeling Solution – ISO 15000-5 Core Components ! What:
! A methodology for developing semantic data models ! The integration mechanism for coordination between Architectures, Process Models, Data Models, and Syntax Expressions ! A way to identify, capture and maximize the re-use of business information to support and enhance information interoperability across multiple business situations ! How: ! Syntax and Context Neutral conceptual models ! Context specific physical/logical models ! Transformation to syntax specific information exchanges
SAP 2006, EcoSystem Industry Standards / 6
15000-5 is an Implementation of ISO 11179
ISO 11179 – ! Describes the standardizing and registering of data elements to make data understandable and shareable ! Provides concrete guidance on the formulation and maintenance of discrete data element descriptions and semantic content – Identifiers, Definitions, & Classification Categories ! Used to formulate data elements in a consistent, standard manner ! Provides guidance for establishing a data element registry
SAP 2006, EcoSystem Industry Standards / 7
ISO 15000-5 Benefits ! Enables interoperability among different industries and applications ! Holds related information together and avoids semantic fragmentation ! Facilitates multilingual support ! Syntax neutral "Models
can be readily expressed in XML Schema, UML diagrams, JAVA classes, SQL based relational data bases, etc.
! Guarantees semantic understanding in any technical implementation and interface ! Does not require complicated and expensive mappings between interfaces. ! Significantly reduces data total cost of ownership
SAP 2006, EcoSystem Industry Standards / 8
ISO 11179/ISO 15000-5 Naming Rules Semantic rules – enable meaning to be conveyed ! Example: Components consist of discrete terms: " Object
class terms, property terms, representation terms, qualifier terms
Syntactic rules – relate items in a consistent, specified order ! Example: a rule might require the property term is always the second component in the name
Lexical rules – (word form and vocabulary) rules reduce redundancy and increase precision ! Example: Nouns are used in the singular only
Uniqueness rule – ensures names are unique within a context. ! Example: Homonyms shall not occur in a namespace "bank (embankment) "bank (place where money is kept)
SAP 2006, EcoSystem Industry Standards / 9
ISO 11179 and ISO 15000-5 Named Constructs
11179
15000-5
Object class
Address
Property 1: representation 1 Property 2: representation 2 Property 3: representation 3 Property 4: representation 4
Street: text Post code: text Town: text Country: identifier
SAP 2006, EcoSystem Industry Standards / 10
The Core Component Model ! Core Components are the centerpiece of the approach
Core Component (CC)
Aggregate Core Component (ACC)
Association Core Component (ASCC)
+ Object Class Term: String
Registry Class
Basic Core Component (BCC) 0..*
0..*
+ Unique Identifier: String + Version Identifier: String
1
! Conceptual in nature ! Used as reference only
1
0..*
1 ASCC Property
+ Association Type: Association Type 1..*
1
CC Property
BCC Property
+ Cardinality: Cardinality + Property Term: String
+ Representation Term: Representation Term 0..*
! Never instantiated
1 1
+ Data Type Term: Data Type Term
! Intended to have single global reference model
1 1..* CDT Supplementary Component
1 CDT Content Component + Primitive Type: Primitive Type
SAP 2006, EcoSystem Industry Standards / 11
Core Data Type (CDT)
+ Cardinality: Cardinality + Primitive Type: Primitive Type
Common Information + + + + +
Business Term: String [0..*] Definition: String Dictionary Entry Name: String Possible Value: String [0..*] Usage Rule: String [0..*]
Aggregate Core Component (ACC) A collection of related pieces of business information that together convey a distinct business meaning, independent of any specific Business Context Expressed in modelling terms, it is the representation of an Object Class, independent of any specific Business Context Core Components
Aggregate Core Component
Person. Details
Basic Core Components
Person. Given. Name Person. Gender. Indicator Person. Title. Text
One property must be present, either as a BCC
Association Core Component
Person. Address
or an ASCC
SAP 2006, EcoSystem Industry Standards / 12
Basic Core Component (BCC) ! Simple properties ! Equivalent to attribute of a class ! Key feature is consistent Tri-partite Naming ! Object:Property:Representation
Core Components
Class Diagram Class
Class Attributes
Item Description Quantity Identification
SAP 2006, EcoSystem Industry Standards / 13
Aggregate Core Component
Item. Details
Basic Core Components
Item. Description. Text Item. Quantity. Quantity Item. Identification. Identifier
Core Data Type A Core Data Type signifies the “type” of information represented by a Basic Core Component.
1 Content Content Component Component carries carriesthe theactual actual value value Core Core Data Data Type Type
for creation of
Core Data Types do not contain business semantics – they are “semantic-neutral”
1..n Supplementary Supplementary Component Component gives givesextra extradefinition definition totothe value the value
Dictionary Entry Name Unqualified Data Types (CCTs + Secondary Representation Terms): . Type 22 Defined Data types
Object Class –Term Property ISO 11179 Term Conventions
Qualified Data Types: [?_*] . Typ Unlimited Related Data types
SAP 2006, EcoSystem Industry Standards / 14
Object Class Qualifier
Object Class–Term Property ISO 11179 Term Conventions
Association Core Component (ASCC) ! Complex Property ! Naming mechanism for expressing the relationship between two object classes ! Expresses the nature of the association Organization. Contact. Address Class Diagram
Association
Organization Name Identification
Aggregate Core Component
Aggregate Core Component 1..* Address Line One Line Two City Name Postal Code
SAP 2006, EcoSystem Industry Standards / 15
Organization Name Identification
Address Contact
Line One Line Two City Name Postcode
From Conceptual to Real World
SAP 2006, EcoSystem Industry Standards / 16
The Advantage of Conceptual and Context Specific Semantics Unambiguous understanding of business information in any industry (semantic) and application (technique) Same use of business information internally ( applications) and externally (between business partners Less effort for internal/external interoperability
Registry Registry & & Repository Repository CPPA CPPA
Profiles Profiles & & Scenarios Scenarios
CPPA CPPA
Catalog Catalog Catalogue Catalogue Proc. Proc.
Catalogue Catalogue Proc. Proc.
Core Core Comp. Comp. &Documents &Documents
API API
API API
Order OrderProcess Process
Order OrderProcess Process
Order Order Invoice Invoice
Pay PayProcess Process
Common Internal Process Business Process
Backend System SAP 2006, EcoSystem Industry Standards / 17
Pay PayProcess Process
Common Business Process Internal Process
Messaging Systems
ERP System
Context Specific Artifacts - Business Information Entities 1
1 Business Information Entity (BIE)
Aggregate Business Information Entity (ABIE) + Object Class Qualifier: String [0..*] + Object Class Term: String
1
Business Context
Association Business Information Entity (ASBIE)
Basic Business Information Entity (BBIE)
Registry Class + Unique Identifier: String + Version Identifier: String
0..* 1
0..* 0..*
1 Common Information
ASBIE Property + Association Type: Association Type
+ + + 0..* + +
1 BBIE Property
Business Term: String [0..*] Definition: String Dictionary Entry Name: String Possible Value: String [0..*] Usage Rule: String [0..*]
+ Representation Term: Representation Term 1..* BIE Property
Business Data Type (BDT)
1
+ Cardinality: Cardinality + Property Qualifier: String [0..*] + Property Term: String
+ Data Type Qualifier: String [0..*] + Data Type Term: Data Type Term
1..*
BDT Supplementary Component
Component Restriction 0..* + + + +
1 1 BDT Content Component + Primitive Type: Primitive Type
SAP 2006, EcoSystem Industry Standards / 18
0..*
!BIE composites are suitable for reuse with the same context values – as well as different context values !BIEs aggregate up to and including the message assembly level
1
1
+ Cardinality: Cardinality 1 + Primitive Type: Primitive Type
!BIEs are built from their corresponding CCs through the application of qualifiers and context
Expression Type: String [0..1] Expression Type Language: String [0..1] Restriction Type: Restriction Type [0..1] Restriction Value: String [0..1]
!BIEs specify restrictive data typing as appropriate for context specific instantiations !BIE models can be global, federated, or stand alone
Differentiating Context Through Qualifiers Qualifiers are used when the three data element name parts described earlier are not sufficient to uniquely identify a data element Qualifiers can be added in front of an Object Class, a Property Term, or both
Examples: !Office_ Address. City. Name " "
“Office” is a Qualifier for the “Address” Object Class Differentiates this data element from one named Home_ Address. City. Name
!Organization. Primary_ Contact. Name " "
“Primary” is a Qualifier for the “Contact” Property Term Differentiates this data element from one named Organization. Secondary_ Contact. Name
Basic Business Information Entity Credit Credit _ Object Qualifier Object Qualifier qualifies qualifies the the primary primary concept of a concept of a data data element element
Payment Payment Card Card Object Object Class Class
New New Property Property Qual. Qual.
identifies identifies the the primary concept primary concept of of aa data data element element
qualifies qualifies add. add. the the characteristics characteristics of of the the object object class class
Object SAP 2006, EcoSystem Industry Standards / 19
_
Expiration Expiration Property Property Term Term identifies identifies the the characteristics characteristics of of the the object object class class
Property
Date Date Rep. Rep. Term Term categorizes categorizes the the format of the data format of the data element element
Differentiating Context Through 8 Space Values
SAP 2006, EcoSystem Industry Standards / 20
Supporting Reuse: Metadata For Each Construct Association Information
! 9 Metadata Classes ! 35 Unique pieces of information
+ + + +
associated with 0..* Registry Class
0..* 0..1
Association Multiplicity: Cardinality Association Type: Association Type Comment: String [0..*] Usage Description: String Common Information
has a previous version
+ Unique Identifier: String 0..1 + Version Identifier: String
+ + + + +
replaced by Replacement Information
0..1
+ Replacement Date: Date + Replacement Description: String
! Maps to ebXML RIM Status Information
1 + + + + +
Comment: String [0..*] Reason: String [0..1] Reference: String [0..*] Start Date: Date Status: String
Change History + + 1..* + + + + +
Representation Information + Constraint: String [0..*] + Representation: String + Representation Syntax: String
SAP 2006, EcoSystem Industry Standards / 21
1
Administrative Information + Registrar: String + Registration Authority: String + Submitting Organisation: String
Change Date: Date Change Description: String Change Type: Change Type Comment: String [0..*] Reference: String [0..*] Request By: String Request Date: Date
Descriptive Information
0..1
0..*
Business Term: String [0..*] Definition: String Dictionary Entry Name: String Possible Value: String [0..*] Usage Rule: String [0..*]
+ + + +
Acronym: String [0..*] Comments: String [0..*] Keyword: String [0..*] Reference Document: String [0..*]
The Data Interoperability Dilemma ISO 15000-5 Core Components Process Models, CCTS, and Syntax CCTS and The Semantic Web CCTS in SAP
Coordinated Standards Are Key
# # # #
Stages of development over time Enterprise Archicture & Business Process Analysis
#
UML / UMM
Component Reuse Requirements Process Modeling Data Analysis and Design Syntax Expression
Information Analysis/Data Modeling
ISO 11179 / ISO 15000-5 XML Development
XML / XSD / NDR
Overlaps in standards SAP 2006, EcoSystem Industry Standards / 23
UN/CEFACT Modelling Methodology (UMM) Business Collaboration Patterns Business Transaction Patterns Business Information Entities Core Components
UN/CEFACT Modeling Methodology (UMM)
Registry/Repository
UMM-Metamodel
Business Domain View (BDV)
Business Requirement View (BRV)
Business Transaction View (BTV)
Business Service View (BSV)
UMM-Workflows
Business Modeling Workflow
Requirements Workflow
Analysis Workflow
Design Workflow
Business Experts
Worksheets
Analysts
Designers
• Describe Business Domain Model • Describe Business Area(s) • Describe Process Area(s) • Identify Business Process(es)
• REA-Worksheet • Business Process • Business Collaboration Specification • Business Process Metric • Business Collaboration • B-Collaboration Lifecycle • Business Entity • Business Entity Lifecycle
• Business Collaboration Protocol • Business Transaction • Business Information
• Service Collaboration • Business Objects
• Area / Process Area (Package) • Library Supported Business Processes (UseCase) • Final BDV-Use Case Diagram (UseCase)
• Business Processes and Partners (UseCase) • Business Process Activity Model (Activity) • Conceptual Business Information Model (Class) • Business Process Use Case • Business Collaboration Use Case
• Business Collaboration Object Flow Diagram • Use Case Diagram • Business Transaction Object Flow Diagram • Final Business Information Model
• Service Collaboration SequenceDiagram • BusinessObject Class Diagram
UML-Diagramtypes
SAP 2006, EcoSystem Industry Standards / 24
Creating the Syntax – Optimized XSD !Context Neutral Core Components provide the conceptual model !Context specific BIEs provide the physical model !XSD expressions following optimized Naming and Design Rules provide the syntax specific instantiations !Tight integration between all three layers maximizes interoperability within and across industries
SAP 2006, EcoSystem Industry Standards / 25
Example Progression
Organization
Organization Atlas
Data Modeling
Business Process
Class Model
1
Organization Nam e Addres s of Organization Department Name
Object Model
0..*
Inven tory Datab ase IIN - Inventory Identification Number Nam e of Organization Addres s of Organization
Item Inventory Identification Number Quantity Description
Core Component Item. Details Item. Identification. Identifier Item. Quantity Item. Description. Text
XML Development
Name Address
XML Schema
SAP 2006, EcoSystem Industry Standards / 26
0..* CPFR Database 0..* Item IIN - Inventory Identification Num ber Quantity Des cription
Product Tracked Quantity On-Hand Date IIN - Inventory Identification Number Organization Name Department Name Address of Organization Status of ForecastUpdate
Business Information Entity Availability Inventory_ Item. Details Availability Inventory_ Item. Stock_ Identification. Identifier Availability Inventory_ Item. Total_ Quantity. Quantity Availability Inventory_ Item. Description. Text
ABIE Inventory_ Item. Details Details of an inventory item. Item
The Data Interoperability Dilemma ISO 15000-5 Core Components Process Models, CCTS, and Syntax CCTS and The Semantic Web CCTS in SAP
Synergy Between CCTS, OWL, RDF and Semantic Web Semantic Web Stack
!RDF is Semantic Web locator !OWL is Semantic Web language
an t Da ic B ta as e
!Consistency to data structures, meaning and use
Se m
!CCTS can be heavy lifter at database level for easing burdens on XML/RDF/OWL
d
!XML is expression of information
!Consistency in metadata
Courtesy W3C
SAP 2006, EcoSystem Industry Standards / 28
CCTS & RDF Alignment
! RDF Triple
Subject
! Core Component Triple
Object Class
SAP 2006, EcoSystem Industry Standards / 29
Property
Property Term
Value
Representation Term (Value Domain)
As s
oc ia t
Association
io n
Association
OWL Triples # Classes (general things) in the many domains of interest # The relationships that can exist among things # The properties (or attributes) those things may have
Classes
Properties SAP 2006, EcoSystem Industry Standards / 30
R
el at
io ns hi ps
Relationships
Relationships
Core Components and OWL Alignment
Classes
la e R
s ip h ns o ti
Relationships
Properties
As
n io t a ci o s Association
CC Triples # Object Class # Associations # Properties (Property Term + Representation Term)
The Data Interoperability Dilemma ISO 15000-5 Core Components Process Models, CCTS, and Syntax CCTS and The Semantic Web CCTS in SAP
Enterprise Services (Platform View) Enterprise Standards ! Reliability, scalability, performance, security Composite Applications SAP SAP
SAP SAP
Enterprise Enterprise Services Services Repository Repository
Legacy Legacy System System
3rd 3rd Party Party
3rd 3rd Party Party
! Driven by business and legal requirements ! Mostly user-specific ! Examples: throughput of 100.000 invoices per hour, Section 508 accessibility
Web Services Standards SAP SAP NetWeaver NetWeaver
SAP SAP
! SOA using Internet standards (XML, HTTP, etc.) ! Driven by interoperability needs with partner platforms (e.g. IBM WebSphere, Microsoft .NET) ! Covered by W3C, OASIS, WS-I ! Examples: WSDL, SOAP, WSSecurity, WS-ReliableMessaging
SAP 2006, EcoSystem Industry Standards / 32
Introducing Standards for Standards Development Methodology Standards ! Modeling and design rules
Composite Applications SAP SAP
SAP SAP
3rd 3rd Party Party
! Driven by development and integration efficiency and quality needs ! Covered by OMG, UN/CEFACT ! Examples: UML, XMI, CCTS, XML NDR
$ Effectively enhance reuse and address the Business Standards Dilemma
Enterprise Enterprise Services Services Repository Repository
SAP SAP NetWeaver NetWeaver
$ SAP is leveraging ISO 15000-5 CCTS and XML NDR for the semantic-based definition of Enterprise Services $ CCTS For Global Data Types
Legacy Legacy System System
3rd 3rd Party Party
SAP SAP
SAP 2006, EcoSystem Industry Standards / 33
$ XML NDR for XML internal and External expressions
Questions?
SAP 2006, EcoSystem Industry Standards / 34
Take The Business Perspective SOA IS REQUIRED BUT NOT ENOUGH Common Business Semantics are required
+
SOA ES ESA
SAP 2006, EcoSystem Industry Standards / 35
Platform Ecosystem
Collective Innovation - Customers, Partners, ISVs & SAP - Develop and prioritize Enterprise Service Definitions
SAP 2006, EcoSystem Industry Standards / 36
Based on Open Standards - Interoperability: Web Services - Methodology: CCTS, etc.
Copyright 2006 SAP AG. All Rights Reserved ! No
part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
! Some
software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
! Microsoft,
Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
! IBM,
DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.
! Oracle ! UNIX,
is a registered trademark of Oracle Corporation.
X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
! Citrix,
ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
! HTML,
XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
! Java
is a registered trademark of Sun Microsystems, Inc.
! JavaScript
is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
! MaxDB
is a trademark of MySQL AB, Sweden.
! SAP,
R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
! These
materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP 2006, EcoSystem Industry Standards / 37
