% !TEX TS-program = pdflatex
% !TEX encoding = UTF-8 Unicode

% This is a simple template for a LaTeX document using the "article" class.
% See "book", "report", "letter" for other types of document.

\documentclass[11pt]{article} % use larger type; default would be 10pt

\usepackage[utf8]{inputenc} % set input encoding (not needed with XeLaTeX)

\usepackage{url}
%\usepackage{svn-multi}

% Subversion Information
%\svnidlong
%{$HeadURL: $}
%{$LastChangedDate: $}
%{$LastChangedRevision: $}
%{$LastChangedBy: $}
%\svnid{$Id$} 


%%% Examples of Article customizations
% These packages are optional, depending whether you want the features they provide.
% See the LaTeX Companion or other references for full information.

%%% PAGE DIMENSIONS
\usepackage{geometry} % to change the page dimensions
\geometry{a4paper} % or letterpaper (US) or a5paper or....
%\geometry{margin=1cm} % for example, change the margins to 2 inches all round
\topmargin=-0.5in
\textheight=700pt
% \geometry{landscape} % set up the page for landscape
%   read geometry.pdf for detailed page layout information

\usepackage{graphicx} % support the \includegraphics command and options

% \usepackage[parfill]{parskip} % Activate to begin paragraphs with an empty line rather than an indent

%%% PACKAGES
\usepackage{booktabs} % for much better looking tables
\usepackage{array} % for better arrays (eg matrices) in maths
\usepackage{paralist} % very flexible & customisable lists (eg. enumerate/itemize, etc.)
\usepackage{verbatim} % adds environment for commenting out blocks of text & for better verbatim
%\usepackage{subfig} % make it possible to include more than one captioned figure/table in a single float
% These packages are all incorporated in the memoir class to one degree or another...

%%% HEADERS & FOOTERS
\usepackage{fancyhdr} % This should be set AFTER setting up the page geometry
\pagestyle{plain} % options: empty , plain , fancy
\renewcommand{\headrulewidth}{0pt} % customise the layout...
\lhead{}\chead{}\rhead{}
\lfoot{}\cfoot{\thepage}\rfoot{}

%%% SECTION TITLE APPEARANCE
\usepackage{sectsty}
\allsectionsfont{\sffamily\mdseries\upshape} % (See the fntguide.pdf for font help)
% (This matches ConTeXt defaults)

%%% ToC (table of contents) APPEARANCE
\usepackage[nottoc,notlof,notlot]{tocbibind} % Put the bibliography in the ToC
%\usepackage[titles,subfigure]{tocloft} % Alter the style of the Table of Contents
%\renewcommand{\cftsecfont}{\rmfamily\mdseries\upshape}
%\renewcommand{\cftsecpagefont}{\rmfamily\mdseries\upshape} % No bold!

%%% END Article customizations

%%% The "real" document content comes below...

\title{SMC4LRT - Master Outline}
\author{Matej Durco}
%\date{} % Activate to display a given date or no date (if empty),
         % otherwise the current date is printed 

\begin{document}
\maketitle

\tableofcontents

\include{Introduction}


\include{Literature}


\section{Definitions}
We want to clarify or lay down a few terms and definition, ie explanation of our understanding

\begin{description}
\item[Concept]  sense, idea, philosophical problem, which we don't need to discuss here. For our purposes we say: Basic "entity" in an ontology? that of what an ontology is build 
\item[Ontology]  "a explicit specification of a conceptualization" [cite!], but for us mainly a collection of concepts as opposed to lexicon, which is a collection of words.
\item[Word]  a lexical unit, a word in a language, something that has a surface Realization (writtenForm) and is a carrier of sense. so a Relation holds: hasSense(Word, Concept)
\item[Lexicon]  a collection of words, a (lexical) vocabulary
\item[Vocabulary] an index providing mapping from Word (string) to Concept (uri)
\item[(Data)Category] (almost) the same as Concept; Things like "Topic", "Genre", "Organization", "ResourceType" are instantiations of Category
\item[ConceptualDomain] the Class of entities a Concept/Category denotes. For Organization it would be all (existing) organizations,  CD(ResourceType)={Corpus, Lexicon, Document, Image, Video, ...}. Entities of the domain can itself be Categories (ResourceType:Image), but it can be also individuals (Organization University of Vienna)
\item[Entity] 
\item[Resource] informational resource, in the context of CLARIN-Project  mainly Language Resources (Corpus, Lexicon, Multimedia)
\item[Metadata Description] description of some properties of a resource.  MD-Record
\item[Schema] - CMD-Profile
\item[Annotation] 


\end{description}

\section{Analysis}

\subsection{Data landscape}

Describe situation regarding the datasets and formats 

collections, profiles/Terms, ResourceTypes!

DC, OLAC,
ISLE/IMDI, CHILDES, TEI, EAF!
(CES/XCES)

\subsection{Infrastructure}

CMDI \cite{Broeder2010}


\subsection{Ontologies, Controlled Vocabularies, Knowledge Organizing Systems}


