[osis-core] OSIS_0105:10 <revisionDesc> no <p>?

[Todd Tillinghast]

This is a multi-part message in MIME format.

------=_NextPart_000_002D_01C1DE94.933F2680
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

See the attached counter example to the statements below.

The pTest.xsd demonstrates a schema that has <p> operating in two modes
and pText.xml demonstrates with comments of what is not valid in each
location.

(In fact it seems that we are able to have a "top" level xs:element and
an "inline" element in an "xsd" file by virtue of the same pattern.)

If you agree with the pattern.  Then I resubmit my original request for
a simple <p> in <revisionDesc>.

Todd

> -----Original Message-----
> From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
> core@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> Sent: Saturday, April 06, 2002 12:17 PM
> To: osis-core@bibletechnologieswg.org
> Subject: [osis-core] OSIS_0105:10 <revisionDesc> no <p>?
> 
> Todd,
> 
> Todd Tillinghast wrote:
> 
> >Notes on OSIS_0104
> >
> >
> >2) <revisionDesc> can now all kinds of things as decendants via <p>.
> This
> >sort of behavior is not intended and is just the result of <p>s
behavior.
> >Should we NOT use <p> by reference in this case an just create a
simple
> <p>
> >"inline" within <revisionDesc>.
> >
> Can't redefine within the same schema as an element can only have one
> content model in the schema. Works a little differently if you are
> calling from another schema to derive other elements but then you are
> building other elements, not just changing the content model within a
> single schema.
> 
> Suggestion: Should <revisionDesc> for this release only be xs:string?
> 
> Patrick
> 
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> pdurusau@emory.edu
> 
> 


------=_NextPart_000_002D_01C1DE94.933F2680
Content-Type: text/xml;
	name="pTest.xsd"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="pTest.xsd"

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<!-- edited with XML Spy v4.3 U (http://www.xmlspy.com) by Todd =
Tillinghast (private) -->
<xs:schema xmlns:xs=3D"http://www.w3.org/2001/XMLSchema" =
elementFormDefault=3D"qualified" attributeFormDefault=3D"unqualified">
<xs:element name=3D"revisionDesc">
<xs:complexType>
<xs:sequence>
<xs:element name=3D"p" maxOccurs=3D"unbounded">
<xs:simpleType>
<xs:restriction base=3D"xs:string"/>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name=3D"mainElement">
<xs:complexType>
<xs:sequence>
<xs:element ref=3D"revisionDesc"/>
<xs:element ref=3D"div" maxOccurs=3D"unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name=3D"div">
<xs:complexType>
<xs:sequence maxOccurs=3D"unbounded">
<xs:element ref=3D"div" minOccurs=3D"0" maxOccurs=3D"unbounded"/>
<xs:element ref=3D"p" minOccurs=3D"0" maxOccurs=3D"unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name=3D"p">
<xs:complexType mixed=3D"false">
<xs:sequence>
<xs:element ref=3D"milestone" maxOccurs=3D"unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name=3D"milestone" type=3D"xs:date"/>
</xs:schema>

------=_NextPart_000_002D_01C1DE94.933F2680
Content-Type: text/xml;
	name="pTest.xml"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="pTest.xml"

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<mainElement xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xsi:noNamespaceSchemaLocation=3D"D:\OSIS\pTest.xsd">
	<revisionDesc>
		<p>Text	</p>
<!-- Not Valid Here		<p>	<milestone>2001-04-07</milestone></p> -->
	</revisionDesc>
	<div>
		<div>
			<!-- Not valid here <p>Text	</p> -->
			<p>	<milestone>2001-04-07</milestone></p>
		</div>
	</div>
</mainElement>

------=_NextPart_000_002D_01C1DE94.933F2680--