Re: [Tools-discuss] bibxml3 database reload frequency

[Henrik Levkowetz <[e-mail]>]

Hi Kent,

On 2020-08-21 00:24, Kent Watsen wrote:
> Hi Henrik and Carsten - thanks for the responses!
> 
> It worked, and then it didn’t. Too late for me now, but you should
> know, I think datatracker's cache may need to be cleared befor each
> run...

Huh, right (or rather, the xml2rfc reference cache on datatracker.ietf.org).

Good point.  Will have to think about how to best deal with this.


Best regards,
	
	Henrik

> 
> Below for details.
> 
> K
> 
> 
> My adventure:
> 
> I first updated my XML, e.g.: 
> 
> 	<xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-crypto-types.xml”/>
> 
> But my locally compiled drafts continued to load the *previous*
> version (-17) of the crypto-types draft (though I submitted -18 a few
> hours ago).
> 
> So I ran `xml2rfc —clear-cache`, after which the current (-18)
> revision showed. Yeah!

Yes, xml2rfc keeps a local cache for 24 hours, and that may need clearing.
> 
> Thinking that I conquered it, I submitted the dependent drafts, but
> looking at the uploaded documents, I see the previous version again.
> For instance, the references section of the just-uploaded -13 of the
> “trust-anchors” draft shows -17 for the “crypto-types” draft:
> https://tools.ietf.org/html/draft-ietf-netconf-trust-anchors-13#ref-I-D.ietf-netconf-crypto-types
> <https://tools.ietf.org/html/draft-ietf-netconf-trust-anchors-13#ref-I-D.ietf-netconf-crypto-types>


>
> 
Oh, well, can’t win them all.
> 
> K.
> 
> 
> 
> 
> 
>> On Aug 20, 2020, at 12:36 PM, Henrik Levkowetz <[e-mail]> wrote:
>> 
>> Hi Kent,
>> 
>> On 2020-08-20 18:05, Kent Watsen wrote:
>>> 
>>> Hi Tools Team.
>>> 
>>> How often is https://xml2rfc.tools.ietf.org/public/rfc/bibxml3
>>> rebuilt? Is there a way to have it rebuild more often and/or for
>>> draft authors to externally prompt it to rebuild?
>> 
>> THe short answers, which won't help you are: Once per day, and sorry, no.
>> 
>> The answer that I believe will help you is this:
>> 
>> Please use the draft bibxml references under datatracker.ietf.org/doc/bibxml3/
>> instead.  Those are generated on-the-fly and will reflect a new submission
>> at once.
>> 
>> You can use the old form
>> 
>>  https://datatracker.ietf.org/doc/bibxml3/reference.I-D.draft-ietf-netconf-crypto-types.xml
>> 
>> but also a simplified form that omits the 'reference.I-D.' part:
>> 
>>  https://datatracker.ietf.org/doc/bibxml3/draft-ietf-netconf-crypto-types.xml
>> 
>> 
>> Best regards,
>> 
>> 	Henrik
>> 
>>> 
>>> See below for background info.
>>> 
>>> Thanks,
>>> Kent
>>> 
>>> 
>>> Background:
>>> 
>>> I have one draft depending on another.  The new <relref> element is used, but the resulting hyperlinks point to the previous version of the referenced draft (before it was updated ~1 hour ago).
>>> 
>>> Looking at https://xml2rfc.tools.ietf.org/public/rfc <https://xml2rfc.tools.ietf.org/public/rfc>, I see that “bibxml3” hasn’t been updated for roughly one day:
>>> 
>>> 	bibxml3/	19-Aug-2020 00:49
>>> 
>>> Note that the timestamp for “bibxml” (without the ‘3’) is roughly 24 hours newer:
>>> 
>>> 	bibxml/	20-Aug-2020 00:45
>>> 
>>> In any case, the hyperlinks produced by the <relref> elements are all resolving to the previous version of the referenced draft.   I tried `xml2rfc —clear-cache`, but I think the source issue is with https://xml2rfc.tools.ietf.org/public/rfc/bibxml3 not having updated…
>>> 
>>> How often is https://xml2rfc.tools.ietf.org/public/rfc/bibxml3 built?  Is there a way to prompt it to reload?
>>> 
>>> 
>>> 
>>> ___________________________________________________________
>>> Tools-discuss mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/tools-discuss
>>> 
>>> Please report datatracker.ietf.org and mailarchive.ietf.org
>>> bugs at http://tools.ietf.org/tools/ietfdb
>>> or send email to [e-mail]
>>> 
>>> Please report tools.ietf.org bugs at
>>> http://tools.ietf.org/tools/issues
>>> or send email to [e-mail]
>>> 
>> 
> 
>