\subsubsection{Classification Schemes, Taxonomies }
LCSH, DDC


\subsubsection{Other controlled Vocabularies}
Tagsets: STTS
Language codes ISO-639-1

\subsubsection{Domain Ontologies, Vocabularies}
Organization-Lists
LT-World !?


\subsection{Use Cases}

\begin{itemize}

\item MD Search employing Semantic Mapping
\item MD Search employing Fuzzy Search
\item Content Search
\item Combined MEtadata Content Search
\item Visualization of the Results - charts on facets/dimensions

\item  Create and publish Virtual Collection based on complex Search (intensional/extensional)
\item  Let Create ad-hoc corpus
\end{itemize}

A trivial example for a concept-based query expansion: 
Confronted with a user query: \texttt{Actor.Name = Sue} and knowing that \texttt{Actor} is equivalent or similar to \texttt{Person} and \texttt{Name} is synonym to \texttt{FullName} the expanded query could look like:
\texttt{Actor.Name = Sue OR Actor.FullName = Sue OR Person.Name =  Sue OR Person.FullName= is Sue}

Another example concerning instance mapping: the user looking for all resource produced by or linked to a given institution, does not have to guess or care for various spellings of the name of the institution used in the description of the resources, but rather can browse through a controlled vocabulary of institutions and see all the resources of given institution. While this could be achieved by simple normalizing of the literal-values (and indeed that definitely has to be one processing step), the linking to an ontology, enables to user to also continue browsing the ontology to find institutions that are related to the original institution by means of being concerned with similar topics and retrieve a union of resources for such resulting cluster. Thus in general the user is enabled to work with the data based on information that is not present in the original dataset.

\section{Semantic Mapping}


\subsection{Profiles to Data Categories}
CMD:Profile.Comp.Elem -> DatCat


\subsection{Semantic Relations between (Data)Categories}

Relation Registry

!check DCR-RR/Odijk2010 -follow up
!Cf. Erhard Hinrichs 2009


\subsection{Mapping from strings to Entities}

Based on the textual values in the Metadata-descriptions find matching entities in selected Ontologies.

Identify related ontologies:
LT-World \cite{Joerg2010}

task:
\begin{enumerate}
\item  express MDRecords in RDF
\item  identify related ontologies/vocabularies (category -> vocabulary)
\item  implement (reuse) a lookup/mapping function (Vocabulary Alignement Service? CATCH-PLUS?)

\fbox{	function lookup: Category x String -> ConceptualDomain}

Normally this would be served by dedicated controlled vocabularies, but expect also some string-normalizing preprocessing etc.
\end{enumerate}	



\subsection{Semantic Search}

Main purpose for the undertaking described in previous two chapters (mapping of concepts and entities) is to enhance the search capabilities of the MDService serving the Metadata/Resources-data. Namely to enhance it by employing ontological resources.
Mainly this enhancement shall mean, that the user can access the data indirectly by browsing one or multiple  ontologies, 
with which the data will then be linked. These could be for example ontologies of Organizations and Projects.

In this section we want to explore, how this shall be accomplished, ie how to bring the enhanced capabilities to the user.
Crucial aspect is the question how to deal with the even greater amount of information in a user-friendly way, ie how to prevent overwhelming, intimidating or frustrating the user.

Semi-transparently means, that primarily the semantic mapping shall integrate seamlessly in the interaction with the service, but it shall "explain" - offer enough information - on demand, for the user to understand its role and also being able manipulate easily.

?
Facets
Controlled Vocabularies	
Synonym Expansion (via TermExtraction(ContentSet))

\subsection{Linked Data - Express dataset in RDF}

Partly as by-product of the entities-mapping effort we will get the metadata-description rendered in RDF, linked with 
So theoretically we then only need to provide them "on the web", to make them a nucleus of the LinkedData-Cloud.

Practically this won't be that straight-forward as the mapping to entities will be a hell of a work.
But once that is solved, or for the subsets that it is solved, the publication of that data on the "SemanticWeb" should be easy.

Technical aspects (RDF-store?) / interface (ontology browser?)

defining the Mapping:
\begin{enumerate}
\item convert to RDF
translate: MDREcord -> [\#mdrecord \#property literal]
\item map: \#mdrecord \#property literal  -> [\#mdrecord \#property \#entity]
\end{enumerate}

\subsection{Content/Annotation}
AF + DCR + RR


\subsection{Visualization}
Landscape, Treemap, SOM

Ontology Mapping and Alignement / saiks/Ontology4 4auf1.pdf



\include{System}

\include{Evaluation}


\section{Conclusions and Future Work}

\section{Questions, Remarks}

\begin{itemize}
\item How does this relate to federated search?
\item ontologicky vs. semaziologicky (Semanticke priznaky: kategoriálne/archysémy, difernciacne, specifikacne)
\item "controlled vocabularies"
\end{itemize}


\bibliographystyle{ieee}
\bibliography{../../../2bib/lingua,../../../2bib/ontolingua}


\end{document}
