Digitization of scholarly publishing is about the same age as the Web
In 1995, libraries didn't want to build additional wings to house stacks of journals
JSTOR was created to solve a real estate problem
Earliest online journals were HTML
The appeal and efficiency of desktop publishing was too good to pass up
Right now, we have a lot of faith in the “page”
Citations are usually page-based
Even when given the choice of HTML, many researchers choose PDF
Benefit from the crossroads
Reap the benefits of pages, or CSS "fragmentainers"
Don't be contained by the frozen page of desktop publishing
Publications can be living documents, with typography, supported by the full stack of web technology
Serious electronic literature (for scholarship, detailed controversy and detailed collaboration) must support bidirectional and profuse links, which cannot be embedded; and must offer facilities for easily tracking re-use on a principled basis among versions and quotations.
Theodor H. Nelson, "Xanalogical Structure, Needed Now More than Ever:
Parallel Documents, Deep Links to Content,
Deep Versioning and Deep Re-Use"
Hypertext gives us a lot of the same information as print and a protocol for sharing it
Hypermedia gives us an interactive layer
Hyperdata gives us networked, living information
How Are We Doing?
We are still looking for the best way to convey "deeply intertwingled" information
Traditional links rot. Is there a better way to convey relationships?
Can information from one resource change or affect something in another resource?
Is it possible to add information to a resource without touching it?
Hierachical information is pretty comfortable
Associative information has come a long way
Convey metadata and relational information without tweaking the content
Convey data in a manner that does not require hopping in and out of systems
An Associative Index?
Read more about the extensible TEI and XML code base.
Not too long ago (and often still) author information and titles were just meaningless blobs of text
The author provides a Jupyter Notebook to host the code on the Quant Platform for a standardized execution environment
Lessons from the Past
In 2012 Wiley launched a site called Functional Chemistry
Instead of publishing raster images of compounds that originated in ChemDraw, we extracted InChIKeys from the ChemDraw files
This enabled our machines to identifying existing and novel compounds
Users able to view the compound labels, images, and schemes as well as the spectra associated with compounds
Live data, annotations allow authors and users to constantly update a publication
If an author updates the data in GitHub, the graphic representation of it will change in the article
What, then is the "publication of record"?
Can this be managed by versioning?
Use Case: Cochrane Library Systematic Reviews
Cochrane Reviews are systematic reviews of primary research in human health care and health policy, and are internationally recognised as the highest standard in evidence-based health care. They may either investigate the effects of interventions for prevention, treatment, and rehabilitation, or alternatively may assess the accuracy of a diagnostic test for a given condition in a specific patient group and setting. A unique feature of Cochrane Reviews is that they are living documents in that they are updated with new evidence that emerges. They were conceived as electronic publications from the outset, and designed to take advantage of features unique to electronic publishing.
There is still work to do
We have come a long way in exploiting the value of data on the web and data about the web