Markus,
Other opinions on that? Is this a requirement that we should include
in the policy requirements document, and more specifically is this a
requirement for rule languages? I.e. is it required that the rule
language allows
(a) specification/indication of service parameters,
Service parameters( system load, N/W condition and possibly others) can be
predefined. And service( third party) authors can be asked to mention those
parameters( in which they are interested) in Service description language(
OMML). Then OPES engine can call the services either( local or remote) and pass
those specific parameters( mentioned in service description data). Here,
parameters mentioned should be only the predefined ones. In this way, we can
pass dynamic parameters. As you said, we can have local modules for setting
these system parameters.
Apart from this, if there is any user specific( static) data such as user-id or
group-id, those can be mentioned in rule file. I think, this is the right place
for putting such data, because rule author is the source of such information.
It might also be possible to separate service parameter specification
from the rule language and move it into the remote execution
environment (e.g. why should the rule author care about specific
I agree with you. Rule Author need not care about specific service parameters.
service parameters)? It would than be the responsibility of the remote
execution environment to determine and set the correct parameter
values (for example based on meta-information on the service and
actual values of environment variables or so...). Any views on that?
-Markus
-Rajnish