commit: 7a9ffcc1158524b3fd98daa65c4166e65974802b
parent 9c5435a1eafc7f244fd53084e7bc460d66d05b2d
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date: Wed, 25 Nov 2020 05:01:53 +0100
ap-compat: Migrate to SHTML
Diffstat:
2 files changed, 25 insertions(+), 29 deletions(-)
diff --git a/ap-compat.md b/ap-compat.md
@@ -1,29 +0,0 @@
----
-title: "LitePub for ActivityPub Implementors"
----
-
-## JSON-LD context
-
-LitePub implementations are not required to use `@context` properties on their messages.
-A conformant ActivityPub implementation is required to process these messages with an
-injected `@context` of `"https://www.w3.org/ns/activitystreams"` as described in the
-[ActivityStreams 2.0 Core Specification][AS2-CORE-JSON-LD].
-
- [AS2-CORE-JSON-LD]: https://www.w3.org/TR/activitystreams-core/#jsonld
-
-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
-[LitePub JSON-LD Context][litepub-jsonld] as their `@context`. 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 `@context` as it defines the full
-LitePub Core Vocabulary in a way that is useful to JSON-LD processors.
-
- [litepub-jsonld]: https://litepub.social/litepub/context.jsonld
-
-
-## Signatures
-
-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.
diff --git a/ap-compat.shtml b/ap-compat.shtml
@@ -0,0 +1,25 @@
+<!--#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" -->
