• To: xml-dev@l...
• Subject: Unrestricted order and unrestricted cardinality?
• From: Marielou <marielou_h@y...>
• Date: Wed, 21 Jun 2006 10:31:09 +0100 (BST)
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Iek806i8sS/al0o2y7q9p+FGrgAj7utmgnsltjoy5cLuITQQQJ49AGVcrArzps2rFZ8CN98gYI8cnghTG1qoOahG/PTSxtQhDWfxTiOijM3DhOIcIDO1isGqFV9HE/Y3YIHbXak5f2kKt5QX+Xosim4xiVkh66VNnIRq2JsAux8= ;
• In-reply-to: <NBBBIBMKFOFCNEBAKDPLOELNKPAA.xml-dev-list@b...>

Is it possible to have unrestricted order and
unrestricted cardinality? the options <all> <sequence>
and <choice> dont make this easy. I have implemented
my schema using <sequence> to enable me to achieve the
unrestricted cardinality I require but this is not
what I need as each XML I am validating has a
different order. Is there some pattern i can use in my
schema to combine elements to achieve unrestricted
order and unrestricted cardinality? is there some
(probably )complex design which could get round the
limitations? please help! even if the answer is a
known "no this is most definately not possible with
the restrictions on XML schema please confirm!"








	
	
		
___________________________________________________________ 
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine 
http://uk.docs.yahoo.com/nowyoucan.html

• Follow-Ups:
  • Re: Unrestricted order and unrestricted cardinality?
    • From: Frank Richards <frank@t...>

• References:
  • RE: minOccurs maxOccurs doesnt seem to be working correctly in my schema
    • From: "Paul Spencer" <xml-dev-list@b...>

• Prev by Date: Re: SVG interoperability
• Next by Date: Re: Unrestricted order and unrestricted cardinality?
• Previous by thread: RE: minOccurs maxOccurs doesnt seem to be working correctly in my schema
• Next by thread: Re: Unrestricted order and unrestricted cardinality?
• Index(es):
  • Date
  • Thread