Re: [rfc-i] Where was the discussion?

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 22 January 2020 01:53 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 732B0F406F4 for <rfc-interest@rfc-editor.org>; Tue, 21 Jan 2020 17:53:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level:
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, SURBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BGOHUOBUrQks for <rfc-interest@rfc-editor.org>; Tue, 21 Jan 2020 17:52:59 -0800 (PST)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) by rfc-editor.org (Postfix) with ESMTPS id 65958F406F3 for <rfc-interest@rfc-editor.org>; Tue, 21 Jan 2020 17:52:59 -0800 (PST)
Received: by mail-pj1-x102d.google.com with SMTP id kx11so2302122pjb.4 for <rfc-interest@rfc-editor.org>; Tue, 21 Jan 2020 17:53:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=cf7GphS7a5BiXpmAOP31VjatCmqIpHe0RWYAcK1HCek=; b=Bub7v5PrJGKTL/5IAbI6cWwEKt1GNr6CQTcimXXAG9/5zmkaGmGJC7h+c95cE+OwtO I8ssOyx8pmSZr/HhkJB0IhevjVfT2hawUbfQ5nkSm/OOtXrVicSW2eC3+/FpDU8TCv1j 07xsGK8UQPnKOuh+O95bPfBmAzjZZhO9Lgy1k3IrVPuOU3ZI3/l7uNgbuzCHH7/BHYJP 3NkI7cbwAWJBqAyEeQEHvUhwk4pKPjgD73VWWnMwvGq/lNYPTWoaDyXKeHvRyArMqra0 fm4c7pScnI9UjEX1D++rCHhZRyUKo4t6RiAFOR1x4Nfd4Rl9BA240DGBeIxgTwjdgbYq IuLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=cf7GphS7a5BiXpmAOP31VjatCmqIpHe0RWYAcK1HCek=; b=byTEHE7Xc3J2658xY5ngS0Ty7hLFVg4z4iAhAj1UE1kfGqbphmEcfDdtgu3HqW0slu ZjHscApdUz8D510Qvfm579d+TL1bvUx25pJn3WBdcNjRDEiC2mxa0R03tb8AUGfsWmiO n06tQdK/UIVCDdvMl8fIw6mORWK075JMOph+lzCDO76NuQBEJX1j8W5L+blVhvR0cm3Q neE3ympB6knuNsIOUlyTWVQMM7Vznth92I++JN06cZDPoqetARLsrpVhjUb8d6phmmpM sfspcy8Z49O+1iPn+DDqXRul0tLmMbVqGsJUAOfMXDkwaERwo+LjPqzNkEYzlSDSnnWf 2log==
X-Gm-Message-State: APjAAAU9RoH6xVaqbpgc2ptJaIUcBX2326Bd/IFtSLtB5Q/OmeYVVDIs 4ieB9X4yZCbMCSpbB4KYNpnyYShY
X-Google-Smtp-Source: APXvYqxphraQJY8uub2OQC/YHxQTPR8OpBAAKV4T7298cD/PMggx7hPK/O4loNKYvxOggeVsBo3H3A==
X-Received: by 2002:a17:90a:25c2:: with SMTP id k60mr144419pje.127.1579657986910; Tue, 21 Jan 2020 17:53:06 -0800 (PST)
Received: from [192.168.178.30] (88.161.69.111.dynamic.snap.net.nz. [111.69.161.88]) by smtp.gmail.com with ESMTPSA id 68sm42397236pge.14.2020.01.21.17.53.05 for <rfc-interest@rfc-editor.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Jan 2020 17:53:06 -0800 (PST)
To: rfc-interest@rfc-editor.org
References: <CAMm+LwiXhhJO7qYi41+DC4W7uMUVipXqyq75Fq2vagA1ppJNdA@mail.gmail.com> <10cca93f-a8b8-4c42-0653-3b12fa67ad12@gmail.com> <CAMm+LwgA-1UffBfrH-Y3J6pfh7ni9kNrndp=gHNyUyi5j=oLxg@mail.gmail.com> <53607da4-6608-783b-b875-65551e3add19@gmail.com> <CAMm+LwgNU2Dr3bB+A8k+UwbQiRRzgUkoRRh60tc6+bBv6CXwfQ@mail.gmail.com> <70ed6362-41ee-faf5-8f90-d094455dbdf4@gmail.com> <CAMm+Lwhy-AV_K5evzGdpDi-ynpLE4RxXCVB1HercickYfZaubg@mail.gmail.com> <e8bc039a-b85f-61e8-966d-912ec1cfd861@gmail.com> <1d18f689-781a-2306-3c98-ae8536a01bdd@gmx.de> <CAMm+LwjzqHTpBOTSfKMDYXrJZ1oHfWJuZBt0dG6uVSHHoRsn3w@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <38557d27-5e29-6162-ac50-019ac4f581c3@gmail.com>
Date: Wed, 22 Jan 2020 14:53:03 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAMm+LwjzqHTpBOTSfKMDYXrJZ1oHfWJuZBt0dG6uVSHHoRsn3w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Subject: Re: [rfc-i] Where was the discussion?
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2020 01:53:03 -0000

