- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Dec 2019 13:03:11 +0000
- To: public-web-nfc@w3.org
I think we don't need artificial constraints here, and starting exactly with `:` would overlap badly with external records (not long ago there was an idea that the implementation could generate the domain part and apps only specify `:<ext-type-name>`. The algorithms will first check on the record types in our spec, so there will be a match (causing an error later, potentially). Then, if no standard names match, then we check for a valid external type name. If that is not a match, we check for a valid local name. At that point we won't have any overlaps, but we can still include in the validation steps. So I see no reason to introduce a new constraint here. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/375#issuecomment-566051754 using your GitHub account
Received on Monday, 16 December 2019 13:04:02 UTC