title: Validating quartz's JobDataMap
body: <p>Jobs in Quartz are passed a JobDataMap for the arguments that it may need. Obviously this introduces potential for the data to be the wrong types, wrong data values etc. </p>
  
  <p>Some ideas:</p>
  
  <ul>
  <li><p>Each job has a <code>Config</code> class that behaves a bit like a ViewModel in that it has all the data the job needs contained in it. This could then use DataAnnotations for the validation.</p></li>
  <li><p>Extending the IJob class and creating custom objects which internally validates (seems like too much work)</p></li>
  </ul>
  
  <p>How is validation normally asserted on JobDataMaps?</p>