Forth RMSIG Workshop

1
Forth RMSIG Workshop

• Building Blocks of the Reference Model

Wolfram Höpken
2
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

3
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

4
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

5
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)

6
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

7
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

8
Modeling Language (2)
UML
Common metalevel
Domain model
concrete level
9
Modeling Language (2)
UML
Common meta level
Tourism modeling language
Domain specific meta level
Domain model
concrete level
10
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,...)

11
Building Blocks (2)
12
Modeling Levels
13
XML Perspective
14
XML Example
UML diagram
XML DTD lt!ELEMENT HOTEL (NAME, CATEGORY,
ROOM)gt lt!ELEMENT NAME (PCDATA)gt lt!ELEMENT
CATEGORY (PCDATA)gt lt!ELEMENT ROOM (TYPE,
PRICE)gt lt!ELEMENT TYPE (PCDATA)gt lt!ELEMENT PRICE
(PCDATA)gt

• XML document
• ltHOTELgt
• ltNAMEgtHoliday Innlt/NAMEgt
• ltCATEGORYgt5lt/CATEGORYgt
• ltROOMgt
• ltTYPEgtsinglelt/TYPEgt
• ltPRICEgt1250 ATSlt/PRICEgt
• lt/ROOMgt
• lt/HOTELgt

15
Distributed Object Perspective
UML model (concept)
UML model (BOI)
16
Architecture
Metalevel
Service states
Common entities
Tourism services
Types
Processes
Syno-nyms
Building blocks
Process layer
Information processes
Booking processes
Entity layer
Common entities
Elementary tourism services
Composition services
Base layer
Basic types
Data main-tenance
Session manage-ment
Lookup service
Base classes
Basic elements
17
Metalevel
Metalevel
Service states
Common entities
Tourism services
Types
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
  for entities of the reference model

18
Building Blocks
Base layer
Basic types
Data main-tenance
Session manage-ment
Lookup service
Base classes
Basic elements

• 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)

19
Building Blocks (2)
Entity layer
Common entities
Elementary tourism services
Composition services

• 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

20
Building Blocks (3)
Process layer
Information processes
Booking processes

• 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

21
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

22
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

23
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

24
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)

25
Example
26
Example (2)
27
Service States

• Potential Service
• contains all variants and optional components
• instruction for building a concrete service
• Offered Service
• variants are selected
• attributes are evaluated

28
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

29
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

30
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

31
Destination
32
Destination (2)
33
XML DTD

• lt!ELEMENT DESTINATION (ACTIVITIES,
• CHARACTERISTICS)gt
• lt!ELEMENT ACTIVITIES (TYPE)gt
• lt!ELEMENT TYPE (PCDATA)gt
• lt!ELEMENT CHARACTERISTICS (NAME, LANDSCAPE,
  CLIMATE, PRICE, LANGUAGES)gt
• lt!ELEMENT NAME (PCDATA)gt
• lt!ELEMENT LANDSCAPE (PCDATA)gt
• lt!ELEMENT CLIMATE (PCDATA)gt
• lt!ELEMENT PRICE (PCDATA)gt
• lt!ELEMENT LANGUAGES (PCDATA)gt

34
XML Document

• ltDESTINATIONgt
• ltACTIVITIESgt
• ltTYPEgttennislt/TYPEgt
• lt/ACTIVITIESgt
• ltCHARACTERISTICSgt
• ltNAMEgtTyrollt/NAMEgt
• ltLANDSCAPEgtmountainouslt/LANDSCAPEgt
• ltCLIMATEgtcontinentallt/CLIMATEgt
• ltPRICEgt40 ATSlt/PRICEgt
• ltLANGUAGESgtGermanlt/LANGUAGESgt
• lt/CHARACTERISTICSgt
• lt/DESTINATIONgt

35
Accommodation
36
Accommodation (2)
37
XML DTD

• lt!ELEMENT ACCOMMODATION (NUMBERPERSONS,
  PRICE INSTITUTIONS, LIVINGUNITCATEGORIES, LIV
  INGUNITS, PERIODSOFTIME)gt
• lt!ELEMENT NUMBERPERSONS (PCDATA)gt
• lt!ELEMENT PRICE (PCDATA)gt
• lt!ELEMENT INSTITUTIONS (NAME, ADDRESS, LOCATION,
  ACTIVITIES, TARGETGROUPS)gt
