Clarify handling of date-time offsets

smithy-lang · Jan 30, 2023 · 9ebbb0e · 9ebbb0e
1 parent 8437431
commit 9ebbb0e
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/docs/source-1.0/spec/core/protocol-traits.rst b/docs/source-1.0/spec/core/protocol-traits.rst
@@ -305,6 +305,8 @@ Smithy defines the following built-in timestamp formats:
         `RFC3339 section 5.6 <https://www.rfc-editor.org/rfc/rfc3339#section-5.6>`_
         with no UTC offset and optional fractional precision (for example,
         ``1985-04-12T23:20:50.52Z``).
+       *However*, offsets are parsed gracefully, but the datetime is normalized
+       to an offset of zero by converting to UTC.
     * - http-date
       - An HTTP date as defined by the ``IMF-fixdate`` production in
         :rfc:`7231#section-7.1.1.1` (for example,

diff --git a/docs/source-2.0/spec/protocol-traits.rst b/docs/source-2.0/spec/protocol-traits.rst
@@ -221,8 +221,8 @@ Smithy defines the following built-in timestamp formats:
         :rfc:`3339#section-5.6`
         with no UTC offset and optional fractional precision (for example,
         ``1985-04-12T23:20:50.52Z``).
-        *However*, offsets will still be parsed gracefully, but the datetime
-        will be normalized to an offset of zero (i.e. converted to UTC)
+       *However*, offsets are parsed gracefully, but the datetime is normalized
+       to an offset of zero by converting to UTC.
     * - http-date
       - An HTTP date as defined by the ``IMF-fixdate`` production in
         :rfc:`7231#section-7.1.1.1` (for example,