A program event fires through the framework's event handling. This event causes the creation of a gesture object. One possible refinement of the prototype is to define a mapping between the "hardware" program event and the intent "gesture".
UML Class Diagram
Don't use this
Ontology Driven Development
A hardware event, i.e. "Key_Down keyDownArrow" is translated into a Gesture which is an object that represents the actual intent of the user, i.e. "Move the focus to the Selection Grid". The Gesture (given a context?) maps nicely into a list of program features that need to be invoked.
Refine the "Linked Query". The results of a query (SPARQL, SQL, etc.) has a "current row" concept. The current row has associated relatable "keys". The results of a query is derived from the query's restrictions with variables carried as parameters whose in-values are expected to keys from the current row of some other query in a "current" state. Classic master-child type of pattern only this extends into a network of queries all linked via the key values of the their respective current row and the in-values of their parameters.
Current Row Out-Values
Network of Atomic Query Objects