moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-27 03:32:16 -05:00
Code Issues Releases Wiki Activity

XEP-0385: Fix typos

Browse Source 
s/exiting/existing/
s/contant/content/
s/availablity/availability/
This commit is contained in:
LNJ 2018-04-06 15:21:29 +02:00
parent d8ed29765f
commit 16623200cb
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
xep-0385.xml
View File

@ -121,7 +121,7 @@ TODO:
<li>Can be improved by server components for taking load of clients</li> <li>Can be improved by server components for taking load of clients</li>
<li>Media sharing should work and enable a good UX in multi-user chats like &xep0045; and &xep0369;</li> <li>Media sharing should work and enable a good UX in multi-user chats like &xep0045; and &xep0369;</li>
<li>Media sharing should work great together with conversation synchronization protocols like &xep0280; and &xep0313;</li> <li>Media sharing should work great together with conversation synchronization protocols like &xep0280; and &xep0313;</li>
<li>Reuse exiting protocols for the actual transport of the data, i.e. &xep0096;, &xep0234; or &xep0363;</li> <li>Reuse existing protocols for the actual transport of the data, i.e. &xep0096;, &xep0234; or &xep0363;</li>
<li>Guarantee file integrity</li> <li>Guarantee file integrity</li>
<li>Enable aggresive caching</li> <li>Enable aggresive caching</li>
<li>Provide users with metadata, e.g. file size, file type or thumbnail, to help them decide whether or not they want to load the media file</li> <li>Provide users with metadata, e.g. file size, file type or thumbnail, to help them decide whether or not they want to load the media file</li>
@ -164,7 +164,7 @@ TODO:
<p>A client MAY retrieve the file from other sources than these mentioned in the sources element. This may be via &xep0234; from the senders' other resources or from a <p>A client MAY retrieve the file from other sources than these mentioned in the sources element. This may be via &xep0234; from the senders' other resources or from a
media caching service located at the local service. The standardization of such cache is out of scope for this document.</p> media caching service located at the local service. The standardization of such cache is out of scope for this document.</p>
<p>Regardless of the transport method used to obtain the file, the received content MUST be verified against one of the hashes. <p>Regardless of the transport method used to obtain the file, the received content MUST be verified against one of the hashes.
If the verification fails, the retrieved contant MUST be discarded and retrieval using a different source can be attempted.</p> If the verification fails, the retrieved content MUST be discarded and retrieval using a different source can be attempted.</p>
</section2> </section2>
</section1> </section1>
<section1 topic='Business Rules' anchor='rules'> <section1 topic='Business Rules' anchor='rules'>
@ -233,7 +233,7 @@ TODO:
</section2> </section2>
<section2 topic='MUC and MIX related rules'> <section2 topic='MUC and MIX related rules'>
<p>In cases where media is shared in a &xep0045; or &xep0369; room the sender has to expect that a large number of clients may retrieve the shared media automatically. Ideally multiple sources, including HTTP or other high availability sources, are provided in the &lt;sources&gt; tag of the &lt;media-sharing&gt; tag in case the media is shared in a MUC/MIX room.</p> <p>In cases where media is shared in a &xep0045; or &xep0369; room the sender has to expect that a large number of clients may retrieve the shared media automatically. Ideally multiple sources, including HTTP or other high availability sources, are provided in the &lt;sources&gt; tag of the &lt;media-sharing&gt; tag in case the media is shared in a MUC/MIX room.</p>
<p class='box'>TODO: Describe protocol for MIX members to advertise media availablilty to peers in a dedicated MIX channel PubSub node. Maybe as a dedicated XEP.</p> <p class='box'>TODO: Describe protocol for MIX members to advertise media availabililty to peers in a dedicated MIX channel PubSub node. Maybe as a dedicated XEP.</p>
</section2> </section2>
<section2 topic='MAM and Carbons related rules'> <section2 topic='MAM and Carbons related rules'>
<p>For the media sharing described in this XEP to work, it is REQUIRED for MAM to store the whole stanza instead of only the body content. If the MAM component of the user's server strips away the &lt;media-sharing&gt; tag, any shared media will be missing in archived messages.</p> <p>For the media sharing described in this XEP to work, it is REQUIRED for MAM to store the whole stanza instead of only the body content. If the MAM component of the user's server strips away the &lt;media-sharing&gt; tag, any shared media will be missing in archived messages.</p>