Supporting Web-based Scholarly Annotation
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Supporting Web-based Scholarly Annotation

on

  • 390 views

Presented at W3C Workshop on Annotation, 2 April 2014

Presented at W3C Workshop on Annotation, 2 April 2014

Statistics

Views

Total Views
390
Views on SlideShare
360
Embed Views
30

Actions

Likes
2
Downloads
1
Comments
0

1 Embed 30

https://twitter.com 30

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Supporting Web-based Scholarly Annotation Presentation Transcript

  • 1. Supporting Web-based Scholarly Annotation Anna Gerber
  • 2. Scholarly Annotation Requirements • Citable – Including private annotations • Precise • Annotation of segments / regions • Annotate extensible list of media types e.g. text, HTML, PDF, raster images, vector images, video, audio, 3D objects, research data e.g. protein crystallography models, repositories • Annotate within dynamic web applications e.g. maps
  • 3. Scholarly Annotation Requirements • Migrate / display annotations across – Multiple copies of identical resource – Multiple representations of equivalent resource • E.g. TEI/XML rendered using different stylesheets to HTML/PDF, 3D objects at different resolutions – Multiple versions of resource • E.g. versions of web page over time, versions within a scholarly edition, pre-print vs publisher copy of journal article • Copyright concerns
  • 4. Semantic scholarly annotations • Annotate non-information resources e.g. identifiers for concepts, database entities • "Stand-off" annotation to retain integrity of original resource • Multiple targets – Particularly expressing relationship between targets • Multiple bodies/ structure content – E.g. multiple semantic tags + commentary
  • 5. Implementation concerns • Our systems use Annotea, OA – Shared generic backend, custom clients • Discoverability, sharability between systems requires agreed protocols & APIs not just shared model • Flexibility of model needs to be balanced with ease of implementation