From 7a42a617129e36ae0bb2c4a6ef9fb20142406bd2 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 29 Jan 2007 05:04:09 +0000 Subject: [PATCH] Jabber to XMPP git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@437 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0082.xml | 10 +++++----- xep.ent | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/xep-0082.xml b/xep-0082.xml index a74935e9..5df8a0d4 100644 --- a/xep-0082.xml +++ b/xep-0082.xml @@ -6,8 +6,8 @@
- Jabber Date and Time Profiles - This document specifies a standardization of ISO 8601 profiles and their lexical representation for use in Jabber/XMPP protocol extensions. + XMPP Date and Time Profiles + This document specifies a standardization of ISO 8601 profiles and their lexical representation for use in XMPP protocol extensions. &LEGALNOTICE; 0082 Active @@ -66,7 +66,7 @@
-

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" The concept of an ISO 8601 profile is used in both RFC 3339 (http://www.ietf.org/rfc/rfc3339.txt) and a W3C Note (http://www.w3.org/TR/NOTE-datetime). 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;.

+

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" The concept of an ISO 8601 profile is used in both RFC 3339 (http://www.ietf.org/rfc/rfc3339.txt) and a W3C Note (http://www.w3.org/TR/NOTE-datetime). 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;.

 @@ -95,7 +95,7 @@ CCYY-MM-DD -

This profile is equivalent to the 'date' datatype defined in XML Schema The 'date' datatype is defined at <http://www.w3.org/TR/xmlschema-2/#date>.. 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.

+

This profile is equivalent to the 'date' datatype defined in XML Schema The 'date' datatype is defined at <http://www.w3.org/TR/xmlschema-2/#date>.. 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.

1776-07-04 @@ -105,7 +105,7 @@ CCYY-MM-DDThh:mm:ss[.sss]TZD -

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).

+

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).

This profile is equivalent to the 'dateTime' datatype defined in XML Schema The 'dateTime' datatype is defined at <http://www.w3.org/TR/xmlschema-2/#dateTime>.. 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.

1969-07-21T02:56:15Z diff --git a/xep.ent b/xep.ent index cf21ba36..9d418e9f 100644 --- a/xep.ent +++ b/xep.ent @@ -667,7 +667,7 @@ Advanced Message Processing XEP-0079: Advanced Message Processing <http://www.xmpp.org/extensions/xep-0079.html>." > User Geolocation XEP-0080: User Geolocation <http://www.xmpp.org/extensions/xep-0080.html>." > Jabber MIME Type XEP-0081: Jabber MIME Type <http://www.xmpp.org/extensions/xep-0081.html>." > -Jabber Date and Time Profiles XEP-0082: Jabber Date and Time Profiles <http://www.xmpp.org/extensions/xep-0082.html>." > +XMPP Date and Time Profiles XEP-0082: XMPP Date and Time Profiles <http://www.xmpp.org/extensions/xep-0082.html>." > Nested Roster Groups XEP-0083: Nested Roster Groups <http://www.xmpp.org/extensions/xep-0083.html>." > User Avatar XEP-0084: User Avatar <http://www.xmpp.org/extensions/xep-0084.html>." > Chat State Notifications XEP-0085: Chat State Notifications <http://www.xmpp.org/extensions/xep-0085.html>." >