]>

Prague Czech Republic jim@webcomposite.com https://jim.fuller.name/

General temporal scheme 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.

• Editor's Copy
• Datatracker Page

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

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 when, and only when, they appear in all capitals, as shown here. This document uses ABNF . It also uses the date-time rule from .

The "temporal" URI Scheme The "temporal" URI scheme allows for the construction of a URI which represents a discrete point in time. See for a definition of date-time. For example, given the URI: Would represent a discrete point in time of "2022-12-22T16:28:13Z". The following examples would also be valid URIs: 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'.

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)

Security Considerations TBA

Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK] This document defines a date and time format for use in Internet protocols that is a profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.

Acknowledgements The definition of date-time is from .