Open strogonoff opened 2 years ago
This is not the same as #10. In case of #10, missing version did not exist on xml2rfc server (e.g., http://xml2rfc.tools.ietf.org/public/rfc/bibxml-ids/reference.I-D.draft-leiba-imap-implement-guide-09.xml). In this case, the version exists there, but not in our source.
This needs to be filed at relaton-ietf.
@rjsparks we noticed that some IDs are available from bibxml3
but not in the bibxml-ids
rsync endpoint.
For example: @andrew2net you're right, I only see:
$ rsync -avcizxL rsync.ietf.org::bibxml-ids ./bibxml-ids
$ cd bibxml-ids
$ ll | grep abarth-cookie
reference.I-D.draft-abarth-cookie-07.xml
In this case only draft-abarth-cookie-07.xml
is present, but in bibxml3 there are all previous versions:
Perhaps there is some data missing in bibxml-ids
?
This is a side-effect of the datatracker not yet knowing about some older drafts, or in this particular case, have information about particular versions of older drafts. This is a datatracker issue that will be addressed at some point in the future. It's ok that the new service will not serve those references until the data issue is repaired in the datatracker.
+1 to what Robert said
Thank you @rjsparks @TonyLHansen for the clarification! We will keep this ticket open for future tracking.
For example, we don’t have this one: http://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-abarth-cookie-02.xml
(There’s nothing here: https://github.com/ietf-ribose/relaton-data-ids/blob/main/data/draft-abarth-cookie-02.yaml)
It exists on xml2rfc server, but we don’t import it into our sources? If that’s intentional, feel free to close.