## 6 Demonstration and Results
### Summary Results of Schema Matching Process  
We presented in Section 6.1 the integration of the training sessions gathered with a Polar RS300X watch in addition with a Polar S1 foot pod, to the ubiquitous user model. The XML document of the training sessions mentioned was modeled with a concept scheme \(P\) containing 31 source concepts to be aligned with the concepts of the target ubiquitous user model concept scheme \(U\). The outcomes were evaluated by a human expert who decided if the semantic relations found were correct and recommendations make sense. The outcomes of the matching process done for the alignment of the  
\begin{table}
\begin{tabular}{|c|c|c|} \hline
**weight** & Date & Height \\ \hline
**LogWeight** & 0.25 & 0.8333 \\ \hline
**date** & **1** & 0.57 \\ \hline \end{tabular}
\end{table}
Table 11: Similarity matrix for the sets of neighbors of _weight_.  
\begin{table}
\begin{tabular}{l l l l l} \hline \hline \(\mathbf{c_{s}}\) & \begin{tabular}{l} **Rule** \\ **applied** \\ \end{tabular} & \begin{tabular}{l} **Element level matching** \\ **result** \\ \end{tabular} & \multicolumn{1}{l}{**Structure level matching result**} & \multicolumn{1}{l}{_MAP(\(\mathbf{c_{s}}\),\(\mathbf{c_{h}}\))_} \\ \hline \multirow{4}{*}{**date**} & \multirow{2}{*}{1} & \multirow{4}{*}{\begin{tabular}{l} _Relation(\(c_{s}\),\(c_{tb}\)) is equivalence_ \\ _and sim\({}_{0}\)=11 in_ \\ _[Physical activity \& training]_ \\ _and sim\({}_{0}\)=1 in [Health O\&M ]_ \\ \end{tabular} & \begin{tabular}{l} _Relation(\(c^{{}^{\prime}}\),\(c^{{}^{\prime}}\),\(c^{{}^{\prime}}\)) is equivalence in_ \\ determined as \\ skos:exactMatch \\ \end{tabular} \\ \hline \multirow{4}{*}{**weightInKg**} & \multirow{2}{*}{1} & \multirow{4}{*}{\begin{tabular}{l} _Relation(\(c_{s}\),\(c_{tb}\)) is equivalence_ \\ _and sim\({}_{0}\)=1_ \\ _and sim\({}_{0}\)=1 in_ \\ _[Health O\&M ]_ \\ \end{tabular} & \
\begin{tabular}{l} _Relation(\(c^{{}^{\prime}}\),\(c^{{}^{\prime}}\)) is equivalence in_ \\ _[Health O\&M ]_ \\ \end{tabular} &
\begin{tabular}{l} _MAP(\(c_{s}\),\(c_{tb}\))_ \\ determined as \\ skos:exactMatch. \\ \end{tabular} \\ \hline \hline \end{tabular}
\end{table}
Table 12: Mappings determined after rule application.  
concepts in the concept schemes \(P\) and \(U\) are shown in Table 13. The best exactMatch semantic relations were found for nine concepts. The best suited concept for alignment in the target concept scheme for four concepts was not found.  
This error is due to the use of abbreviations in the source XML document (for example _avg_ instead of _average_). This problem can be solved using alternate and hidden SKOS labels in the target concept scheme, but this knowledge must be provided by a human expert or domain ontology. All recommendations given by the process was described as reasonable by the expert. No closeMatch relation was found.  
After the integration of the previous mentioned source document, we try to reuse some of the information of this profile supplier to personalize a Web service of provider \"B\", in this case LogWeight Web Service from Training peaks. A concept scheme \(W\) was built with the concept labels of the SOAP web service request parameters, in this case _date_ and _weight_. It is important to notice that for this experiment authentication parameters were not considered. The outcomes of the matching process done for the alignment of the concepts in the concept schemes \(W\) and \(U\) are shown in Table 14:  
With this toy example, we showed that enrichment of a fitness application and web service personalization was possible with our proposed solution. The results with this toy example only proof the feasibility of our solution.