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-0389: inline examples in Retrieving the Flows

Browse Source
This commit is contained in:
Sam Whited 2020-05-06 09:02:30 -04:00
parent eb3ccc48f0
commit 19c32fce88
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
xep-0389.xml
View File

@ -293,19 +293,17 @@
<register> or <recovery> element qualified by the
"urn:xmpp:register:0" namespace.
</p>
<example caption='Registration flows query'><![CDATA[
<iq type='get'>
<register xmlns='urn:xmpp:register:0'/>
</iq>]]></example>
<p>
When responding to a query for registration or recovery flows the list of
challenges should be included just as it would be if during stream feature
negotiation.
That is, a "register" or "recovery" element containing a list of flows,
each with an id, containing a name and a list of challenges.
If an entity supports this specification but does not provide any flows
after stream negotiation it MUST respond with an empty list.
</p>
<example caption='Registration flows query'><![CDATA[
<iq type='get'>
<register xmlns='urn:xmpp:register:0'/>
</iq>]]></example>
<example caption='Registration flows results'><![CDATA[
<iq type='result'>
<register xmlns='urn:xmpp:register:0'>
@ -324,6 +322,10 @@
</flow>
</register>
</iq>]]></example>
<p>
If an entity supports this specification but does not provide any flows
after stream negotiation it MUST respond with an empty list.
</p>
<example caption='Empty registration flows results'><![CDATA[
<iq type='result'>
<register xmlns='urn:xmpp:register:0'/>