XML Metadata Interchange (XMI)

U ni ys
s
We eat, sleep and drink this stuff (metadata)!

XML Metadata Interchange (XMI)
From UML Object Models to
XML DTDs and Documents

OMG TC Meeting
November 15-18 ; Cambridge
Sridhar Iyengar
Unisys Fellow
Unisys Corporation
sridhar.iyengar2@unisys.com

Copyright 1999, UNISYS Corporation Slide 1

Topics Covered
s Introduction
s OMG Modeling and Metadata Architecture
– XMI, UML and MOF
– Applied to Enterprise Application Development,
CORBA Components, Data Warehousing
– Coming : Document Management, Business
Objects, Vertical Domains, EAI
s How can OMG (across various groups), OAG,
OASIS work together


Model & Metadata based
Integration : Sample Initiatives
s Modeling Technologies
– Modeling OMG UML, (Meta)Modeling OMG MOF
s Metadata Integration Technologies
– W3C XML, OMG XMI, OMG MOF
s Information/Content Models, Meta Models, DTDs
– OMG UML, Data Warehousing CWM, CORBA CCM,
Document Management, MDC OIM, Knowledge
Management, OMG EAI WG, .. OMG Vertical domains,
OAG, OASIS, BizTalk..
s Middleware Infrastructure
– CORBA/CCM, EJB, COM+, HTTP, XML, SOAP...

OMG Overview
• About 800 member companies, world’s largest software
consortium.
• Founded April 1989.
• Small staff (27 full time); no internal development. In
U.S.A., Germany, Japan, U.K, Australia, India.
• Started the Object World series of conferences, which
continues as COMDEX/Enterprise.
• Dedicated to creating and popularizing object-oriented
standards for application integration and development

OMG History : Major Events
s 1989 OMA Vision & Architecture
s 1991 CORBA 1.0
s 1995 CORBA 2.0 IIOP - CORBA
InteroperabilityDemo
s 1997 MOF and UML Adopted, Domain
specs begin to be adopted
s 1998 XMI Specification & Demo
s 1999 XMI, CORBA 3.0 Components
s 2000 CWM, XML/CORBA, EAI...


OMG Metadata Summary

UML MOF
Model & Design Manage &
Discover
XMI
Framework
DTDs
Documents
Schemas*

XML EAI?
CCM
CWM
* Target XMI 1.2 eXchange UML

The Unisys Application Life Cycle
Architecture Centric, Business driven,
Iterative and Incremental Manage
Discovery and
Transformation Components

Modeling Add Component
Build /Wrap Assemble Configure
Architecture, Business Runtimes
Integrate & Test &Deploy
Object, Data… Logic (EJB, CCM..)
Components Components Components
Models, Metadata, Components, Middleware

Business
Requirem Rigorous Acquired
ents
Components
Modeling
Short Cut!

Work In Progress!

OMG Metadata and Modeling
Architecture

Tools, Applications, Repositories, Registries

MetaModels (UML, CCM, CWM…)

XML Metadata Interchange (XMI)
Meta Object Facility (MOF)
Object Services

Internet CORBA Java
CORBA/COM Interworking


OMG OMA Architecture
and Metadata Repositories

Repositories Repository Common Facility
Tools
Applications MOF XMI UML, CWM

APIs APIs
Information
MetaModels
CORBA, Internet,...

Object Services (Naming, Transactions…)

Iyengar (c) 1995, Unisys


A UML rendering of the OMA

<<Subsystem>>
<<Subsystem>>
Applications, <<Met adata/Models>>
Tools, Repositories Business Domain Frameworks Horizontal Technology
(Air Traffic, Financial...) Frameworks (UML, MOF, XMI...)

<<Subsystem>>
CORBA ORB CORE, IIOP Engine...

<<Subsystem>> <<Subsystem>>
<<Subsystem>>
Object Services Interface, Component,
(Transactions, Security) Application Management
MetaObject Repositories
Frameworks

Object Management Achitecture (With UML/MOF/XMI) using the UML Notation
(c) 1999, Unisys Corporation (Iyengar99)

OMG Development/Metadata
Environment

<<Subsystem>> Java/C++ Component Component
UML Modeling IDE's Assembly Tools Management Tools
Tools

