diff --git a/xep-0277.xml b/xep-0277.xml index 699605154..bceb5bc5a 100644 --- a/xep-0277.xml +++ b/xep-0277.xml @@ -6,8 +6,8 @@
- Microblogging over XMPP - This specification defines a method for microblogging over XMPP. + Publishing + This specification defines a method for publishing over XMPP. &LEGALNOTICE; 0277 Deferred @@ -109,15 +109,14 @@
-

Microblogging is an increasingly popular technology for lightweight interaction over the Internet. It differs from traditional blogging in that:

+

Diginal publishing (or microblogging) is an increasingly popular practice for lightweight interaction over the Internet. It fundamentally differs from traditional journal pubblishing in that:

-

These characteristics map well to instant messaging systems such as those built using Jabber/XMPP technologies (e.g., permissions can be based on existing presence subscriptions as reflected in the XMPP roster or "buddy list"). Furthermore, the push nature of XMPP (especially as formalized in the &xep0163; profile of &xep0060;) overcomes the problems of polling for updates via HTTP, which has caused scaling issues in existing microblogging services. Therefore this specification defines a method for microblogging over XMPP, building on the existing method for transporting Atom syndication data &rfc4287; over XMPP as described in &atomsub;. These XMPP-based methods are complementary to HTTP-based methods, and can provide an XMPP interface to existing microblogging services (which may also be accessible via HTTP, Short Message Service (SMS), and other messaging transports).

+

These characteristics map well to instant messaging systems such as those built using Jabber/XMPP technologies (e.g., permissions can be based on existing presence subscriptions as reflected in the XMPP roster or "buddy list"). Furthermore, the push nature of XMPP (especially as formalized in the &xep0163; profile of &xep0060;) overcomes the problems of polling for updates via HTTP, which has caused scaling issues in existing publishing services. Therefore this specification defines a method for publishing over XMPP, building on the existing method for transporting Atom syndication data &rfc4287; over XMPP as described in &atomsub;. These XMPP-based methods are complementary to HTTP-based methods, and can provide an XMPP interface to existing publishing services (which may also be accessible via Gemini, HTTP, Short Message Service (SMS), and other messaging transports).

 @@ -138,7 +137,7 @@ xmpp:romeo@montague.lit?;node=urn%3Axmpp%3Amicroblog%3A0

Romeo can publish a post via any interface provided by his service, such as a website, the Atom Publishing Protocol (see &rfc5023;), SMS, an IM bot, or XMPP pubsub. Here we assume that the post is provided via XMPP pubsub.

-

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 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 a "link" element with the textual source code of the XHTML content. For XHTML publishing, see &xep0060;.

Note: Publishing via HTTP, AtomPub, SMS, or IM bot is simpler for the client (e.g., because the client does not need to generate an Item ID).

We have described two pubsub nodes types here: the one is for the microblog itself and the other one is for comments to posts.

Usage specific requires the special parameters to these nodes to be specified. This section describes recommendation for them.

-

Here are recommendations for a microblogging node (usually located at PEP and named by the "urn:xmpp:microblog:0" namespace) configuration:

+

Here are recommendations for a publishing node (usually located at PEP and named by the "urn:xmpp:microblog:0" namespace) configuration:

  1. The "pubsub#notify_retract" MUST be set to true to provide clients the ability to track if some items were retracted and reflect such changes in the UI correctly.
  2. The "pubsub#max_items" SHOULD be increased from the default value to some reasonable value.
    3. @@ -495,7 +494,7 @@ xmpp:romeo@montague.lit?;node=urn%3Axmpp%3Amicroblog%3A0 -

    Depending on service policies and the value of the "pubsub#include_body" node configuration option, microblogging notifications SHOULD include a message "body" element for backwards-compatibility with Jabber clients that are not pubsub-capable. It is RECOMMENDED for the XML character value of the "body" element to be the same as that of the "atom:title" child of the "atom:entry".

    +

    Depending on service policies and the value of the "pubsub#include_body" node configuration option, publishing notifications SHOULD include a message "body" element for backwards-compatibility with Jabber clients that are not pubsub-capable. It is RECOMMENDED for the XML character value of the "body" element to be the same as that of the "atom:title" child of the "atom:entry".