27.01.2001 slide 1 wolfram höpken rmsig reference model special interest group forth rmsig workshop...

27.01.2001 Slide 1Wolfram Höpken RMSIGRMSIGReference Model Special Interest Group

Forth RMSIG Workshop

Building Blocks of the Reference Model

Wolfram Höpken


Workshop Objective

• first and second workshop– discuss and agree upon methodology and process

• third workshop– identify basic modeling concepts and mechanisms

– specify tourism specific modeling language

• forth workshop– specify reference model building blocks

– prepare first version of reference model


Agenda

• The reference model

• Elementary tourism services

• Composition services

• Market processes

• Employment of the reference model

• Tourtags.org

• Tourism ontology building and management


Agenda






• Tourtags.org



The reference model

• framework for modeling electronic tourism markets– uniform language with standardized building

blocks as vocabulary for describing electronic tourism markets

– conceptual, abstract modeling of tourism markets

– modeling based on the Unified Modeling Language (UML)


UML – Unified Modeling Language

• graphical language for describing and visualizing models of systems

• UML 1.3 adopted as standard by the OMG• enables the modeling of

– static structure of a system• entities, their internal structure• relationships between entities

– behavior of a system• interactions between entities (scenarios)• state sequences, activity sequences


Modeling Language

• tourism specific modeling language based on the UML– extends the UML by domain specific concepts

and mechanisms• composition mechanism• market interface descriptions

– provides building blocks as specific modeling elements

– enables the flexible description of specific models


Modeling Language (2)

UMLUML

Domain modelDomain model

Common metalevel

concrete level


Modeling Language (2)

UMLUML

Domain modelDomain model

Common meta level

concrete level

Tourism modeling languageTourism modeling language Domain specific meta level


Building Blocks

• building blocks as specific modeling elements

• building blocks are provided on different levels of granularity– elementary building blocks (date, location,...)– tourism services (flight, hotel,...)– process building blocks (searching, booking,...)


Building Blocks (2)

Process layer

Entity layer

Base layer

Name

Category

Room

Hotel Time

Route

Class

Flight Name

Address

Age

Customer

Criteria

Customer

ResultList

Searching Service

Customer

Date

Booking

StartLocation

EndLocation

RouteDate

Time

FacilitiesLocation

Address

Name


Modeling Levels

UML model

XML model Distributed object model


XML Perspective

XMI documents

XML DTDs

UML DTDs

Meta level

XML documentsData level

UML model


XML Example

XML document

<HOTEL><NAME>Holiday Inn</NAME><CATEGORY>5</CATEGORY><ROOM>

<TYPE>single</TYPE><PRICE>1250 ATS</PRICE>

</ROOM></HOTEL>

Name

Category

Room

Hotel

XML DTD

<!ELEMENT HOTEL (NAME, CATEGORY, ROOM+)>