<<OMG Metadata>> <<Subsystem>>
XMI Framework CORBA ORB CORE, IIOP Engine, Java/IDL,
COM/CORBA...
(from OMG Object Management Architecture (MOF/UML/XMI))

<<Subsystem>> <<Subsystem>> <<Subsystem>> <<Subsystem>>
UML CWM MOF Component
Repositories Warehouses Repositories Repositories

OMG Metadata Architecture showing use of CORBA or XMI
(c) 1999, Unisys (Iyengar99)


OMG - Modeling and Metadata
Standards
s Object Analysis & Design Facility : Unified
Modeling Language (UML)
s Model driven Metadata Management : Meta
Object Facility (MOF)
s Stream based Model Interchange Format : XML
Metadata Interchange (XMI)
s Data Warehouse Management : Common
Warehouse Metamodel (CWM*)
s Business Objects : Business Object Initiative
(BOI*)
*In development

Four Layer Metamodeling
Architecture
User Objects <Acme_Software_Share
Layer (M0) 98789>, 654.56, sell_limit_
order, <Stock_Quote_Svr
32123>

Model StockShare, askPrice,
Layer(M1) sellLimitOrder,
StockQuoteServer
[Models, BODs, CBOs..]

Metamodel UML::Class,Attribute,
Layer(M2) Operation, Component
[UML, CWM, EAI…]

Meta-Metamodel MOF::Class, MOF::
Layer (M3) Attribute
[MOF]


MOF Overview

s Foundation for OMG repository (meta
data) architecture
– Defines metamodels starting with the UML
– Provides generic meta-object interfaces (common to
MOF and all MOF defined Meta-models...)
– Provides MOF-IDL mapping to automate generation of
concrete object interfaces for specific metamodels
– Provides MOF-XML mappings to automate generation
of XML DTDs and Documents (XMI specification)
– Can also be used with COM using COM/CORBA
Interoperability software
s MOF uses UML for (meta)modeling

MOF Architecture

< < C O R B A ID L M o d u le > >
Discover & M O F 1 .1 R e fle c t ive

Manipulate
metadata
< < OM G M e ta -m e t a m o d e l> >
M O F M o de l
Model using
UML/MOF
precisely
Find and Manage M O F F a c ilit y

Metadata
Repositories

MOF Model
(short for MOF meta-metamodel)
s Shares the UML core concepts
– Behavioral extensions (operations and constraints) added
for repository/metaobject manipulation
s Intentionally not ‘thin’ to support better
integration/alignment with UML
s Defined using UML notation diagram,
constraints (OCL) and textual description
– Self describing; MOF IDL, DTD generated from MOF
s Interfaces used to create and manipulate MOF
compliant metamodels and models

OMG MOF 1.1/1.3 Model
Contains ModelElement +c onstrainedE lement

0..1 1.. *
0..* Constrains
+container
{ordered} 0..*

Namespace Feature Constraint
+containedElement

+subtype
Generaliz es
0..* GeneralizableElement BehavioralFeature St ruc turalFeature
+supertype

{ordered} 0..*

Package Classifier Operation Reference MofAttribute

0.. * +referent

RefersTo
Dat aType Class Association +referencedEnd
1
AssociationEnd


MOF/UML Tools
Interoperability Options
Tool/App Tool/App

MetaObject Facility
MOF/Repository write read
Reflective

Model Transfer
DTD Generation Intermediate Stream/File (XML)
(XMI)
Object
Model Access Analysis &
Design(UML)
Unisys/IBM et al proposal Facility

UML 1.3 : All Diagrams
B e h a vio ra l_ E le m e n t s
Model business
(fro m U M L ) processes
A c t iv it y _ G ra p h s
( fro m B e h a v io ra l _E le m e n t s )

C o l l a b ora ti o ns S t a t e _ M a c h in e s
Us e_C as es
(fro m B e h a vio ra l_ E l e m e n t s ) (fro m B e h a vio ra l_ E l e m e n t s )
(fro m B e h a vio ra l_ E l e m e n t s )

M o d e l_ M a n a g e m e n t
(fro m U M L )
C o m m o n _ B e h a vi o r
(fro m B e h a vio ra l_ E l e m e n t s )

F o u n d a t io n
(fro m U M L )

E x t en s i on _
Model business
Core
(fro m F o u n d a t i o n )
M e c h a n is m s
data/structures
D a ta _ Ty p e s


