ANNOTATION OF KAYSERS.AT WEBSITE WITH SCHEMA.ORG

Size: px

Start display at page:

Download "ANNOTATION OF KAYSERS.AT WEBSITE WITH SCHEMA.ORG"

Brianne McDowell
6 years ago
Views:

1 STI INNSBRUCK ANNOTATION OF KAYSERS.AT WEBSITE WITH SCHEMA.ORG Zaenal Akbar, Ioan Toma STI Innsbruck, University of Innsbruck, Technikerstraße 21a, 6020 Innsbruck, Austria Semantic Technology Institute Innsbruck STI INNSBTRUCK Technikerstraße 21a A 6020 Innsbruck Austria 1

2 Contents 1. Introduction Content Mapping Implementation Website Backend Modified Database Annotated Pages Result Article Offer Hotel Discussion References

3 1. Introduction This document presents our implementation of annotating the website of the Kaysers 4-Star Hotel [1] with Schema.org [2]. The implementation was performed by injecting the related Class and Properties into the content of the website. The outputs of this implementation are: 1. The final mapping between the identified content types from the website to Schema.org classes including their relevant properties. 2. The selected method on how to inject the annotation into the content. 2. Content Mapping Contents in the website are divided into a few categories and sub-categories: 1. The Kaysers: Philosophy, Impressions, Newsletter, Gutschein, Hotel Assessment, Press, Partner, Weather, Jobs, Current Events 2. Rooms And Prices: Rooms And Prices, Gourmet- & Vital Board, Enquire & Book, Zusatzleistungen, Winter Offers, Summer Offers 3. Wellness: Kaysers Spa, Wellness Packages, Beauty Treatments, Massages, Time For Two 4. Nature & Indulgence: Natural Hideaway, Culinary Specialities, Kaysers In Winter, Kaysers In Summer 5. Movement: Tennis, Golf, Hike & Bike, Yoga & Co, Skiing In Tyrol, Cross-Country Skiing, Winter Walking, Culture, Cultural City Of Innsbruck 6. Contact: Contact, How To Get To Us, Imprint The mapping is representing a relation between the identified content types (including properties) of the website to the classes and properties of Schema.org. Original mapping described in [3] was used as the reference, but a change will be applied if necessary. Table 1 Mapping the Content Types to Schema.org No. Content Type Class 1 The Kaysers Article 2 Rooms and Prices 2.1 Rooms and Prices Offer Schema.org Property articlebody Specification validfrom validthrough 2

4 2.2 Gourmet & Vital Board Article 2.3 Additional Services Offer 2.4 Winter Offers Offer 2.5 Summer Offers Offer 3 Wellness 3.1 Kaysers Spa Article 3.2 Wellness Packages Offer 3.3 Beauty Treatments Offer QuantitativeValue QuantitativeValue articlebody Specification eligiblequantity value Specification validfrom validthrough Specification validfrom validthrough articlebody Specification eligiblequantity value 3

5 3.4 Massages Offer 3.5 Time for Two Offer 4 Nature & Indulgence Article 5 Movement 5.1 Tennis Offer QuantitativeValue QuantitativeValue QuantitativeValue QuantitativeValue Article 5.2 Golf,, Culture Article Specification eligiblequantity value Specification eligiblequantity value Specification eligiblequantity value articlebody Specification eligiblequantity value articlebody articlebody 4

6 6 Contact 6.1 Contact Hotel 6.2 Imprint Hotel PostalAddress AggregateRating PostalAddress telephone address streetaddress addresslocality addressregion postalcode addresscountry aggregaterating ratingvalue ratingcount telephone faxnumber address streetaddress addresslocality addressregion postalcode addresscountry Compared to the original mapping explained in [3], a few changes have been made to fit the content type to the most suitable class. For example, when a page has no information then the page will be annotated as Article (instead of Offer ). Used classes of Schema.org: 1. Hotel Quantitative Value 4. Article 5. PostalAddress 6. AggregateRating 5

7 3. Implementation In this section, we describe how the annotation was implemented, encountered problems and used solutions. 3.1 Website Backend The website uses Typo3 CMS [4] as its backend, with MySQL [5] as its database. Since there is no plugin available yet for schema.org annotation, we decided to inject the annotation directly into the content. Typo3 is integrated with Rich Text Editors (RTE) for text user input. Originally, our plan was to injecting the annotation through this editor, but RTE has strict restriction in which html tags are accepted and it will clean up the unrecognized tags. Since for annotation, special tags (meta-tags) are required, a modification is necessary to the RTE configuration, which is risky. Therefore, we decided to inject the annotation directly through the database, in this case through MySQL tables. 3.2 Modified Database There are five tables were modified in order to annotated the website. Those database tables are: 1. tt_contents. This table holds general pages. 2. tx_mpnews_news. This table holds specific pages which are categorized into predefined categories, for example winter and summer offers. 3. tx_mpwellness_items. This table holds various items of wellness category, for example packages, beauty treatments. 4. tx_mpzimmerpreise_seasons. This table holds various date intervals (from to) for several available seasons. 5. tx_mpzimmerpreise_rooms. This table holds various room items including their ses for a specific season. 3.3 Annotated Pages In total, we were able annotating 268 pages/sub-pages in three different languages (German/Default, English, and France). 4. Result In this chapter, we show the results of several annotated pages when extracted using Structured Data Testing from Google [7]. 6

8 4.1 Article Article is used to annotated a generic page contains generic information. For example a page about Philosophy of the hotel as shown at Figure 1. Figure 1 Extracted Article 7

9 4.2 Offer A page could contain one Offer with several s. For example in offer for Rooms, the Offer contains variety s according to the availability duration as shown at Figure 2. Figure 2 Extracted Offer 8

10 A page also could contain more than one Offer. For example for Beauty Treatment as shown at Figure 3. Figure 3 Extracted several Offers 9

11 A page also could contain Offer and Article at the same time. For example for the Tennis as shown at Figure 4. Figure 4 Extracted Offer and Article 10

12 4.3 Hotel Information about the Hotel can be obtained from the page Contact as shown at Figure 5. Figure 5 Extracted Hotel 11

13 Hotel also can be obtained from the page Imprint as shown at Figure 6. Figure 6 Extracted Hotel 12

14 5. Discussion As mentioned above, the annotations were injected directly through the database tables. This approach raises a few potential problems in the future: - A content modification through RTE will be discarding all inserted annotation, i.e. meta-tags will be discarded automatically by RTE. o To avoid this situation, a future content modification should be through the database interface. - Second option is to customize the RTE configuration in a way capable of accepting those special meta-tags. References [1] Kaysers 4-Star Hotel, [2] Shema.org, [3] Zaenal Akbar, Ioan Toma, Analysis of Kaysers.at Website, Technical Report, STI Innsbruck, [4] TYPO3 The Enterprise Open Source CMS, [5] MySQL Open Source Database, [6] Rich Text Editors (RTE), [7] Structured Data Testing Tool, 13

How to Speak Search Engine

How to Speak Search Engine Using Schema.org and Structured Data to Power the Search Results of the Future Want Your Search Results to Look Like This? Search engines want to provide more rich data in search