ESciDoc Services Annotator

IN PROGRESS

Introduction

The motivation for defining an Annotator service comes from MPI MB Demonstrator proposal. Main aim is to be able to enrich publications with references or short descriptions/comments on resources about which a publication (or another form of work) is about. There is an assumption that most of these are external resources and are not managed by MPDL services. However, this does not have to be the case.

Some premisses:

• The solution shall not be heavy for PubMan and shall be applicable to other applications as well
• The solution shall be flexible enough and allow for extensions of various types of resources
• The solution shall be scalable
• ...

Related concepts/implementations

• see RDF Metadata store
• see Open Annotation Collaboration (OAC)

Data Model

• For basic data model and definitions please check OAC
• The ontology developed for the Annotator service at MPDl is shown below

• A Resource is a class of all individuals representing content which is managed in the system. In the depicted ontology, Annotation(SylvaAnnotation) and Body are considered as a Resource.
• An Annotation is a subclass of managed Resource class.
• A Body is the class of individuals with which particular Annotation is associated.
• A Target is the class of individuals about which the Body in general is.
• A SylvaAnnotation is a subclass of an Annotation referencing all Sylva database resources (see MPDL Demonstrator Marine Microbiology for more details)
• A Service is a class of individual services that may be associated with particular types of annotations, e.g. Sylva browser

In particular cases Body does not exists. In this case Annotation individual does not have a Target i.e. it is assumed that it is a e.g. "textual" annotation.

Example

Max Planck Digital Library

Publication Management

Owner Architect Client