ietf-tools / relaton-data-ids

Bibliographic data information for Internet-Drafts in Relaton format
7 stars 11 forks source link

Some Internet-Drafts are not provided by Datatracker due to incomplete information, pending future repair #11

Open strogonoff opened 2 years ago

strogonoff commented 2 years ago

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.

strogonoff commented 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.

ronaldtse commented 2 years ago

This needs to be filed at relaton-ietf.

ronaldtse commented 2 years ago

@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:

Screenshot 2022-04-29 at 8 59 43 PM

Perhaps there is some data missing in bibxml-ids?

rjsparks commented 2 years ago

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.

TonyLHansen commented 2 years ago

+1 to what Robert said

ronaldtse commented 2 years ago

Thank you @rjsparks @TonyLHansen for the clarification! We will keep this ticket open for future tracking.