More precisely, there exists an implicit ontology of
restaurants utilized by the ChefMoz project (ChefMoz, 2005), but it cannot be used
directly as a Semantic Web resource, due to the fact that data stored there is infested
with bugs that make its automatic utilization impossible without pre-processing that
also involves manual operations (see Gawinecki, Gordon, Paprzycki, et al., 2005
and Gordon, Kowalski, et al., 2005 for more details).
This being the case we have proceeded in two directions. First, as reported in Gawinecki,
Gordon, and Paprzycki, et al. (2005) and Gordon, Kowalski, et al. (2005) we
have reverse engineered the restaurant ontology underlying the ChefMoz project
and cleaned data related to Polish restaurants. Separately we have proceeded with
designing hotel ontology using a pragmatic approach. Our hotel ontology is to be used
to represent, manipulate, and manage hotel information actually appearing within
Web-based repositories (in context of travel; i.e., not hotels as landmarks, or sites
of historical events). Therefore we have studied content of the 10 largest Internet
travel agencies and found out that most of them describe hotels using very similar
vocabulary.
Pages:
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687