Changeset 3665 for SMC4LRT/chapters/Data.tex

Timestamp:

10/02/13 19:52:31 (11 years ago)

Author:

vronk

Message:

rework of Results, Definitions, appendix, added Conclusion,
smaller changes to Design, Data

File:

• SMC4LRT/chapters/Data.tex (modified) (6 diffs)

SMC4LRT/chapters/Data.tex

@@ -11 +11 @@
 \label{def:CMD}
 
-The \emph{Component Metadata Framework} (CMD) is the data model of the CLARIN metadata infrastructure. (See \ref{CMDI} for information about the infrastructure. The XML-schema of CMD -- the general-component-schema -- is featured in appendix \ref{lst:general-component-schema}.)
+The \emph{Component Metadata Framework} (CMD) is the data model of the CLARIN Component Metadata Infrastructure. (See \ref{def:CMDI} for information about the infrastructure. The XML-schema defining CMD -- the \xne{general-component-schema} -- is featured in appendix \ref{lst:cmd-schema}.)
 CMD is used to define the so-called \var{profiles} being constructed out of reusable \var{components} -- collections of metadata fields. The components can contain other components and they can be reused in multiple profiles. Profile itself is just a special kind of a component (a sub class), with some additional administrative information.
 The actual core provision for semantic interoperability is the requirement, that each CMD element (i.e. metadata field) refers ``via a PID to exactly one data category\footnote{persistently referenceable concept definition} (cf. \ref{def:DCR}), thus 
 indicating unambiguously how the content of the field in a metadata description should be interpreted'' \cite{Broeder+2010}. 
 
+This approach of integrating prerequisites for semantic interoperability directly into the process of metadata creation is fundamentally different from the traditional methods of schema matching that try to establish pairwise alignments between already existing schemas -- be it algorithm-based or by means of explicit manually defined crosswalks\cite{Shvaiko2005}. 
+
 While the primary registry for data categories used in CMD is the \xne{ISOcat} Data Category Registry (cf. \ref{def:DCR}), other authoritative sources are accepted (so-called ``trusted registries''), especially the set of terms maintained by the Dublin Core Metadata Initiative \cite{DCMI:2005}.
 
@@ -32 +34 @@
 \caption{The development of defined profiles and DCs over time}
 \label{table:dev_profiles}
-  \begin{tabular}{ l | r | r | r | r }
+%  \begin{tabular}{ l | r | r | r | r }
+  \begin{tabular}{ l  r  r  r  r }
+
     \hline
 date     & 2011-01 & 2012-06 & 2013-01 & 2013-06  \\
@@ -51 +55 @@
 
 
-\subsection{Instance Data}
-
-
-\todoin{ add historical perspective on data - list overall}
+\subsubsection{Instance Data}
+
+
+%\todoin{ add historical perspective on data - list overall}
 
 The main CLARIN OAI-PMH harvester\footnote{\url{http://catalog.clarin.eu/oai-harvester/}}
@@ -65 +69 @@
 \caption{Top 20 profiles, with the respective number of records}
 \begin{center}
-  \begin{tabular}{ r | l }
+  \begin{tabular}{ r l }
+    \hline
 \# records & profile \\
     \hline
@@ -96 +101 @@
 \caption{Top 20 collections, with the respective number of records}
 \begin{center}
-  \begin{tabular}{ r | l }
+  \begin{tabular}{ r l }
+    \hline
 \# records & colleciton \\
     \hline
@@ -154 +160 @@
 
 \subsection{TEI / teiHeader}
+\label{tei}
+
  TEI/teiHeader/ODD,
+
 
 \subsection{ISLE/IMDI}