...
Both the Annotations raise the general questions of modeling Annotation associations. These seem to support the idea of having a general annotation association, with a type and possibly an additional information entity defined per type.
Object versus Resource modeling
We will likely need to make a clear distinction between an CollectionObject (which is a conceptual reference to some real-world entity), and the representations, surrogates and documentation thereof. Images are representations, and so are resources. 3-D and other surrogates are resources for the same reasons. Papers and books that discuss or cite an object and are managed in the system as documents are similarly resources (linked to the object(s) as annotations). However, in some workflows, images collected with specimens may be first class objects as well, which raises some modeling complexity. When is something an Object and when is it a resource? Is it a question of function? Does this get too complex for folks to manage? Can things change function over time?
...