moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

Jabber to XMPP 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@437 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-01-29 05:04:09 +00:00
parent 9d5976b02f
commit 7a42a61712
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
xep-0082.xml
View File

@ -6,8 +6,8 @@
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
<title>Jabber Date and Time Profiles</title>
<abstract>This document specifies a standardization of ISO 8601 profiles and their lexical representation for use in Jabber/XMPP protocol extensions.</abstract>
<title>XMPP Date and Time Profiles</title>
<abstract>This document specifies a standardization of ISO 8601 profiles and their lexical representation for use in XMPP protocol extensions.</abstract>
&LEGALNOTICE;
<number>0082</number>
<status>Active</status>
@ -66,7 +66,7 @@
</revision>
</header>
<section1 topic='Introduction'>
<p>A number of Jabber protocols specify that dates and times should follow the format defined in &iso8601;. Unfortunately, ISO 8601 provides a great deal of flexibility with regard to the possible date and time "profiles" <note>The concept of an ISO 8601 profile is used in both RFC 3339 (<link url='http://www.ietf.org/rfc/rfc3339.txt'>http://www.ietf.org/rfc/rfc3339.txt</link>) and a W3C Note (<link url='http://www.w3.org/TR/NOTE-datetime'>http://www.w3.org/TR/NOTE-datetime</link>).</note> as well as their lexical representation. While that flexibility can lead to confusion, it is also true that the Jabber community has tended to use only a few restricted profiles of ISO 8601 dates and times (albeit with inconsistent lexical representations). This document formalizes those profiles and their lexical representation through reference to the datatypes defined in &w3xmlschema2;.</p>
<p>A number of XMPP protocol extensions specify that dates and times should follow the format defined in &iso8601;. Unfortunately, ISO 8601 provides a great deal of flexibility with regard to the possible date and time "profiles" <note>The concept of an ISO 8601 profile is used in both RFC 3339 (<link url='http://www.ietf.org/rfc/rfc3339.txt'>http://www.ietf.org/rfc/rfc3339.txt</link>) and a W3C Note (<link url='http://www.w3.org/TR/NOTE-datetime'>http://www.w3.org/TR/NOTE-datetime</link>).</note> as well as their lexical representation. While that flexibility can lead to confusion, it is also true that the Jabber/XMPP community has tended to use only a few restricted profiles of ISO 8601 dates and times (albeit with inconsistent lexical representations). This document formalizes those profiles and their lexical representation through reference to the datatypes defined in &w3xmlschema2;.</p>
</section1>
<section1 topic="Terminology">
<section2 topic='Time Terms'>
@ -95,7 +95,7 @@
<code>
CCYY-MM-DD
</code>
<p>This profile is equivalent to the 'date' datatype defined in XML Schema <note>The 'date' datatype is defined at &lt;<link url='http://www.w3.org/TR/xmlschema-2/#date'>http://www.w3.org/TR/xmlschema-2/#date</link>&gt;.</note>. When an XML schema is used to define a Jabber protocol that uses this profile, the datatype MUST be an XML Schema 'date'. If there are differences between the description in this document and those in XML Schema, the latter overrule.</p>
<p>This profile is equivalent to the 'date' datatype defined in XML Schema <note>The 'date' datatype is defined at &lt;<link url='http://www.w3.org/TR/xmlschema-2/#date'>http://www.w3.org/TR/xmlschema-2/#date</link>&gt;.</note>. When an XML schema is used to define an XMPP protocol extension that uses this profile, the datatype MUST be an XML Schema 'date'. If there are differences between the description in this document and those in XML Schema, the latter overrule.</p>
<example caption='The date of American independence'>
1776-07-04
</example>
@ -105,7 +105,7 @@
<code>
CCYY-MM-DDThh:mm:ss[.sss]TZD
</code>
<p>The Time Zone Definition is mandatory and MUST be either UTC (denoted by addition of the character 'Z' to the end of the string) or some offset from UTC (denoted by addition of '[+|-]' and 'hh:mm' to the end of the string). The fractions of a second are optional and MAY be ignored if included (although a Jabber protocol using the DateTime profile MAY require the fractions of a second).</p>
<p>The Time Zone Definition is mandatory and MUST be either UTC (denoted by addition of the character 'Z' to the end of the string) or some offset from UTC (denoted by addition of '[+|-]' and 'hh:mm' to the end of the string). The fractions of a second are optional and MAY be ignored if included (although an XMPP protocol extension using the DateTime profile MAY require the fractions of a second).</p>
<p>This profile is equivalent to the 'dateTime' datatype defined in XML Schema <note>The 'dateTime' datatype is defined at &lt;<link url='http://www.w3.org/TR/xmlschema-2/#dateTime'>http://www.w3.org/TR/xmlschema-2/#dateTime</link>&gt;.</note>. When an XML schema is used to define a Jabber protocol that uses this profile, the datatype MUST be an XML Schema 'dateTime'. If there are differences between the description in this document and those in XML Schema, the latter overrule.</p>
<example caption='Datetime of the first human steps on the Moon (UTC)'>
1969-07-21T02:56:15Z

2
xep.ent
View File

@ -667,7 +667,7 @@
<!ENTITY xep0079 "<span class='ref'>Advanced Message Processing</span> <note>XEP-0079: Advanced Message Processing &lt;<link url='http://www.xmpp.org/extensions/xep-0079.html'>http://www.xmpp.org/extensions/xep-0079.html</link>&gt;.</note>" >
<!ENTITY xep0080 "<span class='ref'>User Geolocation</span> <note>XEP-0080: User Geolocation &lt;<link url='http://www.xmpp.org/extensions/xep-0080.html'>http://www.xmpp.org/extensions/xep-0080.html</link>&gt;.</note>" >
<!ENTITY xep0081 "<span class='ref'>Jabber MIME Type</span> <note>XEP-0081: Jabber MIME Type &lt;<link url='http://www.xmpp.org/extensions/xep-0081.html'>http://www.xmpp.org/extensions/xep-0081.html</link>&gt;.</note>" >
<!ENTITY xep0082 "<span class='ref'>Jabber Date and Time Profiles</span> <note>XEP-0082: Jabber Date and Time Profiles &lt;<link url='http://www.xmpp.org/extensions/xep-0082.html'>http://www.xmpp.org/extensions/xep-0082.html</link>&gt;.</note>" >
<!ENTITY xep0082 "<span class='ref'>XMPP Date and Time Profiles</span> <note>XEP-0082: XMPP Date and Time Profiles &lt;<link url='http://www.xmpp.org/extensions/xep-0082.html'>http://www.xmpp.org/extensions/xep-0082.html</link>&gt;.</note>" >
<!ENTITY xep0083 "<span class='ref'>Nested Roster Groups</span> <note>XEP-0083: Nested Roster Groups &lt;<link url='http://www.xmpp.org/extensions/xep-0083.html'>http://www.xmpp.org/extensions/xep-0083.html</link>&gt;.</note>" >
<!ENTITY xep0084 "<span class='ref'>User Avatar</span> <note>XEP-0084: User Avatar &lt;<link url='http://www.xmpp.org/extensions/xep-0084.html'>http://www.xmpp.org/extensions/xep-0084.html</link>&gt;.</note>" >
<!ENTITY xep0085 "<span class='ref'>Chat State Notifications</span> <note>XEP-0085: Chat State Notifications &lt;<link url='http://www.xmpp.org/extensions/xep-0085.html'>http://www.xmpp.org/extensions/xep-0085.html</link>&gt;.</note>" >