Annotation tool as core or pluggable functionality

[jbhoward-dublin]

The production releases of Mirador 2.X have provided an annotation tool with limited functionality and flexibility. Use cases have bene identified that call for expanded general functionality on the one hand, and very specific context- or project-specific functionality on the other. To list a few examples:

• authenticated annos
• annos created for public, private or group consumption/interaction
• tagging or classification requirements calling upon specific controlled vocabularies
• annotation of dynamic media objects such as audio or video

And so on. Should not annotation therefore be based fundamentally on a plugin framework? Possibly with a generic annotation tool, but capabilities for selecting more specialised tools that might serve educational purposes, specific projects, etc.? In the current design sketches an Annotation tool is presented as a core component rather than a plugin. hence raising the issue as a general question.

[christopher-johnson]

This relates to #19. Annotations entail authentication and authorization. The question of NPOV, provenance and the policy issues raised on the mailing list are central to an annotation implementation. Separating a core authentication API from annotation implementation components (i.e. plugins...) would be a requirement in any use case.