moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-23 17:52:15 -05:00
Code Issues Releases Wiki Activity

right scrolling is bad, and other formatting fixes

Browse Source
This commit is contained in:
Peter Saint-Andre 2012-07-16 09:21:51 -06:00
parent 19103f4e66
commit 6472355d20
1 changed files with 22 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
xep-0297.xml
View File

@ -76,7 +76,10 @@
<section2 topic='Overview'>
<p>Let us suppose that a Romeo receives a message from Juliet:</p>
<example caption='Receiving a message'><![CDATA[
<message to='romeo@montague.lit' from='juliet@capulet.lit/orchard' type='chat' id='0202197'>
<message from='juliet@capulet.lit/orchard'
id='0202197'
to='romeo@montague.lit'
type='chat'>
<body>Yet I should kill thee with much cherishing.</body>
<mood xmlns='http://jabber.org/protocol/mood'>
<amorous/>
@ -90,7 +93,11 @@
<body>A most courteous exposition!</body>
<forwarded xmlns='urn:xmpp:forward:0'>
<delay xmlns='urn:xmpp:delay' stamp='2010-07-10T23:08:25Z'/>
<message to='romeo@montague.lit' from='juliet@capulet.lit/orchard' type='chat' id='0202197' xmlns='jabber:client'>
<message from='juliet@capulet.lit/orchard'
id='0202197'
to='romeo@montague.lit'
type='chat'
xmlns='jabber:client'>
<body>Yet I should kill thee with much cherishing.</body>
<mood xmlns='http://jabber.org/protocol/mood'>
<amorous/>
@ -101,32 +108,32 @@
]]></example>
</section2>
<section2 topic='Business rules'>
<ul>
<li>Forwarded stanzas SHOULD include all relevant child elements of the original stanza by default.
<ol>
<li><p>Forwarded stanzas SHOULD include all relevant child elements of the original stanza by default.
However, an implementation MAY omit elements it deems irrelevant and safe to discard. An example
would be omitting &xep0085; elements from &lt;message&gt; stanzas which typically do not make sense
outside the context of a conversation session. However it should be noted that removing such
elements can invalidate any digital signature on a stanza. If preserving a signature is important
in the context this extension is used then child elements SHOULD NOT be removed.</li>
<li>The forwarding entity SHOULD add a &lt;delay/&gt; child to the &lt;forwarded/&gt; element
in the context this extension is used then child elements SHOULD NOT be removed.</p></li>
<li><p>The forwarding entity SHOULD add a &lt;delay/&gt; child to the &lt;forwarded/&gt; element
to indicate to the recipient the date/time that the forwarding entity received the original
stanza. The format of this element is described in &xep0203;.</li>
<li>The namespace of the forwarded stanza MUST be preserved (this is typically 'jabber:client').
stanza. The format of this element is described in &xep0203;.</p></li>
<li><p>The namespace of the forwarded stanza MUST be preserved (this is typically 'jabber:client').
If no 'xmlns' is set for the stanza then as per XML namespacing rules it would inherit the
'urn:xmpp:forward:0' namespace, which is wrong.</li>
<li>When this extension is employed simply for a user to forward a given message to a contact, the
'urn:xmpp:forward:0' namespace, which is wrong.</p></li>
<li><p>When this extension is employed simply for a user to forward a given message to a contact, the
outer &lt;message/&gt; SHOULD contain a body (even if empty) and a receiving client should pay
particular attention to ensure it renders both the sender's text and the forwarded message
unambiguously.</li>
<li>When a forwarded stanza forms part of an encapsulating protocol, the &lt;forwarded/&gt; element
unambiguously.</p></li>
<li><p>When a forwarded stanza forms part of an encapsulating protocol, the &lt;forwarded/&gt; element
SHOULD be a child of a tag of that protocol, and SHOULD NOT be included as a direct child of the
transmitted stanza.</li>
</ul>
transmitted stanza.</p></li>
</ol>
</section2>
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>Forwarding stanzas can reveal information about the original sender, including possible presence leaks as well as the stanza payloads themselves. Any extensions using this format must therefore consider the implications of this.</p>
<p>Forwarding can either be used as-is, or in the context of another specification, with different security considerations:</p>
<p>Forwarding can either be used as-is, or in the context of another specification, with different security considerations as described below.</p>
<section2 topic='As-is' anchor='as-is-sc'>
<p>Receipt of a forwarded stanza from a third-party does not guarantee that the original stanza was actually received, or that the content has not been modified, by the forwarder. Integrity of the original stanza can only be determined through digital signing mechanisms such as described in &xep0285; and &xep0290;.</p>
<p>Considering the above an end-user client should take special care in its rendering of forwarded stanzas, such as forwarded messages, to ensure that the user cannot mistake it for a message received directly from the original sender.</p>
@ -146,13 +153,6 @@
xmlns='urn:xmpp:forward:0'
elementFormDefault='qualified'>
<xs:annotation>
<xs:documentation>
The protocol documented by this schema is defined in
XEP-xxxx: http://www.xmpp.org/extensions/inbox/forwarding.html
</xs:documentation>
</xs:annotation>
<xs:element name='forwarded'>
<xs:complexType>
<xs:sequence xmlns:delay='urn:xmpp:delay'>