> So the 'extensive discussions with the community' I was being told I should defer to earlier turn out to be private discussions on a private list the community never saw. Perhaps people who took offense at my earlier use of the term 'clique' might wish to reconsider?

No, I wouldn't. Yes, of course, obviously, there was a detailed technical design team, which I was not involved in. But the significant choices were not made in secret (as my two previous messages show); they were exposed in drafts as they should have been, and they were discussed on this list by people who took an interest.

None of which means that the decisions are sacred. Could we please focus on debugging the current format, and separately on possible proposals to extend it?

Regards
   Brian Carpenter

On 22-Jan-20 08:43, Phillip Hallam-Baker wrote:
> 
> 
> On Tue, Jan 21, 2020 at 1:42 PM Julian Reschke <julian.reschke@gmx.de <mailto:julian.reschke@gmx.de>> wrote:
> 
>     On 21.01.2020 19:26, Doug Royer wrote:
>     > On 1/20/20 11:01 PM, Phillip Hallam-Baker wrote:
>     >> I have read all posts on the RFC-I list that include the string 'SVG'.
>     >> I find that almost no mention whatsoever was made of SVG-Tiny until it
>     >> appeared in the drafts. There is barely any mention of an SVG profile
>     >> before it is asserted that the decision to use a profile of SVG is
>     >> immutable in 2014. I therefore reject the suggestion that this was
>     >> sufficiently discussed at the time.
>     >>
>     >> If people want to claim that something was discussed and decided, I am
>     >> going to be asking for a link to the post where that happened.
>     >
>     > I also agree. I ran across this topic because someone Cc'd the topic on
>     > a WG years ago. At the time I said that it needed to be discussed in a
>     > more open forum. It never was.
>     >
>     > There seems to be some channel of RFC's that make it, and I never seen
>     > the discussion. Mostly I do not care. In this case I added myself to
>     > that list when I found it. The feedback was limited. And I could not
>     > find the discussion history.
>     >
>     > That is the problem with non-WG drafts. Assuming you can find the
>     > mailing list (if any), often no history is preserved.
> 
>     There was a mailing list (rfc-design), and yes, it was preserved. But it
>     wasn't public, so the archives aren't either.
> 
>      From my recollection, there wasn't a lot of discussion on SVG itself,
>     as most of the team members were busy with different parts of the specs.
> 
>     And then of course this all was supposed to be finished years earlier,
>     and a new iteration in the works already.
> 
>     Best regards, Julian
> 
> 
> So the 'extensive discussions with the community' I was being told I should defer to earlier turn out to be private discussions on a private list the community never saw. Perhaps people who took offense at my earlier use of the term 'clique' might wish to reconsider?
> 
> One of the reasons I did not want to get involved at the time was precisely because I didn't want to make things take even longer.
> 
> The SVG 2.0 spec is already under development. SVG-Tiny 2.0 is not being considered. I am looking into making a formal proposal to move SVG-Tiny to historic.
> 
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>