The bigger picture …

<?xml version="1.0" encoding="UTF-8"?>
  <?xml-model href="http://www.wwp.northeastern.edu/outreach/seminars/_current/handouts/ODD_exercise/schemas/odd4odds.rnc" type="application/relax-ng-compact-syntax"?>
  <?xml-model href="http://www.wwp.northeastern.edu/outreach/seminars/_current/handouts/ODD_exercise/schemas/odd4odds.isosch" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
  <TEI xml:lang="en">
    <teiHeader>
      <fileDesc>
        <!-- metadata about your ODD file -->
      </fileDesc>
      <revisionDesc>
        <!-- change log is always a good idea -->
      </revisionDesc>
    </teiHeader>
    <text>
      <body>
        <p><!-- description of the schema --></p>
        <!-- more prose documentation -->
        <schemaSpec ident="test" targetLang="en">
          <!-- actual customization stuff -->
        </schemaSpec>
      </body>
    </text>
  </TEI>

Here is a view of the basic layout of your ODD file. Just like in any TEI file, you will have a TEI header, in which you can put the metadata about your ODD. We also recommend that you include a change log in your <teiHeader> so that you can keep track of any revisions you make. This step is important for project documentation!

The <body> of your ODD can contain the element <p>, which you can use to provide a prose description of your schema. The <body> also contains <schemaSpec>, which is where you put all of the schema specifications we’ve discussed so far.