|
|
@@ -7,44 +7,99 @@
|
|
|
<xsl:template match="odML">
|
|
|
<html>
|
|
|
<head>
|
|
|
- <link rel="stylesheet" href="./odml_style.css" />
|
|
|
- <link href="./odMLIcon.ico" rel="shortcut icon" livesrc="./odMLIcon.png" />
|
|
|
+ <meta charset="utf-8" />
|
|
|
+ <title>odML | Open metadata markup language - Templates and Terminologies -</title>
|
|
|
+ <meta name="description"
|
|
|
+ content="Templates and Terminologies for the storage of scientific metadata" />
|
|
|
+ <link rel="stylesheet" href="https://terminologies.g-node.org/_resources/odml_style.css" />
|
|
|
+ <link rel="icon" href="https://terminologies.g-node.org/_resources/odMLIcon.ico" />
|
|
|
</head>
|
|
|
|
|
|
- <body>
|
|
|
+ <body>
|
|
|
<header>
|
|
|
- <h1>odML Terminologies</h1>
|
|
|
- <p>data model for storing arbitrary metadata</p>
|
|
|
+ <h1>odML Terminologies</h1>
|
|
|
+ <p>Data model for storing arbitrary metadata</p>
|
|
|
</header>
|
|
|
|
|
|
<div class="wrapper">
|
|
|
- <section>
|
|
|
- <p><a href="index.html"><img src="./odMLTitle.png" /></a></p>
|
|
|
- <ol>
|
|
|
- <xsl:if test="section">
|
|
|
- <xsl:for-each select="section">
|
|
|
- <xsl:call-template name="sectionTemplate"/>
|
|
|
- </xsl:for-each>
|
|
|
- </xsl:if>
|
|
|
- </ol>
|
|
|
- </section>
|
|
|
- </div>
|
|
|
+ <sec>
|
|
|
+ <p><a href="https://terminologies.g-node.org/index.html">
|
|
|
+ <img src="https://terminologies.g-node.org/_resources/odMLTitle.png"
|
|
|
+ title="Terminologies home" />
|
|
|
+ </a></p>
|
|
|
+ <h1>odML - Terminologies</h1>
|
|
|
+ <p>This repository contains Terminologies; odML facilitates and encourages
|
|
|
+ standardization of scientific metadata by providing such terminologies.
|
|
|
+ An odML-file can be based on such a terminology.
|
|
|
+ In that case one does not need to provide definitions since they are part of
|
|
|
+ the linked terminology. This page hosts all currently available odML
|
|
|
+ Terminology files.</p>
|
|
|
+
|
|
|
+ <p>
|
|
|
+ A general introduction to odML and its usage can be found at the
|
|
|
+ <a href="http://www.g-node.org/odml" rel="nofollow">main odML page</a>.
|
|
|
+ A brief introduction can be found at the bottom of the page.</p>
|
|
|
+
|
|
|
+ <p>If you would like to contribute and provide additions to the terminology
|
|
|
+ collection to be shared with and used by the community, please open an
|
|
|
+ issue or even create a Pull Request with your terminology on the
|
|
|
+ corresponding <a href="https://github.com/G-Node/odml-terminologies" rel="nofollow">
|
|
|
+ github repository</a>.</p>
|
|
|
+
|
|
|
+ <h1>Terminology collection</h1>
|
|
|
+ <ol>
|
|
|
+ <xsl:if test="section">
|
|
|
+ <xsl:for-each select="section">
|
|
|
+ <xsl:call-template name="sectionTerminology"/>
|
|
|
+ </xsl:for-each>
|
|
|
+ </xsl:if>
|
|
|
+ </ol>
|
|
|
+
|
|
|
+ <h2>A brief introduction to odML and metadata</h2>
|
|
|
+ <p>odML (open metadata Markup Language) is a framework, proposed by
|
|
|
+ <a href="http://journal.frontiersin.org/article/10.3389/fninf.2011.00016/full"
|
|
|
+ rel="nofollow">Grewe et al. (2011)</a>,
|
|
|
+ to organize and store experimental metadata in a human- and machine-readable,
|
|
|
+ XML based format (odml). In this tutorial we will illustrate the conceptual
|
|
|
+ design of the odML framework and show hands-on how you can generate your own
|
|
|
+ odML metadata file collection. A well organized metadata management of your
|
|
|
+ experiment is a key component to guarantee the reproducibility of your research
|
|
|
+ and facilitate the provenance tracking of your analysis projects.</p>
|
|
|
+
|
|
|
+ <h3>What are metadata and why are they needed?</h3>
|
|
|
+ <p>Metadata are data about data. They describe the conditions under which the
|
|
|
+ actual raw-data of an experimental study were acquired. The organization of
|
|
|
+ such metadata and their accessibility may sound like a trivial task, and
|
|
|
+ most laboratories developed their home-made solutions to keep track of
|
|
|
+ their metadata. Most of these solutions, however, break down if data and
|
|
|
+ metadata need to be shared within a collaboration, because implicit
|
|
|
+ knowledge of what is important and how it is organized is often
|
|
|
+ underestimated.</p>
|
|
|
+ <p>While maintaining the relation to the actual raw-data, odML can help to
|
|
|
+ collect all metadata which are usually distributed over several files and
|
|
|
+ formats, and to store them unitedly which facilitates sharing data and
|
|
|
+ metadata.</p>
|
|
|
+
|
|
|
+ <h3>Key features of odML</h3>
|
|
|
+ <ul>
|
|
|
+ <li>open, XML based language, to collect, store and share metadata</li>
|
|
|
+ <li>Machine- and human-readable</li>
|
|
|
+ <li>Python-odML library</li>
|
|
|
+ <li>Interactive odML-Editor</li>
|
|
|
+ </ul>
|
|
|
+ </sec>
|
|
|
+ </div>
|
|
|
</body>
|
|
|
</html>
|
|
|
</xsl:template>
|
|
|
|
|
|
<!-- ************************************************ -->
|
|
|
- <!-- section template. -->
|
|
|
- <xsl:template name="sectionTemplate" match="section">
|
|
|
+ <!-- section terminology. -->
|
|
|
+ <xsl:template name="sectionTerminology" match="section">
|
|
|
<!--create the list item -->
|
|
|
<xsl:variable name="linkurl" select="include"/>
|
|
|
<li>
|
|
|
- <a href="{$linkurl}"><xsl:value-of select="concat(type, ': ', name, ' (Type/Name)')"/></a>
|
|
|
- <ul>
|
|
|
- <xsl:for-each select="section">
|
|
|
- <xsl:call-template name="sectionTemplate"/>
|
|
|
- </xsl:for-each>
|
|
|
- </ul>
|
|
|
+ <a href="{$linkurl}"><xsl:value-of select="concat(type,' - type, name: ',name)"/></a>
|
|
|
</li>
|
|
|
</xsl:template>
|
|
|
|
