moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 23:28:51 -05:00
Code Issues Releases Wiki Activity

XEP-0329: Remove unnecessary whitespace around examples

Browse Source
This commit is contained in:
Emmanuel Gil Peyrot 2016-08-07 21:41:42 +01:00
parent 3945c638c1
commit 6b53252c7f
1 changed files with 16 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

56
xep-0329.xml
View File

@ -71,19 +71,15 @@
<section1 topic='Getting Information About Files ' anchor='disco'>
<section2 topic='Traversing Files' anchor='traver'>
<p>If a requesting entity wishes to know what files are being shared by an offering entity, it can do so by sending the following query:</p>
<example caption='Requester queries the root of the shared folder'>
<![CDATA[
<example caption='Requester queries the root of the shared folder'><![CDATA[
<iq type='get'
from='juliet@capulet.com/chamber'
to='romeo@montague.net/home'
id='1234'>
<query xmlns="urn:xmpp:fis:0" />
</iq>
]]>
</example>
</iq>]]></example>
<p> If the offering entity wishes to share files with the requesting entity, it may respond with a list of shared folders. It MUST not include any files in this response.</p>
<example caption='The offering entity responds with shared directories'>
<![CDATA[
<example caption='The offering entity responds with shared directories'><![CDATA[
<iq type='result'
from='romeo@montague.net/home'
to='juliet@capulet.com/chamber'
@ -93,35 +89,26 @@
<directory name='pics'/>
<directory name='audio'/>
</query>
</iq>
]]>
</example>
</iq>]]></example>
<p>if the offering entity has no files to offer</p>
<example caption='The offering entity responds with no files'>
<![CDATA[
<example caption='The offering entity responds with no files'><![CDATA[
<iq type='result'
from='romeo@montague.net/home'
to='juliet@capulet.com/chamber'
id='1234'>
<query xmlns="urn:xmpp:fis:0" />
</iq>
]]>
</example>
</iq>]]></example>
<p>Requesting the list of files and directories within a directory.</p>
<example caption='The requesting entity wants to know about a particular directory'>
<![CDATA[
<example caption='The requesting entity wants to know about a particular directory'><![CDATA[
<iq type='get'
from='juliet@capulet.com/chamber'
to='romeo@montague.net/home'
id='1234'>
<query xmlns="urn:xmpp:fis:0" node="documents" />
</iq>
]]>
</example>
</iq>]]></example>
<p>When replying with a list of files, the offering entity can choose to either reply with verbose information on the file using the file attributes defined by &xep0234; or it may reply only with the 'name' attribute, which is required and MUST be included in every response.</p>
<p>It is RECOMENDED, when the list files to be sent is small, that a verbose response be made (in order to avoid going back and forth requesting information), and that a non-verbose reponse be made otherwise. This recomendation is made to save bandwidth.</p>
<example caption='The offering entity replies with information about a particular directory'>
<![CDATA[
<example caption='The offering entity replies with information about a particular directory'><![CDATA[
<iq type='result'
from='romeo@montague.net/home'
to='juliet@capulet.com/chamber'
@ -140,22 +127,16 @@
</file>
<directory name="secret docs" />
</query>
</iq>
]]>
</example>
</iq>]]></example>
<p>If the requesting entity wants to get detailed information about a file. It can do so by providing its full path.</p>
<example caption='The requesting entity wants to know about a particular file'>
<![CDATA[
<example caption='The requesting entity wants to know about a particular file'><![CDATA[
<iq type='get'
from='juliet@capulet.com/chamber'
to='romeo@montague.net/home'
id='1234'>
<query xmlns="urn:xmpp:fis:0" node="documents/test2.txt" />
</iq>
]]>
</example>
<example caption='The offering entity responds with more information'>
<![CDATA[
</iq>]]></example>
<example caption='The offering entity responds with more information'><![CDATA[
<iq type='result'
from='romeo@montague.net/home'
to='juliet@capulet.com/chamber'
@ -166,9 +147,7 @@
<size>1000</size>
</file>
</query>
</iq>
]]>
</example>
</iq>]]></example>
</section2>
</section1>
<section1 topic='Bandwidth Considerations' anchor='bandwidth'>
@ -186,8 +165,7 @@
<section1 topic='Implementation Notes' anchor='implementation'>
<section2 topic='File identification' anchor='file_id'>
<p> As it was previously discussed, when requesting detailed information about a file, only the "name" attribute is required, but it is strongly RECOMMENDED that the hash attribute be included, in order to reduce the chances of sending the wrong file. When requesting the file to be transferred using &xep0234;, the information that must be provided has to identify the file uniquely. It is then RECOMMENDED that when requesting a file, the full path of the file in the shared folder be included in the "name" attribute.</p>
<example>
<![CDATA[
<example><![CDATA[
<jingle xmlns='urn:xmpp:jingle:1'
action='session-initiate'
initiator='juliet@capulet.com/chamber'
@ -202,9 +180,7 @@
</request>
</description>
</content>
</jingle>
]]>
</example>
</jingle>]]></example>
</section2>
<section2 topic='File Sharing in MUCs' anchor='fis_muc'>
<p>For the most part, discovering files in a MUC is exactly the same as what has been described in this document. However, it is RECOMMENDED that a participant in a MUC should have a single shared folder associated with the entire room, as opposed to advertise different files to different participants of the room. This is to reduce the complexity of the client software. Also, due to volatile nature of the participants in a room, keeping track of permissions is more trouble than what it is worth.</p>