> [[There appears to be an order dependency with 
:required.  The 
> :required field must come before any of the fields that 
satisfy the 
> requirement.  This is because the "required" list is emptied 
as fields 
> are processed.  The code could be re-worked to use a 
post-processing 
> phase that would be order independent, but it's probably 
easier just 
> to document the restriction as I've done above.  When the 
":required" 
> specification is parsed, you could also add code to check 
for any 
> already-set fields.]] 
 
We can't guarantee that the :required field will appear 
before anything else (the order of form variables is 
random). Yes, something needs to be done here...