Re: [rfc-i] document dependence, was Meta decorations in generated HTML
John C Klensin <john-ietf@jck.com> Sat, 28 May 2022 23:05 UTC
Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C3C25C15AE39 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sat, 28 May 2022 16:05:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1653779131; bh=Z3GcQGUXX6jycdQPcmpQYvd+UgZI5LumnU8T4EpREiE=; h=Date:From:To:In-Reply-To:References:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=nls6oloaFQVqMWaYudnSbRd4888jCwloXUksodeHxvcP+1tkGlsukcPSLViaU3zhk DY/jgeisLDSuoW6Ft3OHR7VAH7wvoc8nO2igVWyazFmIXi0o0Pcm8PVYW1REuW1N50 kfhFqXyrhnfAo9KVM4Kg87xgMpIYq0mZgP5gWyf4=
X-Mailbox-Line: From rfc-interest-bounces@rfc-editor.org Sat May 28 16:05:31 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB6BC1595E6; Sat, 28 May 2022 16:05:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1653779131; bh=Z3GcQGUXX6jycdQPcmpQYvd+UgZI5LumnU8T4EpREiE=; h=Date:From:To:In-Reply-To:References:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=nls6oloaFQVqMWaYudnSbRd4888jCwloXUksodeHxvcP+1tkGlsukcPSLViaU3zhk DY/jgeisLDSuoW6Ft3OHR7VAH7wvoc8nO2igVWyazFmIXi0o0Pcm8PVYW1REuW1N50 kfhFqXyrhnfAo9KVM4Kg87xgMpIYq0mZgP5gWyf4=
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB51C1595E6 for <rfc-interest@ietfa.amsl.com>; Sat, 28 May 2022 16:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 2fyOkhkanIbx for <rfc-interest@ietfa.amsl.com>; Sat, 28 May 2022 16:05:26 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED946C157B49 for <rfc-interest@rfc-editor.org>; Sat, 28 May 2022 16:05:25 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1nv5Un-000HTw-Ed; Sat, 28 May 2022 19:05:21 -0400
Date: Sat, 28 May 2022 19:05:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>, rfc-interest@rfc-editor.org
Message-ID: <D7E0CF477D37A269FDDD6561@PSB>
In-Reply-To: <20220528221515.EA52141DB4A0@ary.qy>
References: <20220528221515.EA52141DB4A0@ary.qy>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/uDy-Km1wPS5fgM-pvTbWwOqi8cQ>
Subject: Re: [rfc-i] document dependence, was Meta decorations in generated HTML
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
John, Thanks for your patience. I, unfortunately, have not had time to read every posting on this list carefully and, when I get overextended, sometimes do not follow it for weeks at a time. Glad part of the question was useful and thanks for the answer to that. best, john --On Saturday, May 28, 2022 18:15 -0400 John Levine <johnl@taugh.com> wrote: > It appears that John C Klensin <john-ietf@jck.com> said: >> John, Eliot, >> >> Combining the recent exchange about large code blocks and >> stability with Eliot's comment about tracking policy sources, >> a question: how does additional tagging interact with >> long-term stability/archival issues? If the answer is that >> this is a matter of what gets generated for the HTML version >> only and that the XML is not affected at all, I suppose it is >> not an issue. > > As I thought I said several times, it is in the HTML only. > Both the tags Scholar uses and the OG tags have been stable > for at least a decade. > >> But the conversation about intentionally stable URLs and >> hosting images at the datatracker at ticket 776 caused me to >> wonder. One of the ways of looking at the RFC stability >> problem is to ask whether, if the IETF were to implode and >> the entire tree of names and associated files and data >> vanish, would documents and all of their content still be >> accessible and usable without editing or hunting expeditions? > > Good questions. The text version is text, the PDF is PDF/A-3 > which should render in any compatible PDF viewer. RFC 7992 > says > > The HTML document will be self-contained, without > requiring external files for images, CSS, JavaScript, or > the like. > > But in fact the rendered HTML includes > https://www.rfc-editor.org/js/metadata.min.js, and imports > three fonts from Google. I think the HTML will display legibly > if none of those are available but I haven't checked. > > R's, > John _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Meta decorations in generated HTML John R Levine
- Re: [rfc-i] Meta decorations in generated HTML Lars Eggert
- Re: [rfc-i] Meta decorations in generated HTML Julian Reschke
- Re: [rfc-i] Meta decorations in generated HTML (f… John R Levine
- Re: [rfc-i] Meta decorations in generated HTML John Levine
- Re: [rfc-i] Meta decorations in generated HTML Julian Reschke
- Re: [rfc-i] Meta decorations in generated HTML Carsten Bormann
- Re: [rfc-i] Meta decorations in generated HTML Julian Reschke
- Re: [rfc-i] Meta decorations in generated HTML John R Levine
- Re: [rfc-i] Meta decorations in generated HTML Larry Masinter
- Re: [rfc-i] Meta decorations in generated HTML Michael Richardson
- Re: [rfc-i] Meta decorations in generated HTML John R Levine
- Re: [rfc-i] Meta decorations in generated HTML Michael Richardson
- Re: [rfc-i] Meta decorations in generated HTML Salz, Rich
- Re: [rfc-i] Meta decorations in generated HTML John R Levine
- Re: [rfc-i] Meta decorations in generated HTML John R Levine
- Re: [rfc-i] Meta decorations in generated HTML Eliot Lear
- Re: [rfc-i] Meta decorations in generated HTML John C Klensin
- Re: [rfc-i] document dependence, was Meta decorat… John Levine
- Re: [rfc-i] document dependence, was Meta decorat… John C Klensin
- Re: [rfc-i] document dependence, was Meta decorat… Martin Thomson
- Re: [rfc-i] Meta decorations in generated HTML Jay Daley
- Re: [rfc-i] Meta decorations in generated HTML John Levine
- Re: [rfc-i] Meta decorations in generated HTML Martin J. Dürst