-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTML output: capture date of XML file prep and date of HTML rendering #1032
Comments
This change adds the created datetime in the UTC time zone using ISO datetime format for HTML output of an RFC. Example: ``` <meta content="2023-09-21T10:47:04.440964+00:00" name="created"> ``` Fixes ietf-tools#1032
With the change proposed in #1033,
|
This change adds the created datetime in the UTC time zone using ISO datetime format for HTML output of an RFC. Example: ``` <meta content="2023-09-21T10:47:04.440964+00:00" name="created"> ``` Fixes ietf-tools#1032
This change adds the created datetime in the UTC time zone using ISO datetime format for HTML output of an RFC. Example: ``` <meta content="2023-09-22T11:16Z" name="created"> ``` Fixes ietf-tools#1032
I've updated the
|
@ajeanmahoney, Are you proposing to have two new meta tags with this request? Do we need to include time as well? Note that the current |
Yes, two new meta tags, which don't need HH:MM info:
|
If we have the time, why not include it? |
Mainly it's an accuracy versus precision thing. There is a nonzero span of time between generating the document and making it publicly available. It's why RFCs currently show only the month and year in the doc header. In these meta tags, it doesn't matter as much, but if we were to show this information in the document itself, say in a colophon at the end of the doc, day resolution should be sufficient for the reader. |
Description
Currently the HTML output captures the version of xml2rfc in the
<meta>
element, e.g.,<meta content="xml2rfc 3.17.4" name="generator">
and also in a comment:When the HTML output is created, it would be good to also have a timestamp of publication (that is, propagate the timestamp from the prepTime attribute found in the XML file) and a timestamp that captures when the HTML was rendered. If the HTML is then rerendered in the future, then these two timestamps will capture that info (that is, the publication timestamp will be older than the rendering timestamp).
See the RPAT meeting notes.
Code of Conduct
The text was updated successfully, but these errors were encountered: