Well formedness errors in datatypes.xsd and other comments

• From: Arnold, Curt <Curt.Arnold@hyprotech.com>
• Date: Mon, 27 Sep 1999 14:32:39 -0600
• To: "'www-xml-schema-comments@w3.org'" <www-xml-schema-comments@w3.org>
• Message-ID: <61DAD58E8F4ED211AC8400A0C9B468731AAFA3@THOR>

1. Missing closing tags on

  <element name='minAbsoluteValue' type='real'>  
  <element name='maxAbsoluteValue' type='real'>

Should be:

  <element name='minAbsoluteValue' type='real'/>  
  <element name='maxAbsoluteValue' type='real'/>


2. Second enumeration start tag instead of a enumeration close

  <datatype name='encodings'>
     <basetype name='NMTOKEN'/>
	 <enumeration>
	    <literal>hex</literal>
		<literal>base64</literal>
     <!--   should be /enumeration  -->
     <enumeration>
  </datatype>


3. <period> element used in datatypes.xsd not defined in datatypes.dtd

4. In the content model of the datatype element in datatypes.xsd,
minInclusive and maxInclusive appear twice, once as part of the archetype
reference of "minBound" or "maxBound" and once explicitly (at least by my
interpretation of the schema).  The explicit references should be removed.

  <element name='datatype'>
     <archetype order='all'>
        <element ref='basetype'/>
        <element archRef='maxBound' minOccurs='0'/>
        <element archRef='minBound' minOccurs='0'/>
        <element ref='minAbsoluteValue' minOccurs='0'/>
        <element ref='maxAbsoluteValue' minOccurs='0'/>
        <element ref='maxInclusive' minOccurs='0'/>
        <element ref='minInclusive' minOccurs='0'/>
        ...

Received on Monday, 27 September 1999 16:34:49 UTC