From 5600afd2ad9f8ccd4c500abfd642faf3f1067aad Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= Date: Wed, 12 Oct 2022 18:09:29 +0200 Subject: [PATCH] Fix various XML issues --- inbox/pubsub-social-feed.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/inbox/pubsub-social-feed.xml b/inbox/pubsub-social-feed.xml index 7fc4e6e3..30890877 100644 --- a/inbox/pubsub-social-feed.xml +++ b/inbox/pubsub-social-feed.xml @@ -69,7 +69,7 @@ -

The publication of a Post consist of a valid &rfc4287 entry embeded in a &xep0060; item.

+

The publication of a Post consist of a valid &rfc4287; entry embeded in a &xep0060; item.

The post content itself can be either text (content element without "type" attribute or with "type" attribute with "text" value) or XHTML ("content" element "type" attribute with "xhtml" value). If Romeo publishes XHTML content, his client MUST publish two "content" elements: a text one, and a XHTML one. For XHTML publishing, see &xep0060;.

The "pubsub#deliver_payloads" SHOULD be set to `false`. The social content can be quite large so it is advised to let the clients to manually query the content if it is not already cached. - +

This profile is defined by the PubSub type `urn:xmpp:microblog:0` as defined in &xep0277; and MUST be created and configured under the PEP `urn:xmpp:microblog:0` node.

@@ -331,7 +331,7 @@
  • The "pubsub#access_model" SHOULD be set to `presence` by default to allow the other presence JIDs to receive the newly published elements without an explicit subscription (using the +notify feature of &xep0163;).
  • - +

    This profile is defined by the PubSub type `urn:xmpp:gallery:0` and can be hosted on any PubSub service.

    @@ -341,7 +341,7 @@ ]]> - +
    @@ -366,4 +366,4 @@

    - \ No newline at end of file +