Information Technology Reference
In-Depth Information
Figure 3.11.
Diagram of design classes for the itinerary search service
3.5.4.
Implementation of the personalized service
The applications (
Search
,
ResultSearch
,
Choice
, etc.) have been implemented
through
ASP.NET
pages. Implementation of the
PersonalizeSystem
module provides
a function (
getPerSyst
) that has the objective of sending back an object enabling
PerSyst primitives to be invoked.
This object determines the data that the service and PerSyst should exchange
while respecting the data models defined in the phase of service analysis. These data
are transcoded in the XML format (Figure 3.12 gives an example of XML data for
an itinerary search request)
2
.
The presentations are carried out via an XSLT transformation using Archimed's
JSE
3
transformation motor. Figure 3.13 presents the itinerary search page also
enabling the visualization and modification of user preferences.
2 XML (
eXtensible Markup Language
, www.w3.org) is a standard for the exchange of data
between applications. It also facilitates the development of an adaptive interface [HAB 04]
that is multi-targeted [PUE 02] and multi-modal (with VoiceXML [ROU 04] or UsiXML
[STA 05]) and even multi-context [LIM 05].
