Suppor&ngWebbasedScholarly Annota&on)

12
Suppor&ng Webbased Scholarly Annota&on Anna Gerber

Transcript of Suppor&ngWebbasedScholarly Annota&on)

Page 1: Suppor&ngWebbasedScholarly Annota&on)

Suppor&ng  Web-­‐based  Scholarly  Annota&on    

Anna  Gerber  

Page 2: Suppor&ngWebbasedScholarly Annota&on)
Page 3: Suppor&ngWebbasedScholarly Annota&on)
Page 4: Suppor&ngWebbasedScholarly Annota&on)
Page 5: Suppor&ngWebbasedScholarly Annota&on)
Page 6: Suppor&ngWebbasedScholarly Annota&on)
Page 7: Suppor&ngWebbasedScholarly Annota&on)
Page 8: Suppor&ngWebbasedScholarly Annota&on)
Page 9: Suppor&ngWebbasedScholarly Annota&on)

Scholarly  Annota0on  Requirements  

•  Citable  –  Including  private  annota0ons  

•  Precise  •  Annota0on  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  applica0ons  e.g.  maps  

Page 10: Suppor&ngWebbasedScholarly Annota&on)

Scholarly  Annota0on  Requirements  

•  Migrate  /  display  annota0ons  across  – Mul0ple  copies  of  iden0cal  resource  – Mul0ple  representa0ons  of  equivalent  resource  •  E.g.  TEI/XML  rendered  using  different  stylesheets  to  HTML/PDF,  3D  objects  at  different  resolu0ons  

– Mul0ple  versions  of  resource  •  E.g.  versions  of  web  page  over  0me,  versions  within  a  scholarly  edi0on,  pre-­‐print  vs  publisher  copy  of  journal  ar0cle  

•  Copyright  concerns  

Page 11: Suppor&ngWebbasedScholarly Annota&on)

Seman0c  scholarly  annota0ons  

•  Annotate  non-­‐informa0on  resources  e.g.  iden0fiers  for  concepts,  database  en00es  

•  "Stand-­‐off"  annota0on  to  retain  integrity  of  original  resource  

•  Mul0ple  targets  – Par0cularly  expressing  rela0onship  between  targets  

•  Mul0ple  bodies/  structure  content  – E.g.  mul0ple  seman0c  tags  +  commentary  

Page 12: Suppor&ngWebbasedScholarly Annota&on)

Implementa0on  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  implementa0on