marcoscaceres commented on this pull request.
> </p>
</section>
</section>
<section>
<h2>
+ Security consideration
+ </h2>
+ <p>
+ The URLs relied upon by this specification are only expected to be used
+ by APIs, or internally by the user agent. As such, there is no
+ expectation that URLs defined in this specification would ever be
+ rendered or passed around by end-users. However, in the off-chance that
+ they are, implementers need to be aware of the <a data-cite=
+ "!URL#security-considerations">security considerations</a> from the
+ [[!URL]] specification.
You are right. Can definitely write this "as the world is today" - where there are no known instances of these URLs being rendered. Will fix.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments-method-identifiers/pull/35#discussion_r113637017