From a441358f3587e0172c8e0674b2d3de7c74881809 Mon Sep 17 00:00:00 2001 From: ID Bot Date: Thu, 19 Oct 2023 19:21:42 +0000 Subject: [PATCH] Script updating gh-pages from af4dbb0. [ci skip] --- draft-ietf-sedate-datetime-extended.html | 2 +- draft-ietf-sedate-datetime-extended.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-sedate-datetime-extended.html b/draft-ietf-sedate-datetime-extended.html index 0eda08b..03dfb0c 100644 --- a/draft-ietf-sedate-datetime-extended.html +++ b/draft-ietf-sedate-datetime-extended.html @@ -1540,7 +1540,7 @@

local offset reduces the level of interoperability that can be achieved in using this feature; the present specification however does not formally deprecate this syntax. -With the update to RFC 3339, the local offset Z can be used in its +With the update to RFC 3339, the local offset Z should now be used in its place.ΒΆ

diff --git a/draft-ietf-sedate-datetime-extended.txt b/draft-ietf-sedate-datetime-extended.txt index 2a174b5..d9633b8 100644 --- a/draft-ietf-sedate-datetime-extended.txt +++ b/draft-ietf-sedate-datetime-extended.txt @@ -337,7 +337,7 @@ Table of Contents -00:00 as a local offset reduces the level of interoperability that can be achieved in using this feature; the present specification however does not formally deprecate this syntax. With the update to - RFC 3339, the local offset Z can be used in its place. + RFC 3339, the local offset Z should now be used in its place. 3. Internet Extended Date/Time format (IXDTF)