IST-1-002104-STP SATINE: Semantic-based Interoperability Infrastructure for Integrating Web Service Platforms to Peer-to-Peer Networks (http://www.srdc.metu.edu.tr/webpage/projects/satine/)

1
IST-1-002104-STP SATINE Semantic-based
Interoperability Infrastructure for Integrating
Web Service Platforms to Peer-to-Peer
Networks(http//www.srdc.metu.edu.tr/webpage/proj
ects/satine/)

• Asuman Dogac
• METU-SRDC, Ankara, Turkey

2
Outline of the Presentation

• Objective of the project
• Work planned, research and technological
  innovation
• Expected outcome
• Dissemination events
• Consortium, contact information

3
Project Objective

• The objective of the project is to develop
• a semantic-based interoperability framework
• for exploiting Web service platforms
• in conjunction with Peer-to-Peer networks
• The application will be demonstrated in travel
  industry

4
Work planned, research and technological
innovation
5
Putting the Work into Perspective
6
Web services

• Repositories and software systems are
  programmatically accessed by business processes
• The definition of interfaces and their access at
  runtime is not uniform at all
• Every enterprise uses different technology for
  the programmatic access
• Web Services are proposed as a uniform and
  universal technology for this problem

7
Why Web Services?

• For B2B interactions, applications need to talk
  to each other on the Web Interoperability is
  needed
• A change in an application should not effect the
  apps it is talking to
• Web services provide these through WSDL and SOAP
• WSDL is the established public contract with the
  outside world

WSDL and SOAP Public contract with the outside
world
8
W3C Description of a Web Service

• A Web service is a software system designed to
  support interoperable machine-to-machine
  interaction over a network
• It has an interface described in a
  machine-processable format (specifically WSDL)
• Other systems interact with the Web service in a
  manner prescribed by its description using
  SOAP-messages, typically conveyed using HTTP with
  an XML serialization in conjunction with other
  Web-related standards

9
Current State-of-the-Artin Web Service Technology

• The WSD is a machine-processable specification of
  the Web services interface
• It defines
• the message formats,
• datatypes,
• transport protocols, and
• transport serialization formats
• one or more network locations ("endpoints") at
  which a Web service can be invoked, and
• may provide some information about the message
  exchange pattern that is expected
• This is all syntax, there is no semantics in WSD!

10
WSDL is Syntax not Semantics!
Service
Where to access it
Port (e.g. http//host/svc)
Port
How to access it
Binding (e.g. SOAP, JMS, direct call)
Binding
Operation An Exchange of Messages between a
service Requestor and a Service provider
Abstract definition of the service (set
of Operations)
Abstract interface
portType
operation(s)
inMesage
outMessage
11
Web Service Model
Service Registry (ebXML or UDDI) - Web service
descriptions
Discover service
Publish service
Service Consumer
Service Provider - Web service - Service
Description in WSDL
Invoke service through SOAP
12
What is Semantic Web?

• The Semantic Web is about making the Web
  machine-processable
• To be useful, semantic should be defined through
  standard ontology languages
• W3C is developing Web Ontology Language (OWL) for
  this purpose

13
Web services and Semantic Web

• The concept of "the Semantic Web" has excited
  researchers in areas ranging from distributed
  information systems to AI
• Very recently, the combination of the so-called
  "Semantic Web Services" have started to attract
  many researchers as the combination of the best
  of the two worlds Web Services and Semantic Web
• When it comes to details, however, the concept is
  still somewhat unclear!

14
Semantic Web and NetworkedBusinesses

• The current interoperability standards like
• EDI
• RosettaNet
• Are rigid They fix
• The message formats exchanged (e.g. a Purchase
  Order)
• Business Vocabulary (e.g., product names,
  numbers, etc.)
• The sequencing of messages (e.g. after sending a
  purchase order message, an Purchase Order
  Acknowledgement message must be received)
• The public business process (e.g. after a
  purchase order is accepted, the an invoice must
  be sent)
• The network protocol and the transport binding
  (Internet (http, ftp, etc.) or VAN)
• The security to be provided (like encryption,
  non-repudiation)

15
Can we make Networked BusinessStandards more
Flexible throughSemantics?

• This can be possible by introducing semantics to
  Web services
• By classifying Web services with well-known
  taxonomies, ontologies and controlled
  vocabularies
• By introducing semantics to the messages exchanged

16
What is an Ontology?
An explicit formal specification of the terms in
the domain and relations among them. - Noy
and McGuinness, Ontology Development 101

• The word ontology comes from the Greek ontos
  (being) and logos (word)
• An ontology describes objects and concepts as
  classes
• These classes are arranged in a hierarchy, and
  then class attributes and relationships are
  described with properties

17
Ontology Languages and OWL
DAMLDarpa Agent Markup Language
OIL Ontology Inference Layer (Commission
Project)
DAMLOIL
RDF (Resource Description Framework)
OWL Web Ontology Language (Being Standardized
by W3C)
18
OWL-S Defines an Upper Ontology for Web Services
in OWL
describedByHow it works
19
Open Travel Alliancehttp//www.opentravel.org/

• A self-funded, non-profit organization
• Comprised of major airlines, hoteliers, car
  rental companies, leisure suppliers, travel
  agencies, global distribution systems (GDS),
  technology providers and other interested parties
• Working to create and implement industry-wide,
  open e-business specifications
• To form a common e-business language that will
  encourage development of systems to create new
  collections of services to better meet the
  demands and expectations of travelers and the
  travel industry

20
Workgroups

• Air, representing major airlines and airline
  associations
• Car, representing a variety of car rental
  agencies
• Hotel, representing major hotel corporations and
  hotel associations
• Leisure supplier, representing tour operators,
  railways, ferry operators, cruise operators and
  any other area of travel, tourism and leisure
• Travel Insurance
• Non-supplier, representing Global Distribution
  Systems, software providers, and travel agencies

21
Sample OTA Messages forCar Rental

• Vehicle Availability Rates Messages (2001b)
• OTA_VehAvailRateRQ - Requests availability of
  vehicle(s) by specific criteria that may include
  preferences such as vehicle type, pickup location
  and date/time, return location and date/time. It
  may also include special instructions, coverages
  etc.
• OTA_VehAvailRateRS - Returns information about
  the available vehicle that meets the criteria
  supplied at the time of request. The message may
  or may not include rates. If the rates are
  available then the various types of rates will be
  supplied. For example Hourly, Daily, Weekly,
  Weekend and Monthly. The response message may
  include Warnings from business processing rules
  or errors if the request did not succeed. In case
  the rates are not available, the response will
  contain zero rates.

22
Hotel Availability, Rate and Inventory Messages

• OTA_HotelAvailNotifRQ /RS
• OTA_HotelBookingRuleNotifRQ /RS
• OTA_HotelRateAmountNotifRQ /RS
• OTA_HotelSummaryNotifRQ /RS
• OTA_HotelInvCountNotifRQ/RS
• OTA_HotelInvNotifRQ /RS
• OTA_HotelInvBlockNotifRQ/RS
• OTA_HotelRatePlanNotifRQ /RS
• OTA_HotelDescriptiveContentNotifRQ /RS

23
OTA Membership List (Partial)

• Accor
• Accovia
• Active Hotels
• Adapsys L.P.
• AgentWare
• Air Transport Association
• Airline Automation, Inc. (AAI)
• Airlines Reporting Corporation
• Alaska Airlines
• Amadeus
• American Airlines
• American Express
• American Hotel Motel Association
• American Automobile Association
• AMTRAK
• ANC Rental
• Anite Travel Systems
• Arroyo Group, LLC
• Atinera, LLC

ATPCO Avis Rent A Car System, Inc. Baymont Inns
Suites Best Western International, Inc. BTI
Canada Budget Group, Inc. Carlson Hospitality
Carlson Wagonlit Travel Cendant Corporation
Contal Information Technology PLC Continental
Airlines, Inc. Cruise411.com CSA Travel
Protection Datalex Communications USA, Inc.
Daylight Software, Inc. Delta Air Lines
DerbySoft, Inc. Dollar Rent A Car Systems, Inc.
The Eastman Group EC Promotion Organization for
Travel Industry Eland Technologies Enterprise
Rent-A-Car Eurostar (UK) Ltd. Expedia
Farelogix.com, Inc. Fidelio Cruise Software
GmbH Galileo International Get2Hawaii, Inc.
Global Matrix Goldenware Travel Technologies,
LLC Golfswitch Government of Canada-Treasury
Board Secretariat
24
Use of OTA in SATINE

• A Web service architecture can be developed based
  on OTA and we will realize this
• However it is restrictive to think that every
  company in the travel domain will develop OTA
  compliant services
• Why not develop the necessary semantic tools for
  flexibility in providing networked business
  interoperability We will attack this!

25
P2P Computing
26
Why P2P?

• Discovery of resources
• Eliminating the single-source bottleneck
• Eliminating the risk of a single point of failure

27
SATINE P2P

• Web service registries are centralized
• A service can be located once a service registry
  is located
• But how to locate the service registry in the
  first place?
• Also a service may not be registered to a service
  registry How to find such a service?
• Through P2P search!
• This will also make distributed Web service
  registries possible

28
An Example Scenario to Demonstrate the
Capabilities of SATINE
29
(No Transcript)
30
He sends a query to find a tourism agency
31
SATINE Contribution

• Technology involved Web services, Semantic Web
  and P2P in the travel domain
• Innovation Discovering services through their
  semantics and P2P search mechanisms in the travel
  domain

32
Reservation is done
Attributes for InsuranceBookRequest InsuranceCust
omer PlanCost
33
SATINE Contribution

• Interoperability between the insurance company
  and the airline company is achieved through Web
  service technology
• Composition of Web services into workflows using
  the semantic definitions

34
The travel agency searches for a hotel In Rome
UDDI
UDDI
UDDI
UDDI
35
SATINE Contribution

• Distributed Web service registries
• Semantic routing of the queries
• Discovery of the Service Registries in the P2P
  environment based on the semantic information
  published in the P2P environment

36
AirAvailability Web Service

• Interface part
• AirAvailability (AvailOriginDestinationInfo
  arg1, AvailSpecificFlightInfo arg2,
  AvailTravelPreferences arg3, TravelerInfoSummary
  arg4)
• Implementation part
• AirAvailabilityImpl (AvailOriginDestinationInfo
  arg1, AvailSpecificFlightInfo arg2,
  AvailTravelPreferences arg3, TravelerInfoSummary
  arg4)

37
InsuranceBook Web Service

• Interface part
• InsuranceBook(InsuranceCustomer arg1, PlanCost
  arg2)
• Implementation part
• InsuranceBook(InsuranceCustomer arg1, PlanCost
  arg2)

38
Expected Outcome
39
SATINE Architecture Overview
40
SATINE Overview of Components
41
Expected Outcome

• From the Infrastructure Provider viewpoint A
  semantic Web Service based tool kit with using
  P2P discovery mechanisms to locate the Web
  service registries and Web services
• From Business User viewpoint Tools that
  facilitate the advertisement and discovery of
  their Web services especially for SMEs
• From End User point of view Easy discovery and
  execution of services

42
Dissemination and Exploitation

• For dissemination we are targeting the following
  journals and conferences (this is just the
  initial list)
• IEEE Pervasive Computing
• IEEE Internet Computing
• Semantics in Peer-to-Peer and Grid Computing
• IEEE International Conference on Web Services
  (ICWS 2004), Convergence of Web Services, Grid
  Computing, e-Business and Autonomic Computing
• Fourth International Conference on Web
  Engineering (ICWE'04)
• VLDB Workshop on Databases, Information Systems
  and P2P Computing
• Intl. Workshop on E-Services and the Semantic Web
  (ESSW) (associated with International World Wide
  Web Conference)
• eChallenges 2004, Dublin
• IST 2005

43
Dissemination and Exploitation

• Throughout the project duration the exploitation
  activities will cover the
• assessment of the market,
• assessment of the related technological
  developments and
• the business potential by the partners

44
The Consortium
45
SATINE Partners

• Partners
• 1. SRDC, Middle East Technical
  University,
• Turkey (Coordinator, Prime
  Contractor)
• 2. Fraunhofer Institute, FOKUS, Germany
• 3. European Dynamics, Greece
• 4. Oxymel, France
• 5. Intro Solutions, Turkey
• 6. Royal Melbourne Institute of
  Technology
• (RMIT), Australia

46
Contact Point

• Coordinator
• Prof. Dr. Asuman Dogac
• Software RD Center
• Dept. of Computer Eng.
• Middle East Technical University
• 06531, Ankara, Turkey
• Email asuman_at_srdc.metu.edu.tr
• Phone [phone]
• Fax[phone]

47
Thank you for your attention!
48
Extra Slides
49
XML Messaging SOAP

• The current standard for XML Messaging is Simple
  Object Access protocol (SOAP)
• Applications typically communicate with Web
  services via SOAP messaging
• Typically HTTP is used as RPC transport
• XML is used as RPC encoding scheme

50
SOAP

• SOAP consists of three parts
• an envelope that defines what is in a message,
• a set of encoding rules for expressing instances
  of application-defined data types, and
• a convention for representing remote procedure
  calls (RPC) and responses
• SOAP can be used in combination with by a variety
  of network protocols such as HTTP, SMTP, FTP, MQ
  or RMI over IIOP

51
SOAP over HTTP
HTTP POST Message
SOAP Endpoint Reference
XML Message
SOAP Payload
SOAP Envelope
SOAP Header
SOAP Body
52
SOAP Endpoint Reference
IP Host Address
TCP Port No
Object Endpoint ID
144.122.230.16
80
/ProductCataloggetPrice
POST /ProductCatalog HTTP/1.0 Host
http//www.srdc.metu.edu.tr Content-Type
text/xml charset"utf-8" Content-Length
500 SOAPAction http//www.srdc.metu.edu.tr/P
roductCataloggetPrice"
53
SOAP Body

• ltSOAP-ENVHeader /gt
• ltSOAP-ENVBodygt
• ltsgetPrice xmlnss"http//www.srdc.metu.edu.tr
  /ProductCatalog"gt
• ltproduct_name xsitype"xsdstring"gtPalm
  Pilotlt/product_namegt
• lt/sgetPricegt
• lt/SOAP-ENVBodygt
• lt/SOAP-ENVEnvelopegt

Method Name
Input Parameter
54
SOAP Response

• HTTP/1.0 200 OK
• Content-Type text/xml charset"utf-8"
• Content-Length 400
• ltSOAP-ENVEnvelope
• xmlnsSOAP-ENV" http//schemas.xmlsoap.org/
  soap/envelope/"
• SOAP-ENVencodingStyle" http//schemas.xmls
  oap.org/soap/encoding"
• xmlnsxsi"http//www.w3.org/1999/XMLSchema-
  instance"
• xmlnsxsd"http//www.w3.org/1999/XMLSchema"
  gt
• ltSOAP-ENVHeader /gt
• ltSOAP-ENVBodygt
• ltsgetPriceResponse xmlnss"http//www.srdc.me
  tu.edu.tr/ProductCatalog"gt
• ltproduct_price xsitype"xsdfloat"gt2000.lt/prod
  uct_pricegt
• lt/sgetPriceResponsegt
• lt/SOAP-ENVBodygt
• lt/SOAP-ENVEnvelopegt

Standard Suffix