## 6 Demonstration and Results
### Results of Mapping the Concepts from a New Source to Existing Concepts in the Ubiquitous User Model
\begin{table}
\begin{tabular}{l l l l l} \hline \(c_{s}\) & \
\begin{tabular}{l} **Rule** \\ **applied** \\ \end{tabular} &
\begin{tabular}{l} **Element level** \\ **matching result** \\ \end{tabular} & \multicolumn{1}{l}{\(\textit{Structure level}\)} & \multicolumn{1}{l}{\(\textit{MAP(c_{s}c_{th})}\)} \\ \hline
**name** & 3 & \begin{tabular}{l} _Relation(c\({}_{s}\),c\({}_{th}\)) is equivalence_ \\ _and sim\({}_{0}\)=1_ \\ _\end{tabular} & \begin{tabular}{l} _Relation(c\({}_{s}\),c\({}_{th}\)) is related_ \\ _and sim\({}_{0}\)=1_ \\ _\end{tabular} & \
\begin{tabular}{l} _Relation(c\({}_{s}\),c\({}_{th}\)) is related_ \\ _and is not member of O\&M_ \\ _collection_ \\ \end{tabular} &
\begin{tabular}{l} Homonymous \\ (no mapping) \\ \end{tabular} \\ \hline
**calories** & 1 & \begin{tabular}{l} _Relation(c\({}_{s}\),c\({}_{th}\)) is equivalence_ \\ _and sim\({}_{0}\)=1 in_ \\ _[Physical activity \& \& \& \begin{tabular}{l} _Relation(c\({}_{s}\),c\({}_{th}\)) is equivalence in_ \\ _[Physical activity \& training]_ \\ _and sim\({}_{0}\)=1 in [Food \&Diet]_ \\ \end{tabular} & \begin{tabular}{l} _Relation(c\({}_{s}\),c\({}_{th}\)) is equivalence in_ \\ _[Physical activity \& training]_ \\ _and sim\({}_{0}\)=1 in [Food \&Diet]_ \\ \end{tabular} & \begin{tabular}{l} _Relation(c\({}_{s}\),c\({}_{th}\)) is equivalence in_ \\ _[Health O\&M]_ \\ \end{tabular} & \
\begin{tabular}{l} _Relation(c\({}_{s}\),c\({}_{th}\)) is equivalence in_ \\ _[Health O\&M]_ \\ \end{tabular} &
\begin{tabular}{l} _MAP(c\({}_{s}\),c\({}_{th}\))_ \\ determined as \\ skos:exactMatch. \\ \end{tabular} \\ \hline
**weight** & 1 & \begin{tabular}{l} _Relation(c\({}_{s}\),c\({}_{th}\)) is equivalence_ \\ _and sim\({}_{0}\)=1 in_ \\ _[Health O\&M]_ \\ \end{tabular} & \
\begin{tabular}{l} _Relation(c\({}_{s}\),c\({}_{th}\)) is equivalence in_ \\ _[Health O\&M]_ \\ \end{tabular} &
\begin{tabular}{l} _Relation(c\({}_{s}\),c\({}_{th}\)) is equivalence in_ \\ determined as \\ skos:exactMatch. \\ \end{tabular} \\ \hline \end{tabular}
\end{table} 
Table 8: Mappings determined after rule application. The process of structure level matching successfully determined the right match for _calories_, despite the resulting conflict of the element level matching. Likewise, the mapping for concept _weight_ was successful. Results of Personalizing a Web Service Reusing Information with the Mediation of the Ubiquitous User Model  
The same process of concept alignment for interoperability used for mapping the concepts from a new source to existing concepts in ubiquitous user model is functional for interoperability with web services. First of all, the concept labels of the SOAP web service request are selected as concepts \(\boldsymbol{c}_{s}\boldsymbol{\in}\boldsymbol{C}_{s}\). It is important to notice that for this experiment authentication parameters were not considered. For the target side, a selection of relevant skos:prefLabels of the ubiquitous user model are used as concepts \(\boldsymbol{c}_{t}\boldsymbol{\in}\boldsymbol{C}_{T}\). The similarity matrix is calculated with the web service request concepts and the ubiquitous user model concepts in the element level matching, is analogous to Table 3, which was built for the source XML document. In Table 9, we present this similarity matrix. It shows that for the concept _date_ three best suited concepts for alignment were found. Date is a concept that is almost always attached to different kind of observations and measurements, since the nature of this information is dynamic. Once again, structure level matching will help to determine the sub collection of membership of the concept _date_. For the concept _weightInKg_, one _equivalence_ is found and the best suited concept for alignment in the target side is _weight_. Since all the resulting best suited concepts for alignment are in the same collection, to determine the most related collection is fairly straightforward, and it correspond to _Observations &measurement_. The structure level matching process is also followed as described in Section 4.5.3.