RE: ambiguous content model - yea or nay?

Morris Matsa answered your question in more detail. Short version, yes
it is ambiguous and no it isn't an invalid schema fragment. 
 

--
PITHY WORDS OF WISDOM
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
rights.



 
 

  _____  

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

	I suppose it isn't illegal to create a schema that has an
ambiguous content model.  
	 
	My gun, my bullet, my foot, right?
	 
	 

		----- Original Message ----- 
		From: Dare Obasanjo <mailto:dareo@microsoft.com>  
		To: Paul Kiel <mailto:paul@hr-xml.org>  ;
xmlschema-dev@w3.org 
		Sent: Tuesday, February 11, 2003 3:54 PM
		Subject: RE: ambiguous content model - yea or nay?

		I can't think of any W3C XML Schema constraints this
complex type violates. Why do you think it is invalid? 

		--
		PITHY WORDS OF WISDOM
		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 rights.
		
		

		 
		 

  _____  

			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:complexType>
			     <xsd:sequence maxOccurs="unbounded">
			          <xsd:element
name="AvailabilityStartDate" type="AnyDateTimeNkType" minOccurs="0"/>
			          <xsd:element
name="AvailabilityEndDate" type="AnyDateTimeNkType" minOccurs="0"/>
			     </xsd:sequence>
			</xsd:complexType>
			 
			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.)
			 
			Curiously,
			 
			Paul Kiel
			HR-XML Consortium