Section 6: Non-normative but containing implementation requirements?

[magnus-git]

It is stated that Section 6 is non-normative. However, Section 6.2 contains a list of requirements on implementations of the Geolocation API. Aren't they normative? Normative terminology with upper-case usage (e.g., "MUST") is used.

[reillyeon]

I agree that the use of normative terms in this section is unusual. I view this section as a description of the use cases and requirements for the specification itself rather than implementations. It is therefore non-normative from the perspective of implementers but normative from the perspective of us, as editors.

[samuelweiler]

This seems odd, and I agree with @magnus-git. It also relates to an issue I commented on before: https://github.com/w3c/geolocation-api/issues/49#issuecomment-653037317

[samuelweiler]

@magnus-git Are you satisfied with this resolution?

[magnus-git]

My recommendation is to not use normative language with capital letters indicating that they are normative in a section that is clearly marked as non-normative. I think there's a risk this causes confusion, and the statement "it is ... non-normative from the perspective of implementers but normative from the perspective of ... editors" is unusual in itself and indicative of this.

Thanks,

On Mon, Mar 22, 2021 at 9:13 PM Samuel Weiler @.***> wrote:

@magnus-git https://github.com/magnus-git Are you satisfied with this resolution?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/w3c/geolocation-api/issues/56#issuecomment-804602800, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHCSF6UFW4XAVMF6RTPI2SLTFAINNANCNFSM4PZR67ZQ .

-- -- Magnus

[marcoscaceres]

@magnus-git, just to be clear, https://github.com/w3c/geolocation-api/pull/63 (which closed this issue) does what you suggested: it removed the use of "MUST" in the non-normative section. Could you kindly double check the updated spec, and let us know that you are satisfied with the changes (yes/no)? (really sorry for the bureaucratic going around in circles on this - but we need to record a clear resolution that your issue has been addressed).

[magnus-git]

Thanks for clarifying, Marcos. Yes, I am good with these updates!

On Mon, Mar 22, 2021 at 11:23 PM Marcos Cáceres @.***> wrote:

@magnus-git https://github.com/magnus-git, just to be clear, #63 https://github.com/w3c/geolocation-api/pull/63 (which closed this issue) does what you suggested: it removed the use of "MUST" in the non-normative section. Could you kindly double check the updated spec https://w3c.github.io/geolocation-api/, and let us know that you are satisfied with the changes (yes/no)? (really sorry for the bureaucratic going around in circles on this - but we need to record a clear resolution that your issue has been addressed).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/w3c/geolocation-api/issues/56#issuecomment-804651601, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHCSF6VOOBN2JFHHFONB6I3TFAXVBANCNFSM4PZR67ZQ .

-- -- Magnus

[samuelweiler]

Reopening this to confirm one thing: it looks like the requirements has since been removed entirely. Is that right?

[marcoscaceres]

@samuelweiler, that is correct. The Requirements section is now gone (as the specification itself is the requirements it meets).