This finally adds the usage checking functionality, the last bit of #87. To check that the submitter of the workflow has use rights to the outputs, we need to know who it is, so we add the submitting party to the Job class. Sending an identifier is obviously not very secure, but this will be replaced by a signature when we add certificates. Then there's the MayUse rule, and the logic for evaluating it.
This finally adds the usage checking functionality, the last bit of #87. To check that the submitter of the workflow has use rights to the outputs, we need to know who it is, so we add the submitting party to the Job class. Sending an identifier is obviously not very secure, but this will be replaced by a signature when we add certificates. Then there's the MayUse rule, and the logic for evaluating it.