<?xml version="1.0" encoding="UTF-8"?>
<?oxygen RNGSchema="file:/C:/Documents%20and%20Settings/Kevin/My%20Documents/tei_odds_ext.rng" type="xml"?>
<schemaSpec xmlns="http://www.tei-c.org/ns/1.0" ident="mets_spec" start="mets" ns="http://www.loc.gov/METS/" xmlns:sch="http://www.ascc.net/xml/schematron">
   
     <!--Abbreviated mocku-up of how METS could be reimaged as module based system based upon the
            TEI ODD format.  This markup also incluedes some examples of how the     -->
    

    <moduleRef key="header"/>
    <moduleRef key="descriptiveMetadata"/>
    <moduleRef key="administrativeMetadata"/>
    <moduleRef key="fileSection"/>
    <moduleRef key="sMap"/>
    <moduleRef key="sLink"/>
    <moduleRef key="behaviorSection"/>
    
    <elementSpec ident="structMap" module="sMap">
        <content>
            <sch:rule context="structMap" xmlns="http://www.ascc.net/xml/schematron">
            <sch:assert test="not(ancestor::par)">Par elements are not allowed in the structure map for this profile</sch:assert> 
        </sch:rule>
        <sch:rule context="structMap/@TYPE='physical' | structMap/@TYPE='mixed'">
            <sch:assert test="not(ancestor::par|ancestor::seq)">&lt;structMap&gt;'s with a TYPE of "mixed" or "physical" cannot have &lt;par&gt; or &lt;seq&gt; elements.</sch:assert>
        </sch:rule>
        </content>
            
    </elementSpec>
    
    <elementSpec ident="fptr" module="sMap"
        relationship="isPartOf">
        <!-- omitted -->
        <attList>
            <attDef ident="FILEID" usage="opt" references="file">
                <!-- omitted -->
            </attDef>
            </attList>
            </elementSpec>
                
</schemaSpec>
