There is little interoperability among scholarly repositories on the web. Most focus on access via the user interface. Some provide APIs for machine access, in which case each repository platform has its own. But how about some uniform approaches to allow machines to interact with repositories? Wouldn't that make it a lot easier/cheaper to implement cross-repository services? Understanding that resources are scarce, the "Signposting the Scholarly Web" effort provides really simple approaches that repositories can implement to improve machine accessibility of their content. It is not a formal standardization effort. It's an accumulation of ideas from people that have spent a lot of time thinking about the web and scholarly communication on the web, working on specifications to improve on the interoperability status quo. The specifications provided under the Signposting umbrella are fully aligned with hypermedia (REST, HATEOAS) lines of thinking regarding web interoperability.
Key Achievements
The "Signposting the Scholarly Web" effort started in 2016 by recommending patterns, based on typed links, that repositories can implement to make it easier for machines to navigate the scholarly objects they host. By 2024, the effort provides several specifications that repositories can implement to make their objects more accessible to machines. FAIR Signposting Profile provides a guideline with concrete recipes for the implementation of the Signposting patterns. FAIRiCat specifies the content, syntax, and discoverability of the FAIR Interoperability Catalogue, a static file that repositories can publish to advertise the interoperability affordances they provide, including repository-level and object-level affordances. Signmap shows how Sitemaps, that have been the dominant approach to help web crawlers find a server's resources since 2009, can be augmented to include Signposting links as a means to create a self-contained inventory of scholarly objects managed by a repository.