-
Notifications
You must be signed in to change notification settings - Fork 38
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
<name> not accepted under <references> #398
Comments
@paf@frobbit.se commented In email Henrik said the RFC tag should have a version="3" tag, and thought it should be there due to the fact I had used the v2v3 tool. It was not there. Addition of it required addition of other things to the RFC tag to what is now accepted:
is still not accepted after . I because of that changed to use title again as attribute to so that it ends up like this:
That works. Unknown if this is the right thing. I think it is wrong the way I read RFC7991. |
@paf@frobbit.se uploaded file Here is the full XML that I try to use. The XML is produced with the v2v3 tool. |
@henrik@levkowetz.com changed status from |
@henrik@levkowetz.com changed resolution from `` to |
@henrik@levkowetz.com commented Fixed in 0aabbd9: Fixed an issue with sections where duplicate name entries could be created during the prep phase, leading to schema validation failure. Fixes issue #398. |
owner:henrik@levkowetz.com
resolution_fixed
type_defect
| by paf@frobbit.seWhen adding under an error is triggered:
XML (line 686 is the line below):
Issue migrated from trac:398 at 2022-02-05 12:48:02 +0000
The text was updated successfully, but these errors were encountered: