litepub.social

ap-compat.shtml (1459B)

<!--#set var="title" value='LitePub for ActivityPub Implementors'--><!--#include file="templates/header.shtml" -->
<h2 id="json-ld-context">JSON-LD context</h2>
<p>
LitePub implementations are not required to use <code>@context</code> properties on their messages.  
A conformant ActivityPub implementation is required to process these messages with an
injected <code>@context</code> of <code>"https://www.w3.org/ns/activitystreams"</code> as described in the
<a href="https://www.w3.org/TR/activitystreams-core/#jsonld">ActivityStreams 2.0 Core Specification</a>
</p>
<p>
However, the LitePub Core Vocabulary differs from the ActivityStreams 2.0 Vocabulary.
It is suggested that LitePub implementations supply a locally hosted version of the
<a href="https://litepub.social/litepub/context.jsonld">LitePub JSON-LD Context</a> as their <code>@context</code>.  It may be useful to
inject a local copy of the LitePub JSON-LD Context instead of the default ActivityStreams
2.0 context when a message is received without a <code>@context</code> as it defines the full
LitePub Core Vocabulary in a way that is useful to JSON-LD processors.
</p>
<h2>Signatures</h2>
<p>
LitePub implementations MUST use HTTP Signatures to verify the authenticity of
messages being delivered to or from peering nodes.  The details surrounding
the way HTTP Signatures are implemented in LitePub are discussed on the Overview
page.
</p>
<!--#include file="templates/footer.shtml" -->