I read the article at: http://www.devmaster.net/articles/oo-game-design/, but I'm having a hard time wrapping my brain around some of the ideas presented. I'm not sure how some of the concepts presented would be implimented in C++. In figure 6-A it gave the following psudo-code for a main loop:

while(appActive)
{
  foreach Entity E in LogicalSpace
  {
    E.DoActions();
    E.Form.Mesh.RenderSelf();
  }
}

The problem is not all Entities have Form. Only the Renderable objects would have Form. In another part of the article it mentioned querying Entities to see if they have certain Actions, States, etc., I'm not sure how this would effectively be done. Would this be done with something like boost::ptr_map mapping search queries to pointers to the Actions and States being queried for? How might the Actions and States be implimented, so that other entities can make use of them? Can somebody maybe give a small source-code example explaining how Entities, Actions, Forms, States, and Spaces could all work together in a game? It seems complex, and I'm not sure how they would all interact with eachother.

You can take ations list from Enity to the external list.
e.g. you have a EntityManager which keep 2 lists of actions
active - actions for execute in this game loop
possible - actions waiting for use
In such situation entity register its actions as possible and if it's needed move its to the active list, and in the game loop you do: foreach active.

Such system is similar to listeners systems.

PS. RenderSelf also can be action ;)