title: Why do people accept XSD requiring elements in a particular order?
body: <p>In a recent task at work, I've been building the PHP end (using SimpleXMLElement) of an XML interaction with a .NET app. I've been encountering differences in conceptual thinking with my counterparts in .NET land, specifically because they're just using the XSD/XML libraries in .NET without thinking much about that, whilst I'm finding myself having to bend over backwards because of XSD's limitations. In other words, I couldn't understand why their XML ingestor falls over if I give elements in the 'wrong' order or has ones it doesn't know about, and they don't understand why I care. (Instead my opinion of their development practices is lowered <em>because</em> they don't want to care.)</p>
  
  <p>Is blind acceptance of XSD generation the real culprit here? Why do people accept it being so fussy? </p>