• lt!ELEMENT NAME (PCDATA)gt
• lt!ELEMENT LOCATION (PCDATA)gt
• lt!ELEMENT ACTIVITIES (PCDATA)gt
• lt!ELEMENT TARGETGROUPS (PCDATA)gt

38
XML DTD (2)

• lt!ELEMENT ADDRESS (STREET, CITY, ZIPCODE,
  COUNTRY)gt
• lt!ELEMENT STREET (PCDATA)gt
• lt!ELEMENT CITY (PCDATA)gt
• lt!ELEMENT ZIPCODE (PCDATA)gt
• lt!ELEMENT COUNTRY (PCDATA)gt
• lt!ELEMENT LIVINGUNITS (UNITNUMBER)gt
• lt!ELEMENT UNITNUMBER (PCDATA)gt
• lt!ELEMENT PERIODSOFTIME (BEGIN, END)gt
• lt!ELEMENT BEGIN (DATE, TIME)gt
• lt!ELEMENT END (DATE, TIME)gt
• lt!ELEMENT DATE (PCDATA)gt
• lt!ELEMENT TIME (PCDATA)gt

39
XML Document

• ltACCOMMODATIONgt
• ltNUMBERPERSONSgt1lt/NUMBERPERSONSgt
• ltPRICEgt1250 ATSlt/PRICEgt
• ltINSTITUTIONSgt ... lt/INSTITUTIONSgt
• ltLIVINGUNITCATEGORIESgt ... lt/LIVINGUNITCATEGORIE
  Sgt
• ltLIVINGUNITSgt ... lt/LIVINGUNITSgt
• ltPERIODSOFTIMEgt ... lt/PERIODSOFTIMEgt
• lt/ACCOMMODATIONgt

40
XML Document (2)

• ltINSTITUTIONSgt
• ltNAMEgt Holiday Innlt/NAMEgt
• ltADDRESSgt
• ltSTREETgtLuisenplatz 14lt/STREETgt
• ltCITYgtInnsbrucklt/CITYgt
• ltZIPCODEgt65342lt/ZIPCODEgt
• ltCOUNTRYgtAustrialt/COUNTRYgt
• lt/ADDRESSgt
• ltLOCATIONgtcentrallt/LOCATIONgt
• ltACTIVITIESgttennislt/ACTIVITIESgt
• ltTARGETGROUPSgtfamilylt/TARGETGROUPSgt
• lt/INSTITUTIONSgt

41
XML Document (3)

• ltLIVINGUNITSgt
• ltUNITNUMBERgt205 lt/UNITNUMBERgt
• lt/LIVINGUNITSgt
• ltPERIODSOFTIMEgt
• ltBEGINgt
• ltDATEgt 26012001lt/DATEgt
• ltTIMEgt1500lt/TIMEgt
• lt/BEGINgt
• ltENDgt
• ltDATEgt 27012001lt/DATEgt
• ltTIMEgt1200lt/TIMEgt
• lt/ENDgt
• lt/PERIODSOFTIMEgt

42
Hotel
43
Hotel (2)
44
XML DTD

• lt!ELEMENT HOTEL (NUMBERPERSONS, PRICE,
  INSTITUTIONS, LIVINGUNITCATEGORIES, LIVINGUNITS,
  PERIODSOFTIME, MEALPLANS, EXTRABEDS)gt
• lt!ELEMENT INSTITUTIONS (NAME, ADDRESS, LOCATION,
  ACTIVITIES, TARGETGROUPS, TYPE, CATEGORY)gt
• lt!ELEMENT TYPE (PCDATA)gt
• lt!ELEMENT CATEGORY (PCDATA)gt
• lt!ELEMENT LIVINGUNITCATEGORIES (TYPE,
  EQUIPMENT)gt
• lt!ELEMENT TYPE (PCDATA)gt
• lt!ELEMENT EQUIPMENT (PCDATA)gt

45
XML DTD (2)

• lt!ELEMENT MEALPLANS (TYPE, PRICE)gt
• lt!ELEMENT TYPE (PCDATA)gt
• lt!ELEMENT PRICE (PCDATA)gt
• lt!ELEMENT EXTRABEDS (BEDTYPE, PRICE)gt
• lt!ELEMENT BEDTYPE (PCDATA)gt
• lt!ELEMENT PRICE (PCDATA)gt

