title: nillable and minOccurs XSD element attributes
body: <p>I am going back and forth with setting an element to <code>minOccurs="0"</code> and <code>nillable="true"</code>.</p>
  
  <p>I was reading <a href="http://www.ibm.com/developerworks/webservices/library/ws-tip-null.html" rel="noreferrer">this</a> article and now in my WSDL I'm not sure if using both is worth it. The article gives a good example of representing arrays where you might have null values interspersed throughout, as this can't be done with just <code>minOccurs="0"</code>. Now, the convention I've been going with is that if an element isn't optional it is not nillable. 
  The difference as I understand it, and where my question lies, is that by applying the nillable property to an element, I am saying that you can pass in the XSD equivalent of a NULL value? Otherwise, an element without the nillable property, has to have a value within the restriction placed on it?</p>