I thought the acs_events table was there to store all things that denote
temporal data? Then there's the timespans and the time_intervals tables whose
sense I still haven't grasped...
To me a decent service-contract on the database level is to define a table
that holds the minimum amount of fields to be shown. Packages would insert
into this "central" table via a triggr (-> that's the service-contract).
Unfortunately I'm not (yet!) familiar with the acs-service-contract package -
how can it be of use in "temporal-data"?
Don, you seem to have a rough idea what has to be done? Can you post your
thoughts?
