All - Element limitation - XML Schema

[Istvan Loerincz]

Hi !

"The all element provides an XML representation that describes an
unordered set of element types."

But for minOccurs, and maxOccurs I can only use "0" or "1". How can I
achieve that I can have more than 1 or 0 elements of the element types
inside the all element ?

..I recognized this problem with .NET Framework 1.1 , XML Schema
Validation, but I though before that in minOccurs and maxOccurs allow
also more than "1".

Best regards,
Istvan

*** Sent via Developersdex http://www.developersdex.com ***

[John Saunders]

"Istvan Loerincz" <no****@devdex.comwrote in message
news:u2*************@TK2MSFTNGP04.phx.gbl...

Hi !

"The all element provides an XML representation that describes an
unordered set of element types."

But for minOccurs, and maxOccurs I can only use "0" or "1". How can I
achieve that I can have more than 1 or 0 elements of the element types
inside the all element ?

I recognized this problem with .NET Framework 1.1 , XML Schema
Validation, but I though before that in minOccurs and maxOccurs allow
also more than "1".

xs:all allows the elements to be present in any order. That can cause
ambiguities in parsing, so xs:all is heavily restricted and rarely used.

Can you acheive your goals using xs:sequence instead? That will require that
elements be present in a known order, but it is the most often used
technique.

John

[Istvan Loerincz]

Hello John
I have it now with <xs:seuquence>, but what I make will be a
configuration file and wanted to reach a little bit more flexibility.
But it's ok, now I use then <xs:sequencefurther.
Thank you for your answer.

Best Regards,
Istvan

*** Sent via Developersdex http://www.developersdex.com ***