<!ELEMENT NAME (#PCDATA)>

<!ELEMENT CATEGORY (#PCDATA)>

<!ELEMENT ROOM (TYPE, PRICE)>

<!ELEMENT TYPE (#PCDATA)>

<!ELEMENT PRICE (#PCDATA)>

UML diagram


Distributed Object Perspective

UML model (concept) UML model (BOI)

XMI documents

XML DTDs

XML documents

Meta level

Data level BOs

IDL descriptions

XMI documents


Architecture

Building blocks

Metalevel

Process layer

Entity layer

Base layer

Information processes Booking processes

Commonentities

Elementarytourism services

Composition services

Service states

Common

entities

Tourism service

sTypes

Processes

Basic types

Data main-

tenance

Session manage-ment

Lookup service

Base class

es

Syno-nyms

Basic elemen

ts


MetalevelMetalevel

Service states

Common

entities

Tourism service

sTypes

Processes

Syno-nyms

• types: metaclasses for modeling tourism-specific basic types

• common entities: metaclasses, which are used in different packages of the metamodel

• tourism services: metaclasses, providing concepts for constructing tourism services

• service states: metaclasses, for dealing with different states of tourism services

• processes: metaclasses for describing market processes and interfaces

• synonyms: metaclasses for defining synonyms forentities of the reference model


Building Blocks

• Basic types: tourism specific types at the fringe of the reference model (e.g. room type, bed type, category)

• Base classes: fundamental, abstract base classes (e.g. object, entity)

• Basic elements: basic building blocks for the construction of tourism

entities (e.g. climate, opening hours, address, etc.)

• Data maintenance: maintain tourism service data

• Session management: manage user sessions

• Lookup service: request meta data (available services and their structure)

Base layerBasic types

Data main-

tenance

Session manage-ment

Lookup

service

Base class

es

Basic elements


Building Blocks (2)

• Common entities: entities used in different packages of the

entity or process layer (e.g. tourism service, customer profile)

• Elementary tourism services: elementary services like hotel, flight, etc.

• Composition services: services composed of elementary services

Entity layerCommonentities

Elementarytourism services

Composition services


Building Blocks (3)

• Information processes: retrieval of information about tourism services (e.g. searching for tourism services, checking the availability)

• Booking processes: booking tourism services, altering a booking, canceling a booking

Process layerInformation processes Booking processes


Current State

• integrated are:– requirements and use cases– information and booking processes– most important tourism services

(accommodation, transportation, event, institution, hired vehicle, destination)

– general composition service

• still missing:– XML and BOI model– selection hierarchies


Agenda






• Tourtags.org



Composition Mechanism

• flexible construction of tourism services– elementary tourism services out of service components

(e.g. hotel out of room and meal plan)– composition services out of elementary services

(e.g. package tour out of flight and hotel)

• composition consists of– components (collection of building blocks to enable

combination possibilities)– attributes (depending of component attributes)– evaluation instruction for evaluating attribute values– constraints (restrict combination possibilities)


Example


Example (2)


Service StatesPotential Service:

• contains all variants and optional components

• instruction for building a concrete service

Offered Service:

• variants are selected

• attributes are evaluated


Elementary Tourism Services

• classification of tourism services (page 79)

– accommodation (hotel, vacation apartment, campsite)

– transportation (flight, train, bus, ship)

– institution (exhibition, museum, sight, sport leisure)

– event (conference, lecture, course, cultural, sport, film)

– hired vehicle (car, bus, motorbike, bike, camper, boat)

– destination (country, region, city)

– gastronomy

– shopping

– cruise


Surveys

• general RMSIG survey– requirements for tourism markets– market processes and core data– necessary types of tourism services

• specific surveys for tourism services– tourism services accommodation,

transportation, hired car, institution– concrete tourism services and their

characteristics/attributes


Data Dictionary

• reference list of terms or entities of the tourism domain (described by name, meaning and structure)

• structured into– tourism services

– basic components

– basic types

• specifies the basic structure and semantic of corresponding elements of the reference model


Destination


Destination (2)


XML DTD

<!ELEMENT DESTINATION (ACTIVITIES*,

CHARACTERISTICS+)>

<!ELEMENT ACTIVITIES (TYPE)>


<!ELEMENT CHARACTERISTICS (NAME, LANDSCAPE, CLIMATE, PRICE, LANGUAGES*)>


<!ELEMENT LANDSCAPE (#PCDATA)>

<!ELEMENT CLIMATE (#PCDATA)>


<!ELEMENT LANGUAGES (#PCDATA)>


XML Document

<DESTINATION>

<ACTIVITIES>

<TYPE>tennis</TYPE>

</ACTIVITIES>

<CHARACTERISTICS>

<NAME>Tyrol</NAME>

<LANDSCAPE>mountainous</LANDSCAPE>

<CLIMATE>continental</CLIMATE>

<PRICE>40 ATS</PRICE>

<LANGUAGES>German</LANGUAGES>

</CHARACTERISTICS>

</DESTINATION>


Accommodation


Accommodation (2)


XML DTD

<!ELEMENT ACCOMMODATION (NUMBERPERSONS, PRICEINSTITUTIONS, LIVINGUNITCATEGORIES,

LIVINGUNITS, PERIODSOFTIME)>

<!ELEMENT NUMBERPERSONS (#PCDATA)>


<!ELEMENT INSTITUTIONS (NAME, ADDRESS, LOCATION, ACTIVITIES, TARGETGROUPS)>


<!ELEMENT LOCATION (#PCDATA)>

<!ELEMENT ACTIVITIES (#PCDATA)>

<!ELEMENT TARGETGROUPS (#PCDATA)>


XML DTD (2)

<!ELEMENT ADDRESS (STREET, CITY, ZIPCODE, COUNTRY)><!ELEMENT STREET (#PCDATA)><!ELEMENT CITY (#PCDATA)><!ELEMENT ZIPCODE (#PCDATA)><!ELEMENT COUNTRY (#PCDATA)>

<!ELEMENT LIVINGUNITS (UNITNUMBER)><!ELEMENT UNITNUMBER (#PCDATA)>

<!ELEMENT PERIODSOFTIME (BEGIN, END)><!ELEMENT BEGIN (DATE, TIME)><!ELEMENT END (DATE, TIME)><!ELEMENT DATE (#PCDATA)><!ELEMENT TIME (#PCDATA)>


XML Document

<ACCOMMODATION>

<NUMBERPERSONS>1</NUMBERPERSONS>


<INSTITUTIONS> ... </INSTITUTIONS>

<LIVINGUNITCATEGORIES> ... </LIVINGUNITCATEGORIES>

<LIVINGUNITS> ... </LIVINGUNITS>

<PERIODSOFTIME> ... </PERIODSOFTIME>

</ACCOMMODATION>


XML Document (2)

<INSTITUTIONS>

<NAME> Holiday Inn</NAME>

<ADDRESS>

<STREET>Luisenplatz 14</STREET>

<CITY>Innsbruck</CITY>

<ZIPCODE>65342</ZIPCODE>

<COUNTRY>Austria</COUNTRY>

</ADDRESS>

<LOCATION>central</LOCATION>

<ACTIVITIES>tennis</ACTIVITIES>

<TARGETGROUPS>family</TARGETGROUPS>

</INSTITUTIONS>


XML Document (3)

<LIVINGUNITS><UNITNUMBER>205 </UNITNUMBER>

</LIVINGUNITS>

<PERIODSOFTIME><BEGIN>

<DATE> 26012001</DATE><TIME>1500</TIME>

</BEGIN><END>

<DATE> 27012001</DATE><TIME>1200</TIME>

</END></PERIODSOFTIME>


Hotel


Hotel (2)


XML DTD

<!ELEMENT HOTEL (NUMBERPERSONS, PRICE, INSTITUTIONS, LIVINGUNITCATEGORIES, LIVINGUNITS, PERIODSOFTIME, MEALPLANS, EXTRABEDS*)>

<!ELEMENT INSTITUTIONS (NAME, ADDRESS, LOCATION, ACTIVITIES, TARGETGROUPS, TYPE, CATEGORY)>


<!ELEMENT CATEGORY (#PCDATA)>

<!ELEMENT LIVINGUNITCATEGORIES (TYPE, EQUIPMENT*)>


<!ELEMENT EQUIPMENT (#PCDATA)>


XML DTD (2)

<!ELEMENT MEALPLANS (TYPE, PRICE)>



<!ELEMENT EXTRABEDS (BEDTYPE, PRICE)>

<!ELEMENT BEDTYPE (#PCDATA)>



XML Document

<HOTEL>

<NUMBERPERSONS>3</NUMBERPERSONS>


<INSTITUTIONS> ... </INSTITUTIONS>

<LIVINGUNITCATEGORIES> ... </LIVINGUNITCATEGORIES>

<LIVINGUNITS> ... </LIVINGUNITS>

<PERIODSOFTIME> ... </PERIODSOFTIME>

<MEALPLANS> ... </MEALPLANS>

<EXTRABEDS> ... </EXTRABEDS>

</HOTEL>


XML Document (2)

<INSTITUTIONS><NAME> Holiday Inn</NAME><ADDRESS>

<STREET>Luisenplatz 14</STREET><CITY>Innsbruck</CITY><ZIPCODE>65342</ZIPCODE><COUNTRY>Austria</COUNTRY>

</ADDRESS><LOCATION>central</LOCATION><ACTIVITIES>tennis</ACTIVITIES><TARGETGROUPS>family</TARGETGROUPS><TYPE>hotel</TYPE><CATEGORY>5</CATEGORY>

</INSTITUTIONS>


XML Document (3)

< LIVINGUNITCATEGORIES >

<TYPE>double</TYPE>

<EQUIPMENT>bath</EQUIPMENT>

<EQUIPMENT>tv</EQUIPMENT>

</LIVINGUNITCATEGORIES>

<MEALPLANS>

<TYPE>breakfast</TYPE>


</MEALPLANS>

<EXTRABED>

<BEDTYPE>single</BEDTYPE>


</EXTRABED>


Transportation


Transportation (2)


XML DTD<!ELEMENT TRANSPORTATION (PRICE, MEANSOFTRANSPORT,

SECTIONS,

TRANSPORTATIONUNITCATEGORIES,TRANSPORTATIONUNITS)>

<!ELEMENT PRICE (#PCDATA)><!ELEMENT MEANSOFTRANSPORT (TARGETGROUPS*,

LUGGAGE*)><!ELEMENT TARGETGROUPS (#PCDATA)><!ELEMENT LUGGAGE (#PCDATA)>

<!ELEMENT SECTIONS (ROUTE, PERIODSOFTIME)><!ELEMENT ROUTE (BEGIN, END)><!ELEMENT BEGIN (NAME, ADDRESS)><!ELEMENT NAME (#PCDATA)><!ELEMENT END (NAME, ADDRESS)>


XML Document<TRANSPORTATION>

<PRICE>180 DM</PRICE><MEANSOFTRANSPORT>

<LUGGAGE>ski</LUGGAGE></MEANSOFTRANSPORT><INSTITUTIONS> ... </INSTITUTIONS><SECTIONS>

<ROUTE><BEGIN>

<NAME>Frankfurt Main Station</NAME><ADDRESS> ... </ADDRESS>

</BEGIN><END>

<NAME>Innsbruck Main Station</NAME><ADDRESS> ... </ADDRESS>

</END></ROUTE>


XML Document (2)

<PERIODOFTIME>

<BEGIN>

<DATE>25012001</DATE>

<TIME>0645</TIME>

</BEGIN>

<END>

<DATE>25012001</DATE>

<TIME>1300</TIME>

</END>

</PERIODOFTIME>

</SECTIONS>

</TRANSPORTATION>


Agenda






• Tourtags.org



Composition Services

• supplier-initiated and customer-initiated compositions

• common interface for all tourism services– attributes describing the start and end state concerning

place and time

– enables general specification of evaluation instructions and constraints

• relationships between components– successor (e.g. hotel as successor of outward flight)

– companion (e.g. event as a companion of hotel)


Evaluation Instructions

• begin time = begin time of the first component• begin point = begin point of the first component• end time = end time of the last component• end point = end point of the last component• price = sum of all component prices

Example package tour:• begin time/point = begin time/point of the outward

flight• end time/point = end time/point of the return flight


Evaluation Instructions


Constraints

Successor relationship:

• end time = begin time of its successor

• end point = begin point of its successor

Companion relationship:

• begin time < begin time of its companion

• end time > end time of its companion

• begin point = begin point of its companion

• end point = end point of its companion


Constraints


Example Package Tour


Example Round Trip


Specific Compositions

• specific constraints for specific service combinations?– e.g. identical flight classes or hotel categories?

• specific composition services for specific service combinations?– with specific attributes, evaluation instructions,

constraints– e.g. specific composition services for round

trips or event trips


Agenda






• Tourtags.org



Market Interface Definitions

• market components provide a set of services or processes

• interfaces of market components are described by the available processes and their input and output

• lookup service provides market interface descriptions to other market participants


Processes

• lookup process (request metadata)• session management processes• data maintenance processes• information processes

– search for tourism services– check availability

• booking processes– book tourism service– alter booking– cancel booking


Request Metadata Process


Request Metadata Interface


Request Metadata Interface (2)

XML DTD

<!ELEMENT REQUESTMETADATA

(STATE, SESSION, TYPE, TYPEDEFINITION?)>

<!ELEMENT STATE (#PCDATA)>

<!ELEMENT SESSION (#PCDATA)>


<!ELEMENT TYPEDEFINITION (#PCDATA)>


Request Metadata Interface (3)

XML documents

<REQUESTMETADATA><STATE>request</STATE><SESSION>0001</SESSION><TYPE>Hotel</TYPE>

</REQUESTMETADATA>

<REQUESTMETADATA><STATE>response</STATE><SESSION>0001</SESSION><TYPE>Hotel</TYPE><TYPEDEFINITION>Hotel.xmi</TYPEDEFINITION>

</REQUESTMETADATA>


Search Process


Search Interface


Search Interface (2)



XML DTD

<!ELEMENT SEARCH (STATE, SESSION, SEARCHREQUEST, RESULTLIST?)>

<!ELEMENT SEARCHREQUEST (CUSTOMERS+, REQUESTEDSERVICES+)>

<!ELEMENT CUSTOMERS (CUSTOMERDATA, PAYMENTMETHODS*)>

<!ELEMENT CUSTOMERDATA (NAME, AGE, TYPE, ADDRESS)>

<!ELEMENT RESULTLIST (NUMBERRESULTS, RESULTS*)>

<!ELEMENT NUMBERRESULTS (#PCDATA)>

<!ELEMENT RESULTS (...)>


Search Interface (4)XML documents<SEARCH>

<STATE>request</STATE><SESSION>0001</SESSION><SEARCHREQUEST>

<CUSTOMERS><CUSTOMERDATA>

<NAME>Wolfram Höpken</NAME><AGE>34</AGE><TYPE>adult</TYPE><ADDRESS>...</ADDRESS>

</CUSTOMERDATA></CUSTOMERS>



<REQUESTEDSERVICES><HOTEL>

<CATEGORY>5</CATEGORY><LOCATION>central</LOCATION><ADDRESS>

<CITY>Innsbruck</CITY></ADDRESS><ROOM>

<TYPE>single</TYPE></ROOM>

</HOTEL></REQUESTEDSERVICES>

</SEARCHREQUEST></SEARCH>



<SEARCH><STATE>response</STATE><SESSION>0001</SESSION><SEARCHREQUEST>...</SEARCHREQUEST><RESULTS>

<HOTEL><IDENTIFIER> 00045245</IDENTIFIER><NAME>Holiday Inn</NAME><CATEGORY>5</CATEGORY>...<PRICE>1250 ATS</PRICE>

</HOTEL></RESULTS>

</SEARCH>


Book Service Process


Book Service Interface


Book Service Interface (2)



XML DTD

<!ELEMENT BOOKSERVICE (TOURISMSERVICEID?, CUSTOMERS?, BOOKING?)>

<!ELEMENT TOURISMSERVICEID (#PCDATA)>

<!ELEMENT CUSTOMERS (...)>

<!ELEMENT BOOKING (CUSTOMERS+, TOURISMSERVICE)>



XML documents<BOOKSERVICE>

<STATE>request</STATE><SESSION>0001</SESSION><TOURISMSERVICEID>00045245</TOURISMSERVICEID><CUSTOMERS>

<CUSTOMERDATA>...</CUSTOMERDATA><PAYMENTMETHODS>

<TYPE>creditCard</TYPE><OWNER>Wolfram Höpken</OWNER><CARDNUMBER>4724 2615 5238

3745</CARDNUMBER><EXPIRATIONDATE>07/01</EXPIRATIONDATE>

</PAYMENTMETHODS></CUSTOMERS>

</BOOKSERVICE>


Book Service Interface (5)XML documents<BOOKSERVICE>

<STATE>response</STATE><SESSION>0001</SESSION><BOOKING>

<CUSTOMERS>...</CUSTOMERS><TOURISMSERVICE>

<HOTEL><TOURISMSERVICEID>00045245</TOURISMSERVICEID><NAME>Holiday Inn</NAME><CATEGORY>5</CATEGORY>...

</HOTEL></TOURISMSERVICE>

</BOOKING></BOOKSERVICE>


Cancel Booking Process


Cancel Booking Interface


Cancel Booking Interface (2)

XML DTD

<!ELEMENT CANCELBOOKING (BOOKINGID?, CANCELLEDBOOKING?, CANCELINGCHARGE?)>

<!ELEMENT BOOKINGID (#PCDATA)>

<!ELEMENT CANCELLEDBOOKING (CUSTOMERS+, TOURISMSERVICE)>

<!ELEMENT CANCELINGCHARGE (#PCDATA)>


Cancel Booking Interface (3)XML documents<CANCELBOOKING>

<STATE>request</STATE><SESSION>0001</SESSION><BOOKINGID>00046283</BOOKINGID>

</CANCELBOOKING>

<CANCELBOOKING><STATE>response</STATE><SESSION>0001</SESSION><CANCELLEDBOOKING>

<CUSTOMERS>...</CUSTOMERS><TOURISMSERVICE>...</TOURISMSERVICE>

</CANCELLEDBOOKING><CANCELINGCHARGE>600 ATS</CANCELINGCHARGE>

</CANCELBOOKING>


Agenda






• Tourtags.org



Building Concrete Models

• concrete models with specific entities are described or modeled by the UML-based tourism modeling language

• the provided building blocks can be used as basic modeling elements– composition: describe a specific entity as a

composition of building blocks– derivation: describe a specific entity as a

refinement of a building block


Specific model

Reference model

Building Concrete Models (2)

Name

Category

Room

Hotel

CureServices

Name

Category

Room

CureHotel

derive

Category

Room

Time

MoonFlight

compose

MealPlan

Time

Route

Class

compose

XYFlight

Time

Class

Room

Name

Route

Category

CureServices

MealPlan


Building Concrete Models (3)

• take over the common building blocks without changes

• tailor the common building blocks to specific requirements by deriving specific building blocks

• construct specific building blocks by composing the common building blocks (on each level)

• construct completely new building blocks by using the tourism modeling language (i.e. basic concepts and mechanisms)


Interoperability

Derive specific building blocks:• derived building blocks can be

accessed just as the corresponding common building blocks

• only new characteristics have to be learned

• common parts can be automatically mapped between different models

Name

Category

Room

Hotel

CureServices

Name

Category

Room

CureHotel

derive


Interoperability (2)

Construct specific building blocks by composing common building blocks

• contained common building blocks cover common syntax and semantic

• modeling language provides the context the building blocks are used in

• partial mapping between components of building blocks

MealPlan

Time Route

Class

MealPlan

Time

Route

Class

XYFlight


Interoperability (3)

• synonyms enable an explicit mapping of specific elements to the corresponding elements of the reference model


Tourism Repository

• provides a library of common building blocks

• enables the maintenance and extension of the library of common building blocks

• ensures universal validity of building blocks

• avoids unnecessary diversity


Agenda






• Tourtags.org



Next Activities

• elaborate first version of the reference model

• execute review process within the RMSIG

• disseminate results

• ENTER 2001 – Open Standards Workshop– present RMSIG results– discuss relationship with other initiatives and

possible cooperation

27.01.2001 slide 1 wolfram höpken rmsig reference model special interest group forth rmsig workshop...

Documents