<div dir="auto">That's the placeholder for the ISO version. XML2RFC automatically creates the normative reference at the end, which does not go well with the ISO Directives. </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">2024年9月10日(火) 9:50 Michael Jones via Openid-specs-ekyc-ida <<a href="mailto:openid-specs-ekyc-ida@lists.openid.net">openid-specs-ekyc-ida@lists.openid.net</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="m_-2910659630996157928WordSection1">
<p class="MsoNormal">Reviewing the drafts at <a href="https://openid.net/public-review-proposed-final-openid-connect-for-identity-assurance/" target="_blank" rel="noreferrer">
https://openid.net/public-review-proposed-final-openid-connect-for-identity-assurance/</a>, I couldn’t help but notice that each draft had two sections both called “Normative References”.  In each case, first one is empty other than a reference to the second
 one.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Please delete the first ones when publishing the final specifications.  This can be done editorially because it’s a non-normative editorial action.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">                                                                -- Mike<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>

-- <br>
Openid-specs-ekyc-ida mailing list<br>
<a href="mailto:Openid-specs-ekyc-ida@lists.openid.net" target="_blank" rel="noreferrer">Openid-specs-ekyc-ida@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-ekyc-ida" rel="noreferrer noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-ekyc-ida</a><br>
</blockquote></div>