Module 8: Customising TEI, ODD, Roma

You can test what you've learned in the tutorial for TEI by Example Module 8: Customising TEI, ODD, Roma by taking the following quiz.

It consists of a number of multiple choice questions, each providing a number of possible answers. Select the answer you think is correct by clicking it. There are 2 possibilities:

The answer is correct: hurrah! a popup box appears telling you why this is the correct answer. You can still check why the other answers are incorrect by clicking them. This will not reduce your score, though.
The answer is incorrect: pity, but you get a second chance! A popup box tells you why the answer is incorrect. You can still choose the other answers until you find the correct one. Mind you, until you clicked the correct answer, each incorrect answer will reduce your score.

ODD stands for...
1. Online text Delivery Device
2. One Document Does it all
3. Online tei Definition Device
4. ODD Defines Documents
From a longevity point of view, which part of your TEI customisation is most important?
1. An ODD file.
2. TEI documentation.
3. A TEI schema.
4. The encoded text.
What's wrong with following <schemaSpec> definition:
```
<schemaSpec ident="TBEcustom" docLang="en" xml:lang="en" prefix="">
 <moduleRef key="core"/>
 <moduleRef key="tei"/>
 <moduleRef key="header"/>
 <moduleRef key="textstructure"/>
 <elementSpec module="header" ident="teiHeader" mode="delete"/>
</schemaSpec>
```
<schemaSpec xmlns="http://www.tei-c.org/ns/1.0" ident="TBEcustom" docLang="en" lang="en" prefix="">
<moduleRef key="core"/>
<moduleRef key="tei"/>
<moduleRef key="header"/>
<moduleRef key="textstructure"/>
<elementSpec module="header" ident="teiHeader" mode="delete"/>
</schemaSpec>
1. Nothing at all. Perfectly right.
2. The <teiHeader> element is not defined in the header module, but in the tei module.
3. You can't delete a <teiHeader>.
4. The transcr module isn't included.
What is the correct definition of an attribute named "layer", added to the att.transcriptional attribute class, wich takes a single number as value?
1. ```
<schemaSpec ident="myTei">
 
 <elementSpec ident="add" module="core" mode="change">
 <attList>
 <attDef ident="layer" mode="add" usage="opt">
 <desc/>
 <datatype minOccurs="1" maxOccurs="1">
 <dataRef key="teidata.numeric"/>
 </datatype>
 </attDef>
 </attList>
 </elementSpec>
 
</schemaSpec>
```
  <schemaSpec xmlns="http://www.tei-c.org/ns/1.0" ident="myTei">
  
  <elementSpec ident="add" module="core" mode="change">
  <attList>
  <attDef ident="layer" mode="add" usage="opt">
  <desc/>
  <datatype minOccurs="1" maxOccurs="1">
  <dataRef key="teidata.numeric"/>
  </datatype>
  </attDef>
  </attList>
  </elementSpec>
  
  </schemaSpec>
2. ```
<schemaSpec ident="myTei">
 
 <classSpec ident="att.transcriptional" type="model" mode="change" module="tei">
 <attList>
 <attDef ident="layer" mode="add" usage="opt">
 <desc/>
 <datatype minOccurs="1" maxOccurs="1">
 <dataRef name="teidata.numeric"/>
 </datatype>
 </attDef>
 </attList>
 </classSpec>
 
</schemaSpec>
```
  <schemaSpec xmlns="http://www.tei-c.org/ns/1.0" ident="myTei">
  
  <classSpec ident="att.transcriptional" type="model" mode="change" module="tei">
  <attList>
  <attDef ident="layer" mode="add" usage="opt">
  <desc/>
  <datatype minOccurs="1" maxOccurs="1">
  <dataRef name="teidata.numeric"/>
  </datatype>
  </attDef>
  </attList>
  </classSpec>
  
  </schemaSpec>
3. ```
<schemaSpec ident="myTei">
 
 <classSpec ident="att.transcriptional" type="atts" mode="change" module="tei">
 <attList>
 <attDef ident="layer" mode="add" usage="opt">
 <desc/>
 <datatype minOccurs="1" maxOccurs="unbounded">
 <dataRef name="teidata.name"/>
 </datatype>
 </attDef>
 </attList>
 </classSpec>
 
</schemaSpec>
```
  <schemaSpec xmlns="http://www.tei-c.org/ns/1.0" ident="myTei">
  
  <classSpec ident="att.transcriptional" type="atts" mode="change" module="tei">
  <attList>
  <attDef ident="layer" mode="add" usage="opt">
  <desc/>
  <datatype minOccurs="1" maxOccurs="unbounded">
  <dataRef name="teidata.name"/>
  </datatype>
  </attDef>
  </attList>
  </classSpec>
  
  </schemaSpec>
