[osis-core] mixed type error on lgCT

[Todd Tillinghast]

Patrick,

The following should make <lg> not mixed="false" while still allowing
other elements derived from <milestonable> to be remain mixed="true"

<!-- don't say anything about mixed so other complex types can derive by
extension and declare either mixed="false" or mixed="true".

<xs:complexType name="milestoneable">
	<xs:attribute name="sID" type="xs:string" use="optional"/>
	<xs:attribute name="eID" type="xs:string" use="optional"/>
</xs:complexType>


<!-- mixed="false" added -->
<xs:complexType name="lgCT" mixed="false"> 
	<xs:complexContent>
	<xs:extension base="milestoneable">
	....

Other complex types are already stated to be mixed="true" (should be
completely verified).

Todd

Todd
> -----Original Message-----
> From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> Sent: Friday, October 03, 2003 5:44 AM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] mixed type error on lgCT
> 
> Guys,
> 
> Actually the answer is yes, it will cause a problem. Try resetting
> milestoneable to remove mixed="yes" and see the results on the files
> Todd forwarded. Suddenly, text becomes unavailable in verses.
> 
> Todd: Unless you have another answer, looks like lgCT is going to have
> to become mixed. Can say in the docs to only use elements but it is
the
> only one where we will allow mixed content where we really don't want
it
> anyway.
> 
> Still working on the namespace issue. Real bundle of silliness every
for
> the W3C.
> 
> Hope everyone is at the start of a great day!
> 
> Patrick
> 
> Patrick Durusau wrote:
> > Guys,
> >
> > Looks like the mixed type error relating to lgCT was caused by the
> > following:
> >
> > <xs:complexType name="milestoneable" mixed="true">
> >
> >         <xs:attribute name="sID" type="xs:string" use="optional"/>
> >
> >         <xs:attribute name="eID" type="xs:string" use="optional"/>
> >
> >     </xs:complexType>
> >
> > By removing mixed="true" the error is resolved. Started to say it
does
> > not make any sense with milestoneable, err, except that some of the
> > complexTypes derived from milestoneable have mixed content. Hmmm...
> >
> > This includes abbrCT, chapterCT, closerCT, divCT, foreignCT, headCT,
> > lCT, qCT, saluteCT, segCT, signedCT, speechCT, and verseCT.
> >
> > Thoughts on whether this will cause a problem or not?
> >
> > Hope everyone is having a great day!
> >
> > Patrick
> >
> 
> 
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> Patrick.Durusau@sbl-site.org
> Chair, V1 - Text Processing: Office and Publishing Systems Interface
> Co-Editor, ISO 13250, Topic Maps -- Reference Model
> 
> Topic Maps: Human, not artificial, intelligence at work!
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core