Re: [w3ctag/design-reviews] Web NFC (#461)

@hober thanks for the links, the _principle_ is understood and fine. 

However, the guides and texts you cite are hardly enough deterministic, consistent and exact for the substantial claims drawn above (if based on them). Is there is enough information that 8 people out of 10 could give consistent (10% relative std deviation) ranking to any given permission currently implemented in the browsers? If there are no measurements on that, we don't have a consistent process.

With such substantial claims that a given feature should not be exposed even with permissions IMHO warrants a well defined, deterministic and specific process. If the links above qualify for that (they are good, and the most usable metrics I found are this [flowchart](https://github.com/w3cping/adding-permissions/blob/master/AdriennePorterFelt-flowchart.png ) and [checklist](https://github.com/w3cping/adding-permissions/blob/master/README.md#how-to-ask-for-permission-on-the-web)), in particular, I am interested in
- where exactly do the Web NFC permissions fail in the context given above
- has Web NFC been given feedback about that and has it had the chance to implement those, and 
- in general is there a process of curating and improving a feature permission in order to pass a kind of certification for being "good enough permission"?

If issue discussions like this serve that purpose, then please be more specific about the subject of criticism and the preferred mitigations.




-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/461#issuecomment-587843657