Re: [xml2rfc] XInclude should be used instead of PI include

[Randy Bush <[e-mail]>]

>>> i have a local rsunk repo and am doing
>>> 
>>>     <references title="Normative References">
>>>       <?rfc include="reference.RFC.2119.xml"?>
> 
> That would look like <xi:include
> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
> 
> All of Carsten's observation about this hardcoding an external
> reference and that the URLs have been changing a _lot_ recently are
> correct, as you can see from the before-preptool source for one of the
> most recently published RFCs:
> 
> rjsparks@undex feat-rfc % curl --no-progress-meter
> https://www.rfc-editor.org/prerelease/rfc9425.notprepped.xml | grep
> 8174
>     <xref target="RFC8174"/> when, and only when, they appear in all
> capitals,
> <xi:include
> href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
> 
> (The RPC is shifting to using bib.ietf.org to which xml2rfc.ietf.org
> redirects).
> 
> For Internet-Drafts, you'll need to use an href that looks like
> 
> https://bib.ietf.org/public/rfc/bibxml-ids/reference.I-D.ietf-rtgwg-segment-routing-ti-lfa.xml
> 
> That is, using xi:include comes with the extra burden of knowing the
> names of the bibxml datasets.
> 
> There are conversations ongoing about how to avoid these
> author-unfriendly aspects.

i demand a refund!!!!

i need to build when there is no net connectivity.  this is why i have
rsunc repos.

randy