On Jan 29, 2009, at 1:22 PM, Schiffel, Jeffrey A wrote:
> > Jeff:
> > I suggest that the behaviors among components are better understood if model as
> > hierarchies of commands and constraints.
> What exactly do you mean by a 'command' here? Do you mean a program?
No, I don't. Perhaps I should have written, "request," or "request for service." The request may or may not be accompanied by a parameter. The requestor is blind to how the request is satisfied. The provider is blind to the reason for the request.
Interesting. OK, so what you were saying, above, is that behaviors are better understood if modeled as hierarchies of requests (in the above sense) and constraints. Right? I confess that is not a way of thinking that immediately jumps to my mind, but Im sure one could attempt to describe it in a ontology. One of the issues I can see immediately is how to describe a parameter adequately. Can there be situations where a parameter is left partly unspecified and the servicing of the request fills in missing detail? (As in a query to s database, for example.) Because if so, parameter binding will have to be described in rather painful detail in a logical description.