Resources, controllers and models mapping

I have a person table and an event table (and many mores, but these
two illustrates my problem)
A person has many events
I have a person resource and an event resource to manage the records
in the tables
Now I also want to manage person and events together in a more user
friendly way.

My problem is now how to design the application ?
1. Should I have one person controller and one person resource, one
event controller and on event resource and add a set of actions to the
person and/or event controller to handle the user friendly management
of persons and events ?

2. Should I have specifc controllers and resources representing
different representations of persons and events, as the user friendly
integrated representation and the table representation, each (if
possible) limited to the seven basic actions (index, show, new , edit
etc) ? E.g a person controller, an event controller and a person-event
controller and corresponding resources!

3. Should I have a specific person-event controller with many specific
actions, in addition to the person and event controller, that uses the
same person and event resources?

Thanks for the advice
However, I think all proposed solutions (1-3) will work, (I use
solution 3 for the moment, that also works), but which one is the most
RESTful one and which is to prefer from a software design point of
view

Hans Marmolin wrote:

Thanks for the advice
However, I think all proposed solutions (1-3) will work, (I use
solution 3 for the moment, that also works), but which one is the most
RESTful one and which is to prefer from a software design point of
view

If I understand the original post correctly, the simplest and most
easily RESTful solution would be 2.

Best,

Marnen, I agree
but as I had not found any guides recommending 2, I hesitated to take
that approach
I am just now implementing it supported by your recommendation

Thanks for all help