> For the complete documentation index, see [llms.txt](https://open.janastu.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open.janastu.org/projects/renarration/sweet.md).

# SWeeT

[SWeeTs and SWeeT Web](http://www.janastu.org/home/index.html#/sweet). The Social Web of today is characterized by participatory content creation and syndicated communication. Wikipedia is an example of participatory content creation, while the micro-blogging exchange using the Twitter service are examples of communication. A parallel and equally significant development of the web has been the steady effort on infusing the data on the web with semantics and the resultant growth of the Semantic Web. Various initiatives to leverage the social web have been applied to collectively build the Social Semantic Web. A SWeeT is an elementary unit of structured information that can be used by people to pronounce a semantic relationship of information on the web. Like "tweets" are used by people to express an idea or an interest on twitter(@/#), SWeeTs can be used to express a relationship. SWeeTs differ from Twitter tweets in two important ways: First, they are decentralized; the SWeeTs may be curated in arbitrary stores. Second, SWeeTs are structured so as to reflect a semantic relationship between web elements governed by an ontology. SWeeT (short for "semantic web tweet") work began around 2012 and initiated a community managed decentralised content accessibility process that became the basis for Renarration and then interconnecting archives work (<http://milli.link>). SWeeTs contributed to Wed Annotation standard WG discussions, and then replaced by W3C Web Annotations.

{% embed url="<http://wiki.janastu.org/wiki/Sweet_Web>" %}

{% tabs %}
{% tab title="Docs" %}

* <http://swtr.in/>
* <https://thestore.swtr.in/>
* <http://dash.swtr.us/>
  {% endtab %}
  {% endtabs %}


---

# 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://open.janastu.org/projects/renarration/sweet.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.