- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Oct 2019 19:29:07 +0000
- To: public-web-nfc@w3.org
Charter change is possible, it's at least 30 days to process. The way I read [the Out of Scope](https://w3c.github.io/web-nfc/charter/#out-of-scope) section, we need to do that charter change for v2. It's a challenging task to come up with a new, broader scope that would be web-like, simple, with real, validated use cases, implementable, secure, etc., and get consensus on that. Maybe we should set up some brainstorming about that as soon as this release is out. Until then, we can update the spec if there is consensus or a decision about the desired behavior and policies. I don't like the current Note about how non-formatted tags should be handled, either. So we can do what @taralx proposed: on non-formatted tag read, fire an event with a message that has empty record array. In addition, we can include an `overwrite` flag to push options as @reillyeon suggested (which currently is `true`, and default value may remain the same, but apps would be able to set it to `false`). We should also include notes / algorithmic steps that handle recent questions: - what happens if other tech is on the tag that exposes NDEF (informative) - when `mediaType` needs to be specified and when can it be empty (normative) - FQDN in external type records (normative) - will check if there is anything else. Is that an acceptable solution for now @reillyeon ? -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/367#issuecomment-540744193 using your GitHub account
Received on Thursday, 10 October 2019 19:29:09 UTC