[Sedate] Regarding “[sic]”. [ was: Re: (No subject) ]

[Mark McFadden <[e-mail]>]

With my WG Chair hat off:

I’d like to keep the “[sic]” in place as well. It’s a style issue that will be caught by the RFC Editor in any event, but it seems appropriate not just to the context of the draft, but also consistent with the discussions we’ve had in-person and on the list.

Just my two cents,

Mark

Mark McFadden

CTO | internet policy advisors, llc

Madison Wisconsin US

[e-mail]

On Jan 19, 2023, at 2:21 PM, Richard Gibson <[e-mail]> wrote:



I'm in favor of preserving the "sic", with or without exclamation. It is Latin for "thus", and useful not just for highlighting errors in the source, but more generally for explicitly confirming any aspect of source content that readers might notice and question the authenticity of.

On Thu, Jan 19, 2023 at 2:51 PM Justin Grant <[e-mail]> wrote:

Great news!  Very exciting for this to be moving forward.

Are we expecting to make any more editorial changes or wordsmithing changes that won't affect the functional claims of the document?

I ask because I noticed the following text in the doc draft: 

 (note that the Etc/GMT+10 time zone has a constant UTC Offset of -10:00 [sic!])

Is the "[sic!]" appropriate here?  Are we intending to keep it in the final RFC text? And are there other minor proofreading that needs to happen to finalize the text?

BTW, re: "[sic!", the IANA names of constant GMT +/- time zones have reversed signs from the offsets used inside timestamp strings. Explanation from https://data.iana.org/time-zones/tzdb/etcetera" target="_blank" rel="nofollow">https://data.iana.org/time-zones/tzdb/etcetera: 

# Be consistent with POSIX TZ settings in the Zone names,
# even though this is the opposite of what many people expect.
# POSIX has positive signs west of Greenwich, but many people expect
# positive signs east of Greenwich.  For example, TZ='Etc/GMT+4' uses
# the abbreviation "-04" and corresponds to 4 hours behind UT
# (i.e. west of Greenwich) even though many people would expect it to
# mean 4 hours ahead of UT (i.e. east of Greenwich).

My understanding was that "[sic]" is only used when a quote contains an error or typo, so that the reader will know that the source of the error or typo was in the original quote from the original author and not a mistake made by whoever was transcribing that quote into the document. In this case, it's weird behavior to maintain POSIX compatibility, but it seems too strong to say that it's an outright error.

Cheers,

Justin

On Thu, Jan 19, 2023 at 10:17 AM Mark McFadden <[e-mail]> wrote:

The chairs have drafted a document shepherd write up and will submit it and the -07 draft on to the responsible AD later today. Thanks to everyone who has made this happen.

Mark

Mark McFadden
CTO | internet policy advisors, llc
Madison Wisconsin US
[e-mail]

> On Jan 19, 2023, at 11:40 AM, Carsten Bormann <[e-mail]> wrote:
>
> On 2023-01-17, at 18:47, Carsten Bormann <[e-mail]> wrote:
>>
>> One detail that was found during WGLC was the “TBD” in the security considerations section.
>> A draft for such a section now is in
>>
>> https://github.com/ietf-wg-sedate/draft-ietf-sedate-datetime-extended/pull/32" rel="noreferrer nofollow" target="_blank">https://github.com/ietf-wg-sedate/draft-ietf-sedate-datetime-extended/pull/32
>>
>> This PR should cover all security considerations that came up.
>> If you have additional security considerations in mind, or can suggest better text, please comment on the PR.
>
> The authors have received several positive and no negative comments on this PR.
> I have now submitted -07 with this change.
> This should be ready for submission to IESG.
>
> Grüße, Carsten
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sedate-datetime-extended/" rel="noreferrer nofollow" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-sedate-datetime-extended/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-sedate-datetime-extended-07.html" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/archive/id/draft-ietf-sedate-datetime-extended-07.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-sedate-datetime-extended-07" rel="noreferrer nofollow" target="_blank">https://author-tools.ietf.org/iddiff?url2=draft-ietf-sedate-datetime-extended-07
> --
> Sedate mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/sedate" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/sedate

--
Sedate mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/sedate" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/sedate

--
Sedate mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/sedate" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/sedate