W3C home > Mailing lists > Public > xmlschema-dev@w3.org > February 2003

RE: ambiguous content model - yea or nay?

From: Dare Obasanjo <dareo@microsoft.com>
Date: Tue, 11 Feb 2003 12:54:00 -0800
Message-ID: <B885BEDCB3664E4AB1C72F1D85CB29F804B54C8C@RED-MSG-10.redmond.corp.microsoft.com>
To: "Paul Kiel" <paul@hr-xml.org>, <xmlschema-dev@w3.org>
I can't think of any W3C XML Schema constraints this complex type
violates. Why do you think it is invalid? 

Computers are unreliable, but humans are even more unreliable. Any
system which depends on human reliability is unreliable.

This posting is provided "AS IS" with no warranties, and confers no



	From: Paul Kiel [mailto:paul@hr-xml.org] 
	Sent: Tuesday, February 11, 2003 11:37 AM
	To: xmlschema-dev@w3.org

	Question all,
	I am getting an "ambiguous content model" error when validating
an instance conforming to this schema:
	     <xsd:sequence maxOccurs="unbounded">
	          <xsd:element name="AvailabilityStartDate"
type="AnyDateTimeNkType" minOccurs="0"/>
	          <xsd:element name="AvailabilityEndDate"
type="AnyDateTimeNkType" minOccurs="0"/>
	I only get the error from 1 of 5 parsers/tools that I validate
against.  And only when validating the instance (the schema validates
just fine with that same tool).
	The more I looked at it, the more it seemed "technically" true
but I wasn't sure.
	(For the record, this is a bug fix - I plan on eliminating the
maxOccurs attribute on the sequence.)
	Paul Kiel
	HR-XML Consortium
Received on Tuesday, 11 February 2003 15:54:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:15:09 UTC