Changeset 4460 for CMDI-Interoperability

Timestamp:

02/06/14 11:02:56 (10 years ago)

Author:

vronk

Message:

updated numbers on CMD data and corrected a few typos

Location:

CMDI-Interoperability/CMD2RDF/trunk/docs/papers/2014-LREC

Files:

• CMD2RDF.bib (modified) (4 diffs)
• CMD2RDF.tex (modified) (8 diffs)

CMDI-Interoperability/CMD2RDF/trunk/docs/papers/2014-LREC/CMD2RDF.bib

@@ -193 +193 @@
 }
 
+@STANDARD{ISODIS24622-1_2013,
+  title = {Language resource management -- Component Metadata Infrastructure
+        -- Part 1: The Component Metadata Model (CMDI-1)},
+  organization = {ISO},
+  author = {{ISO/DIS 24622-1}},
+  type = {International Standard},
+  number = {24622-1},
+  address = {Geneva, Switzerland},
+  year = {2013},
+  url = {http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=37336},
+  owner = {m},
+  publisher = {ISO},
+  timestamp = {2014.02.05}
+}
+
 @STANDARD{ISO12620:2009,
   title = {Specification of data categories and management of a Data Category
@@ -215 +230 @@
 
 @INPROCEEDINGS{Joerg2010,
-  author = {Brigitte J\'{o}rg and Hans Uszkoreit and Alastair Burt},
+  author = {Brigitte J\"{o}rg and Hans Uszkoreit and Alastair Burt},
   title = {LT World: Ontology and Reference Information Portal},
   booktitle = {LREC},
@@ -389 +404 @@
 
 @INPROCEEDINGS{SchuurmanWindhouwer2011,
-  author = {I. Schuurman and M.A. Windhouwer.},
+  author = {Ineke Schuurman and Menzo Windhouwer},
   title = {Explicit Semantics for Enriched Documents. What Do ISOcat, RELcat
         and SCHEMAcat Have To Offer?},
@@ -604 +619 @@
 }
 
-@STANDARD{ISODIS24622-1_2013,
-  title = {Language resource management -- Component Metadata Infrastructure -- Part 1: The Component Metadata Model (CMDI-1)},
-  organization = {ISO},
-  author = {{ISO/DIS 24622-1}},
-  type = {International Standard},
-  number = {24622-1},
-  address = {Geneva, Switzerland},
-  year = {2013},
-  url = {http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=37336},
-  abstract = {},
-  owner = {m},
-  publisher = {ISO},
-  timestamp = {2014.02.05}
-}
-
-
 @comment{jabref-meta: selector_publisher:}
 

CMDI-Interoperability/CMD2RDF/trunk/docs/papers/2014-LREC/CMD2RDF.tex

@@ -65 +65 @@
 \title{From CLARIN Component Metadata to Linked Open Data}
 
-\name{Matej Durco, Menzo Windhouwer}
+\name{Matej \v{D}ur\v{c}o, Menzo Windhouwer}
 
 \address{ Institute for Corpus Linguistics and Text Technology (ICLTT), The Language Archive - DANS \\
                Vienna, Austria, The Hague, The Netherlands \\
-               matej.durco@assoc.oeaw.ac.at, menzo.windhouwer@dans.knaw.nl\\}
+               matej.durco@oeaw.ac.at, menzo.windhouwer@dans.knaw.nl\\}
 
 \abstract{In the european CLARIN infrastructure a growing number of resources are described with Component Metadata. In this paper we
@@ -81 +81 @@
 \section{Motivation}
 %
-Although semantic interoperability has been one of the main motivations for CLARIN's Component Metadata Infrastructure (CMDI), until now there has been no work on the obvious -- bringing CMDI to the Semantic Web. We believe that providing the CLARIN CMD records as Linked Open Data (LOD) interlinked with external semantic resources, will open up new dimensions of processing and exploring of the CMD data by employing the power of semantic technologies. In this paper, we lay out how individual parts of the CMD Infrastructure can be expressed in RDF and made ready to be interlinked with existing external semantic resources (ontologies, knowledge bases, vocabularies). 
+Although semantic interoperability has been one of the main motivations for CLARIN's Component Metadata Infrastructure (CMDI), until now there has been no work on the obvious -- bringing CMDI to the Semantic Web. We believe that providing the CLARIN CMD records as Linked Open Data (LOD) interlinked with external semantic resources, will open up new dimensions of processing and exploring of the CMD data by employing the power of semantic technologies. In this paper, we lay out how individual parts of the CMD data domain can be expressed in RDF and made ready to be interlinked with existing external semantic resources (ontologies, taxonomies, knowledge bases,  vocabularies). 
 %This conversion lays a foundation / is groundwork for providing the original dataset as a \emph{Linked Open Data} nucleus within the \emph{Web of Data}\cite{TimBL2006} as well as for real semantic (ontology-driven) search and exploration of the data.
 
@@ -107 +107 @@
 
 \subsubsection{CMD Profiles }
-Currently 133 public profiles and 772 components are defined in the CR.
+Currently 146 public profiles and 857 components are defined in the CR.
 Next to the `native' ones a number of profiles have been created that implement existing metadata formats, like OLAC/DCMI-terms, TEI Header or the META-SHARE schema. 
 %The resulting profiles proof the flexibility/expressi\-vi\-ty of the CMD metamodel.
@@ -119 +119 @@
 
 The main CLARIN OAI-PMH harvester\footnote{\url{http://catalog.clarin.eu/oai-harvester/}}
-regularly collects records from the -- currently 69 -- providers, all in all over 550.000 records. 
-16 of the providers offer CMDI records, the other 53 provide around 140.000 OLAC/DC records, that are converted into the corresponding CMD profile. 
+regularly collects records from the -- currently 58 -- providers, all in all over 600.000 records. 
+Some 20 of the providers offer CMDI records, the rest provides around 140.000 OLAC/DC records, that are converted into the corresponding CMD profile. 
 %Next to these 81.226 original OLAC records, there a few providers offering their OLAC or DCMI-terms records already converted into CMDI, thus all in all OLAC, DCMI-terms records amount to 139.152.
 %On the other hand, some
@@ -312 +312 @@
 \begin{example3}
 \_:actor1  & a & cmd:Actor . \\
-\_:actor1lang1  & a & cmd:Actor. \\
- &  & Actor\_Language . \\
+\_:actor1lang1  & a  & cmd:Actor.Language . \\
 \_:actor1  & cmd:contains & \_:actor1lang1 . \\
 \end{example3}
@@ -349 +348 @@
 \_:org & a & cmd:Person.Organisation ; \\
         & \multicolumn{2}{l}{cmd:hasPerson.OrganisationElementValue \quad 'MPI'\^{}\^{}xs:string ;} \\
-        & \multicolumn{2}{l}{ cmd:hasPerson.OrganisationElementEntity  \quad <http://www.mpi.nl/> . }\\
-
-<http://www.mpi.nl/> & a  & cmd:OrganisationElementEnity . 
+        & \multicolumn{2}{l}{ cmd:hasPerson.OrganisationElementEntity  \quad \textless http://www.mpi.nl/\textgreater . }\\
+
+\textless http://www.mpi.nl/\textgreater & a  & cmd:OrganisationElementEnity . 
 \end{example3}
 \end{center}
@@ -370 +369 @@
 \section{Mapping field values to semantic entities}
 \label{sec:values2entities}
-
-\commentx{this is probably definitely too much for one abstract  - so we could just anounce the need for this mapping process.}
 
 This task is a prerequisite to be able to express also the CMD instance data in RDF. The main idea is to find entities in selected reference datasets (controlled vocabularies, ontologies) matching the literal values in the metadata records. The obtained entity identifiers are further used to generate new RDF triples, representing outbound links.
@@ -452 +449 @@
 Of course, language is just one dimension to use for mapping. 
 Step by step we will link other categories like countries, geographica, organisations, etc.
-to some of the central nodes of the LOD cloud , like \xne{dbpedia}, \xne{Yago} or \xne{geonames}, 
+to some of the central nodes of the LOD cloud, like \xne{dbpedia}, \xne{Yago} or \xne{geonames}, 
 but also to domain-specific semantic resource like the ontology for language technology \xne{LT-World} \cite{Joerg2010} developed at DFKI.