-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A better error message for when an STD is not found would be helpful #403
Comments
Label ( |
But Paul's point still stands. |
Just to check: is bibxml-rfcsubseries the long-term solution for RFCs, STDs, and drafts? It appears to work today, but I have not seen this before. |
it's been there for a very long time (as bibxml9). |
I was working from https://authors.ietf.org/en/references-in-rfcxml, which should probably be updated. In addition, maybe the xml2rfc tool can make this as a suggestion when parsing. |
The old web page for xml2rfc documented the bibxml-name equivalents for all of the bibxml-# names that have been around for at least 10 years. All of the bibxml-# for # > ~4 were added first as bibxml-name and then a # equivalent assigned. |
So, now I'm very confused with this thread. If I read correctly, @rjsparks said above that bibxml-rfcsubseries should work for everything, but https://bib.ietf.org/public/rfc/bibxml-rfcsubseries/reference.RFC.9460.xml in the browser returns {"error": {"message": "Error resolving bibliographic item. Tried methods: auto (RfcSubseriesAdapter: ): uncategorized issue, fallback (): not indexed"}} Noting that this might be related to us getting "Submission rejected: A system error occurred while processing the submission." when trying to submit the -00 for this draft, even though xml2rfc 3.19.0 on the local laptop has no problem creating a good HTML output. |
After offline converstation with Robert, I now understand the three targets for the URLs. The "let's have a better error message" suggestion still stands, but now it applies to bibxml, bibxml-ids, and bibxml-subseries. |
Just in case others read this, the right target for the subseries is bibxml-rfcsubseries. |
And for drafts, the right target is bibxml-ids. For example https://bib.ietf.org/public/rfc/bibxml-ids/reference.I-D.dnsop-deleg.xml |
bibxml-rfcsubseries, bibxml-ids, bibxml-misc, bibxml-w3c, bibxml-ieee, bibxml-3gpp, bibxml-nist, bibxml-iana, bibxml-doi see the complete list in #7 |
Description
Making a guess about which xi:include to use for an STD:
https://bib.ietf.org/public/rfc/bibxml/reference.STD.0069.xml
This leads to an error:
Error resolving bibliographic item. Tried methods: auto (RfcAdapter: no refs found): not found (Item not found), fallback (): not indexed
A better error message would be:
That item is not available here. If you are looking for STDs, instead try "bibxml9" instead of "bibxml"
Code of Conduct
The text was updated successfully, but these errors were encountered: