Dynamically load annotation lists from third-party annotation servers

[mikeapp]

Annotations and annotation lists are likely to be stored in locations that are unknown to the manifest provider. There should be a mechanism for discovering and loading relevant annotation lists from annotation servers that are either referenced in the manifest or provided to the viewing software by an end user. For example:

• a professor might configure her Mirador instance to load any available annotations lists from her institutional annotation storage account; she then accesses manifests from multiple repositories and is able to see the annotations she has made on each of them
• a repository might find it cumbersome to update each manifest as OCR text is generated; instead they choose to reference the annotation server once in the manifest, and viewer software queries the server for relevant annotations as it displays each canvas

[azaroth42]

unknown to the manifest provider

is the important aspect here.

[aisaac]

From Vatican: this case can be relevant from the perspective of notifications. (discover stuff about the things published)