Prepare spec as Last Call for Review of Proposed Amendments

[himorin]

description is under development!

links and references

• Process 6.2.5. Candidate Amendments
• original draft
• diff from last REC to current
  • dated last REC 2022/09/01, news

matching candidate-* in SoTD

(from previous investigation Updated to match with 2025-07-11)

• picked up items from whole document (numbers are ordered from top of the spec, not consistent with id of aside)
  • C1 (PR128, PR161) section 6.2 Candidate Correction: Updated reference to the global object to use this for consistency in error handling within geolocation retrieval.
  • C2 (PR128, PR161) section 6.3 Candidate Correction: Simplified reference to the global object in the method steps for checking document's activity status.
  • C3 (PR157) section 6.5 Candidate Correction: Added missing step to handle non-secure contexts.
  • C4 (PR153) section 6.6 Candidate Correction: Updated to ensure that the algorithm terminates immediately if a valid cached position is used, avoiding unnecessary steps.
  • C5 (PR153, PR173) section 6.6 Candidate Correction: We now use a map to represent the position data. Clarified the units and reference systems for latitude, longitude, and altitude, ensuring consistency with the updated attribute definitions. Updated the descriptions of the speed and heading to specify measurement units and conditions for null values, aligning with the overall enhancements to attribute accuracy and clarity.
  • A1 (missing PR?) section 8.3 Candidate Addition: Introduce a toJSON() method to allow the GeolocationPosition object to be easily converted into a JSON representation, facilitating interoperability and ease of use in web applications.
  • C6 (PR138) section 9.1 Candidate Correction: To improve clarity and precision, the description of latitude and longitude attributes has been updated to specify that these are real numbers in degrees according to the [WGS84] geodetic system, instead of just stating "decimal degrees."
  • A2 (PR162, PR175) section 9.1 Candidate Addition: To improve clarity and precision, a description of the accuracy attribute has been added, defining it as meters of radius.
  • A3 (missing PR?) section 9.5 Candidate Addition: Extend the toJSON() method functionality to the GeolocationCoordinates object, allowing it to be serialized into a JSON format which enhances data handling and integration capabilities in web applications.
  • C7 (PR153, PR138) section 9.6 Candidate Correction: Constructor now takes a map of position data, a timestamp, and a boolean indicating high accuracy as arguments. We iterate over the map to set the attributes of the GeolocationCoordinates.
  • C8 (PR157) section 10.1 Candidate Correction: Updated the description of the PERMISSION_DENIED constant to clarify the reasons for permission denial, including non-secure context and user denials.
  • A4 (PR183, PR187) section 12 Candidate Addition: Introduce emulated position data to enable user-agent automation.
• ones listed in SoTD
  • Correction: Clarify that only the emulated error code is used (#187)
  • Addition: support geolocation emulation (#183)
  • Correction: Use null instead of NaN when stationary (#173)
  • Correction: Update acquisition algorithm to define data types and han…
  • Addition: Define units for accuracy (#162)
  • Correction: check for non-secure contexts (#157)
  • Addition: expose .toJSON() on GeolocationCoordinates + GeolocationPos…
  • Correction: Clarify units and reference geodetic system for latitude …

changes pointed by htmldiff, and investigations

Spec name change from Geolocation API to Geolocation are not listed below.
Changed but not captured as candidate-* is highlighted as bold.
Candidate corrections marked up correctly are highlighted as italic (candidate IDs are to be added).
Leading bold shows origin of change made, ch is from code highlighter.

• ch section 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7 example: markup change by code highlighter
• PR161 section 2.6 non-normative statement: newly added, but editorial change
• PR131 section 2.7 leading text and title of example: following spec name change in non-normative block, editorial change
• ch section 5 WebIDL block: markup change by code highlighter
• ch section 6 (top) WebIDL block: markup change by code highlighter
• section 6.2
  • C1 (PR161) Procedure 1 changed and captured as candidate correction
  • PR129 Procedure 2 changed (in parallel)
• section 6.3
  • C2 (PR161) Procedure 1 changed and captured as candidate correction
  • PR129 Procedure 4 changed (in parallel)
• section 6.5
  • PR129 leading text, Procedure 1 and 2 (removing this)
  • ch Procedure 3 is markup change by code highlighter
  • C3 (PR157) Procedure 4 (addition) is captured as candidate correction
  • PR129 Procedures 6-10 (old) are united into in parallel
  • A4 Procedure 7-5-1 (old 10-1) last sentence User agents MUST consider invoking set emulated position data as a significant change. has newly added
• section 6.6
  • A4 algorithm 5-3-1 added
  • C4 algorithm 5-3-3-2 modified
  • C5 algorithm 5-3-6-1 added
  • algorithm 5-3-6-2 grammar fixed
  • PR172 algorithm 5-3-8 WebIDL change
• PR172 section 6.7, algorithm 3, WebIDL change
• ch section 7, WebIDL markup block change by code highlighter
• PR147, ch section 8, WebIDL block, toJSON() added without candidate correction, markup block change by code highlighter
• A1 section 8.3, A1 - should be moved to top of section 8, and mark while section 8.3 (incl. h?) as ins?
• PR147, ch section 9, WebIDL block, toJSON() added without candidate correction, markup block change by code highlighter
• C6, A2 section 9.1, show current mismatch
• A3 section 9.5, whole added
• C7 section 9.6
• ch section 10, WebIDL markup block change by code highlighter
• C8 section 10.1
• section 11, spec name change
• A4 section 12, whole added
• Appendix A - changes of toJSON, code highlighter

For changes section from previous REC

PRs after 2022-09-01, from PR127

• might be substantive change
  • Addition: expose .toJSON() on GeolocationCoordinates + GeolocationPosition #147 - only WebIDL change, heading WebIDL block of section 8 and 9 not marked as candidate addition
  • Correction: Update acquisition algorithm to define data types and handle cached positions #153 - C4, C5, grammar fix in section 6.6, C7 (which overrides some change made without PR?)
  • Correction: check for non-secure contexts #157 - C3, C8
  • Addition: Define units for accuracy #162 - update C6 with adding aside of correction (which overrides some change made without PR?)
  • Correction: Use null instead of NaN when stationary #173 - update part of C5, removing NaN
  • Addition: support geolocation emulation #183 - A4, text in algorithm 7-5-1 in section 6.5, new algorithm 5-3-1 in section 6.6 (should mark li within ins?), new section 12
  • Correction: Clarify that only the emulated error code is used #187 - fix applied in A4
• marked non-normative or editorial
  • Editorial: use [=this=] to get global #128 - switch current settings object into this (C1 and C2, change in section 6.5 is overwritten by PR129)
  • Editorial: fix 'in parallel' usage #129 - corresponds with section 6.5 in parallel part; in parallel of section 6.2 and 6.3, leading text and algorithm 1,2 of section 6.5
  • Editorial: Fix references to "default allowlist" #133 - changes in section 2.7
  • Correction: Clarify units and reference geodetic system for latitude and longitude #138 - corresponds with section 9.1 C6, and section 9.6 (should be re-updated by another PR)
  • chore: put in updatable rec infra #149 - added updatableRecFilter() and moved changes section for previous REC
  • Editorial: Minor corrections prior to republication #161 - marking non-normative for section 2.6, fixed JS syntax of example 3, fixed grammar in C1 and C2
  • Editorial: rename spec to Geolocation #164 - spec name changed to Geolocation (should be listed in changes section??)
  • Editorial: Update use of WebIDL "invoke a callback function" #172 - WebIDL issue 1425 change, fixed C4 and algorithm 5-3-8 in section 6.6; algorithm 3 in section 6.7
  • chore: fix purple box marker #175 - fixed heading line of A2
• non-spec PR
  • Editorial: retire Marcos as Editor #127 (respec config)
  • Update w3c.json #141 (w3c.json)
  • chore: bring Marcos out of retirement #143 (respec config)
  • Added webapps as group #144 (respec config)
  • docs: show new .toJSON() capability #151 (README.md)
  • chore: enable dark mode #152 (respec config)
  • Disable /TR/ publication for errata.html #158 (GHAction, errata.html)
  • minor text fix, for pubrules #159 (respec config, pubrules)
  • chore: rewrite implementation report #165 (implementation report)
  • link fix for ipr #166 (implementation report)
  • Added ipr to gh-action #167 (GHAction)
  • removed revisionTypes #168 (respec config)

edits directly committed main

picked up from history, which seems does not have corresponding PR (ignoring line break or respec only changes)

• 1360745
• initial addition of candidates
  • a74c23e
  • b6bfdb2
  • ea16b03
  • 27fce83
  • bfb5325
  • 561c0ef

[himorin]

• A1 and A3 added at 561c0ef (w/o PR), fixed style by newer commits (e.g. bfb5325).

[himorin]

ToDo

• Update list of candidate-* in SoTD
• Prepare Changelog with 1) dividing changes before and after previous REC publication 2022-09-01, 2) manually listing PRs since some changes marked as editorial: has candidate-* changes, 3) capture change commit related to A1 and A3 in changes section w/o corresponding PR
• mark toJSON() in WebIDL block (section 8 and 9) into candidate addition
• fix show current mismatch in section 9.1
• evaluate whether PR129 should be turned into candidate correction or not