source: SMC4LRT/chapters/Conclusion.tex @ 3665

\chapter{Conclusions and Future Work}
\label{ch:conclusions}

With this work, a technical description together with a prototypical implementation for the \emph{Semantic Mapping Component} was delivered -- one module within an infrastructure for providing metadata, the \emph{Component Metadata Infrastructure}.

SMC features a concept-based crosswalk service providing correspondences between fields in metadata formats and a module for query expansion building on top of it, allowing concept-based semantic search. Further work is needed on the crosswalk service providing more complex types of response (similarity ratio, relation types) with implications for the query expansion module. The integration of the semantic mapping features in the search user interface is only rudimentary at present, calling for a more elaborate solution.
% Dynamic integration of the information from the Relation Registry into the search interface and search processing.

A whole separate track is the effort to deliver the CMD data as \emph{Linked Open Data}, for which only the groundwork has been done by specifying the modelling of the data in RDF. Further steps are: setup of a processing workflow to apply the specified model and transform all the data (profiles and instances) into RDF, a server solution to host the data and allow querying it and finally, on top of it offer a web interface for the users to explore the dataset.

%Irrespective of the additional levels - the user wants and has to get to the resource. (not always) to the "original" 
And finally, a visualization tool for the schema level data of the discussed data collection was developed -- the \emph{SMC Browser}. 
Considering the feedback received until now from the colleagues in the community, it is already now a useful tool with high further potential. As detailed in \ref{smc-browser-extensions}, there is a number of features, that could enhance the functionality and usefulness of the tool: integrate with instance data to be able to directly see which profiles are effectively being used; allow set operations on subgraphs (like intersection and difference) to enable differential views; generalize the matching algorithm; enhance the tool to act as an independent visualization service, by accepting external graph data (from any domain).

Within the CLARIN community a number of (permanent) tasks has been identified and corresponding task forces have been established,
one of them being metadata curation. The results of this work represent a directly applicable groundwork for this ongoing effort.
One particularly pressing aspect of the curation is the consolidation of the actual values in the CMD records, a topic explicitly treated in this work.