en.wikipedia.org/wiki/Well-known_URI

The table column is explicitly labeled “Date of IANA registration.” For that field, the authoritative source is IANA’s Well-Known URIs registry. In that registry, the acme-challenge entry is listed with Date Registered: 2016-08-18.

The date 2019-03-01 matches the publication month of RFC 8555 (the ACME RFC), but that is not the same thing as the IANA registration date shown in the registry. So the article’s value in this column is incorrect.

This number appears in the “Date of IANA registration” column, so the authoritative source is IANA’s Well-Known URIs registry. That registry lists the security.txt entry with Date Registered: 2021-07-13.

The linked specification for security.txt is RFC 9116, which was published in April 2022. In any case, IANA’s own registry contradicts the article’s 2018-08-20 value. Therefore the date shown in this row is wrong.

In the table, this date appears under “Date of IANA registration.” The authoritative source for that field is IANA’s Well-Known URIs registry.

IANA’s registry currently contains entries around this alphabetical region such as security.txt and ssf-configuration, but no smart-configuration entry appears in the registry. That means 2023-03-01 cannot be its IANA registration date.

The likely source of the mistaken date is the SMART App Launch specification itself: HL7’s official SMART App Launch guide says the guide version is “Active as of 2023-03-01” and separately says SMART uses a discovery document at .well-known/smart-configuration. That date belongs to the HL7 implementation guide version, not to an IANA well-known-URI registration.