- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Aug 2015 11:05:18 +0000
- To: public-web-nfc@w3.org
So it sounds like the prose around the term [obtain permission][1] should be rephrased. The term itself could be renamed too, but I don't have better suggestions for the name at this time. However, here's a suggested rewording for the prose to start: >The term *obtain permission* for a certain operation indicates that the user agent has either obtained *expressed permission*, *asks for forgiveness*, or ensures a *prearranged trust relationship* exists. I'm not sure whether there is a better term for the "ask for forgiveness" approach. IIRC this term was first coined by Robert O'Callahan et al. in the [Why does the HTML fullscreen API ask for approval after entering fullscreen, rather than before?][2] blog post. Then, we should explain what the term *ask for forgiveness* means. Here's my first stab along the lines of @sicking's suggestion, borrowing some language from the [Fullscreen API][3] spec too: >The term *ask for forgiveness* refers to some form of unobtrusive notification that informs the user of an operation while it is running. User agents SHOULD provide the user with means to ignore similar future operations from the same origin and advertise this to the user. If this resonates with people I can craft a PR to get the spec updated. [1]: https://w3c.github.io/web-nfc/index.html#dfn-obtain-permission [2]: http://blog.pearce.org.nz/2013/12/why-does-html-fullscreen-api-ask-for.html [3]: https://fullscreen.spec.whatwg.org/#security-and-privacy-considerations -- GitHub Notif of comment by anssiko See https://github.com/w3c/web-nfc/issues/3#issuecomment-132543578
Received on Wednesday, 19 August 2015 11:05:21 UTC