<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Nat<div><br></div><div>I agree there’s no need to allow them in the #rfc.section. form in most other documents - this should only apply to documents that previously used the pre-mmarkdown publishing process.</div><div><br></div><div>FAPI2 and so on (with the current <a href="https://hub.docker.com/r/danielfett/markdown2rfc">https://hub.docker.com/r/danielfett/markdown2rfc</a> publishing processing) use the #section. form instead.</div><div><br></div><div>The conformance suite makes extensive use of links in both formats, but we’re probably not the only people doing so as this is a well-known property of xml2rfc generated documents.</div><div><br></div><div>Thanks</div><div><br></div><div>Joseph</div><div><br></div><div><br><div><br><blockquote type="cite"><div>On 29 Jun 2023, at 04:02, Nat Sakimura via Openid-specs-fapi <openid-specs-fapi@lists.openid.net> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr">So, the current one has two anchors. The ones that are used by the ToC in the old workflow is like <a href="https://openid.net/specs/openid-financial-api-part-2-1_0-final.html#algorithm-considerations">https://openid.net/specs/openid-financial-api-part-2-1_0-final.html#algorithm-considerations</a><div>which is the same as the pandoc-generated ones. This should continue work. Internal links like #rfc.section.8.6 can be added as well, but that's not a very desirable name that we have to live with as it is not rfc. Going forward, we probably do not want them. </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">2023年6月28日(水) 23:42 josephheenan via Openid-specs-fapi <<a href="mailto:openid-specs-fapi@lists.openid.net">openid-specs-fapi@lists.openid.net</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">New issue 614: Pandoc publishing - the internal link names have I think changed<br><br></blockquote></div></div></blockquote><a href="https://bitbucket.org/openid/fapi/issues/614/pandoc-publishing-the-internal-link-names">https://bitbucket.org/openid/fapi/issues/614/pandoc-publishing-the-internal-link-names</a><blockquote type="cite"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Joseph Heenan:<br>
<br>
The pandoc output I think has different internal link names in the FAPI1 Errata to the current document. e.g. this form of link should continue to navigate to the right place:<br>
<br>
`<a href="https://openid.net/specs/openid-financial-api-part-2-1_0-final.html#rfc.section.8.6" rel="noreferrer" target="_blank">https://openid.net/specs/openid-financial-api-part-2-1_0-final.html#rfc.section.8.6`</a><br>
<br>
\(Also that note in FAPI2 and other things using the mmarkdown\+xml2rfc pipeline I believe the links are in the same form but without the `rfc.` on the beginning.\)<br>
<br>
<br>
<br>
_______________________________________________<br>
Openid-specs-fapi mailing list<br>
<a href="mailto:Openid-specs-fapi@lists.openid.net" target="_blank">Openid-specs-fapi@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-fapi" rel="noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-fapi</a><br>
</blockquote></div>
_______________________________________________<br>Openid-specs-fapi mailing list<br>Openid-specs-fapi@lists.openid.net<br>https://lists.openid.net/mailman/listinfo/openid-specs-fapi<br></div></blockquote></div><br></div></body></html>