From 04ad1885aa2518db95910c62b3ee157c32df45ed Mon Sep 17 00:00:00 2001 From: Doug Davis Date: Thu, 12 Nov 2026 19:38:03 +0000 Subject: [PATCH] Clarify timestamps Signed-off-by: Doug Davis --- cloudevents/spec.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/cloudevents/spec.md b/cloudevents/spec.md index 37aa889ca..64753a13b 100644 --- a/cloudevents/spec.md +++ b/cloudevents/spec.md @@ -243,7 +243,10 @@ string-encoding for each type that MUST be supported by all implementations. - String encoding: `URI-reference` as defined in [RFC 3986 Section 4.1](https://tools.ietf.org/html/rfc3986#section-4.1). - `Timestamp` - Date and time expression using the Gregorian Calendar. - - String encoding: [RFC 3339](https://tools.ietf.org/html/rfc3339). + - String encoding: [RFC 3339](https://tools.ietf.org/html/rfc3339). Note + that the RFC mentions using a character other that `T` as the separator + between the date and time; implementationts MUST use `T`. While lowercase + `t` and `z` are also permitted, only uppercase variants SHOULD be used. All context attribute values MUST be of one of the types listed above. Attribute values MAY be presented as native types or canonical strings.