[Openid-specs-fapi] Issue #614: Pandoc publishing - the internal link names have I think changed (openid/fapi)

[Joseph Heenan]

Hi Nat

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.

FAPI2 and so on (with the current https://hub.docker.com/r/danielfett/markdown2rfc publishing processing) use the #section. form instead.

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.

Thanks

Joseph



> On 29 Jun 2023, at 04:02, Nat Sakimura via Openid-specs-fapi <openid-specs-fapi at lists.openid.net> wrote:
> 
> So, the current one has two anchors. The ones that are used by the ToC in the old workflow is like https://openid.net/specs/openid-financial-api-part-2-1_0-final.html#algorithm-considerations
> 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. 
> 
> 2023年6月28日(水) 23:42 josephheenan via Openid-specs-fapi <openid-specs-fapi at lists.openid.net <mailto:openid-specs-fapi at lists.openid.net>>:
>> New issue 614: Pandoc publishing - the internal link names have I think changed
>> 
https://bitbucket.org/openid/fapi/issues/614/pandoc-publishing-the-internal-link-names
> 
>> 
>> Joseph Heenan:
>> 
>> 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:
>> 
>> `https://openid.net/specs/openid-financial-api-part-2-1_0-final.html#rfc.section.8.6` <https://openid.net/specs/openid-financial-api-part-2-1_0-final.html#rfc.section.8.6>
>> 
>> \(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.\)
>> 
>> ‌
>> 
>> _______________________________________________
>> Openid-specs-fapi mailing list
>> Openid-specs-fapi at lists.openid.net <mailto:Openid-specs-fapi at lists.openid.net>
>> https://lists.openid.net/mailman/listinfo/openid-specs-fapi
> _______________________________________________
> Openid-specs-fapi mailing list
> Openid-specs-fapi at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-fapi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20230630/b5ccb490/attachment.html>