4. ```
<schemaSpec ident="myTei">
 
 <classSpec ident="att.transcriptional" type="atts" mode="change" module="tei">
 <attList>
 <attDef ident="layer" mode="add" usage="opt">
 <desc/>
 <datatype minOccurs="1" maxOccurs="1">
 <dataRef name="teidata.numeric"/>
 </datatype>
 </attDef>
 </attList>
 </classSpec>
 
</schemaSpec>
```
  <schemaSpec xmlns="http://www.tei-c.org/ns/1.0" ident="myTei">
  
  <classSpec ident="att.transcriptional" type="atts" mode="change" module="tei">
  <attList>
  <attDef ident="layer" mode="add" usage="opt">
  <desc/>
  <datatype minOccurs="1" maxOccurs="1">
  <dataRef name="teidata.numeric"/>
  </datatype>
  </attDef>
  </attList>
  </classSpec>
  
  </schemaSpec>
What kind of encoding would following customisation allow:
```
<schemaSpec ident="myTei" docLang="en" xml:lang="en">
 <moduleRef key="core"/>
 <moduleRef key="tei"/>
 <moduleRef key="header"/>
 <moduleRef key="textstructure"/>
 <elementSpec ident="review" ns="http://myTEI.namespace" mode="add">
 <desc>provides a brief review of the text in this text division</desc>
 <classes>
 <memberOf key="model.divTopPart"/>
 <memberOf key="att.interpLike"/>
 </classes>
 <content>
 <textNode/>
 </content>
 </elementSpec>
</schemaSpec>
```
<schemaSpec xmlns="http://www.tei-c.org/ns/1.0" ident="myTei" docLang="en" lang="en">
<moduleRef key="core"/>
<moduleRef key="tei"/>
<moduleRef key="header"/>
<moduleRef key="textstructure"/>
<elementSpec ident="review" ns="http://myTEI.namespace" mode="add">
<desc>provides a brief review of the text in this text division</desc>
<classes>
<memberOf key="model.divTopPart"/>
<memberOf key="att.interpLike"/>
</classes>
<content>
<textNode/>
</content>
</elementSpec>
</schemaSpec>
1. ```
<div>
 <head>Adding elements</head>
 <review xmlns="http://myTEI.namespace" resp="TBEcrew">This section 
 discusses the addition of new elements.</review>
 <p>As illustrated above, the TEI core module already provides the 
 <soCalled>name</soCalled> element, whose @type attribute can be used 
 to provide more details about the type of name.</p>
 
</div>
```
  <div xmlns="http://www.tei-c.org/ns/1.0">
  <head>Adding elements</head>
  <review xmlns="http://myTEI.namespace" resp="TBEcrew">This section discusses the addition of new elements.</review>
  <p>As illustrated above, the TEI core module already provides the
  <soCalled>name</soCalled>
  element, whose @type attribute can be used to provide more details about the type of name.</p>
  
  </div>
2. ```
<div>
 <head>Adding elements</head>
 <p>As illustrated above, the TEI core module already provides the 
 <soCalled>name</soCalled> element, whose @type attribute can be used 
 to provide more details about the type of name.</p>
 
 <review xmlns="http://myTEI.namespace" resp="TBEcrew">This section 
 discusses the addition of new elements.</review>
</div>
```
  <div xmlns="http://www.tei-c.org/ns/1.0">
  <head>Adding elements</head>
  <p>As illustrated above, the TEI core module already provides the
  <soCalled>name</soCalled>
  element, whose @type attribute can be used to provide more details about the type of name.</p>
  
  <review xmlns="http://myTEI.namespace" resp="TBEcrew">This section discusses the addition of new elements.</review>
  </div>
3. ```
<div>
 <head>Adding elements</head>
 <review resp="TBEcrew">This section discusses the addition 
 of new elements.</review>
 <p>As illustrated above, the TEI core module already provides the 
 <soCalled>name</soCalled> element, whose @type attribute can be used 
 to provide more details about the type of name.</p>
 
</div>
```
  <div xmlns="http://www.tei-c.org/ns/1.0">
  <head>Adding elements</head>
  <review resp="TBEcrew">This section discusses the addition of new elements.</review>
  <p>As illustrated above, the TEI core module already provides the
  <soCalled>name</soCalled>
  element, whose @type attribute can be used to provide more details about the type of name.</p>
  
  </div>
4. ```
<div>
 <head>Adding elements</head>
 <review xmlns="http://myTEI.namespace" resp="TBEcrew">This section 
 discusses the addition of new elements, like <soCalled>animalName</soCalled>.</review>
 <p>As illustrated above, the TEI core module already provides the 
 <soCalled>name</soCalled> element, whose @type attribute can be used 
 to provide more details about the type of name.</p>
 
</div>
```
  <div xmlns="http://www.tei-c.org/ns/1.0">
  <head>Adding elements</head>
  <review xmlns="http://myTEI.namespace" resp="TBEcrew">This section discusses the addition of new elements, like
  <soCalled>animalName</soCalled>
  .</review>
  <p>As illustrated above, the TEI core module already provides the
  <soCalled>name</soCalled>
  element, whose @type attribute can be used to provide more details about the type of name.</p>
  
  </div>

↑Dashboard

Module 8 Sections

Module 8: Customising TEI, ODD, Roma