- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Jan 2020 10:40:42 +0000
- To: public-web-nfc@w3.org
Also, as @sleevi notes [here](https://github.com/w3c/web-nfc/issues/350#issuecomment-570312505), > > Let asciiDomain be the result of running domain to ASCII on domain. > You've omitted the optional boolean beStrict, which means it defaults to false. This permits certain implementation-dependent characters. It's unclear if that was intended here - that is, the relationship between the external type and the current origin are unclear me, but I would suspect that NFC-RTD makes a normative dependency on DNS, which means that beStrict should be true, even if UAs allow the current domain to contain a U+005F (_) LOW LINE (underbar). My general advice is "be strict in what you accept" - if you're validating caller textual input or NFC tag input (versus the current origin/domain), then omitting _ seems entirely reasonable. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/511#issuecomment-570535834 using your GitHub account
Received on Friday, 3 January 2020 10:40:43 UTC