Serialising Extended Data About Times and Events (sedate)
|WG||Name||Serialising Extended Data About Times and Events|
|Area||Applications and Real-Time Area (art)|
|Personnel||Chairs||Bron Gondwana , Mark McFadden|
|Area Director||Francesca Palombini|
|Jabber chat||Room address||xmpp:firstname.lastname@example.org?join|
Charter for Working Group
RFC 3339 defines a text format as a profile of ISO 8601 that can reliably
express an instant in time, either in UTC or in a local time along with the
offset against UTC. However, datetime data often has additional context, such
as the timezone or calendar system that was in use when that instant was
Particularly when using times for interval, recurrence, or offset calculations,
it is necessary to know the context in which the timepoint exists. It would be
valuable to have a standard text serialisation format for this contextual data.
This working group will develop and publish a format meeting that requirement,
subject to the additional constraints described below.
* This format must be able to round-trip through intermediate systems which do
not understand the full context.
* Systems which don’t understand all the contextual fields must still be able
to reliably extract the instant in time.
Changes to RFC 3339 are explicitly outside the charter for this working group.
If a need for an RFC 3339bis emerges, this group must recharter before
performing that work. In this case, the changes to RFC 3339 will need to be
clearly motivated, evaluated and precisely scoped during the rechartering
process, and will need to make only changes that keep the timestamp
specification a profile of current versions of ISO 8601. Stability of the RFC
3339 timestamp format is important to existing IETF protocols and the Internet
generally, and any rechartering process should frown on anything that would
invalidate the existing timestamp format.
The working group will coordinate with ECMA International TC39 and ISO/TC 154
to ensure that this work remains a strict extension of ISO 8601 and its various
parts rather than becoming a conflicting standard.
|Jun 2022||Submit extended date and time draft to the IESG for publication||
|Done||Adopt a draft for extended date and time handling||