You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So far - we don't have a very clean way of handling different sets of rule types within our reasoning components; and instead have an architecture in which we assume that each actor includes whatever rule tests it needs to in its test method.
It may be worth considering the use of an architecture similar to that of the parse actors which are able to handle specific file types.
For instance I'm thinking that an optimization actor would look something like:
So far - we don't have a very clean way of handling different sets of rule types within our reasoning components; and instead have an architecture in which we assume that each actor includes whatever rule tests it needs to in its
test
method.It may be worth considering the use of an architecture similar to that of the parse actors which are able to handle specific file types.
For instance I'm thinking that an optimization actor would look something like:
Long term it would be useful to also have an RDF configuration file that defines subset inclusion of rule types; for instance
and hence the JSDoc config from above would become
The text was updated successfully, but these errors were encountered: