1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-22 01:02:17 -05:00

Changed XEP-0277 0.2.1 version.

This commit is contained in:
Vanaryon 2011-04-24 16:03:08 +02:00 committed by stpeter
parent a0acb7c6c9
commit ec0e814de0

View File

@ -82,7 +82,7 @@ xmpp:romeo@montague.lit?;node=urn%3Axmpp%3Amicroblog%3A0
</section2> </section2>
<section2 topic='Publishing a Post' anchor='publish'> <section2 topic='Publishing a Post' anchor='publish'>
<p>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.</p> <p>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.</p>
<p>The post content itself can be either text ("content" element "type" attribute with "text" value) or XHTML ("content" element "type" attribute with "xhtml" value). If Romeo publishes XHTML content, the post's "body" element MUST be plain text encoded. For XHTML publishing, see &xep0060;.</p> <p>The post content itself can be either text ("content" element "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;.</p>
<p>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).</p> <p>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).</p>
<example caption="Publishing a post"><![CDATA[ <example caption="Publishing a post"><![CDATA[
<iq from='romeo@montague.lit/pda' <iq from='romeo@montague.lit/pda'