Changeset 3551 for SMC4LRT/chapters/Literature.tex
- Timestamp:
- 09/11/13 18:04:14 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
SMC4LRT/chapters/Literature.tex
r3140 r3551 4 4 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 5 5 6 This work is guided by \todoin{two (or three? + Infrastructure} main dimensions: the data - in broad, Language Resource and Technology and the method -Semantic Web technologies. This division is reflected in the following chapter:6 This work is guided by two main dimensions: the \textbf{data} -- in broad, Language Resource and Technology -- and the \textbf{method} -- Schema matching and Semantic Web technologies. This division is reflected in the following chapter: 7 7 8 8 \section{(Infrastructure for) Language Resources and Technology} … … 14 14 Chapter \ref{ch:data} examines the field of LRT in more detail. 15 15 16 16 17 \subsection{Metadata} 17 A comprehensive architecture for harmonized handling of metadata -- the Component Metadata Infrastructure (CMDI)\footnote{\url{http://www.clarin.eu/cmdi}} \cite{Broeder +2011} -- is being implemented within the CLARIN project\footnote{\url{http://clarin.eu}}. This service-oriented architecture consisting of a number of interacting software modules allows metadata creation and provision based on a flexible meta model, the \emph{Component Metadata Framework}, that facilitates creation of customized metadata schemas -- acknowledging that no one metadata schema can cover the large variety of language resources and usage scenarios -- however at the same time equipped with well-defined methods to ground their semantic interpretation in a community-wide controlled vocabulary -- the data category registry \cite{Kemps-Snijders2009,Broeder2010}.18 A comprehensive architecture for harmonized handling of metadata -- the Component Metadata Infrastructure (CMDI)\footnote{\url{http://www.clarin.eu/cmdi}} \cite{Broeder2011} -- is being implemented within the CLARIN project\footnote{\url{http://clarin.eu}}. This service-oriented architecture consisting of a number of interacting software modules allows metadata creation and provision based on a flexible meta model, the \emph{Component Metadata Framework}, that facilitates creation of customized metadata schemas -- acknowledging that no one metadata schema can cover the large variety of language resources and usage scenarios -- however at the same time equipped with well-defined methods to ground their semantic interpretation in a community-wide controlled vocabulary -- the data category registry \cite{Kemps-Snijders+2009,Broeder2010}. 18 19 19 Individual components of this infrastructure will be described in more detail in the section \ref{ch: components}.20 Individual components of this infrastructure will be described in more detail in the section \ref{ch:infra}. 20 21 22 A number of solution evolved in the recent years. 23 The first to undertake standardization efforts for the exchange of catalog information were digital libraries. 24 25 Z39.50 as base protocol, Worldcat, mapping/configuration files. 26 These catalogs are further described in the section \ref{sec:other-md-catalogs} 27 28 In the recent years the evolving research infrastructures all identified a common/harmonized search as a crucial component of the system and came up with a number of solutions, however often reduced to collecting metadata, reducing to dublincore 29 and offering a lucene/solr based facetted search. 30 These catalogs are further described in the section \ref{sec:lrt-md-catalogs}. 31 32 Riley and Becker \cite{Riley2010seeing} put the overwhelming amount of existing metadata standards into a systematic comprehensive overview analyzing the use of standards from four aspects: community, domain, function, and purpose. 21 33 22 34 \subsection{Content Repositories} … … 79 91 \todoin{check if relevant: http://schema.org/} 80 92 93 \subsection{Existing Crosswalk services} 94 95 \url{http://www.oclc.org/developer/services/metadata-crosswalk-service} 96 97 http://semanticweb.org/wiki/VoID 98 http://www.dnb.de/rdf 99 81 100 \subsection{Ontology Visualization} 82 101
Note: See TracChangeset
for help on using the changeset viewer.