In using the events module more and more, I have begun to understand that the events core is more of a time / location / recurrence hub, than an all encompassing time & resource scheduler.
For instance, we recently migrated all event eCommerce aspects away from the CORE events display mechanism.
Basically the event is a brochure to a time-constrained Store Product Offering.
This was done for many reasons, there needs to be an on-going log of purchases, refunds, quantity, fraud checking, ticket or asset shipping, digital asset delivery (like a program for speaking engagements).
All of these 'specific business applications' might be better suited for extensions to a common EventID.
Even "Locations" need more in-depth development, and re-use than should be a part of the 'events' module.
What is clearly needed in my opinion is the ability to have recurrance patterns dictate a collection of events, that can then be modified. This collection of events will more suit all the various business models of what 'needs' to be done to an event.
Frankly, I think Alan is doing a great job with this module, and should continue to focus not on the business applications but the core feature-set of 'entity managment' of which an entity has a time, date, description, location etc....
iCal for syndication, and Event Time/Date/Filtering/Viewing are all requirements regardless of the business extension.
Keep up the great work Alan!
To Your Success