46
XML Document

• ltHOTELgt
• ltNUMBERPERSONSgt3lt/NUMBERPERSONSgt
• ltPRICEgt2100 ATSlt/PRICEgt
• ltINSTITUTIONSgt ... lt/INSTITUTIONSgt
• ltLIVINGUNITCATEGORIESgt ... lt/LIVINGUNITCATEGORIE
  Sgt
• ltLIVINGUNITSgt ... lt/LIVINGUNITSgt
• ltPERIODSOFTIMEgt ... lt/PERIODSOFTIMEgt
• ltMEALPLANSgt ... lt/MEALPLANSgt
• ltEXTRABEDSgt ... lt/EXTRABEDSgt
• lt/HOTELgt

47
XML Document (2)

• ltINSTITUTIONSgt
• ltNAMEgt Holiday Innlt/NAMEgt
• ltADDRESSgt
• ltSTREETgtLuisenplatz 14lt/STREETgt
• ltCITYgtInnsbrucklt/CITYgt
• ltZIPCODEgt65342lt/ZIPCODEgt
• ltCOUNTRYgtAustrialt/COUNTRYgt
• lt/ADDRESSgt
• ltLOCATIONgtcentrallt/LOCATIONgt
• ltACTIVITIESgttennislt/ACTIVITIESgt
• ltTARGETGROUPSgtfamilylt/TARGETGROUPSgt
• ltTYPEgthotellt/TYPEgt
• ltCATEGORYgt5lt/CATEGORYgt
• lt/INSTITUTIONSgt

48
XML Document (3)

• lt LIVINGUNITCATEGORIES gt
• ltTYPEgtdoublelt/TYPEgt
• ltEQUIPMENTgtbathlt/EQUIPMENTgt
• ltEQUIPMENTgttvlt/EQUIPMENTgt
• lt/LIVINGUNITCATEGORIESgt
• ltMEALPLANSgt
• ltTYPEgtbreakfastlt/TYPEgt
• ltPRICEgt200 ATSlt/PRICEgt
• lt/MEALPLANSgt
• ltEXTRABEDgt
• ltBEDTYPEgtsinglelt/BEDTYPEgt
• ltPRICEgt400 ATSlt/PRICEgt
• lt/EXTRABEDgt

49
Transportation
50
Transportation (2)
51
XML DTD

• lt!ELEMENT TRANSPORTATION (PRICE,
  MEANSOFTRANSPORT, SECTIONS,
  TRANSPORTATIONUNITCATEGORIES, TRANSPORTAT
  IONUNITS)gt
• lt!ELEMENT PRICE (PCDATA)gt
• lt!ELEMENT MEANSOFTRANSPORT (TARGETGROUPS,
  LUGGAGE)gt
• lt!ELEMENT TARGETGROUPS (PCDATA)gt
• lt!ELEMENT LUGGAGE (PCDATA)gt
• lt!ELEMENT SECTIONS (ROUTE, PERIODSOFTIME)gt
• lt!ELEMENT ROUTE (BEGIN, END)gt
• lt!ELEMENT BEGIN (NAME, ADDRESS)gt
• lt!ELEMENT NAME (PCDATA)gt
• lt!ELEMENT END (NAME, ADDRESS)gt

52
XML Document

• ltTRANSPORTATIONgt
• ltPRICEgt180 DMlt/PRICEgt
• ltMEANSOFTRANSPORTgt
• ltLUGGAGEgtskilt/LUGGAGEgt
• lt/MEANSOFTRANSPORTgt
• ltINSTITUTIONSgt ... lt/INSTITUTIONSgt
• ltSECTIONSgt
• ltROUTEgt
• ltBEGINgt
• ltNAMEgtFrankfurt Main Stationlt/NAMEgt
• ltADDRESSgt ... lt/ADDRESSgt
• lt/BEGINgt
• ltENDgt
• ltNAMEgtInnsbruck Main Stationlt/NAMEgt
• ltADDRESSgt ... lt/ADDRESSgt
• lt/ENDgt
• lt/ROUTEgt

53
XML Document (2)

