Re: [xml2rfc] RfcMarkup not authoritative, HTML is gone?

Anders Rundgren <anders.rundgren.net@gmail.com> Mon, 16 September 2019 15:34 UTC

Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FCDE12012A for <xml2rfc@ietfa.amsl.com>; Mon, 16 Sep 2019 08:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fNeCmZZlnXYV for <xml2rfc@ietfa.amsl.com>; Mon, 16 Sep 2019 08:34:00 -0700 (PDT)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01E64120122 for <xml2rfc@ietf.org>; Mon, 16 Sep 2019 08:34:00 -0700 (PDT)
Received: by mail-wr1-x42c.google.com with SMTP id r5so5415905wrm.12 for <xml2rfc@ietf.org>; Mon, 16 Sep 2019 08:33:59 -0700 (PDT)
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=YktYnW4eVhSs8sBOGgDI6HmwuHYOkmRAmhgwzrye7Ng=; b=e+GLQwxaa5N8Xr5srGvGd+iLOyM45RgEGDusSVghdRI2gUbFB1umagSEkVWzUTCJxE 8YA2BncOdM9abC0b2gc6elSmLxeyJx/fqYpCilz1yo4gyeb6ZwyIuxoYe49ulYjP4YgQ /6kKLUN5T4ItvLE0IfADow+9C1GMwCjZCtuxrgHh2x9p9nLXRE8KYIZHa7lHAAHtg3Sg vr2jwAosIKH5fa2r66+QyCI08lv244YLbyvuo2/cK+c9RxKc9Yc6W8ehu6DKLHjYlR9P CiT7OxLr/kSYRulb8fnANcJzz9ObRCTwOHrqwbaVxig0vzSxF2rQ2dc6KWcQELj1Knwk tMHQ==
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=YktYnW4eVhSs8sBOGgDI6HmwuHYOkmRAmhgwzrye7Ng=; b=I3xAwT/mmXLmBCYuluBSbJtkvmKvrV4GRTagX2vO4CxbZzSDwy4dh78tVPAEuo0eOA 3mvarWDHk0dmpFguN41+sli+OtEPI5DTsvsAmyz0DBlsrMpEFwcWhZq2Mn3OZrBQE+MW ewYdA/sGxqQmjNr7S91wNl6TdlGMNBMYH4aDESeYvzLn7PgjXXDe+Z8Ht70sgj2+RIJI txcQdOdFvsFi5o0lnoxo7sLT9QiXMoFyXhLspNoJQcXPrOOXWyxI+Ch9aQfefOxMJjBH GjV6NqQReymFeh1jPzKBuyYYUb36RML14/q8WdtBfiMsM9VQP5ZWgDa1+TD/oP4SgdIs UEWg==
X-Gm-Message-State: APjAAAWDg4K7UCBHOUGP9Cb8hyDGIF7s9FUh0PZPOibqUmj+TC+yZsXW ywBiizhCF886xRRB7OrLpc0shdLR
X-Google-Smtp-Source: APXvYqzuPrDNczxN5FuWWcXl0DXbJ+gcaiQp3tld/l/qHzxnncX9Kl7gjIdoXJLeVQ5TGi3zjr6F8Q==
X-Received: by 2002:adf:dd41:: with SMTP id u1mr315065wrm.49.1568648038111; Mon, 16 Sep 2019 08:33:58 -0700 (PDT)
Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id f24sm197178wmb.16.2019.09.16.08.33.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Sep 2019 08:33:57 -0700 (PDT)
To: Julian Reschke <julian.reschke@gmx.de>, Paul Kyzivat <pkyzivat@alum.mit.edu>, xml2rfc@ietf.org
References: <94358f7d-3465-4161-1597-f1dbfba73b3f@gmail.com> <d44ac5f1-e4c2-1239-4bea-714a721115b8@levkowetz.com> <9ceb0697-c3ae-4f14-606c-4e089f04e2f2@gmail.com> <a4874a50-ffc3-80f5-cb42-09f82072644c@gmx.de> <04713f10-5c19-2ad5-2fa6-2db5f1ed5599@gmail.com> <f5554cd0-9c74-3a8c-5af9-25b947d499d8@gmx.de> <7bb2a5fb-262d-39b5-3bb0-72e068923ea7@gmail.com> <c3c8db0e-e719-32e6-ca3c-736e25ce8936@gmx.de> <f2f49552-091d-50e4-e2e2-2fdd30cbb7ae@gmail.com> <bd07ad5a-a0a7-f821-54ec-c09ee5614e2a@gmx.de> <d9883584-1d5e-4d34-9bde-00d32dc49435@gmail.com> <599cb714-89e8-271c-4d5e-ba294fa7d3cf@alum.mit.edu> <ee1a1699-a5e3-3c2b-ad53-ff80a120f7eb@gmail.com> <dcf93ec6-bb2c-3323-a98d-41c9bcdc4e8d@gmx.de>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <f9fad0ca-bfdb-33a3-411e-c411608ae96f@gmail.com>
Date: Mon, 16 Sep 2019 17:33:55 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <dcf93ec6-bb2c-3323-a98d-41c9bcdc4e8d@gmx.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/qcuVZ8y7aVbZez32k5rl5vSYG4Q>
Subject: Re: [xml2rfc] RfcMarkup not authoritative, HTML is gone?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 15:34:03 -0000

On 2019-09-16 16:54, Julian Reschke wrote:
> On 16.09.2019 16:46, Anders Rundgren wrote:
>> On 2019-09-16 16:27, Paul Kyzivat wrote:
>>> On 9/16/19 1:22 AM, Anders Rundgren wrote:
>>>> On 2019-09-14 11:41, Julian Reschke wrote:
>>>> <snip>
>>>>>
>>>>> RfcMarkup has no official standing (and yes, I like it as well, and it
>>>>> has served us well for a very long time). It apparently generates
>>>>> XHTML,
>>>>> but the content is served as text/html on tools.ietf.org. It might be
>>>>> good to change it to produce valid HTML5.
>>>>
>>>> This in interesting and but also rather confusing since this is the by
>>>> far most used method for communicating RFCs by developers.
>>>
>>> Do you have any data to backup this claim?
>>
>> No, OTOH, since I mostly work with JSON-based stuff, the documents are
>> fairly recent.
>>
>> What I'm sure that I have newer seen in wild are references to PDF RFCs
>> (which apparently are in plain text).
>> ...
> 
> I agree with that, but I don't see how that supports the statement about
> RfcMarkup... (it may well be true, but RfcMarkup is something that was
> created because we did not have "official" HTML renderings of the
> documents, and this is going to change soon anyway).

I don't think the motives for using HTML has been very strong.
Is there actually a single RFC out there using SVG and Unicode?

Anyway, I surely look forward to HTML!

Lists currently look a bit "crammed" in my opinion:
https://tools.ietf.org/id/draft-rundgren-signed-http-requests-00.html

Anders

> 
> Best regards, Julian
>