Re: [tei-council] XSD seems better, but still broken (was "Re: fun with min and max")

29 Nov 2016

      The anyElement-xenodata problem is a worrying one. I can reproduce it using
your ODD, but this doesn't occur in the Exemplars, where, given the exact
same RNG definition, Trang produces a slightly different (and correct)
xsd:group. Spooky.

The busted one:

    xs:choice

The correct one:

    xs:choice

This from:

  <define name="anyElement-xenoData">
      <element>
         <anyName>
            <except>
               <nsName ns="http://www.tei-c.org/ns/1.0"/>
               <name ns="http://www.tei-c.org/ns/Examples">egXML</name>
            </except>
         </anyName>
         <zeroOrMore>
            <attribute>
               <anyName/>
            </attribute>
         </zeroOrMore>
         <zeroOrMore>
            <choice>
               <text/>
               <ref name="anyElement-xenoData"/>
            </choice>
         </zeroOrMore>
      </element>
   </define>

On Tue, Nov 29, 2016 at 12:32 AM, Syd Bauman 
wrote:
...
I tested XSD output on the same file (using teitoxsd with the
sydb-occurs2 stylesheets), and the result seems correct -- there
were 2 errors:
1) The content of <xenoData> is flagged as ambiguous. This is a
    problem with anyXML, the Stylesheets, or xenoData itself; it has
    nothing to do with the changes in sydb-occurs2, as the exact same
    problem occurs with the dev branch of the stylesheets.
2) The customized content model for <bibl> is flagged as ambiguous;
    which, it turns out, it is.
When I run the same ODD through teitoxsd with the dev stylesheets,
the errors are quite a bit worse: spurious maxOccurs="unbounded" are
inserted in some places, breaking the XSD.
...
...
I think you should also check what DTD and XSD outputs look like.
As I said on the original ticket, we ought not to generate dtd or
xsd which is actually illegal, even if it matches what the ODD
says it should less well than the RNG output.
True enough. IIRC, current DTD and XSD generation produces schemas
which are valid, but match incorrect # of things?
--
tei-council mailing list
tei-council@lists.tei-c.org
http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived

Re: [tei-council] XSD seems better, but still broken (was "Re: fun with min and max")

Hugh Cayless