• ltPERIODOFTIMEgt
• ltBEGINgt
• ltDATEgt25012001lt/DATEgt
• ltTIMEgt0645lt/TIMEgt
• lt/BEGINgt
• ltENDgt
• ltDATEgt25012001lt/DATEgt
• ltTIMEgt1300lt/TIMEgt
• lt/ENDgt
• lt/PERIODOFTIMEgt
• lt/SECTIONSgt
• lt/TRANSPORTATIONgt

54
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

55
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

56
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)

57
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

58
Evaluation Instructions
59
Constraints

• Successor relationship
• end time begin time of its successor
• end point begin point of its successor
• Companion relationship
• begin time lt begin time of its companion
• end time gt end time of its companion
• begin point begin point of its companion
• end point end point of its companion

60
Constraints
61
Example Package Tour
62
Example Round Trip
63
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

64
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

65
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

66
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

67
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

68
Request Metadata Process
69
Request Metadata Interface

70
Request Metadata Interface (2)

• XML DTD
• lt!ELEMENT REQUESTMETADATA
• (STATE, SESSION, TYPE, TYPEDEFINITION?)gt
• lt!ELEMENT STATE (PCDATA)gt
• lt!ELEMENT SESSION (PCDATA)gt
• lt!ELEMENT TYPE (PCDATA)gt
• lt!ELEMENT TYPEDEFINITION (PCDATA)gt

71
Request Metadata Interface (3)

• XML documents
• ltREQUESTMETADATAgt
• ltSTATEgtrequestlt/STATEgt
• ltSESSIONgt0001lt/SESSIONgt
• ltTYPEgtHotellt/TYPEgt
• lt/REQUESTMETADATAgt
• ltREQUESTMETADATAgt
• ltSTATEgtresponselt/STATEgt
• ltSESSIONgt0001lt/SESSIONgt
• ltTYPEgtHotellt/TYPEgt
• ltTYPEDEFINITIONgtHotel.xmilt/TYPEDEFINITIONgt
• lt/REQUESTMETADATAgt

72
Search Process
73
Search Interface
74
Search Interface (2)
75
Search Interface (3)

• XML DTD
• lt!ELEMENT SEARCH (STATE, SESSION, SEARCHREQUEST,
  RESULTLIST?)gt
• lt!ELEMENT SEARCHREQUEST (CUSTOMERS,
  REQUESTEDSERVICES)gt
• lt!ELEMENT CUSTOMERS (CUSTOMERDATA,
  PAYMENTMETHODS)gt
• lt!ELEMENT CUSTOMERDATA (NAME, AGE, TYPE,
  ADDRESS)gt
• lt!ELEMENT RESULTLIST (NUMBERRESULTS,
  RESULTS)gt
• lt!ELEMENT NUMBERRESULTS (PCDATA)gt
• lt!ELEMENT RESULTS (...)gt

76
Search Interface (4)

• XML documents
• ltSEARCHgt
• ltSTATEgtrequestlt/STATEgt
• ltSESSIONgt0001lt/SESSIONgt
• ltSEARCHREQUESTgt
• ltCUSTOMERSgt
• ltCUSTOMERDATAgt
• ltNAMEgtWolfram Höpkenlt/NAMEgt
• ltAGEgt34lt/AGEgt
• ltTYPEgtadultlt/TYPEgt
• ltADDRESSgt...lt/ADDRESSgt
• lt/CUSTOMERDATAgt
• lt/CUSTOMERSgt

77
Search Interface (5)

• ltREQUESTEDSERVICESgt
• ltHOTELgt
• ltCATEGORYgt5lt/CATEGORYgt
• ltLOCATIONgtcentrallt/LOCATIONgt
• ltADDRESSgt
• ltCITYgtInnsbrucklt/CITYgt
• lt/ADDRESSgt
• ltROOMgt
• ltTYPEgtsinglelt/TYPEgt
• lt/ROOMgt
• lt/HOTELgt
• lt/REQUESTEDSERVICESgt
• lt/SEARCHREQUESTgt
• lt/SEARCHgt

78
Search Interface (6)

