From 9049000cce06df09961c54a209f057f0f9c23533 Mon Sep 17 00:00:00 2001 From: stpeter Date: Mon, 13 Jun 2011 13:29:59 -0600 Subject: [PATCH] corrected use of cid instead of challenge in section 3.1.2 --- xep-0158.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0158.xml b/xep-0158.xml index 9cd70074..7907f2e9 100644 --- a/xep-0158.xml +++ b/xep-0158.xml @@ -151,7 +151,7 @@
  • The 'xml:lang' attribute of the challenge stanza SHOULD be the same as the one received from the sender, if any.
  • The challenge stanza MUST include a CAPTCHA form, i.e., a data form of type "form" containing one or more challenges. Inclusion of a CAPTCHA form not only makes it possible to flexibly support or require a large number of challenge types, but also enables constrained clients to respond to challenges (e.g., mobile phone clients that cannot present web pages, or clients on XMPP-only networks).
  • The CAPTCHA form MUST include a hidden field named "FORM_TYPE" (in accordance with &xep0068;) whose value MUST be "urn:xmpp:captcha".
    • -
  • The CAPTCHA form MUST include a hidden field named "cid" set to the challenge ID.
    • +
  • The CAPTCHA form MUST include a hidden field named "challenge" set to the challenge ID.
  • The CAPTCHA form MUST include a hidden field named "from" set to the value of the 'to' attribute from the triggering stanza.
  • If the triggering stanza included an 'id' attribute, then the CAPTCHA form MUST include a hidden field named "sid" set to that value.
  • Each of the CAPTCHA form's non-hidden <field/> elements MAY contain a different challenge.