From 0d8db650bbdabcf90b270bcdc1822b58c1af6f94 Mon Sep 17 00:00:00 2001 From: Florian Schmaus Date: Wed, 28 Mar 2018 19:10:27 +0200 Subject: [PATCH] Fix typo in XEP-0122: s/protocols/protocol/ --- xep-0122.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0122.xml b/xep-0122.xml index be48a6c0..8ad77987 100644 --- a/xep-0122.xml +++ b/xep-0122.xml @@ -101,7 +101,7 @@ -

This document defines a new namespace, "http://jabber.org/protocols/xdata-validate". The root element for this namespace is <validate/>, and MUST be contained within a <field/> element (qualified by the 'jabber:x:data' namespace) for each Data Forms field that possesses additional validation information.

+

This document defines a new namespace, "http://jabber.org/protocol/xdata-validate". The root element for this namespace is <validate/>, and MUST be contained within a <field/> element (qualified by the 'jabber:x:data' namespace) for each Data Forms field that possesses additional validation information.

The simplest usage is to provide a more-granular datatype for a <field/> element used in Data Forms. To provide this datatype information, a <validate/> element is included whose 'datatype' attribute specifies the data type of any <value/> contained within the <field/> element:

The use of namespace prefixes is RECOMMENDED for large forms, to reduce the data size. To maintain the highest level of compatibility, implementations sending the form using prefixes SHOULD use the namespace prefix "xdv", and SHOULD declare the namespace prefix mapping in the ancestor <x xmlns='jabber:x:data'/> element:

Sample Form