• ltSEARCHgt
• ltSTATEgtresponselt/STATEgt
• ltSESSIONgt0001lt/SESSIONgt
• ltSEARCHREQUESTgt...lt/SEARCHREQUESTgt
• ltRESULTSgt
• ltHOTELgt
• ltIDENTIFIERgt 00045245lt/IDENTIFIERgt
• ltNAMEgtHoliday Innlt/NAMEgt
• ltCATEGORYgt5lt/CATEGORYgt
• ...
• ltPRICEgt1250 ATSlt/PRICEgt
• lt/HOTELgt
• lt/RESULTSgt
• lt/SEARCHgt

79
Book Service Process
80
Book Service Interface
81
Book Service Interface (2)
82
Book Service Interface (3)

• XML DTD
• lt!ELEMENT BOOKSERVICE (TOURISMSERVICEID?,
  CUSTOMERS?, BOOKING?)gt
• lt!ELEMENT TOURISMSERVICEID (PCDATA)gt
• lt!ELEMENT CUSTOMERS (...)gt
• lt!ELEMENT BOOKING (CUSTOMERS,
  TOURISMSERVICE)gt

83
Book Service Interface (4)

• XML documents
• ltBOOKSERVICEgt
• ltSTATEgtrequestlt/STATEgt
• ltSESSIONgt0001lt/SESSIONgt
• ltTOURISMSERVICEIDgt00045245lt/TOURISMSERVICEIDgtltCU
  STOMERSgt
• ltCUSTOMERDATAgt...lt/CUSTOMERDATAgt
• ltPAYMENTMETHODSgt
• ltTYPEgtcreditCardlt/TYPEgt
• ltOWNERgtWolfram Höpkenlt/OWNERgt
• ltCARDNUMBERgt4724 2615 5238 3745lt/CARDNUMBERgt
• ltEXPIRATIONDATEgt07/01lt/EXPIRATIONDATEgt
• lt/PAYMENTMETHODSgt
• lt/CUSTOMERSgt
• lt/BOOKSERVICEgt

84
Book Service Interface (5)

• XML documents
• ltBOOKSERVICEgt
• ltSTATEgtresponselt/STATEgt
• ltSESSIONgt0001lt/SESSIONgt
• ltBOOKINGgt
• ltCUSTOMERSgt...lt/CUSTOMERSgt
• ltTOURISMSERVICEgt
• ltHOTELgt
• ltTOURISMSERVICEIDgt00045245lt/TOURISMSERVICEIDgt
  ltNAMEgtHoliday Innlt/NAMEgt
• ltCATEGORYgt5lt/CATEGORYgt
• ...
• lt/HOTELgt
• lt/TOURISMSERVICEgt
• lt/BOOKINGgt
• lt/BOOKSERVICEgt

85
Cancel Booking Process
86
Cancel Booking Interface
87
Cancel Booking Interface (2)

• XML DTD
• lt!ELEMENT CANCELBOOKING (BOOKINGID?,
  CANCELLEDBOOKING?, CANCELINGCHARGE?)gt
• lt!ELEMENT BOOKINGID (PCDATA)gt
• lt!ELEMENT CANCELLEDBOOKING (CUSTOMERS,
  TOURISMSERVICE)gt
• lt!ELEMENT CANCELINGCHARGE (PCDATA)gt

88
Cancel Booking Interface (3)

• XML documents
• ltCANCELBOOKINGgt
• ltSTATEgtrequestlt/STATEgt
• ltSESSIONgt0001lt/SESSIONgt
• ltBOOKINGIDgt00046283lt/BOOKINGIDgt
• lt/CANCELBOOKINGgt
• ltCANCELBOOKINGgt
• ltSTATEgtresponselt/STATEgt
• ltSESSIONgt0001lt/SESSIONgt
• ltCANCELLEDBOOKINGgt
• ltCUSTOMERSgt...lt/CUSTOMERSgt
• ltTOURISMSERVICEgt...lt/TOURISMSERVICEgt
• lt/CANCELLEDBOOKINGgt
• ltCANCELINGCHARGEgt600 ATSlt/CANCELINGCHARGEgt
• lt/CANCELBOOKINGgt

89
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

90
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

91
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

92
Building Concrete Models (2)
Reference model
93
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)

94
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

95
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

Time
Route
MealPlan
Class
96
Interoperability (3)

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

97
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

98
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

99
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

100
Agenda

• The reference model
• Elementary tourism services
• Composition services
• Market processes
• Employment of the reference model
• Tourtags.org
• Tourism ontology building and management

101
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