From 2c8ed7641ea94f9aa1c2f1cb20a6784bbf0451db Mon Sep 17 00:00:00 2001 From: tschmidtb51 <65305130+tschmidtb51@users.noreply.github.com> Date: Fri, 25 Oct 2024 22:07:43 +0200 Subject: [PATCH] Date-time - addresses parts of oasis-tcs/csaf#469 - add section on Date and Time to explain the rules --- ...esign-considerations-01-construction-principles.md | 2 +- .../edit/src/design-considerations-02-date-time.md | 11 +++++++++++ 2 files changed, 12 insertions(+), 1 deletion(-) create mode 100644 csaf_2.1/prose/edit/src/design-considerations-02-date-time.md diff --git a/csaf_2.1/prose/edit/src/design-considerations-01-construction-principles.md b/csaf_2.1/prose/edit/src/design-considerations-01-construction-principles.md index 71edbb65..b4a7fa4d 100644 --- a/csaf_2.1/prose/edit/src/design-considerations-01-construction-principles.md +++ b/csaf_2.1/prose/edit/src/design-considerations-01-construction-principles.md @@ -66,4 +66,4 @@ Section [sec](#distributing-csaf-documents) states how to distribute and where t Safety, Security and Data Protection are considered in section [sec](#safety-security-and-data-protection-considerations). Finally, a set of conformance targets describes tools in the ecosystem. -------- + diff --git a/csaf_2.1/prose/edit/src/design-considerations-02-date-time.md b/csaf_2.1/prose/edit/src/design-considerations-02-date-time.md new file mode 100644 index 00000000..dc5fc6fb --- /dev/null +++ b/csaf_2.1/prose/edit/src/design-considerations-02-date-time.md @@ -0,0 +1,11 @@ +## Date and Time + +This standard uses the `date-time` format as defined in JSON Schema Draft 2020-12 Section 7.3.1. +In accordance with RFC 3339 and ISO 8601, the following rules apply: + +- The letter `T` separating the date and time SHALL be upper case. +- The letter `Z` indicating the timezone UTC SHALL be upper case. +- Fractions of seconds are allow as specified in the standards mention above. +- Leap seconds are supported. However, they SHOULD be avoided if possible. + +-------