From 2e028c3676075d588e66d167c6019181296b93f8 Mon Sep 17 00:00:00 2001 From: Emmanuel Gil Peyrot Date: Fri, 10 Feb 2017 22:22:30 +0000 Subject: [PATCH] XEP-0300: Remove extra characters in example. --- xep-0300.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/xep-0300.xml b/xep-0300.xml index 6cda8b99..9f3eb7c1 100644 --- a/xep-0300.xml +++ b/xep-0300.xml @@ -83,7 +83,7 @@

This document defines a new XML element that can be used in any XMPP protocol extension. An example follows.

- 2XarmwTlNxDAMkvymloX3S5+VbylNrJt/l5QyPa+YoU=åå]]> + 2XarmwTlNxDAMkvymloX3S5+VbylNrJt/l5QyPa+YoU=]]>

An XMPP protocol can include more than one instance of the <hash/> element, as long as each one has a different value for the 'algo' attribute:

2AfMGH8O7UNPTvUVAM9aK13mpCY= 2XarmwTlNxDAMkvymloX3S5+VbylNrJt/l5QyPa+YoU=]]> @@ -216,7 +216,7 @@ type='get'> - ]]> +]]> - ]]> +]]>

In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.

@@ -363,7 +363,7 @@ Support for the BLAKE2b-512 hashing algorithm XEP-0300 - ]]> +]]> @@ -388,7 +388,7 @@ - ]]> +]]>