Overprocesses Date

[CxRes]

As per RFCXML reference https://authors.ietf.org/rfcxml-vocabulary#date :

Bibliographic references:

• In order to be able to specify fuzzy dates, such as "2002-2003", "Second quarter 2010", etc., the date element is now permitted to have text content in addition to the year, month, and day attributes. If there is only text content, it will be rendered as is. If there is both text content and date components, both will be rendered, with the expanded date components in parentheses.

However:

informative:
  FETCH:
    author:
      -
        ins: A. van Kesteren
        name: Anne van Kesteren
    target: https://fetch.spec.whatwg.org
    title: Fetch
    seriesinfo:
      WHATWG: Living Standard
    date:  Last Updated 28 May 2025

gets processed as:

        <reference anchor="FETCH" target="https://fetch.spec.whatwg.org">
          <front>
            <title>Fetch</title>
            <author fullname="Anne van Kesteren" initials="A." surname="van Kesteren">
              <organization/>
            </author>
            <date month="May" year="2025"/>
          </front>
          <seriesInfo name="WHATWG" value="Living Standard"/>
        </reference>

There should be a way to specify that date should not be processed when it contains other text. Quoting or block scalars do not help.

[cabo]

On Jun 1, 2025, at 01:16, Rahul Gupta ***@***.***> wrote: date: Last Updated 28 May 2025

Hi Rahul, If you only need to set the “year” attribute to an unprocessed string, you can achieve that by putting its desired value in an array, such as ``` date: ["Last Updated 28 May 2025”] ``` or in more idiomatic YAML ``` date: - Last Updated 28 May 2025 ``` kramdown-rfc currently does not offer a way to set both year and month to unprocessed values; please drop a line if you need that. Please leave this issue active until I have fixed the documentation that doesn’t seem to explain this. Grüße, Carsten

[CxRes]

Hi Carsten,

Yes, that works with the output being:

<date>Last Updated 28 May 2025</date>

For my purposes, this is enough!

What I don't follow is why you have chosen to set it up this way, because kramdown-rfc sets not the "year" attribute but the text inside the <date> tag. It would be more consistent with rfcxml to have unformatted date as a string, and formatted date as array/object.

BR/Rahul

[cabo]

On 2025-06-11, at 16:45, Rahul Gupta ***@***.***> wrote: CxRes left a comment (cabo/kramdown-rfc#260) Hi Carsten, Yes, that works with the output being: <date>Last Updated 28 May 2025</date>

(Actually, it puts the unprocessed string into the year attribute, as in: ``` <date year="Last Updated 28 May 2025"/> ``` )

For my purposes, this is enough!

Good!

What I don't follow is why you have chosen to set it up this way, because kramdown-rfc sets not the "year" attribute but the text inside the <date> tag. It would be more consistent with rfcxml to have unformatted date as a string, and formatted date as array/object.

Kramdown-rfc does not always try to be consistent with rfcxml, but places preference on making simple things easy and complex things possible. The vast majority of dates that authors enter are non-fuzzy. (I’ll need to figure out how to actually place the date into the content of the <date element). Grüße, Carsten

[CxRes]

(Actually, it puts the unprocessed string into the year attribute, as in:

    <date year="Last Updated 28 May 2025"/>

Not in my testing... Here is the sample file and here is the generated XML (I am using author-tools.ietf.org). See line 106.

[cabo]

(Actually, it puts the unprocessed string into the year attribute, as in:

    <date year="Last Updated 28 May 2025"/>

Not in my testing... Here is the sample file and here is the generated XML (I am using author-tools.ietf.org). See line 106.

Ah, you are seeing the v2v3-converted version from the authoring tools, where a non-year value of the year attribute has been moved into the content.

[cabo]

The documentation has been improved at:
https://github.com/cabo/kramdown-rfc/wiki/Syntax#the-yaml-header
(including by adding an example).

Closing this issue now (but of course we can continue to improve the wiki).