From Ben's email of Nov 9, 2007
I've looked into it further (and got help from Valerie) and we've come up with a slightly different way to incorporate xhml into a VPDText element. Here is where we currently are.
The Schema for VPDText would look as follows:
<xsd:complexType name="VPDTextType" mixed="true">
<xsd:element ref="xhtml:div" minOccurs="0" maxOccurs="unbounded"/>
<xsd:attribute name="id" type="xsd:string"/>
<xsd:attribute name="textType" type="TextType"/>
with the 'xhtml' namespace being declared in the top xsd:schema element and imported by an xsd:import statement. We picked the 'div' element because it is a container and can hold basically any other element one would find in the body of a xhtml page. (also this way putting header elements in VPDText will not validate).
On the schema instance side, a VPDText element would look something like:
<VPDText id="1" textType="narrative">
<div xmlns="http://www.w3.org/1999/xhtml" > <b>bla bla bla</b> bla bla <p>blablabla</p></div>
With the xmlns declaration the schema instance validates and everything bellow 'div' will automatically be considered part of the xhtml namespace. Also, this is nice because the content of VPDText can just be fed to a web browser and displayed. No extra work for the programmer.