<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//TaxonX//DTD Taxonomic Treatment Publishing DTD v0 20100105//EN" "../../nlm/tax-treatment-NS0.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:tp="http://www.plazi.org/taxpub" article-type="research-article" dtd-version="3.0" xml:lang="en">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">109</journal-id>
      <journal-id journal-id-type="index">urn:lsid:arphahub.com:pub:3dc5f44e-8666-58db-bc76-a455210e8891</journal-id>
      <journal-title-group>
        <journal-title xml:lang="en">JUCS - Journal of Universal Computer Science</journal-title>
        <abbrev-journal-title xml:lang="en">jucs</abbrev-journal-title>
      </journal-title-group>
      <issn pub-type="ppub">0948-695X</issn>
      <issn pub-type="epub">0948-6968</issn>
      <publisher>
        <publisher-name>Journal of Universal Computer Science</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.3217/jucs-013-07-0924</article-id>
      <article-id pub-id-type="publisher-id">28817</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Article</subject>
        </subj-group>
        <subj-group subj-group-type="scientific_subject">
          <subject>D.2.12 - Interoperability</subject>
          <subject>D.2.1 - Requirements/Specifications</subject>
          <subject>H.4.2 - Types of Systems</subject>
          <subject>M.0 - KNOWLEDGE ACQUISITION</subject>
          <subject>M.4 - KNOWLEDGE MODELING</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>A First Step Mapping IMS Learning Design and Moodle</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Burgos</surname>
            <given-names>Daniel</given-names>
          </name>
          <email xlink:type="simple">daniel.burgos@ou.nl</email>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Tattersall</surname>
            <given-names>Colin</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Dougiamas</surname>
            <given-names>Martin</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Vogten</surname>
            <given-names>Hubert</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Koper</surname>
            <given-names>Rob</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">Open University of the Netherlands, , Netherlands</addr-line>
        <institution>Open University of the Netherlands</institution>
        <country>Netherlands</country>
      </aff>
      <aff id="A2">
        <label>2</label>
        <addr-line content-type="verbatim">Open University of the Netherlands, Heerlen, Netherlands</addr-line>
        <institution>Open University of the Netherlands</institution>
        <addr-line content-type="city">Heerlen</addr-line>
        <country>Netherlands</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Daniel Burgos (<email xlink:type="simple">daniel.burgos@ou.nl</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: </p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2007</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>28</day>
        <month>07</month>
        <year>2007</year>
      </pub-date>
      <volume>13</volume>
      <issue>7</issue>
      <fpage>924</fpage>
      <lpage>931</lpage>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/1DBEF7B2-3647-552A-9BFA-F4861D2820F5">1DBEF7B2-3647-552A-9BFA-F4861D2820F5</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/6999868">6999868</uri>
      <permissions>
        <copyright-statement>Daniel Burgos, Colin Tattersall, Martin Dougiamas, Hubert Vogten, Rob Koper</copyright-statement>
        <license license-type="creative-commons-attribution" xlink:href="" xlink:type="simple">
          <license-p>This article is freely available under the J.UCS Open Content License.</license-p>
        </license>
      </permissions>
      <abstract>
        <label>Abstract</label>
        <p>Mapping the specification IMS Learning Design and the Course Management System Moodle is a logical step forward on interoperability between eLearning systems and specifications in order to increase the best acceptance of the specifications into the widespread world of the eLearning systems and to ensure the standardization of the outputs from the systems to be used in others. IMS Learning Design and Moodle look for a common understanding focused on the integration of information packages modelled by each part in the other. The final goal aims at Moodle playing an IMS LD package. A second step will map a Moodle course to be used in any IMS LD complaint tool. The Unit of Learning in IMS LD and the course in Moodle become the perfect couple where to find several elements that should match each other. This paper shows how to make this understanding, mapping related elements in both to get a list of pairs easy to translate from one to another, and to define also a list of requirements for this protocol.</p>
      </abstract>
    </article-meta>
  </front>
</article>
