Semantic Enterprise Integration

SEMANTIC ENTERPRISE INTEGRATION
Radu’s Research Proposal

Saturday, 3 December 11

OPPORTUNITY
One entrepreneur identiﬁes a great business opportunity


PARTNER IDENTIFICATION
Who can help me deliver the work?


PARTNER SELECTION
Who do I select to implement the different parts?


AGREEMENT
Can we agree to be partners and make a bid for the tender?


COLLABORATION
How do we share information between the partners?


Opportunity Partner Identiﬁcation Partner Selection Agreement Collaboration

PARTNERSHIP FORMATION
How do we go from identifying the business opportunity to delivering the work


West Midlands Collaborative Common Marketplace

Opportunity Partner Identiﬁcation Partner Selection Agreement Collaboration

How do we go from identifying the business opportunity to delivering the work


Collaboration

How do we help the parters to share more information between them?


Assembler

SUPPLY CHAIN EXAMPLE
We can assemble the baby carriages, but where do we get the parts?


Textiles Company

Assembler

Iron Works Company

Where do our suppliers get their materials?


Material Supplier Textiles Company

Assembler

Material Supplier Iron Works Company

And ﬁnally where do the raw materials come from?


Raw Material Supplier


Raw Material Supplier Assembler



How can we share information across the whole supply chain?




Raw Material Supplier Iron Works Company

Raw Material Supplier Material Supplier

HUB INTEGRATION

Raw Material Supplier Material Supplier Textiles Company Assembler

Raw Material Supplier Raw Material Supplier Material Supplier Iron Works Company

SERIAL BUS INTEGRATION

Going on the enterprise service bus
architecture, trying to standardise the way
in which companies communicate via
“blueprints”


Going with the assumption that in a
regional context we can conﬁgure a cloud
with the applications that most
companies need to use


ANY SILVER BULLET
ALTERNATIVE ?
• Cheap, non-proprietary;

• Fast to implement;

• Distributed - no single point of failure;

• Re-use of already systems and data;







DISTRIBUTED INTEGRATION

HOW DO PEOPLE COMMUNICATE
They don’t need rules to govern their communication


HOW TO MACHINES COMMUNICATE
Machines rely heavily on pre-approved rules to govern their communication


1

7
2

Raw Material Supplier 12

3
9 10 11

4

Raw Material Supplier 13 Assembler

5 8


6

DISTRIBUTED INTEGRATION

ROY FIELDING
REST - Representational State Transfer


THE WEB IS THE PLATFORM
Scalable, Fault-Tolerant, Recoverable, Secure, Loosely Coupled


http://wmccm.co.uk/suppliers

{

count:
11000,

filters:
none,

list:
{

{

id:
1,

name:
"A
&
E
Asbestos
Ltd",

competencies:
{

"Asbestos"

}

},

{

id:
2,

name:
"Bedson
Ltd",

competencies:
{

"Material
Handling
&
Packaging",
"Supply
Chain
Management"

}

},
...

}
}


http://wmccm.co.uk/suppliers/2

{

id:
2

name:
"Bedson
Ltd",

postcode:
"CV2
5DB",

phone:
"024
7661
4542",

fax:
"024
7661
4523",

website:
"http://www.bedsons.com",

products-‐services:
{

"inspection
head
lamps",
"surge
protectors",
"low
voltage
transformers"

}

...
}


MACHINES NEED A CONTRACT TO
COMMUNICATE EFFECTIVELY
Is there a way to overcome this limitation?


HATEOAS
THE CONFUSING BIT OF REST
Hypermedia As Engine of The Application State


STARBUCKS EXAMPLE
How would a machine order a coffee?


Request Response
POST /order HTTP 1.1 201 Created
Host: starbucks.com Location: http:/restbucks.com/order/1234
Content-Length: ... Content-Type: application/
vnd.starbucks+xml
<order xmlns="urn:starbucks"> Content-Length: ...
<drink>latte</drink>
</order> <order xmlns="urn:restbucks">
<link rel="payment"
href="https://starbucks.com/
payment/order/1234"
type="application/xml"/>
</order>

REGULAR DAY AT STARBUCKS

Request Response
PUT /payment/order/1234 HTTP 1.1 201 Created
Host: starbucks.com https://starbucks.com/payment/order/1234
Content-Type: application/xml Content-Type: application/xml
Content-Length: ... Content-Length: ...

<payment xmlns="urn:starbucks"> <payment xmlns="urn:starbucks">
<cardNo>123456789</cardNo> <cardNo>123456789</cardNo>
<expires>07/07</expires> <expires>07/07</expires>
<name>John Citizen</name> <name>John Citizen</name>
<amount>4.00</amount> <amount>4.00</amount>
</payment> </payment>


Request Response
GET /order/1234 HTTP 1.1 200 OK
Host: starbucks.com Content-Type: application/
vnd.starbucks+xml
Content-Length: ...

<order xmlns="urn:starbucks">
</order>


Request Response
POST /order HTTP 1.1 201 Created
Host: starbucks.com Location: http:/restbucks.com/
Content-Length: ... order/1234
Content-Type: application/
<order xmlns="urn:starbucks"> vnd.starbucks+xml
<drink>latte</drink> Content-Length: ...
</order>
<order xmlns="urn:restbucks">
</order>

GENEROUS BARISTA AT STARBUCKS

Request Response
GET /order/1234 HTTP 1.1 200 OK
Host: starbucks.com Content-Type: application/
vnd.starbucks+xml
Content-Length: ...

<order xmlns="urn:starbucks">
</order>

GENEROUS BARISTA AT STARBUCKS

SO MACHINES CAN TALK WITHOUT
RULES
But how do we make them talk the same language?


SIR TIM BERNERS-LEE
Father of the World Wide Web and the
Semantic Web


Customer Customer

HomePhone Town ZipPlus FullName Country Address FirstName LastName Email

City ZipCode

ONTOLOGY RECONCILIATION

is-a

Customer Customer
has-a

HomePhone Town ZipPlus FullName Country Address FirstName LastName Email

City ZipCode

same-as

ONTOLOGY RECONCILIATION

GOOD RELATIONS
Used by Google, Yahoo, BestBuy and 10.000 more


DATA SHARING AND SECURITY
This can’t be done in a decentralised way, can it?


WHAT ABOUT KEYS?
Humans already have quite a good method of dealing with distributed security







TOKEN PASSING ALONG THE CHAIN

ANY SILVER BULLET
ALTERNATIVE ?
Cheap, non-proprietary REST Architecture using the WWW

Fast to implement No need to agree on rules, just ontology

Distributed - no single point of failure No single point of failure, 1-to-1 integration

Re-use of already systems and data Ontology reconciliation


THANK YOU!
Time for some criticism...


Semantic Enterprise Integration

Recommended

Recommended

More Related Content

Recently uploaded

Recently uploaded (20)

Featured

Featured (20)

Semantic Enterprise Integration