Is a library appropriate?

[eluser]bretticus[/eluser]
Pretty much everything in your list is an entity object scenario. I like this definition of Entity objects..."Entity objects are classes that encapsulate the business model, including rules, data, relationships, and persistence behavior, for items that are used in your business application. For example, entity objects can represent the logical structure of the business, such as product lines, departments, sales, and regions, business documents, such as invoices, change orders, and service requests, physical items, such as warehouses, employees, and equipment." In the MVC pattern, that's really a model. Libraries should be more generic. For example, I see a library being called from a model much more often than the other way around. Because libraries are often "tool-box" class instances (like helper objects.) That's my two cents anyways.

Cheers!