[Sedate] Lars Eggert's No Objection on charter-ietf-sedate-00-00: (with COMMENT)

Lars Eggert via Datatracker <noreply@ietf.org> Mon, 10 May 2021 11:50 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sedate@ietf.org
Delivered-To: sedate@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA693A19D7; Mon, 10 May 2021 04:50:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Lars Eggert via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: sedate-chairs@ietf.org, sedate@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.28.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Lars Eggert <lars@eggert.org>
Message-ID: <162064744299.18804.8479778474004255522@ietfa.amsl.com>
Date: Mon, 10 May 2021 04:50:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sedate/a7y6z6cN6LiBPhYGBw8kcwPJi_M>
Subject: [Sedate] Lars Eggert's No Objection on charter-ietf-sedate-00-00: (with COMMENT)
X-BeenThere: sedate@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Serialising Extended Data About Times and Events <sedate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sedate>, <mailto:sedate-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sedate/>
List-Post: <mailto:sedate@ietf.org>
List-Help: <mailto:sedate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sedate>, <mailto:sedate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 May 2021 11:50:44 -0000

Lars Eggert has entered the following ballot position for
charter-ietf-sedate-00-00: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-sedate/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools, so there will likely be some false positives. There is no need
to let me know what you did with these suggestions.

"RFC3339", paragraph 1, nit:
- in UTC or in a local time along with the offset against UTC, however datetime
-                                                            ^ ^
+ in UTC or in a local time, along with the offset against UTC. However, datetime
+                          +                                  ^ ^      +

"RFC3339", paragraph 1, nit:
- interval, recurrence, or offset calculations, it's necessary to know the
-                                                 ^
+ interval, recurrence, or offset calculations, it is necessary to know the
+                                                 ^^

"I", paragraph 1, nit:
- It is valuable to have a serialisation format which retains this context and
-                                               ^ ^^^
+ It is valuable to have a serialisation format that retains this context and
+                                               ^ ^^

"I", paragraph 1, nit:
- via intermediate systems which only need to know about the instant in time.
-                          ^ ^^^
+ via intermediate systems that only need to know about the instant in time.
+                          ^ ^^

"T", paragraph 1, nit:
- The TC39 working group at ECMA have developed a format which is a good basis
-                                                        ^ ^^^
+ The TC39 working group at ECMA have developed a format that is a good basis
+                                                        ^ ^^

"I", paragraph 1, nit:
- It is anticipated that this document would be a companion to RFC3339 rather

"I", paragraph 1, nit:
- than a replacement, embedding an un-altered RFC3339 instant along with the
-                                    -                             ---------
- contextual data.
+ RFC3339 rather than a replacement, embedding an unaltered RFC3339 instant along
+ +++++++++++++++
+ with contextual data.
+ +++++

"I", paragraph 1, nit:
- It is also within scope for this group to consider a minor update to RFC3339 to
-                                                                     -----------
- allow larger than 4 digit signed years, to enable representing times further
-                   ^^                                          --------------
- into the past and future.
+ It is also within scope for this working group to consider a minor update to
+                                 ++++++++
+ RFC3339 to allow larger than four-digit signed years, to enable representing
+ +++++++++++                  ^^^^^
+ times further into the past and future.
+ ++++++++++++++