Changeset 4838 for CMDI-Interoperability

Timestamp:

03/28/14 18:34:25 (10 years ago)

Author:

xnrn@gmx.net

Message:

minor corrections

File:

• CMDI-Interoperability/CMD2RDF/trunk/docs/papers/2014-LREC/CMD2RDF.tex (modified) (3 diffs)

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

@@ -192 +192 @@
 \subsection{CMD profile and component definitions}
 These top-level classes and properties are subsequently used for modelling the actual profiles, components and elements as they are defined in the CR.
-For stand-alone components, the IRI is the (future) path into the CR to get the RDFS representation for the profile/component.\furl{http://catalog.clarin.eu/ds/ComponentRegistry/rest/registry/components/clarin.eu:cr1:c_1271859438125/rdf} For ``inner'' components (that are defined as part of another component) and elements the identifier is a concatenation of the nearest ancestor stand-alone component's IRI and the dot-path to given component/element (e.g., Actor:\\ \code{cr:clarin.eu:cr1:c\_1271859438197/rdf \#Actor.Actor\_Languages.Actor\_Language}\footnote{For the sake of readability, in the examples we will collapse the component IRIs, refering to them just by their name, prefixed with \code{cmd:}})
+For stand-alone components, the IRI is the (future) path into the CR to get the RDFS representation for the profile/component.\furl{http://catalog.clarin.eu/ds/ComponentRegistry/rest/registry/components/clarin.eu:cr1:c_1271859438125/rdf} For ``inner'' components (that are defined as part of another component) and elements the identifier is a concatenation of the nearest ancestor stand-alone component's IRI and the dot-path to given component/element (e.g., Actor:\\ \code{cr:clarin.eu:cr1:c\_1271859438197/rdf \#Actor.Actor\_Languages.Actor\_Language}\footnote{For better readability, in the examples we collapse the component IRIs, using just the name, prefixed with \code{cmd:}})
 
 \begin{example2}
@@ -204 +204 @@
 
 \subsubsection{Data Categories}
-The primary concept registry in use by CMDI is ISOcat. The recommended approach to link to the data categories is via an annotation property \cite{Windhouwer2012_LDL}.
+The primary concept registry used by CMDI is ISOcat. The recommended approach to link to the data categories is via an annotation property \cite{Windhouwer2012_LDL}.
 
 \begin{example2}
@@ -277 +277 @@
 
 \begin{example2}
-\_:topComponent1  \\
+\textless lr1.cmd \textgreater  \\
  $\:$ dc:identifier  & \textless lr1.cmd \textgreater ;  \\
  $\:$ dc:creator  & "John Doe" ;  \\