mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-25 02:32:18 -05:00
XEP-0389: add a glossary
This commit is contained in:
parent
a6a2942129
commit
0707b4e3d0
32
xep-0389.xml
32
xep-0389.xml
@ -117,6 +117,38 @@
|
|||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
</section1>
|
</section1>
|
||||||
|
<section1 topic='Glossary' anchor='glossary'>
|
||||||
|
<dl>
|
||||||
|
<di>
|
||||||
|
<dt>Challenge</dt>
|
||||||
|
<dd>
|
||||||
|
A challenge is an action taken during account registration or recovery
|
||||||
|
that requires a response.
|
||||||
|
For example, displaying a form to a user or asking for a token.
|
||||||
|
</dd>
|
||||||
|
</di>
|
||||||
|
<di>
|
||||||
|
<dt>Challenge Type</dt>
|
||||||
|
<dd>
|
||||||
|
The type of a challenge is a unique string that identifies the type of
|
||||||
|
payload that can be expected.
|
||||||
|
For example, a challenge element with type "jabber:x:data" can be
|
||||||
|
expected to contain a data form.
|
||||||
|
Challenge types must be defined and registered in the challenge types
|
||||||
|
registry.
|
||||||
|
When defining a challenge it is often convenient to reuse an XML
|
||||||
|
namespace from the document defining the challenge.
|
||||||
|
</dd>
|
||||||
|
</di>
|
||||||
|
<di>
|
||||||
|
<dt>Flow</dt>
|
||||||
|
<dd>
|
||||||
|
A flow, or more specifically a "registration flow" or "recovery flow",
|
||||||
|
is an ordered collection of challenges.
|
||||||
|
</dd>
|
||||||
|
</di>
|
||||||
|
</dl>
|
||||||
|
</section1>
|
||||||
<section1 topic='Use Cases' anchor='usecases'>
|
<section1 topic='Use Cases' anchor='usecases'>
|
||||||
<ul>
|
<ul>
|
||||||
<li>
|
<li>
|
||||||
|
Loading…
Reference in New Issue
Block a user