W3C home > Mailing lists > Public > public-geolocation@w3.org > August 2020

Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)

From: Reilly Grant via GitHub <sysbot+gh@w3.org>
Date: Mon, 10 Aug 2020 20:50:17 +0000
To: public-geolocation@w3.org
Message-ID: <issue_comment.created-671582802-1597092615-sysbot+gh@w3.org>
From [RFC2119](https://tools.ietf.org/html/rfc2119),

> **SHOULD**  This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

Implementations are the ultimate authority over their user experience, and there are circumstances, such as devices managed by organization, where implementations may behave differently. A *SHOULD* is nearly as strong as a *MUST*, while acknowledging that there are concerns beyond compatibility which may affect how implementations behave.

GitHub Notification of comment by reillyeon
Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/54#issuecomment-671582802 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 August 2020 20:50:19 UTC

This archive was generated by hypermail 2.4.0 : Monday, 10 August 2020 20:50:19 UTC