moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 08:45:04 -05:00
Code Issues Releases Wiki Activity

XEP-0447: Replace broken ProtoXEP reference with its final entity

Browse Source
This commit is contained in:
Emmanuel Gil Peyrot 2022-02-10 12:54:44 +01:00
parent 0c6f1d4fbe
commit 337ccfbf36
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
xep-0447.xml
View File

@ -1,9 +1,5 @@
<?xml version='1.0' encoding='UTF-8'?> <?xml version='1.0' encoding='UTF-8'?>
<!--
Note to editor: Remove xep-file-metadata entity declared below and change all references from &xep-file-metadata; to respective &xepXXXX; to refeence file metadata element when moving to experimental.
-->
<!DOCTYPE xep SYSTEM 'xep.dtd' [ <!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY xep-file-metadata "<span class='ref'><link url='./file-metadata.html'>File metadata element (XEP-xxxx)</link></span> <note>XEP-xxxx: File metadata element &lt;<link url='./file-metadata.html'>https://xmpp.org/extensions/inbox/file-metadata.html</link>&gt;.</note>" >
<!ENTITY % ents SYSTEM 'xep.ent'> <!ENTITY % ents SYSTEM 'xep.ent'>
%ents; %ents;
]> ]>
@ -27,6 +23,12 @@ Note to editor: Remove xep-file-metadata entity declared below and change all re
<supersededby/> <supersededby/>
<shortname>sfs</shortname> <shortname>sfs</shortname>
&larma; &larma;
<revision>
<version>0.1.2</version>
<date>2022-02-10</date>
<initials>egp</initials>
<remark>Replace the ProtoXEP reference with a reference to the published XEP.</remark>
</revision>
<revision> <revision>
<version>0.1.1</version> <version>0.1.1</version>
<date>2020-12-30</date> <date>2020-12-30</date>
@ -53,7 +55,7 @@ Note to editor: Remove xep-file-metadata entity declared below and change all re
<ul> <ul>
<li>No focus on media, generic for every file type.</li> <li>No focus on media, generic for every file type.</li>
<li>No mixed content, body is used for fallback only and not to transmit additional information.</li> <li>No mixed content, body is used for fallback only and not to transmit additional information.</li>
<li>Using &xep-file-metadata;.</li> <li>Using &xep0446;.</li>
<li>Using XML for structured data instead of URIs when possible, adding further extensibility (like providing proper means of sharing encrypted files on http servers).</li> <li>Using XML for structured data instead of URIs when possible, adding further extensibility (like providing proper means of sharing encrypted files on http servers).</li>
<li>Not relying on underspecified usage of &xep0372;.</li> <li>Not relying on underspecified usage of &xep0372;.</li>
</ul> </ul>
@ -75,7 +77,7 @@ Note to editor: Remove xep-file-metadata entity declared below and change all re
<section2 topic='Sharing a file' anchor='file-sharing'> <section2 topic='Sharing a file' anchor='file-sharing'>
<p> <p>
To share a file, a user sends a message stanza including <tt>&lt;file-sharing/&gt;</tt> to the inteded recipient contact or group. To share a file, a user sends a message stanza including <tt>&lt;file-sharing/&gt;</tt> to the inteded recipient contact or group.
The <tt>&lt;file-sharing/&gt;</tt> element includes a <tt>&lt;file/&gt;</tt> metadata element as described in &xep-file-metadata; as well as a <tt>&lt;sources/&gt;</tt> element. The <tt>&lt;file-sharing/&gt;</tt> element includes a <tt>&lt;file/&gt;</tt> metadata element as described in &xep0446; as well as a <tt>&lt;sources/&gt;</tt> element.
The <tt>&lt;sources/&gt;</tt> element provides one or multiple sources that the receiving client may use to obtain the file. The <tt>&lt;sources/&gt;</tt> element provides one or multiple sources that the receiving client may use to obtain the file.
</p> </p>
<example caption='Sharing summit.jpg with juliet@shakespeare.lit'><![CDATA[ <example caption='Sharing summit.jpg with juliet@shakespeare.lit'><![CDATA[
@ -194,7 +196,7 @@ Note to editor: Remove xep-file-metadata entity declared below and change all re
If the protocol that is used when obtaining the file is not secure (e.g. HTTP without TLS), this SHOULD be considered as if the protocol reveals private information. If the protocol that is used when obtaining the file is not secure (e.g. HTTP without TLS), this SHOULD be considered as if the protocol reveals private information.
</p> </p>
<p> <p>
The security considerations of &xep-file-metadata; apply. The security considerations of &xep0446; apply.
</p> </p>
</section1> </section1>
<section1 topic='IANA Considerations' anchor='iana'> <section1 topic='IANA Considerations' anchor='iana'>