moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 02:02:16 -05:00
Code Issues Releases Wiki Activity

Merge branch 'xep-0082' into premerge

Browse Source
This commit is contained in:
Jonas Schäfer 2021-08-31 17:28:20 +02:00
commit f3082e5d44
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
xep-0082.xml
View File

@ -23,6 +23,12 @@
<shortname>N/A</shortname>
&stpeter;
&tobias;
<revision>
<version>1.1.1</version>
<date>2021-08-31</date>
<initials>@Yquas</initials>
<remark><p>Fix typos</p></remark>
</revision>
<revision>
<version>1.1</version>
<date>2013-09-26</date>
@ -146,7 +152,7 @@
<p>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.</p>
</section1>
<section1 topic='Security Considerations'>
<p>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.</p>
<p>The timezone specifier of an 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.</p>
</section1>
<section1 topic='IANA Considerations'>
<p>This document requires no interaction with &IANA;.</p>