Changeset 3862 for CMDI-Interoperability

Timestamp:

10/23/13 14:42:06 (11 years ago)

Author:

vronk

Message:

small stripping

File:

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

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

@@ -213 +213 @@
 dcr:datcat & a  & owl:AnnotationProperty ; \\
  & rdfs:label  & "data category"@en ; \\
- & rdfs:comment  & "This resource is equivalent to  this data category."@en ; \\
- & skos:note  & "The data category should be identified by its PID."@en ; \\
-\end{example3}
-
-That implies that the \code{@ConceptLink} attribute on CMD elements and components as used in the CMD profiles to reference the data category can be modelled as: 
+% & rdfs:comment  & "This resource is equivalent to  this data category."@en ; \\
+% & skos:note  & "The data category should be identified by its PID."@en ; \\
+\end{example3}
+
+The \code{@ConceptLink} attribute on CMD elements and components referencing the data category can be modelled as: 
 
 \begin{example3}
@@ -420 +420 @@
 \section{Implementation}
 
-The transformation of profiles and instances into RDF/XML is accomplished by a set of XSL-stylesheets, that are currently being tested on a sample dataset. The mappings described for the CMD specification (see section \ref{sec:CMDM}) have to be integrated into the CMDI core infrastructure, e.g., the CR. 
+The transformation of profiles and instances into RDF/XML is accomplished by a set of XSL-stylesheets, that are currently being tested on a sample dataset. Once ready they will be integrated into the CMDI core infrastructure, e.g., the CR. 
 %And in the near future, a test on the instances in the complete CLARIN joint metadata domain will be performed.