We use TEI

D. Menota schemas (DTD, RELAX NG, and entity list)

D.1 Menota schemas
D.2 Referring to the Menota schema
D.3 Changes from TEI P4 to TEI P5 which concerns Menota

Version: 2.2 (25 June 2010). Links updated 12 July 2016.

D.1 Menota schemas

In version 1 of the Menota handbook, a number of changes were made to the TEI Guidelines version P4. These changes were implemented in two extension files, “menota.extention.ent” and “menota.extension.dtd”, both written in the DTD syntax for SGML. The Document Type Definition (DTD) was thereafter generated using TEI Pizza Chef. For details on this procedure, see the page Document Type Definition in v. 1.1 of the handbook. Those who wish to encode texts according to TEI P4 should refer to this version of the handbook.

In version 2 of the Menota handbook, additions and changes have been made with reference to TEI Guidelines version P5. In TEI P5, the extensions are in XML in a schema called ODD (One Document Does it all). A new tool ROMA has been used to generate TEI schemas. ROMA allows users to choose between several outputs: a DTD, a RELAX NG schema (which, in spite of its name, can be a stricter schema than a DTD), or a W3C schema.

On the basis of the ODD file for Menota and the entity list, a Document Type Definition (DTD) and a RELAX NG schema for Menota have been generated with the help of ROMA. Those who prefer a W3C schema or a RELAX NG schema with compact syntax, may produce that themselves, using the Menota ODD file and the tool ROMA.

D.1.1 Current versions of Menota schemas

This is a list of all current Menota schemas. Earlier versions of these files have been moved down to the archive below and given a version number. Remember that many browsers will try to open XML files in a new window; in order to download these files, try using right-click (Windows) or alt-click (Mac).

(1) One Document Does it all (ODD)

The ODD file is an XML file which specifies all changes to the TEI Guidelines P5.

Menota 2.0 ODD file for TEI P5 (9 February 2012) – XML file

(2) Entity list

The entity list specifies recommended entities. This is not an obligatory part of a schema, but it is an important part of Menota encoding since a large number of characters have to be encoded by entities. It is essential that characters in the Private Use Area of the Unicode Standard are encoded with entities. The entity list is an ordinary text file.

Menota Entities (13 May 2016) – text file

(3) Document Type Definition (DTD)

The DTD is one of several schemas that are allowed in TEI P5.

Menota DTD (25 June 2010) – text file

Some browsers will attach the extension .xml to this file when downloaded. Just change the extension back to .dtd

(4) RELAX NG schema

The version given here has been generated on the basis of the same ODD file and entity file as the DTD above. Using a RELAX NG schema, data values can be validated to a higher extent than what is possible with a DTD. This applies both to attribute and content values. For example, the attributes “notBefore” and “notAfter” in the element <origDate> have to contain a valid date value if the RELAX NG schema is used. The RELAX NG schema also supports name spaces, which is useful if one wants to mix schemas as we do in Menota.

Menota RELAX NG (7 February 2012) – XML file

D.1.2 Archive of older versions of Menota schemas

(1) One Document Does it all (ODD)

Menota ODD #1 (20 December 2004) – XML file
Menota ODD #2 (7 June 2005) – XML file
Menota ODD #3 (21 June 2005) – XML file
Menota ODD #4 (6 December 2005) – XML file
Menota ODD #5 (6 February 2006) – XML file
Menota ODD #6 (5 December 2006) – XML file
Menota ODD #7 (13 November 2007) – XML file
Menota ODD #8 (6 Februar 2008) – XML file
Menota ODD #9 (6 May 2008) – XML file
Menota ODD #10 (25 June 2010) – XML file

(2) Entity list

Menota Entities #1 (19 November 2004) – text file
Menota Entities #2 (14 December 2005) – text file
Menota Entities #3 (6 December 2006) – text file
Menota Entities #4 (18 December 2006) – text file
Menota Entities #5 (10 January 2007) – text file
Menota Entities #6 (20 June 2009) – text file

(3) Document Type Definition (DTD)

Menota DTD #1 (16 December 2004) – text file
Menota DTD #2 (7 June 2005) – text file
Menota DTD #3 (21 June 2005) – text file
Menota DTD #4 (6 December 2005) – text file
Menota DTD #5 (6 February 2006) – text file
Menota DTD #6 (5 December 2006) – text file
Menota DTD #7 (27 December 2007) – text file
Menota DTD #8 (25 January 2008) – text file
Menota DTD #9 (6 May 2008) – text file

(4) RELAX NG schema

Menota RELAX NG #1 (17 December 2004) – XML file
Menota RELAX NG #3 (21 June 2005) – XML file
Menota RELAX NG #8 (12 February 2008) – XML file
Menota RELAX NG #9 (16 May 2008) – XML file
Menota RELAX NG #10 (18 May 2009) – XML file
Menota RELAX NG #11 (26 June 2010) – XML file


D.2 Referring to the Menota schema

Please note that the links below have been updated after Menota was moved from Oslo to Bergen in the beginning of 2016.

As of TEI P5, a Menotic XML file should refer to two external files, one schema and one list of entities. The beginning of the file using the Menota P5 DTD schema should look like this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE TEI SYSTEM "http://www.menota.org/menotaP5.dtd"
[
<!ENTITY % Menota_entities SYSTEM
'http://www.menota.org/menota-entities.txt'   >
%Menota_entities;]
>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
....
</TEI>

The beginning of the file using the Menota P5 RELAX NG schema might look like this if your are using Oxygen:

<?xml version="1.0" encoding="UTF-8"?>
<?oxygen RNGSchema="http://www.menota.org/menotaP5.rng" type="xml" ?>
<!DOCTYPE TEI 
[
<!ENTITY % Menota_entities SYSTEM
'http://www.menota.org/menota-entities.txt'   >
%Menota_entities;]>

<TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:me="http://www.menota.org/ns/1.0">
....
</TEI>

If you are using another editor, the reference to the schema will be different.

Please note the namespace references in the TEI root element when the RELAX NG schema is used. The default namespace is the TEI namespace, while the additional Menota namespace is listed next as the "xmlns:me" (where “me” is an abbreviation for “Menota”). When the DTD schema is used, the Menota namespace can not the declared. When using the RELAX NG schema, all elements and attributes belonging to the Menota namespace have to use the prefix “me:” in order to be valid, e.g.:

<interpretation me:lemmatized="completely" me:morphAnalyzed="completely">
  <p>The complete text has been lemmatised and morphologically analysed 
  according to the rules specified in ch. 8 of the Menota Handbook, v. 2.0.</p>
</interpretation >
                ...
<w>
  <me:facs>karin<am>&us;</am></me:facs>
  <me:dipl>karin<ex>us</ex></me:dipl>
  <me:norm>Karinus</me:norm>
</w>
                			

See the chapter on the Menota header for downloadable samples of valid Menotic XML headers.


D.3 Changes from TEI P4 to TEI P5 which concerns Menota

TEI P5 1.0 was published on 2 November 2007.

D.3.1 Changes in the XML Document Prologue

The Document Type Declaration had to be changed from the P4 to the P5 version of the Menota schema because an entity list is now a separate document, and not included in the DTD as it was previously. The reason for making the entities into a sperate file is primarily that only DTDs can include entities (RELAX NG as well most other schema languages can not), and secondarily because it is easier to maintain. Section D2 above shows how documents using the Menota encoding should refer to the entities.

D.3.2 Encoding changes from P4 to P5 which concerns Menota

The root element has been changed from <TEI.2> to <TEI>

The attribute @resp in the element <sic> has been removed in P5. It was probably an error to have it declared in P4. Example 22 in chapter 7 of the Menota Handbook used it. This example has been removed from version 2.0 of the handbook.

The content model of <change> in <revisionDesc> is changed, the element <respStmt> is removed, and the content is more narrative. An example may look like this:

<change>On <date value="2006-02-02">2 February 2006</date>, 
<name>Tone Merete Bruvik</name> edited the file according to the 
TEI P5 0.3.1 published on 30 January 2006. </change> 

The attribute @langKey in <textLang> has been changed into @mainLang:

<textLang langKey="oic">Old Icelandic</textLang> 

->

<textLang mainLang="oic">Old Icelandic</textLang></change> 

Encoding of hands has been changed, <handList> has been replaced with <handNotes> and <hand> has been replaced with <handNote>

The element <date> has an attribute @when, which in P4 was called @value

D.3.3 Changes from MASTER to P5

Menota v. 1.1 contained the recommendations from the MASTER project. TEI P5 includes the recommendations from the TEI Manuscript Description Taskforce. Although the recommendations from TEI Manuscript Description Task are based on the MASTER recommendations, there are some differences which Menota has to handle.

The element <msHeading> is not in P5, and the content of this element has to be encoded otherwise.

The elementet <msWriting> has been removed, <handDesc>should be used in its place.

Encoding in MASTER:

<msWriting hands="1">
  <handDesc script="Hybrida" scope="major">
    <p>The main hand (Hand 1) writes <locus>ff. 1r-9r and
    16r-118v</locus> in a practised Gothic hybrid.</p>
  </handDesc>
</msWriting>

Encoding in P5:

<handDesc hands="1">
  <handNote script="Hybrida" scope="major">
    <p>The main hand (Hand 1) writes ff. 1r-9r and
    16r-118v in a practised Gothic hybrid.</p>
  </handNote>
</handDesc>

In MASTER, the attribute @role in the <name> element was used to encode the role of the person whose name was stated in the element. This attribute is not available in P5, so the Menota project had to decide how this should be encoded. This example is given in '10.6 The history of the manuscript':

<provenance>
  <p>According to AM 435 a 4to, ff. 54v-56v, the manuscript had been owned by 
  <name type="person" role="owner">Sr. Þórður Jónsson á 
  <name type="place">Staðastað</name> (1672-1720)</name>, who had got it
  from <name type="person" role="owner">Jón Hákonarson að 
  <name type="place">Vatnshorni</name> ...

We suggest that @subtype is used to replace @role in this case.

It is not longer valid to have both <p> and <msDesc> as child elements of <sourceDesc>. A <p> element should be moved into a <summary> element like this (sample from AM 233 a fol):

<sourceDesc>
  <msDesc>
	  <msIdentifier>
 	    <country key="DK">Denmark</country>
 	    <settlement>Copenhagen</settlement>
 	    <repository>The Arnamagn&aelig;an Institute</repository>
 	    <idno>AM 233 a fol</idno>
    </msIdentifier>
   <msContents>
     <summary>The source is an anonymous translation from Latin 
     into Old Norse made in the second half of the 12th century, 
     possibly in Norway. The original is lost and the text is only 
     preserved in younger Icelandic manuscripts, including the two 
     fragments in AM 233 a fol, fol. 28rA (the first column on the 
     recto page) and 28vB (the second column on the verso page). 
     This fragment is dated to 1350-1360 in "Ordbog over det 
     norrøne prosasprog" (Index volume).</summary>
...

<msDescription> has been changed into <msDesc>

The value of the attribute @defective in <msItem> should have the values 'true' or 'false', not 'yes' or 'no'. This applies to other Boolean attributes as well.

The attributes @technique, @figurative and @illustrative in the <decoNote> element have been removed in P5.

The attribute @reg in the <country> has been removed. Use for instance @key.


First published 8 February 2006. Last updated 12 July 2016. Webmaster.