- From: Han Leon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Aug 2019 02:37:07 +0000
- To: public-web-nfc@w3.org
As nfc forum spec says the domain and type should be treated as case insensitive, web nfc spec using "w3.org:A" does not look worse than "w3.org:a", let's keep with "w3.org:A". In respect of impl, on Android "w3.org:A" will be written into tags as "w3.org:a", on other platforms (in the future) it may still be "w3.org:A", or it'd be written as "W3.oRg:a" via some other non-webnfc routes, anyway, I'd make Chromium webnfc impl compare them on a case insensitive basis so everything is OK. I don't think we need to force the type to be lowercase, also webnfc spec does not need to let users be aware that an external custom-type with uppercase chars will always be converted to lowercase for writing, it's an impl detail, users just do what they want based on the knowledge that the external custom-type is case insensitive. -- GitHub Notification of comment by leonhsl Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/308#issuecomment-525559245 using your GitHub account
Received on Wednesday, 28 August 2019 02:37:09 UTC