Re: [rfc-i] document dependence, was Meta decorations in generated HTML

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
-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest