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

[Patrick Durusau]

Todd,

Todd Tillinghast wrote:

>See the attached counter example to the statements below.
>
Well, at least the IBM Schema Checker (I am not relying upon XMLSpy any 
longer, use it for documentation) does not complain!

Only other problem would be one of overloading <p> depending upon its 
context. Would have to be careful to document that <p> in revisionDesc 
is a special case and not to be confused with the more generic <p>.

I will temporarily insert into OSIS_0105 (and following this week) until 
we can have an online or telephonc confab after Steve gets back in town 
later this week. (Perhaps this coming weekend?)

Keep up the good work!

Patrick

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

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu