Semantic Enterprise Integration

SEMANTIC ENTERPRISE INTEGRATIONRadu’s Research Proposal

Saturday, 3 December 11

OPPORTUNITYOne entrepreneur identifies a great business opportunity


PARTNER IDENTIFICATIONWho can help me deliver the work?


PARTNER SELECTIONWho do I select to implement the different parts?


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


COLLABORATIONHow do we share information between the partners?


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

Opportunity Partner Identification Partner Selection Agreement Collaboration







West Midlands Collaborative Common Marketplace


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

Collaboration


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

Assembler


SUPPLY CHAIN EXAMPLEWhere do our suppliers get their materials?

Assembler

Textiles Company

Iron Works Company


SUPPLY CHAIN EXAMPLEAnd finally where do the raw materials come from?

Material Supplier

Material Supplier

Assembler

Textiles Company

Iron Works Company


SUPPLY CHAIN EXAMPLEHow can we share information across the whole supply chain?

Material Supplier

Material Supplier

Assembler

Textiles Company

Iron Works Company

Raw Material Supplier




HUB INTEGRATION

Material Supplier

Material Supplier

Assembler

Textiles Company

Iron Works Company





SERIAL BUS INTEGRATION

Material Supplier

Material Supplier

AssemblerTextiles Company

Iron Works Company


Raw Material Supplier Raw Material Supplier


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 configure 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

Material Supplier

Material Supplier

Assembler

Textiles Company

Iron Works Company





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


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


DISTRIBUTED INTEGRATION

Material Supplier

Material Supplier

Assembler

Textiles Company

Iron Works Company




2

1

3

4

5

6

7

8

9 10 11

12

13


ROY FIELDINGREST - Representational State Transfer


THE WEB IS THE PLATFORMScalable, 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://example.com/resources/


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" } ...}




http://www.bedsons.com

http://www.bedsons.com

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 EXAMPLEHow would a machine order a coffee?


201 CreatedLocation: http:/restbucks.com/order/1234Content-Type: application/ vnd.starbucks+xmlContent-Length: ...

<order xmlns="urn:restbucks"><drink>latte</drink><link rel="payment" href="https://starbucks.com/ payment/order/1234" type="application/xml"/></order>

POST /order HTTP 1.1Host: starbucks.comContent-Length: ...

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

REGULAR DAY AT STARBUCKS

Request Response


http://restbucks.com


https://starbucks.com

https://starbucks.com

PUT /payment/order/1234 HTTP 1.1Host: starbucks.comContent-Type: application/xmlContent-Length: ...

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

201 Createdhttps://starbucks.com/payment/order/1234Content-Type: application/xmlContent-Length: ...

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


Request Response


https://starbucks.com/payment/order/1234

https://starbucks.com/payment/order/1234

GET /order/1234 HTTP 1.1 Host: starbucks.com

200 OKContent-Type: application/ vnd.starbucks+xmlContent-Length: ...



Request Response


201 CreatedLocation: http:/restbucks.com/ order/1234Content-Type: application/ vnd.starbucks+xmlContent-Length: ...

<order xmlns="urn:restbucks"><drink>latte</drink></order>

POST /order HTTP 1.1Host: starbucks.comContent-Length: ...


GENEROUS BARISTA AT STARBUCKS

Request Response




GET /order/1234 HTTP 1.1 Host: starbucks.com

200 OKContent-Type: application/ vnd.starbucks+xmlContent-Length: ...


GENEROUS BARISTA AT STARBUCKS

Request Response


SO MACHINES CAN TALK WITHOUT RULES

But how do we make them talk the same language?


SIR TIM BERNERS-LEEFather of the World Wide Web and the

Semantic Web


ONTOLOGY RECONCILIATION

Customer

HomePhone Town ZipPlus FullName

Customer

Address FirstName LastName Email

City ZipCode

Country


ONTOLOGY RECONCILIATION

Customer

HomePhone Town ZipPlus FullName

Customer

Address FirstName LastName Email

City ZipCode

Country

is-a

has-a

same-as


GOOD RELATIONSUsed 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

Material Supplier

Material Supplier

Assembler

Textiles Company

Iron Works Company





ANY SILVER BULLET ALTERNATIVE ?

Cheap, non-proprietary

Fast to implement

Distributed - no single point of failure

Re-use of already systems and data

REST Architecture using the WWW

No need to agree on rules, just ontology

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

Ontology reconciliation


THANK YOU!Time for some criticism...


Technology

Semantic Enterprise Integration