Should we support using JSDL elements outside the normal Job-definition context? My inclination is to say "yes" to this,
 but it requires changes through the document to remove the forms of words from all elements that say what element they 
must be a child of; for use in defining a job template, the hierarchy is defined anyway in a top-down way (currently 
it's both top-down and bottom-up)..