Reference Ontology for Business ModelsTowards Interoperability between Business Modeling Ontologies
Licentiate Thesis
Tharaka Ilayperuma
September 28, 2007 2Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Overview
• Motivation• Business Models and Business Modelling
Ontologies– BMO– e3-value– REA
• The Reference Ontology – How we model things?• Facilitating interoperability between BM ontologies
through the Reference ontology– the mappings• Contributions
September 28, 2007 3Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Motivation
• Basic requirement of an Ontology– Being a generic description shared by a
community of users• Interoperability between different
business models
September 28, 2007 4Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Business Models and Ontologies
“Business models describes how a company intends to create value in the market place …”
“Ontologies are viewed as increasingly important tools for structuring domain of interests. ”
September 28, 2007 5Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Business Modelling Ontologies ..
• Business Model Ontology
• e3-value Ontology• Resource Events Agents (REA)
Ontology
September 28, 2007 6Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
BMO Main Concepts
VALUE proposition
WHAT?
Customer group
Relationship
Distribution channel
WHO?
Core capability
Value configuration
Partnership
HOW?
Revenue
CostHOW MUCH?
September 28, 2007 7Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
An e3-value Business Model
September 28, 2007 8Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
REA Ontology – An Example
September 28, 2007 9Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Reference Ontology – Resources, Features, and Rights
RESOURCERESOURCE
FEATUREFEATURE
RIGHTRIGHT
An actor is entitled to An actor is entitled to handle a resource in a handle a resource in a
certain waycertain way
(use, income, transfer)
OwnOwn
BorrowBorrow
(use, income, transfer)
BookBook
Any property or Any property or association of association of the resource
WeightWeight
Number of Number of pages
the resourcepages
September 28, 2007 10Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Three Components of a Transfer
RESOURCERESOURCE
RIGHTRIGHT
WatchWatchTRANSFERTRANSFER
EVIDENCE EVIDENCE DOCUMENTDOCUMENT
TicketTicket
Transfer ofTransfer of
1 Right1 Right
2 Custody (access, enabling)2 Custody (access, enabling)
3 Evidence of right3 Evidence of right
GoodsGoods
ServicesServices
InformationInformation
MoneyMoney
RESOURCERESOURCE
MovieMovie
CustodyCustody
EvidenceEvidence
RightRight
September 28, 2007 11Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Transfer and Conversion
RESOURCERESOURCE
FEATUREFEATURE
RIGHTRIGHTTRANSFERTRANSFER
CONVERSIONCONVERSION
of
on
September 28, 2007 12Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Grouping Transfers and Conversions –The Process Concept
September 28, 2007 13Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Grouping Transfers and Conversions –The Process Concept …
September 28, 2007 14Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Creating Common Understanding
• Use of the Reference Ontology to map concepts in original ontologies. – Too many differences make it difficult to map one
concept to another.• e.g. Value Object in e3-value and Economic Resource in REA
September 28, 2007 15Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Example - BMO to Reference Ontology
ACTOR TYPEACTOR TYPE
DISTRIBUTION CHANNEL
RELATIONSHIPMECHANISM
CUSTOMER SEGMENT
CustomerInterface
Rights Users
Right owners
Rights Clearing department
Artists acquisition department
Standardized mailings
Passive web sign-up for unknown artists
Active artists acquisition for famous artists
EVENT TYPEEVENT TYPEPROCESSPROCESS
TRANSFORMATIONTRANSFORMATION
RightsSocietyRightsSocietyRights collectionRights collection
•• Collecting music rightsCollecting music rights
•• Making paymentsMaking payments
Rights redistributionRights redistribution
•• Clearing music rightsClearing music rights
•• Collecting paymentsCollecting payments
CONVERSION CONVERSION TYPESTYPES
BMO ExampleMapped concepts in the Reference Ontology
September 28, 2007 16Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Example –REA to Reference Ontology
ACTORACTOR
ACTOR TYPEACTOR TYPEEVENTEVENT
TRANSFERTRANSFERExternal Actor
Music Rights SaleMusic Rights Sale
•• SENASENA
REA model for music rights case from an Artist’s perspective
September 28, 2007 17Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Example – e3-value to Reference Ontology
ACTOR TYPEACTOR TYPE
EVENT TYPEEVENT TYPE(increment/decrement)(increment/decrement)
PROCESSPROCESS
EXCHANGEEXCHANGE
TRANSFER TYPETRANSFER TYPE RIGHTRIGHT RESOURCE TYPERESOURCE TYPE
<Exchange rdf:ID="E113"><hasEventTypes>
<TransferType rdf:about="#TT78"><hasTransferredRight rdf:resource="#RightToMakePublic"/><hasTransferredOrConversedResourceType rdf:resource="#Song"/><hasActorType rdf:resource="#Artists"/><isEventType rdf:datatype="http://www.w3.org/2001/XMLSchema#string">decrement</isEventType>
</TransferType></hasEventTypes><hasEventTypes>
<TransferType rdf:about="#TT105"><hasTransferredRight rdf:resource="#RightToMakePublic"/><hasTransferredOrConversedResourceType rdf:resource="#Song"/><hasActorType rdf:resource="#RightsSociety"/><isEventType rdf:datatype="http://www.w3.org/2001/XMLSchema#string">increment</isEventType>
</TransferType></hasEventTypes>
</Exchange>
September 28, 2007 18Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Realising Mappings
Two step mapping process
September 28, 2007 19Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Realising Mappings
declare function local:getTransactionInterfaceProcess() as element()* {
let $docName := doc("musicRights.rdf")let $vi := $docName//a:value_interface
for $j in (distinct-values(local:getTransactionTransferType()))let $q := fn:substring-before($j,"_")let $r := fn:substring-after($j,"_")return
element Transaction {attribute rdf:ID {fn:concat("TP",$j)},for $vi1 in $vi return
for $t in $q returnif (string($vi1/@a:e3_has_uid) = $t ) then
for $i in (local:getExchnagesofInterfaces($t)) returnelement hasExchanges {
element Exchange {attribute rdf:about{fn:concat("#E",$i)},local:getExchangeRelatedValuePort($i)}
}else()
}};
<xsl:template match="Exchange//TransferType"xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"xmlns:owl="http://www.w3.org/2002/07/owl#"xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<xsl:param name="e_resource_id" select="current()/@rdf:about"/><xsl:param name="e_transfer_id" select="substring-after($e_resource_id,'#')"/><xsl:copy>
<xsl:copy-of select="@*"/><xsl:copy-of select="$file2//TransferType[@rdf:ID = $e_transfer_id]/*"/><xsl:apply-templates/>
</xsl:copy></xsl:template>
…………….………………………….
An XQuery function used in Step 1
An XSLT template used in Step 2
September 28, 2007 20Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
The Reference Ontology
1EVENTstockf low 1..1
CONTRAC T
TRANSACTION TYPE
AGREEMENT
EVIDENC E DOCU MEN T
TRANSACTION 0..* 10..* 1
0..*
0..*
0..*
0..*
governs
RIGHT
TRANSFERcustody 0..1 0..*1
TRANSFER TYPE1
1..*
1
1..*
referToRight
1
0..*
1
0..*
isOfTransferType
CONVERSION
COMITTMENT
11..* 11..*
ACTOR
1..*1 1..*1
hasEventActor
EXCHANGE
0..*
1
0..*
1
fulfills
1
1..*
1
1..* consistOf
1
1..*
1
1..*
hasTransfer
RESOURCE
1..*
0..*
1..*
0..*hasResource
FEATURE
TRANSFORMATION TYPE
CONVERSION TYPE
0..*
1
0..*
1
0..* 10..* 1
refersToFeature
PROCESS
ACTOR TYPE
1..*
1..*
1..*
1..*speci fies
1
0..*
1
0..* M
M
M
VALUE PROPOSITION
RESOURCE TYPE
1
0..*
1
0..*
1
0..*
1
0..*
1..*
1..*
1..*
1..*
TRANSFORMATION0..*
1
0..*
1
1
1..*
1
1..*
hasConversion
EVENT TYPEincrement/decrement
0..*
1..*
0..*
1..*
1
...
1
...
hasActorType
1..*
1..*
1..*
1..*
1
0..*
1
0..*
I NTERFACE
1..*
1
1..*
1
1..*0..*
1..*0..*
COMPETITIVE VALUES
0..* 0..*0..* 0..*
hasCompetitiveValue
SECOND ORDER VALUES
COMPLEMENTARY VALUES
September 28, 2007 21Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Thesis Contributions
• Analysis of value transfers• Facilitating the common understanding
between similar concepts in different ontological approaches
• Realisation of mappings between e3-value and the Reference Ontology
September 28, 2007 22Reference Ontology for Business Models
Towards Interoperability between Business Modelling Ontologies© Tharaka Ilayperuma
Thank you!
• Questions/Comments
Top Related