IMO, the above entity 'types' are mutually exclusive and collectively exhaustive categories (any concept or thing you can think of fits neatly into only one, and they should never be conflated or confused with each other). I think it is important to keep their identities very clear and very separate.
I.e., Task =/= Message and I think a system that recognises that is usually better (but, each to their own).
Task
Event
Message
Contact
Reference
Item
Location
Blueprint
Log
IMO, the above entity 'types' are mutually exclusive and collectively exhaustive categories (any concept or thing you can think of fits neatly into only one, and they should never be conflated or confused with each other). I think it is important to keep their identities very clear and very separate.
I.e., Task =/= Message and I think a system that recognises that is usually better (but, each to their own).