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

added missing FORM_TYPE registration, fixed muc#request examples

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@275 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2006-12-15 00:19:53 +00:00
parent fbb3dc0b36
commit 8501cd53e4
1 changed files with 42 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

43
xep-0045.xml
View File

@ -2462,6 +2462,16 @@
label='Requested role'>
<value>participant</value>
</field>
<field var='muc#jid'
type='text-single'
label='User ID'>
<value>hag66@shakespeare.lit/pda</value>
</field>
<field var='muc#roomnick'
type='text-single'
label='Room Nickname'>
<value>thirdwitch</value>
</field>
<field var='muc#request_allow'
type='boolean'
label='Grant voice to this person?'>
@ -2482,6 +2492,12 @@
<field var='muc#role'>
<value>participant</value>
</field>
<field var='muc#jid'>
<value>hag66@shakespeare.lit/pda</value>
</field>
<field var='muc#roomnick'>
<value>thirdwitch</value>
</field>
<field var='muc#request_allow'>
<value>true</value>
</field>
@ -4271,7 +4287,7 @@
<p>The well-known Service Discovery node 'http://jabber.org/protocol/muc#traffic' enables discovery of the namespaces that are allowed in traffic sent through a room (see the <link url='#impl-service-traffic'>Allowable Traffic</link> section of this document).</p>
</section2>
<section2 topic='Field Standardization' anchor='registrar-formtype'>
<p>&xep0068; defines a process for standardizing the fields used within Data Forms qualified by a particular namespace. Within MUC, there are three uses of such forms: room registration within muc#user, room configuration within muc#owner, and service discovery extensions for room information. The reserved fields are defined below.</p>
<p>&xep0068; defines a process for standardizing the fields used within Data Forms qualified by a particular namespace. Within MUC, there are four uses of such forms: room registration (the "muc#register" FORM_TYPE), requesting voice and approving voice requests ("muc#request"), room configuration ("muc#roomconfig"), and service discovery extensions for room information ("muc#roominfo"). The reserved fields are defined below.</p>
<section3 topic='muc#register FORM_TYPE' anchor='registrar-formtype-register'>
<code caption='Registry Submission'><![CDATA[
<form_type>
@ -4310,6 +4326,31 @@
var='muc#register_url'
type='text-single'
label='Your URL'/>
</form_type>
]]></code>
</section3>
<section3 topic='muc#register FORM_TYPE' anchor='registrar-formtype-register'>
<code caption='Registry Submission'><![CDATA[
<form_type>
<name>http://jabber.org/protocol/muc#request</name>
<doc>XEP-0045</doc>
<desc>
Forms enabling voice requests in a
Multi-User Chat (MUC) room or admin
approval of such requests.
</desc>
<field var='muc#role'
type='text-single'
label='Requested role'/>
<field var='muc#jid'
type='text-single'
label='User ID'/>
<field var='muc#roomnick'
type='text-single'
label='Room Nickname'/>
<field var='muc#request_allow'
type='boolean'
label='Whether to grant voice'/>
</form_type>
]]></code>
</section3>