3. Introduction
Mapping
A relation between the elements of Feratel XML and the
classes of Schema.org including their properties
Objectives:
To annotate the Feratel XML with Schema.org such that
users of Feratel could benefit from the annotated data
1. Major search engines (Google, Yahoo!, Bing, Yandex) could
interpret the annotated web pages properly
2. Increasing the visibility of web pages on those search
engines
www.sti-innsbruck.at 3/19
4. Introduction
The mapping steps:
1. For each element in Feratel XML
Find the most suitable class in Schema.org
If not available then find the most suitable property for the
parent elements in Schema.org
2. For each attribute of element in Feratel XML
Find the most suitable property for the element or parent
elements in Schema.org
www.sti-innsbruck.at 4/19
5. Mapping - Example
XML element Event to http://schema.org/Event, Translation
to property name
XML element Position to http://schema.org/GeoCoordinates,
attribute Latitude and Longitude to properties latitude and
longitude respectively
www.sti-innsbruck.at 5/19
6. Events
Property geo is used by type Place only
A property for the relation between PostalAddress and
Organization is required
www.sti-innsbruck.at 6/19
7. Shop Items
Shop Items include brochures, articles and guides
No class for Guide or Brochure
A class for CopyrightHolder is required
www.sti-innsbruck.at 7/19
11. Implementation
Client sends request [1]
Dispatcher forwards the request
to the Feratel API endpoint [2]
The received response [3] then
forwarded to the Annotator [4]
to be annotated
The annotated response [5] then
returned to the Client [6]
www.sti-innsbruck.at 11/19
18. Discussion
1. Several elements and attributes from Feratel XML can not
be mapped to Schema.org classes or properties
2. A request for Service Providers to Feratel API can not be
performed with one invocation due to the large amount of
data. A “request workflow” is required and this feature is
not reflected in the current XSLT yet.
www.sti-innsbruck.at 18/19