Temporal URI scheme

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 28 June 2023.¶

Copyright Notice

Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

This document defines the URI scheme "dt", which describes resources identified by date-time.¶

2. The "temporal" URI Scheme

The "temporal" URI scheme allows for the construction of a URI which represents a discrete point in time.¶

temporal-URI    = temporal-scheme ":" dt
temporal-scheme = "dt"
dt              = date-time

See [RFC3339], Section 5.6.3 for a definition of date-time.¶

For example, given the URI:¶

dt:20221222T162813Z

Would represent a discrete point in time of "2022-12-22T16:28:13Z".¶

The following examples would also be valid URIs:¶

dt:2022-12-22T16:28:13Z
dt:1985-04-12T23:20:50.52Z

This RFC intentionally provides no definition of how URI's might be parsed or compared by applications using them. For example, it is possible to define two URI's which refer to the exact same point in time and it is left to consuming application (or some future specification) to define what that might 'mean'.¶

3. IANA Considerations

This document registers the following value in the "Uniform Resource Identifier (URI) Schemes" registry:¶

Scheme name:

dt¶

Status:

provisional¶

Applications/protocols that use this scheme:

none yet¶

Contact:

iesg@iesg.org¶

Change Controller:

IESG¶

References:

(this document)¶

4. Security Considerations

TBA¶

Acknowledgements

The definition of date-time is from [RFC3339].¶

Author's Address