Some MSTL types can be further constrained:
* The base of mstl:urlType should be xsd:anyURI, not xsd:string
* The lang attribute should conform to the pattern [a-z]{3}
* The script attribute should conform to the pattern [A-Z][a-z]{3}
* The content model of extensionType was to be <xsd:any
processContents="lax" maxOccurs="unbounded"/>
Corporate entities appear in far too many places with different types:
1. mods/name with type="corporate"
2. mads/authority/name with type="corporate"
3. mods/originInfo/publisher
4. mods/location/physicalLocation
5. mods/name/affiliation
6. mads/affiliation/organization
7. mstl:recordInfo/recordContentSource
Have I missed any? These could all be subsumed by a common type based
on the present type of <name> in MODS and MADS.
Another possibility for type unification is
mods/physicalDescription/extent and mods/relatedItem/part/extent.
--Andy
