Re: [xml2rfc] xml2rfc.tools.ietf.org::xml2rfc.bibxml/bibxml3

[Henrik Levkowetz <[e-mail]>]

Hi Sandy,

On 2019-11-26 21:07, Sandy Ginoza wrote:
> Hi Henrik
> 
> Thanks for your quick work on this.  
> 
> Just fyi that I tested this — the reference entry matches output from
> entries pointing to https://xml2rfc.ietf.org/public/rfc/bibxml3/, but
> I don’t think it’s solved the issue regarding having references for
> the most recent versions of the I-Ds. For example, when I use the
> following:
> 
> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.palet-v6ops-464xlat-opt-cdn-caches.xml"/>

Umm.  Yes, that's not the right form.  You're probably getting an old copy
from cache.  The form available currently (I'm changing that to accept the
form you used for the next release, based in part on your experience) is
this:

<xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-palet-v6ops-464xlat-opt-cdn-caches.xml"/>

> I get a ref for -03, even though the datatracker shows draft-palet-v6ops-464xlat-opt-cdn-caches-04.

... which (the correct form above) has -04 content.

> I also tried using the version number
> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.palet-v6ops-464xlat-opt-cdn-caches-04.xml"/>
> 
> but I got the following error:
> Error: Unable to resolve external request: "https://datatracker.ietf.org/doc/bibxml3/reference.I-D.palet-v6ops-464xlat-opt-cdn-caches-04.xml"
> Error: XInclude processing failed: could not load https://datatracker.ietf.org/doc/bibxml3/reference.I-D.palet-v6ops-464xlat-opt-cdn-caches-04.xml, and no fallback was found, line 1597
> Unable to complete processing rfc8683.xml

Yes, same problem -- you're using
'reference.I-D.palet-v6ops-464xlat-opt-cdn-caches-04.xml' as part of the
URL, instead of 'draft-palet-v6ops-464xlat-opt-cdn-caches-04.xml'.


Best regards,

	Henrik

> Thanks,
> Sandy 
> 
> 
> 
>> On Nov 9, 2019, at 7:40 AM, Henrik Levkowetz <[e-mail]> wrote:
>> 
>> Hi,
>> 
>> On 2019-11-07 06:53, Carsten Bormann wrote:
>>> On Nov 7, 2019, at 04:56, HANSEN, TONY L <[e-mail]> wrote:
>>>> 
>>>> Yeah, I started writing a replacements a few times too. I think the proper mechanism is through a Django template.
>>> 
>>> Probably, as long as you prepend a cache.
>>> The last thing we need is longer access times for the bibxml fetches…
>> 
>> My trial implementation of bibxml3 entries generated on-the-fly from the
>> datatracker database is now deployed.
>> 
>> I'd appreciate people trying it out.
>> 
>> The URLs are of the form
>> 
>>  https://datatracker.ietf.org/doc/bibxml3/<DRAFTNAME>.xml
>> and
>>  https://datatracker.ietf.org/doc/bibxml3/<DRAFTNAME>-<REV>.xml
>> 
>> 
>> Best regards,
>> 
>> 	Henrik
>> 
>> 
>> 
>> _______________________________________________
>> xml2rfc mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/xml2rfc
> 
>