XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Unexpected Ambiguous Model in XSD Schema

Per Chris Maden, if I make the figcaption in the second sequence optional and remove the sequence with just img then everyone is happy.

 

Cheers,

 

E.

 

--

Eliot Kimber

http://contrext.com

 

 

From: Dan Sullivan <dsullivan@danal.com>
Date: Friday, December 22, 2017 at 11:18 AM
To: Eliot Kimber <ekimber@contrext.com>
Cc: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
Subject: Re: [xml-dev] Unexpected Ambiguous Model in XSD Schema

 

My guess it that given an instance like:

<figure>

<img/>

</figure>

 

the schema can figure out whether it is the type with maxOccurs="unbounded" or the type with minOccurs="1 maxOccurs="1"

 

maybe minOccurs=2 maxOccurs="unbounded" would fix it.

 

Dan

 

On Fri, Dec 22, 2017 at 12:12 PM Eliot Kimber <ekimber@contrext.com> wrote:

I'm working with a schema developed by others. Both Xerces and Saxon 9.7, run from within Oxygen, report ambiguity on this content model:

<xs:element name="figure">
  <xs:complexType>
   <xs:choice>
     <xs:sequence>
       <xs:element ref="figcaption" minOccurs="1" maxOccurs="1"/>
       <xs:choice maxOccurs="unbounded">
         <xs:element ref="img"/>
       </xs:choice>
    </xs:sequence>
   <xs:sequence>
     <xs:choice maxOccurs="unbounded">
       <xs:element ref="img"/>
     </xs:choice>
     <xs:element ref="figcaption" minOccurs="1" maxOccurs="1"/>
  </xs:sequence>
  <xs:sequence>
   <xs:choice maxOccurs="unbounded">
     <xs:element ref="img"/>
   </xs:choice>
  </xs:sequence>
</xs:choice>
</xs:complexType>
</xs:element>

The error is that element "img" is allowed in multiple places.

If I was coding this as a DTD it would be:

<!ELEMENT figure
   ((figcaption, (img)+) |
    ((img)+, figcaption) |
    ((img)+))
>

Which is definitely not ambiguous.

The intent here is to allow this instance:

<root>
  <figure>
    <figcaption></figcaption>
    <img></img>
  </figure>
  <figure>
    <figcaption></figcaption>
    <img></img>
  </figure>
  <figure>
    <img></img>
  </figure>

</root>

But not:

<figure>
  <figcaption/>
  <img/>
  <figcaption/>
</figure>

So my question: Why is the XSD model ambiguous when the choice does not repeat and therefore no particle can occur more than once?

How does one implement this type of content model in XSD?

Thanks,

Eliot
--
Eliot Kimber
http://contrext.com





_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address:
http://www.oasis-open.org/mlmanage/
Or unsubscribe:
xml-dev-unsubscribe@lists.xml.org
subscribe:
xml-dev-subscribe@lists.xml.org
List archive:
http://lists.xml.org/archives/xml-dev/
List Guidelines:
http://www.oasis-open.org/maillists/guidelines.php



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS