From 92799f6fcde5bd24b59a26ac4100b665afff62d9 Mon Sep 17 00:00:00 2001 From: Yquas <81969859+Yquas@users.noreply.github.com> Date: Wed, 25 Aug 2021 12:58:26 +0200 Subject: [PATCH] Update xep-0082.xml --- xep-0082.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0082.xml b/xep-0082.xml index bc4300a6..67835040 100644 --- a/xep-0082.xml +++ b/xep-0082.xml @@ -146,7 +146,7 @@

The 'date', 'dateTime', and 'time' datatypes defined in XML Schema address several "edge cases" such as dates before the year 0000 and after the year 9999, as well as odd timezones no longer in use; most Jabber applications can safely ignore these edge cases, since it is highly unlikely that a Jabber entity will generate such representations.

-

The timezone specifier of a ISO 8601 encoded time can reveal a geographic location to some degree, if it's set to the local time of a user, and thus concerns users' privcacy. To avoid this issue developers are advised to convert local time to UTC before sending ISO 8601 encoded times into the XMPP network.

+

The timezone specifier of a ISO 8601 encoded time can reveal a geographic location to some degree, if it's set to the local time of a user, and thus concerns users' privacy. To avoid this issue developers are advised to convert local time to UTC before sending ISO 8601 encoded times into the XMPP network.

This document requires no interaction with &IANA;.