From 466aff50af5f032026662cccce5d1b9ff4378d21 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 3 Oct 2025 08:33:02 +0000
Subject: [PATCH 1/2] Initial plan


From f59b0f9bbdc62fe3305261e31da010046eff44cf Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 3 Oct 2025 08:38:56 +0000
Subject: [PATCH 2/2] Add informative section on relationship to other
 specifications

Co-authored-by: marcoscaceres <870154+marcoscaceres@users.noreply.github.com>
---
 index.html | 43 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 43 insertions(+)

diff --git a/index.html b/index.html
index d3c6dd8..24a4e54 100644
--- a/index.html
+++ b/index.html
@@ -490,6 +490,49 @@ <h2>
         [[[#privacy]]].
       </p>
     </section>
+    <section id="relationship-to-other-specifications" class="informative">
+      <h2>
+        Relationship to other specifications
+      </h2>
+      <p>
+        This specification provides location information (latitude, longitude,
+        altitude) and heading. For use cases requiring full orientation data,
+        including pitch and roll, the {{GeolocationCoordinates}} interface can
+        be combined with the <a href="https://w3c.github.io/orientation-sensor/">Generic Sensor API</a>'s
+        <a href="https://w3c.github.io/orientation-sensor/#absoluteorientationsensor">AbsoluteOrientationSensor</a>
+        interface to provide six degrees of freedom (6DoF) positioning data.
+      </p>
+      <p>
+        This approach is relevant to several related specifications and initiatives:
+      </p>
+      <ul>
+        <li>
+          <strong><a href="https://github.com/immersive-web/geo-alignment">Geo-alignment</a></strong> -
+          The W3C Immersive Web Community Group is developing support for geographically-aligned
+          orientation in Extended Reality (XR) contexts. For XR applications, implementers are advised
+          to obtain timing-coordinated positioning data through XR-specific APIs rather than
+          combining Geolocation and sensor data independently.
+        </li>
+        <li>
+          <strong><a href="https://github.com/opengeospatial/GeoPose/">GeoPose</a></strong> -
+          The Open Geospatial Consortium (OGC) is standardizing GeoPose, which represents both
+          location and orientation. The combination of this specification's coordinate data with
+          orientation information from Generic Sensor API provides data equivalent to GeoPose's
+          six degrees of freedom.
+        </li>
+        <li>
+          <strong><a href="https://w3c.github.io/sdw/proposals/geotagging/webvmt/">WebVMT</a></strong> -
+          For geotagged video use cases, this specification provides the necessary geographic
+          location data that can be combined with other APIs for comprehensive spatial-temporal
+          metadata.
+        </li>
+      </ul>
+      <p>
+        Implementers and web developers working on use cases requiring full 6DoF positioning
+        should consider these related specifications and choose the appropriate combination of
+        APIs for their specific context.
+      </p>
+    </section>
     <section id="navigator_interface" data-dfn-for="Navigator">
       <h2>
         Extensions to the `Navigator` interface