Update on Annotating
All Knowledge Coalition
Maryann E. Martone
Hypothes.is
UCSD
#AAKCoalition
What is the coalition?
A growing group of publishers, platforms, libraries, standards bodies and technology groups that share a common interest in bringing an interoperable annotation capability across scholarly content for the benefit of scientists, humanists, students, teachers and citizens.
https://hypothes.is/annotating-all-knowledge/
The Vision
Within three years, most scholarly works -- books, articles and other digital media, new and old -- will come with the capability for readers to create, share, and discover annotations from colleagues, authors, friends and experts around the globe.
This technology will be open source, federated, and based on open standards.
Just like the Web.
What is an “interoperable annotation capability”
Annotation should be like email or web pages:
-Multiple servers and clients
-Shared set of features
Why interoperable annotation for scholarship?
Use cases:
“As a user of academic content I want to pull back search results and annotate both the search results and also each of the articles/abstracts in that search, and then export my annotations in a compatible format to work with the packages that I work within
As a publisher, I want authenticated, blinded reviewers to review articles using annotations. I want to pass reviews on along with the article even if I reject the article.
I am reading a scientific article in Pub Med Central and annotating it; my colleague is reading the same article at the publisher's website and annotating it. I get a notification that there are others annotating the same article and I have a means to view them where I am, with the client I am using.”
Members
Over 60 publishers, platforms, standards bodies and technology organizations.
(Join us!)
Members agree that
Key principles
Be open source
Be standards-based
Support key formats (HTML, PDF, EPUB, images, video and data)
Interoperate (the client should work with any compliant service provider)
Support the notion of the “clean page”, letting readers choose which annotations to layer in.
Ambitious timeline
Design & Build - Y1
Interview users, run experiments, gather requirements. Discussions w/ key platforms. Ship standards. Write software.
Deploy - Y2
Make annotation available with articles, books and other media objects.
Market - Y3+
Drive adoption through partnerships and targeted programs.
Timeline of activities to date
Coalition launched with 40 members
Steering Committee formed
Members surveyed for requirements
Working group formed at FORCE11
Coalition kick off meeting in Portland
All materials are available via the Working Group page; new members welcome
Jan
Apr
Feb
Mar
Dec
2015
AAK Coalition Steering Committee
Scott Edmunds - Gigascience
William Gunn - Elsevier
Laurel Haak - ORCID
Brooks Hanson - AGU
Maryann Martone - Hypothes.is
Johanna McEntyre - PubMed Central
Peter Murray-Rust - ContentMine
Nicole Nogoy - Gigascience
Kristen Ratan - Collab. Know. Fdn
Tara Robenalt - PLOS
John Sack - HighWire Press
Rob Sanderson - Stanford Libraries
Doug Schepers - W3C
Tzviya Siegman - Wiley
Jeffrey Spies - Center for Open Science
Simeon Warner - arXiv
Dan Whaley - Hypothes.is
Rebecca Welzenbach - Michigan Pub. John Unsworth - Brandeis University
http://hypothes.is/annotating
Kick off Meeting: FORCE2016 in Portland
> 70 attendees to together to:
Explore technical opportunities and challenges
Explore publisher’s opportunities and challenges
Converge on a definition of interoperability
Determine use cases that are in scope
Identify next steps
Interoperability
Converged on a set of features for interoperable annotation
What is currently missing:
No standard way on the annotation server to tell what annotations are on this page.
Many different clients that support basic functionality
Portability across hosting services
Persistence of user/document identity across different systems
Technical implementation group
Rob Sanderson, Stanford University Libraries
Nick Stenning, Hypothes.is
Will use the W3C Community Group for discussions
Use cases/user stories
Coalition members agreed to freely share user stories and experiences
No overarching use case was envisioned
Activities planned around:
Portable, annotation-based peer review
Journal-hosted journal clubs
Post-publication, cross-platform peer review
Distinguishing between discursive vs authoritative annotations
Plans to increase awareness and understanding of annotations
Plans to increase number of annotations
Outcomes/next steps
Create dedicated web portal (aakcoalition.org) and grow the coalition
Logo
Place to share user stories
Listing of available tools and technology
Refine set of features into a shared definition of interoperability
Establish technical specifications working group
Conduct usability/user analysis of existing tools to understand user experience better
Join us in creating an interoperable future: coalition@hypothes.is