<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I think we need to clarify 3.1.<div><br></div><div><span class="Apple-style-span" style="font-family: verdana, charcoal, helvetica, arial, sans-serif; font-size: small; "><p style="margin-left: 2em; margin-right: 2em; ">The user identifier can be one of the following:</p><div style="margin-left: 2em; margin-right: 2em; "><br class="webkit-block-placeholder"></div><ul class="text" style="margin-left: 2em; margin-right: 2em; "><li style="margin-left: 3em; ">Hostname</li><li style="margin-left: 3em; ">Email address</li><li style="margin-left: 3em; ">URL</li></ul><div><br></div><div>We need to provide a rule for normalizing URL entered without a scheme.</div><div><br></div><div>Something like:</div><div>1 if the input contains a @ in any position other than the fist one it must be normalized as a Email Address [3.1.2]</div><div>2 Otherwise, the input SHOULD be treated as an https URL; if it does not include a "http" or "https" scheme, the Identifier MUST be prefixed with the string "https://". If the URL contains a fragment part, it MUST be stripped off together with the fragment delimiter character "#"</div><div><br></div><div>We want <a href="http://example.com">example.com</a> and <a href="https://example.com">https://example.com</a> to normalize to the same identifier.</div><div><br></div><div><br></div><div>We are also referring to OP endpoint. Should that be Authorization endpoint or something more specific?</div><div><br></div><div><br></div><div>We also need to be clear that the SWD endpoint is accessed via https:</div><div><br></div><div>John</div></span></div></body></html>