Re: [Geojson] [Editorial Errata Reported] RFC7946 (7253)

Tim Schaub <tim.schaub@gmail.com> Mon, 05 December 2022 18:50 UTC

Return-Path: <tim.schaub@gmail.com>
X-Original-To: geojson@ietfa.amsl.com
Delivered-To: geojson@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD42C14F6E5 for <geojson@ietfa.amsl.com>; Mon, 5 Dec 2022 10:50:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0DnWvPf5L6e7 for <geojson@ietfa.amsl.com>; Mon, 5 Dec 2022 10:50:21 -0800 (PST)
Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94134C14F721 for <geojson@ietf.org>; Mon, 5 Dec 2022 10:50:21 -0800 (PST)
Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-381662c78a9so127936447b3.7 for <geojson@ietf.org>; Mon, 05 Dec 2022 10:50:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=LPUWnDMp8UOliyKuC7Dh7Ffn7g/+xKT888KEMj4e6uI=; b=nDimWBhdVjmCb4Q4o+WbwnHxzXgaRvHOclLSGMEGdB6czRN3N9tPFzYwCWiO7a5Gfm PX52bCho93pQggy4tG0DK9hezZyalrfkFRiBxQxd+Vrp2U89jPmNb6AHsPcgxyfdRHm3 wlgc/LFstQ7VIygYs2gSrEu2Zg2gOTxLQChl+CjUBt1EogYP2YKhChHMrf+fRj/4sjwI Sq7BjubY3UPpF8Zk1xzhJ5vSR2gkaL/NFx8xo3Uy1E50U7GWMJx1pJPLZmqb6bHlgceb aGLMgKafEfrieSaw11DLGxWz6WFg8xeOFQLQmi/mVGnGftZEFHn+69N/2wKSTQ2bQlb0 402Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=LPUWnDMp8UOliyKuC7Dh7Ffn7g/+xKT888KEMj4e6uI=; b=gSUNKQ5BaYxS8vs6hC7AjspcTyQv8sWV0RJ/lTZUltDPPSaJgVKhCGeqhT6a5fs2s4 fEsfmLPks6HJXRmTCCsWG84gE4F1W6cK/lCk9q5Ko2v3hmRiWQjdlMjxq6m6xYMuorxh Q9jkGjfXzplwHtvIktaB6fzNUYytFj2Uivi6bKy356hleEkGseh9PM4nTu5609z4nEP+ xuMYOitV+la4eSLpEe+yKFHEuANZQt8wNIdXwumrhU/VLDdV7vTIdVjWylSqRa8RuhsM nHHcm+9tN5Tbm4xujl3kG0O6J7Fe4FOzy+s5gn9GDb5MrvmE3sfIUX3Oa5SALzhovedp OqRw==
X-Gm-Message-State: ANoB5pmWPU8+e+7SuMyq7+/RsocnjT51lk6+cxge3iUdr6AycKPZKDZw /xIiiW8pa1x8dqtbwtRj4OeyOWcSOXa70O7ExNM=
X-Google-Smtp-Source: AA0mqf4bTW91T4KKILi+AskrJnqkbPmUm8xKEh3YtlvDevXNYNE+OOa0Tm4PLhWGHcjwPqvfNntGfIR45g8pm3MQBQk=
X-Received: by 2002:a05:690c:b81:b0:37e:6806:a5f9 with SMTP id ck1-20020a05690c0b8100b0037e6806a5f9mr63088245ywb.47.1670266220249; Mon, 05 Dec 2022 10:50:20 -0800 (PST)
MIME-Version: 1.0
References: <20221118181034.0A98D55F7E@rfcpa.amsl.com> <588D5D0F-F61D-4645-A56D-BFFBAC3D5B79@amsl.com>
In-Reply-To: <588D5D0F-F61D-4645-A56D-BFFBAC3D5B79@amsl.com>
From: Tim Schaub <tim.schaub@gmail.com>
Date: Mon, 05 Dec 2022 11:50:24 -0700
Message-ID: <CAKdrn+fgDJ1tNiR5QGThPJZK6PfAY-uYa_if4dLCofXSweRhVQ@mail.gmail.com>
To: Chris Smiley <csmiley@amsl.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, Francesca Palombini <francesca.palombini@ericsson.com>, tim@planet.com, howard@hobu.co, martin.daly@cadcorp.com, adoyle@intl-interfaces.com, sean.gillies@gmail.com, stefan@hagen.link, geojson@ietf.org, RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: multipart/alternative; boundary="000000000000bd070f05ef1928da"
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/qhiXqnq8eFElKl9gjRrwTfq3Gs8>
X-Mailman-Approved-At: Sun, 18 Dec 2022 14:07:38 -0800
Subject: Re: [Geojson] [Editorial Errata Reported] RFC7946 (7253)
X-BeenThere: geojson@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF GeoJSON WG <geojson.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geojson>, <mailto:geojson-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/geojson/>
List-Post: <mailto:geojson@ietf.org>
List-Help: <mailto:geojson-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geojson>, <mailto:geojson-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2022 18:50:25 -0000