Overview of XMI
XML Metadata Interchange
s Use W3C eXtensible Markup Language (XML)
for the transfer syntax and interchange format
– Specify XML Document Type Definitions (DTD) to
enable transfer and verification of
• MOF based metamodels (using MOF DTD)
• UML based models (using UML DTD), etc.
s Specify a precise MOF (UML subset) to XML
mapping
– Use of OCL to specify stream production rules
– Allows interchange of any MOF based metamodel
– Enables automatic generation of DTDs
s Unisys, IBM,Oracle, Platinum, DSTC and others

Open Metadata Interchange with XMI

S oftware
Des ign App1 App2
As s ets

Development
XMI R epos itory App6 App3
T ools
v
s
Databas e
R eports
S chema App5 App4

N*N-N = 30 bridges written
6 bridges written by 6 vendors.
by N = 6 vendors.
Versioning issues.


XMI Simplified
OMG Documents : ad/98-10-05, ad/98-10-06

XML UML
UML
Models
CWM
UML
Models*
MOF
UML
MetaModels
Syntax and Encoding

X XML Streams (Models)
(Many - based on each metamodel DTD)

MOF M Validate
Metadata Definitions
& Management I UML 1.1
DTD
CWM* MOF 1.1
DTD DTD

XML DTD (MetaModels)
UML (1 per metamodel used for validation)
Metamodel
Analysis & Design


How to use XMI
s Define the domain or technology specific model
– Middleware models are usually called metamodels by
OMG
– Use UML - only knowledge of Class modeling needed to
get started
s Export model to XMI processor which generates
– XML DTDs for the specific (meta) model
– XML documents that conform to the DTD
s Manage the Models, DTDs and documents in a
MOF/XMI compliant distributed repository


UML 1.3/MOF/XMI Generation
A p p ly UM L to M O F Tra ns fo rm a tio n Rule s
to p ro d uce p hys ica l m e ta m o d e l

< < M odel> > < < M odel> >
UM L 1 .3 L o g ica l UM L 1 .3 P hysica l
M e ta m o d e l M eta m o d e l

< < XM I D TD> > < < XM L D oc um ent> > < < M O F --> ID L> >
UM L 1 .3 X ML D TD UM L 1 .3 UM L 1 .3
X M L D o cum e nt M O F C O RB A ID L

M O F - -> X M L M a p p ing i M O F --> X M L d o cum nt M O F --> C O RB A ID L
n XM I 1 .0 S p e c M a p p ing in X M I 1 .0 M a p p ing in M O F 1 .3
S pec sp e c
IB M & U nisys DTD G e n
Unisys X M L G e n Unisys ID L G e n


UML 1.1 XML DTD Subset

