- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Dec 2019 11:12:25 +0000
- To: public-web-nfc@w3.org
zolkis has just created a new issue for https://github.com/w3c/web-nfc: == Simplify creating external records == Following the discussion [here](https://github.com/w3c/web-nfc/pull/467#discussion_r357220894). @beaufortfrancois: > Thinking about it again, I don't think Web NFC should be smart and use the effective domain of the origin as domain name in external type names when creating/reading external type records. I would argue web developers should always set the full external type record. Think about staging environments, where `staging.example.com:smart-poster` would be written automatically if `:smart-poster` were to be allowed. It would not match when read in a prod environment. So the proposal is to validate input for external type as follows: - find the last occurrence of `:`; - the part after it should validate as an external type - the part before it has to be a domain name that should be validated by the [valid domain](https://url.spec.whatwg.org/#valid-domain) steps from the URL Standard (thanks @kenchris for the pointer). Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/470 using your GitHub account
Received on Friday, 13 December 2019 11:12:26 UTC