I chose "Editorial" as the errata type because I thought this would be
classified as a "syntax error that does not affect the technical meaning"
of the specification.  Clearly it affects the reader's ability to
understand what the specification means, but I wasn't suggesting any
technical change to the specification itself.  Maybe the two are
indistinguishable (the meaning and the ability to understand the meaning).
I also don't have any experience with errata types and don't know if the
choice of type will make any difference going forward.

So for whatever it is worth, I'm ok with the change from "Editorial" to
"Technical" if that fits better with how these terms have been used.

Tim


On Mon, Nov 21, 2022 at 3:12 PM Chris Smiley <csmiley@amsl.com> wrote:

>
> Greetings Area Directors,
>
> We are unable to verify this erratum that the submitter marked as
> editorial.
> Please note that we have changed the “Type” of the following errata
> report to “Technical”.  As Stream Approver, please review and set the
> Status and Type accordingly (see the definitions at
> https://www.rfc-editor.org/errata-definitions/).
>
> You may review the report at:
> https://www.rfc-editor.org/errata/eid7253
>
> Please see https://www.rfc-editor.org/how-to-verify/ for further
> information on how to verify errata reports.
>
> Further information on errata can be found at:
> https://www.rfc-editor.org/errata.php.
>
> Thank you.
>
> RFC Editor/cs
>
>
> > On Nov 18, 2022, at 10:10 AM, RFC Errata System <
> rfc-editor@rfc-editor.org> wrote:
> >
> > The following errata report has been submitted for RFC7946,
> > "The GeoJSON Format".
> >
> > --------------------------------------
> > You may review the report below and at:
> > https://www.rfc-editor.org/errata/eid7253
> >
> > --------------------------------------
> > Type: Editorial
> > Reported by: Tim Schaub <tim@planet.com>
> >
> > Section: 5.2
> >
> > Original Text
> > -------------
> > Consider a set of point Features within the Fiji archipelago,
> > straddling the antimeridian between 16 degrees S and 20 degrees S.
> > The southwest corner of the box containing these Features is at 20
> > degrees S and 177 degrees E, and the northwest corner is at 16
> > degrees S and 178 degrees W.
> >
> > Corrected Text
> > --------------
> > Consider a set of point Features within the Fiji archipelago,
> > straddling the antimeridian between 16 degrees S and 20 degrees S.
> > The southwest corner of the box containing these Features is at 20
> > degrees S and 177 degrees E, and the northeast corner is at 16
> > degrees S and 178 degrees W.
> >
> > Notes
> > -----
> > In the antimeridian-crossing example, the text says that the "northwest"
> corner is at 16 degrees S and 178 degrees W.  It should say this is the
> "northeast" corner instead.
> >
> > Instructions:
> > -------------
> > This erratum is currently posted as "Reported". If necessary, please
> > use "Reply All" to discuss whether it should be verified or
> > rejected. When a decision is reached, the verifying party
> > can log in to change the status and edit the report, if necessary.
> >
> > --------------------------------------
> > RFC7946 (draft-ietf-geojson-04)
> > --------------------------------------
> > Title               : The GeoJSON Format
> > Publication Date    : August 2016
> > Author(s)           : H. Butler, M. Daly, A. Doyle, S. Gillies, S.
> Hagen, T. Schaub
> > Category            : PROPOSED STANDARD
> > Source              : Geographic JSON
> > Area                : Applications and Real-Time
> > Stream              : IETF
> > Verifying Party     : IESG
> >
>
>