title: Different XSD for Create vs Update operations
body: <p>consider the following object:</p>
  
  <pre><code>&lt;Person&gt;
    &lt;Name/&gt;
    &lt;FirstName/&gt;
    &lt;Street/&gt;
    &lt;City/&gt;
    &lt;SocialSecurityNr/&gt;
    &lt;Gender/&gt;
    &lt;Hobby/&gt;
  &lt;/Person&gt;
  </code></pre>
  
  <p>Asume I use this object for a Create web service operation. When calling the Create operation, all fields of the Person object must  be provided except 'hobby'
  Now assume that I also have an Update operation. When updating, only socialsecuritynumber is mandatory: I do not need to update each field.</p>
  
  <p>How do you process this in an XSD? Should you define seperate XSDs for the create and update operation?</p>
  
  <p>The reason I want to make this distinction is that I do not want to send unnecessary fields from sender to recipient when it is not needed. Hence, I want to use minOccurs = 0 as much as possible.</p>
  
  <p>It feels like this is a common problem, but can't find any references about it</p>