> For the complete documentation index, see [llms.txt](https://coartraining.gitbook.io/coar-repository-toolkit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coartraining.gitbook.io/coar-repository-toolkit/nextgen-repositories/technologies.md).

# Technologies

## ResourceSync

ResourceSync is a specification based on Sitemaps that can be used by repository managers to provide information that allows third-party systems to remain in sync with the resources in their repository as they evolve, i.e. are created, updated, deleted. Whereas basic Sitemaps allow exposing a repository inventory and crawl-related metadata, ResourceSync adds ways to expose changes only, and to provide expressive synchronization-related metadata as well as typed links for further discovery. ResourceSync can be used for discovery and synchronization of both content and metadata and uses the Sitemaps XML format. <http://www.openarchives.org/rs/toc>

{% embed url="<https://blog.core.ac.uk/2018/03/17/increasing-the-speed-of-harvesting-with-on-demand-resource-dumps/>" %}

Martin Klein presents "ResourceSync: A Modular Framework for Web-Based Resource Synchronization". Slides can be found at [this](http://doi.org/10.5281/zenodo.1433806) link.&#x20;

{% embed url="<https://youtu.be/tfD-C_LiQXw>" %}

## Signposting

Signposting is an approach to inform machine agents about the nature of the resources that are linked from the resource they currently interact with. It uses typed links (in the HTTP Link header, the HTML element, or the <rs:ln> ResourceSync element) to reveal patterns that occur repeatedly in scholarly portals. Signposting can be used to support automatic discovery of a variety of resources that pertain to a scholarly object, including a bibliographic description, a persistent identifier, a license, authors, or various resources that are part of the object. [http://signposting.org](http://signposting.org/)

Martin Klein, Harihar Shankar and Herbert Van de Sompel introduce Signposting [in this article](https://osf.io/preprints/lissa/wzd89/), "a mechanism to show machines how to maneuver repositories' objects and how to interpret their relationships. Signpostingis based on standard and widely adopted web technologies typed links and HTTP link headers." You can also see the [poster](https://osf.io/68uxm/) at the same link as supplemental material.&#x20;

{% embed url="<https://osf.io/preprints/lissa/wzd89/>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://coartraining.gitbook.io/coar-repository-toolkit/nextgen-repositories/technologies.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.