Internet DRAFT - draft-todo-temporal-uri-scheme
draft-todo-temporal-uri-scheme
TODO Working Group J. Fuller
Internet-Draft 25 December 2022
Intended status: Informational
Expires: 28 June 2023
Temporal URI scheme
draft-todo-temporal-uri-scheme-02
Abstract
This document registers the "dt" URI scheme, to unambiguously
identify a discrete point in time.
Note to Readers
_RFC EDITOR: please remove this section before publication_
The issues list for this draft can be found at
https://github.com/xquery/temporal-uri-scheme
(https://github.com/xquery/temporal-uri-scheme).
* Editor's Copy (https://xquery.github.io/temporal-uri-
scheme/#go.draft-todo-temporal-uri-scheme.html)
* Datatracker Page (https://datatracker.ietf.org/doc/draft-todo-
temporal-uri-scheme)
* Working Group Draft (https://datatracker.ietf.org/doc/html/draft-
todo-temporal-uri-scheme)
* Compare Editor's Copy to Working Group Draft
(https://xquery.github.io/temporal-uri-scheme/#go.draft-todo-
temporal-uri-scheme.diff)
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/.
Fuller Expires 28 June 2023 [Page 1]
Internet-Draft Temporal URI scheme December 2022
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 2
2. The "temporal" URI Scheme . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. Normative References . . . . . . . . . . . . . . . . . . . . 4
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
This document defines the URI scheme "dt", which describes resources
identified by date-time.
1.1. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
This document uses ABNF [RFC5234]. It also uses the date-time rule
from [RFC3339].
Fuller Expires 28 June 2023 [Page 2]
Internet-Draft Temporal URI scheme December 2022
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
Fuller Expires 28 June 2023 [Page 3]
Internet-Draft Temporal URI scheme December 2022
References:
(this document)
4. Security Considerations
TBA
5. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/rfc/rfc2119>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
<https://www.rfc-editor.org/rfc/rfc3339>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008,
<https://www.rfc-editor.org/rfc/rfc5234>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
Acknowledgements
The definition of date-time is from [RFC3339].
Author's Address
James Fuller
Prague
Czech Republic
Email: jim@webcomposite.com
URI: https://jim.fuller.name/
Fuller Expires 28 June 2023 [Page 4]
