-
Notifications
You must be signed in to change notification settings - Fork 7
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
The publisher should not be IETF #15
Comments
Ah right, this is a relaton-ietf issue. Linking it there. |
I was wrong. The current repo is correct: Look at this data: relaton-data-misc/data/reference.PKCS.9.1993.yaml Lines 22 to 27 in fcc1aae
There is no publisher IETF. In the bibxml diff, the publisher is added: I suspect it is the BibXML service that is adding the IETF organization. Can @strogonoff please confirm? |
Can I have an example where BibXML service adds the organization? Here it’s not IETF: https://dev.bibxml.org/public/rfc/bibxml2/reference.PKCS.9.1993.xml Perhaps, if you are testing locally, your instance did not reindex |
This screenshot was taken from the file you provided in https://github.com/ietf-ribose/bibxml-service/issues/222 😉 |
Apparently this is not the case anymore, so we can close this? |
Ah, that’s been a while back :) |
The text was updated successfully, but these errors were encountered: