MITH-OAC Phase II Project Update for January 2012

Currently, the OAC development team at Maryland Institute for Technology in the Humanities (MITH) is busy working the ins and outs of their development milestones. As of now, there is source code available on Github (https://github.com/umd-mith/OACVideoAnnotator) containing the skeleton functionality and design for a Streaming Video Annotation tool. The tool itself has no streaming video, but it does contain functionality to draw shapes on an SVG (RaphaelJS) canvas and sync them with a timer.

Instead of just pointing to the source code and letting those interested and with technical knowledge pick it apart, let’s take a moment to explain our methodology and why we chose the path we took. Our annotation tool is written in Javascript with our own in-house framework, MITHGrid. MITHGrid is developed by James Smith as a faceted browsing system for client-side data that mimics the Simile and Infusion projects. MITHGrid widgets are written using Applications, which house any number of DataStores, or triple-stores, on the client-side. DataStores are broken up by Views, which act like filters for the data inside a particular DataStore (e.g. “Give me all the blue squares in DataStore A”). Presentations then take the filtered data from the Views and render them on the screen. This results in a chain-effect where all data added, updated, or removed within a DataStore flows directly into the Presentation rendering that data, thus allowing for quick updates.

Javascript is being used because of its flexibility with other browsers and its familiarity with the staff. The triple-store data format is being used along with MITHGrid as it conforms well to the principles of the Semantic Web and Linked Data which are recognized and mirrored in the OAC beta specifications. In the specifications, Annotations are defined as connecting two elements together: a Target and a Body (i.e. A Body points to a Target). To expand any annotation (e.g. Add creators, constraints to the annotation Target or Body, etc.) additional triple-store items are added to the main annotation object. This is reflected in a MITHGrid DataStore. Each item has key-value pairs that act as the other two-thirds of the triple store system. An annotation in a MITHGrid DataStore would be represented as:


Annotation [

id -> 1,
    hasTarget -> targetId
hasBody   -> bodyId
hasCreator
    -> creatorId

]

Going between RDF and the MITHGrid JSON data is therefore simplified, since both use the same principles of triples and data storage. Currently, we are working on approaching this problem using NodeJS to ingest external metadata and convert it into JSON. More on that topic will be in a future blog post.

The progress with the OAC Streaming Video Annotation Client is under an ECL2 License and available via Github to clone and pick apart (https://github.com/umd-mith/OACVideoAnnotator).

OAC Phase II Project beginning Development at the Maryland Institute for Technology in the Humanities

We at the Maryland Institute for Technology in the Humanities (MITH), University of Maryland College Park, have recently begun development on a streaming annotation video client for the Alexander Street Press catalog of educational films. The service intends to use the Open Annotation Collaboration (OAC) beta specifications in order to store annotations on the client that coordinate with specific frames of streaming video. The schedule for development plans to have a full working prototype early next year (2012). As of now, we have managed to code a working prototype of the shape drawing canvas, which will be used to select regions of video for annotation.

In addition, I am attending the Interedition Bootcamp conference in Wuerzburg, Germany. Interedition is a focus group of domain experts to discuss and implement interoperable tools for the Digital Humanities. MITH was invited to attend the conference in order to offer our experience and learn from others on interoperability in online annotation tools. So far, the OAC beta specifications have gained a lot of interest among the participants due to their support for working across platforms. To learn more about Interedition and what is happening at the Wuerzburg conference, check their wiki or follow my posts at the MITH blog (Note: my posts are buried along with all the other interesting stuff going on at MITH!).

Grant Dickie
Web Programmer and Programmer for OAC Phase II
Maryland Institute for Technology in the Humanities
University of Maryland, College Park

jdickie at umd dot edu

Brown University Library using Open Annotation in an annotation framework for Fedora

The Brown University Library is developing an annotation framework for Fedora using the Open Annotation data model. This project will implement the Open Annotation data model for an instance of Fedora Commons digital repository software package. The investigators at Brown hope to interlink annotations built with their annotation experiment directly to the TEI-encoded texts contained in their Fedora repository in order to explore how annotations can be targeted to words, structural elements, and semantic data encoded within textual documents. This work will feature items from the Brown University Women’s Writers Project http://www.wwp.brown.edu and other collections of digitized texts used by the students and faculty at Brown. This annotation demonstration experiment is being funded in part by the Open Annotation Collaboration Phase II project. For more information on Brown’s annotation demonstration experiment please contact:

Andrew Ashton
Director
Center for Digital Scholarship
Brown University, Box A
Providence, R.I. 02912
email: andrew_ashton@brown.edu
phone: (401)863-2669

or visit http://library.brown.edu/cds

Open Annotation Beta Data Model Released!

The Collaboration is pleased to announce the release of the Beta version of the Open Annotation data model. This version follows on from discussions at the Workshop held in March in Chicago, and should inform the experiments currently starting up after the awards made from the RFP. Note that there are no changes from the Alpha3 model, only additions and clarifications. In particular:
• There is a discussion document (http://www.openannotation.org/spec/beta/precedence.html) about how to deal with multiple constraints. Any feedback on this issue is greatly appreciated.
• There is clarification of the machine readable body annotation pattern in the Guidelines document.
• There is a document listing the different types of constraint known, and a wiki area set up for community development of further constraints.
• There is a document that will list different types (classes) of annotation, and the same sort of wiki area for development.
Further examples will be available over the next few weeks, and we welcome any submissions of new example documents.

Follow

Get every new post delivered to your Inbox.