In this post I want to have a high level view of travel ontology. Lets look at the issue from the point of view that everything is a service. Hence we can consider three services: ticket reservation, accommodation and car renting as the main sub services of any travel service (combining these three has a long history in web services).
The above classification is based on that the user has chosen the destination and duration however most of the time choosing the most appropriate travel destination and duration for a user based on his own preferences is a big issue itself (This issue is not well studied in literature).
We should add activities as a new category to the traditional categories in order to differentiate travels (in particular destination, date and duration of a travel). Activities involve anything which can make a travel more interesting. Obviously all information about activities (place, date, cost etc) would be represented in the subclasses and slots of the activity concept.
Until now we reviewed the most important parts for any travel service in terms of knowledge representation but service execution is directly related to the constraints which is applied by the user. These parameters should be defined in the travel ontology and later on is used by the user agent (user agent is an agent at user side to perform autonomous or semi autonomous web service execution). User agent compares the information retrieved from the travel ontology, to the information stored in user preferences ontology. User agent can drill in/out within the travel ontology based on the user preferences. A very nice example of filtering data based on user preferences is implemented in Oracle technology Network (OTN) at OTN Semantic Web recently also there is a short nice document as white paper.
The above classification is based on that the user has chosen the destination and duration however most of the time choosing the most appropriate travel destination and duration for a user based on his own preferences is a big issue itself (This issue is not well studied in literature).
We should add activities as a new category to the traditional categories in order to differentiate travels (in particular destination, date and duration of a travel). Activities involve anything which can make a travel more interesting. Obviously all information about activities (place, date, cost etc) would be represented in the subclasses and slots of the activity concept.
Until now we reviewed the most important parts for any travel service in terms of knowledge representation but service execution is directly related to the constraints which is applied by the user. These parameters should be defined in the travel ontology and later on is used by the user agent (user agent is an agent at user side to perform autonomous or semi autonomous web service execution). User agent compares the information retrieved from the travel ontology, to the information stored in user preferences ontology. User agent can drill in/out within the travel ontology based on the user preferences. A very nice example of filtering data based on user preferences is implemented in Oracle technology Network (OTN) at OTN Semantic Web recently also there is a short nice document as white paper.
No comments:
Post a Comment