Re: [xml] validator bug in libxml2-2.4.23?

On Tue, Aug 13, 2002 at 01:13:20AM -0400, Nathan Myers wrote:
xm.xml:12: validity error: Element FareSearch content doesn't follow the DTD
Expecting (((SliceItinerarySpec | SliceItineraryInfo)+ | TripSegmentList) ,
PaxSpec* , CustomerSpec? , PricingSpec? , OutputSpec?),
got (SliceItinerarySpec PaxSpec PricingSpec )

...but it seems to me that the "got" sequence quoted (and found in
the document) should satisfy the "Expecting" expression above it.  
Am I mistaken?  Are nested alternatives like "((( A | B )+ | C), D?)"
not supported?  (I find that "((((A | B), ( A | B )*) | C), D?)"
appears to work.)

  Damn, it seems I really need to switch the validation core algorithm to
the new regexp code developped for Schemas in order to get rid of those
nasty corner case bugs in the existing engine. In the meantime rewriting
the DTD to use one of the alternatives might be the simplest.


Daniel Veillard      | Red Hat Network
veillard redhat com  | libxml GNOME XML XSLT toolkit | Rpmfind RPM search engine

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]