eLML uses W3C XML Schema to define all the elements and attributes that are allowed within an eLML e-Learning lesson. To some extent the content of elements and attributes is also defined (e.g. enumerations). eLML consists of three XML "core" Schema's named elml.xsd, biblio_harvard.xsd and metadata_elml.xsd completed with the project-specific validate.xsd (the latter is not in the structure folder but in the config folder of your project - see chapter about the folder structure). Referencing the validate.xsd from a XML document allows for validation of the document against the eLML structure defined in the XML Schema.

The elml.xsd file

The elml.xsd file is the heart of the eLML structure. All the main elements are defined within this XML Schema. Some explanations about this schema can be found in the schema itself when opened in a simple text editor or with a xml editor. In order to be part of the "eLML community" it is absolutely imperative that everyone is using the same XML Schema. XML documents that can be validated against the standard defined in the eLML XML Schema will be able to share XSLT files, scripts and tools developed for eLML. To validate an eLML lesson XML file use the validate.xsd file described below (it includes all the following files).

The biblio_harvard.xsd file

The elml.xsd file includes the biblio_harvard.xsd file. In the latter all the bibliography elements are defined according to the Harvard standard. The creation of this XML Schema was roughly guided by the referencing guide of the Bournemouth University (SCILS 2004). If you want to use another referencing style you will have to create a new XML Schema defining the needed elements. Call this new XML schema "biblio_yourstylename.xsd" and save into the structure folder. To replace the biblio_harvard.xsl file you will need to change the following line in the validate.xsd

<xs:include schemaLocation="biblio_harvard.xsd"/>
with
<xs:include schemaLocation="biblio_yourstylename.xsd"/>.

Note that then you will also need to change the layout files to include the new bibliography elements.

The metadata_elml.xsd file

The elml.xsd file includes the metadata_elml.xsd file. In the latter all the metadata elements are defined. Those metadata elements were adapted from GITTA and do not directly comply with any official metadata standard such as LOM (Learning Object Metadata by IMS). But the eLML XSLT file contains a template to create an IMS Metadata compatible LOM file! This is actually required for the IMS Content Package manifest file. If you want to use another set of metadata (e.g. an official metadata standard) then you will have to take the xsd file of the selected metadata standard and include it in the validate.xsd file replacing the current reference to the metadata_elml.xsd (see below). Save the xsd file of the selected metadata standard into the structure folder or in a subfolder (to be created) of the structure folder. To replace the metadata_elml.xsl file you will need to change the following line in the validate.xsd

<xs:include schemaLocation="metadata_elml.xsd"/>
with
<xs:include schemaLocation="pathIfNeeded/filenameOfYourStandard.xsd"/>.

Note that then you will also need to change the layout files to include the new metadata elements.

The validate.xsd file

Even though it is recommended that all use the unchanged elml.xsd file there are some possibilities to adapt the structure to the needs of your project. Most of these possibilities are united in the validate.xsd file (located in the config folder of your project not in the core structure folder). Like the name says this is a configuration file in which some changes for the needs of your own project can be made. The parameters that can be changed are:

• the levels of the lessons
• the module names (shortcuts)
• the icons used for the layout
• the institutions and departments
• the lesson labels
• the language shortcuts available
• the copyright statement
• etc.

The config.xsd file

The config.xsd file defines the structure of the content of the config.xml file which lies in the _config folder of your project. You can find more information about the config.xml file in the section Description of the core folder structure where the default_parameter.xml file which is used when no project specific config.xml file is available is described. More information about the project specific config.xml file can be found in the section Adapt the transformation process to your needs - the config.xml file where the content of this file is described in detail.