Kesara Rathnayake

Almost complete list of PIs: https://github.com/ietf-tools/xml2rfc/blob/c10a50c427f8b4002d51f020e506dd2c317e615a/xml2rfc/parser.py#L707-L755 But these might get ignored with v3 xml2rfc.

With the change proposed in #1033, `xml2rfc` will add a new `meta` tag with `name` `created`. This `content` for the meta tag will have the date & time (with UTC...

I've updated the `created` timestamp to show hours and minutes with `Z` instead of `+00:00`. Example: ``` ```

@ajeanmahoney, Are you proposing to have two new meta tags with this request? i.e. publication date (derived from `prepTime`) and HTML created date. Do we need to include time as...

@dthaler Yeah, the bug exists in both `relref` and `xref` when the `section` is empty and `relative` is not empty. `xml2rfc` should not crash but rather warn or spit out...

The bare minimum required is `` to get `Section 4 of [RFC8126]`. You can get customized results by using the `sectionFormat` attribute.

Looks like this issue was introduced with the fix for #606.

**xml2rfc** make use of [lxml](https://lxml.de/) for XML parsing. This looks like an error upstream issue in lxml. Following Python script: ``` from io import StringIO from lxml import etree f...

`id="identifiers"` is used to identify the document header section. https://www.rfc-editor.org/js/metadata.min.js uses this `id` and there are CSS rules specific to this `id`. I don't see a good solution to this...

> (And I'm trying to find the place where specific anchor prefixes are reserved....) https://datatracker.ietf.org/doc/html/rfc7992#section-6.5