Policies with mandatory configuration values?

[zyzzyxdonta]

Should we allow policies that have a mandatory config parameter (i.e. without a default vaue)?

[poikilotherm]

Who would provide the parameter? Having an option to make policy writers give a parameter might be nice. I'm unsure if it would be a good idea to have an end-user (depositor/curator) give a parameter. At the moment I think policies shipped to folks should be self-contained and well defined.

[zyzzyxdonta]

I think this issue isn't phrased well because we haven't decided which words to use yet (see #11). What I meant was:

Someone creates a configurable policy using a placeholder (which we might call an sc:Parameter like here) with a default value (like here). Someone else (a user) re-uses this policy by referencing it in their config file. The user can decide to use the default value or override it with their own desired value.

Should we allow policy writers to define policies that force users to pick a value?

[zyzzyxdonta]

From today's discussion: Yes, policies without default values should be made possible.

Everything else is written down in #22