<!ELEMENT Class (name, visibility, isRoot, isLeaf, isAbstract, isActive,
XMI.extension*,
constraint*, requirement*, provision*, stereotype*,
elementReference*, collaboration*, partition?,
template?, view*, presentation*,
namespace?, behavior*, binding?
implementation*, generalization*, specialization*,
parameter*, structuralFeature*, specification*,
associationEnd*, participant*, createAction*,
instance*, classifierRole*, realization*,
classifierInState*, taggedValue*, ownedElement*,
feature*)?>
<!ATTLIST Class XMI.element.att; XMI.link.att;>
<!ELEMENT name (#PCDATA | XMI.reference)*>
<!ELEMENT feature (Feature| StructuralFeature| Attribute| BehavioralFeature|
Operation| Method Reception)*>
...

XMI 1.0 - XML Document Sample

<Model xmi.id=quot;a1quot;> <name>Business</name><visibility
xmi.value=quot;publicquot;/>
<ownedElement>
<Class xmi. id=quot;a7quot;><name>Customer</name>
<feature>
<Attribute><name>id</name>
<multiplicity><XMI.field>1</ XMI.field>
< XMI.field>1</ XMI.field></multiplicity>
<type>< DataType href=”|a247quot;/></type>
</Attribute>
<Operation><name>update</name>
<scope xmi.value=quot;instancequot;/>
</Operation>
</feature>
</Class>
</ownedElement>
</Model> UNISYS Corporation
Copyright 1999, Slide 26

XMI 1.1 Overview
s Addresses verbosity issues of XMI 1.0
s Incorporates XML namespaces
s Readability significantly improved


XMI for Application Development
OMG November 98 Demo
Web VA DTD VA
Rose
Sphere TC Gen Java

XMI IBM
VisualAge XMI
Oracle
Repository Select
XMI
XMI
XMI
Oracle Unisys XMI Enterprise
Designer
XMI UREP XMI
XMI XMI Non-XMI
Rational Select
MOF Repositories
Rose Enterprise
DTDGen


OMG Common Warehouse
MetaModel
s Scope
– Data Warehouse lifecycle metadata management
s Initial submission : IBM, Unisys, NCR, Hyperion,
Oracle, Genesis, UBS, Dimension EDI...
– Metamodel - Single logical & physical!
– Generated XML DTDs
– Generated MOF - IDL mappings
– Generated XML document
s For final submissions
– Improve based on feedback, vendor specific
metamodels, well formedness rules, demos

CWM Overview
Common Warehouse Metamodel
Warehouse Warehouse Warehouse
Management Process Operation

Data
Transformation OLAP
Analysis
Data Object-
Record-
Oriented Relational MDDB XML
Resources Oriented
(UML)

Warehouse Warehouse
CWMFoundation
Management Deployment

Foundation UML 1.3
(Foundation, Behavioral_Elements, Model_Management)


CWM MetaModel Architecture
CW MFo unda ti on
(fr o m L o g ical View)

W a re house De ploym e nt
(fro m L o g ica l Vie w)

Re la tiona l M DDB XML
Re cordOrie nte d
(fr o m L o g ical View) (fro m L o g ica l Vie w) (f rom L ogi c al Vi ew)

Tra nsform a tion Ola p
(fr o m L o g ical View) (fro m L og ical View)

W a re house P roce ss W a re house Ope ra tion
(fro m Lo g ical View)


XMI for Datawarehousing
November 1999 OMG Demo


CWM Relational :
Tables & Columns
Column
+/owner +/feature precision : Integer +/structuralFeature +/type
ColumnSet SQLDataType
scale : Integer
0..1 0..* isNullable : NullableType 0..* 1
{ordered}

SQLDistinctType SQLSimpleType
characterMaximumLength : Integer
Table characterOctetLength : Integer
SQLQuery
isSystem : Boolean numericPrecision : Integer
numericPrecisionRadix : Integer
numericScale : Integer
dateTimePrecision : Integer

BaseTable View
isTemporary : Boolean isReadOnly : Boolean
temporaryScope : String checkOption : Boolean

CWM Relational -- Tables, columns, and data types


CWM : Record Oriented
1 structu ral Featu re

Classifier type *
Attribute ModelElement
Package
(from Core) (from C or e)
(from Model_Management) (from Core)

valueCondition FieldValueCondition
Field
value : Expression
*
1

Record File

Cl ass
+file
(from Cor e)
* FixedOffsetField
RecordToFile offset : Integer
offsetUnitBits : Integer
{ordered}
* +record

Record
<<0..1>> fieldDelimiter : String Group /ownedElement
/ElementOwnership
<<0..1>> recordDelimiter : String * *
isFixedWidth : Boolean 1 /ownedElement 1
isSelfDescribing : Boolean /namespace
<<0..1>> skipRecords : Integer /namespace
/ElementOwnership
<<0..1>> textDelimiter : String
<<0..1>> formatName : String
CWM Record-Oriented


MOF, UML and XML Integration :
Suggestions
s Use UML for analysis and design of metamodels (these are
models after all!)
s Define and manage metamodels/profiles using the MOF
– Use UML based modeling tools, or MOF interfaces (normative) or
XMI
– Enables life cycle meta data interoperability and design reuse
across metamodels
– Relationships and Subtyping across metamodels supported by the
MOF
s Use XML for exchanging metadata via OMG XMI
s Use MOF-IDL mappings for concrete IDL interfaces to
metamodels
s Inherit MOF Reflective interfaces for interoperable meta
objects across meta-models

Importance of (Meta)modeling
s Provides a regular and rigorous infrastructure at a
higher level of abstraction
s Furnishes an architectural basis for extensions and
evolution of software
s Facilitates alignment with other standards that use a
metamodel architecture
– Potentially eliminate or evolve redundant standards (eg: CDIF
now endorses XMI)
s Supports interoperability and integration across
domains at the semantic level
s Use UML to design metamodels and models, MOF
to implement and manage them and XMI to
interchange them over the Internet

Lessons Learned
s Tool Interoperability issues (vendor politics!)
s Distributed systems are inherently more complex
s Coarse VS Fine grained metadata access
– Don’t use fine grained interfaces over a network if you
need to manipluate lots of complex objects
s Use XML/XMI for exchanging metadata across
network using standard DTDs for validation
s Use fine grained interfaces (MOF, DOM, Java) on
desktop
s Replication and Versioning issues
s Limitations of current standards

OMG use of UML, MOF and XMI

Domains
(Soon) Electronic Telecom Manufacturing Utility
Commerce

Financial Transportation Simulation Life Sciences

CWM - Data Business
UML CORBA
Warehouse Objects

Platform
(Now)

OMG Use of UML/XMI/MOF
for EAI
s These technologies address modeling, interchange
and metadata management for various problem
domains
s EAI/IAI have to solve the problem of managing the
complexity of heterogenous application integration
s Work on UML profile for Messaging and EAI RFP is
in progress
– Integration with UML for modeling business processes,
document structures
– XMI for metadata
– XML (potentially XMI) for data : Send issues to XMI RTF

Extending XML Possibilities
Power of UML, MOF
and XMI frameworks
Using XML is the first
real opportunity to
allow applications to
Semantic XMI be connected
Level of Abstraction

Integration
without excessive
XML Integration support from
systems integrator
Component API Integration and domain experts.

Application Integration Tools The biggest benefit is
speed of delivery
Hand coded integration which is by far the
critical issue for
eBusiness
enablement.

OMG and OAG Opportunity
s OAG has a development process that is moving
towards UML
– Use of OMG UML for modeling and design process
– Use of XMI for DTD (soon Schema) generation
– Use of XMI for model/document interchange
– Use of MOF/XMI for metadata repository interoperability
s OMG is developing domain specifications and has
just started an EAI Working Group
– Use of OAG BODs by OMG?
– Use of OMG domain specs (after UML and XML’isation)
by OAG?
s OMG has established OASIS liasion

OMG Metadata Summary

UML MOF
Model & Design Manage &
Discover
XMI
Framework
DTDs
Documents
Schemas*

XML EAI?
CCM
CWM
* Target XMI 1.2 eXchange UML

Concluding Thoughts
s Ensuring a unified distributed meta object
architecture is key to solving the heterogeneous
integration problem
s Most customers have and will continue to have
components and information from multiple
sources that need integration
s CORBA/EJB, DCOM/ActiveX, MOF/XMI
(Metadata), UML (Modeling) need to work
together with the content (business models,
BODS…)
s Modeling and Metadata matters - Master it : Use it
in your domain

References & further reading
s Object Oriented Strategies, Dec 1995, 1998 - OO Repositories : Paul
Harmon
s Implementing a Corporate Repository, Adrienne Tannenbaum (Wiley)
s Unisys Repository Information Model Technical Overview
– http://www.unisys.com/Products/urep, follow links to documents

s Common Object Request Broker Architecture 2.0, March 1995
s OMG Common Facilities RFI #3 - Repositories
s Unisys Response to RFI#3, OMG TC document tc/95-11-05
s OMG Object Analysis & Design RFP ad/96-05-01
s OMG Common Facilities RFP 5 - Meta Object Facility cf/96-05-02
s Unisys et al OMG Meta Object Facility Response, ad/97-08-14,15
s Rational et al OMG OADF (UML) Response , ad/97-08-10
s Unisys et al XML Metadata Interchange (XMI) proposal, ad/98-10-05, 06
s www.marketplace.unisys.com/urep; www.ibm.com/ad;
www.microsoft.com

Unisys and UREP are registered trademarks of Unisys
Corporation.
OMG is a registered trademark, and ORB, OMG IDL and
CORBA and CORBA are trademarks of Object Management
Group, Inc.
OLE & COM are trademarks of Microsoft Corp.
All other trademarks owned by respective organizations

XML Metadata Interchange (XMI)

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie XML Metadata Interchange (XMI)

Ähnlich wie XML Metadata Interchange (XMI) (20)

Mehr von elliando dias

Mehr von elliando dias (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

XML Metadata Interchange (XMI)