Add informative section documenting relationship to geo-alignment, GeoPose, and related specifications

[Copilot]

Overview

This PR addresses issue #XXX regarding alignment with geo-alignment/GeoPose initiatives by adding an informative section to the specification that clarifies the relationship between the Geolocation API and related specifications.

Changes

Added a new informative section titled "Relationship to other specifications" that:

• Documents that the Geolocation API provides 4 of 6 degrees of freedom (latitude, longitude, altitude, heading)
• Explains how to achieve full 6DoF positioning by combining GeolocationCoordinates with the Generic Sensor API's AbsoluteOrientationSensor interface
• References three related initiatives:
  • Geo-alignment - W3C Immersive Web Community Group's work on geographically-aligned orientation for XR contexts
  • GeoPose - OGC's standardization of location and orientation representation
  • WebVMT - W3C's work on geotagging for video
• Provides guidance for implementers and web developers on choosing appropriate API combinations for their use cases

Rationale

As noted in the issue discussion, the Geolocation API already provides most of the data needed for geo-alignment and GeoPose use cases. Rather than making normative API changes, this documentation clarifies how developers can combine existing APIs to achieve full 6DoF positioning data.

This approach:

• Maintains backward compatibility
• Leverages existing standardized APIs
• Provides clear guidance for developers working on XR, geospatial, and geotagged video applications
• Acknowledges ongoing standardization work in related communities

Testing

• Validated HTML syntax using Python's html.parser
• Confirmed the section follows existing specification structure and style
• No normative changes, so no behavioral testing required

Fixes #XXX

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Alignment with Geo-alignment/GeoPose?</issue_title>
<issue_description>I'm contributing to a renewed effort to support geographically-aligned orientation (or Geo-alignment) in user agents currently under way in the W3C Immersive Web group. This is primarily aimed at Extended Reality (XR) use cases, but overlaps with other areas such as WebVMT for geotagged video. In addition, several of the group are involved in parallel work at the Open Geospatial Consortium (OGC) which is standardising GeoPose (location and orientation) for the geospatial community.

W3C Geolocation API already supports 3D location and heading which constitute four of the six degrees of freedom included in Geo-alignment and GeoPose, so this seems like a good moment to discuss ways in which to align our work given that we share a lot of common ground.

Please let me know whether this is of interest and who best to contact. Many thanks.</issue_description>

<agent_instructions>I have no idea what to do with this issue... can you help? </agent_instructions>

Comments on the Issue (you are @copilot in this section)

@reillyeon I've skimmed some of your documentation and it appears that a combination of the Geolocation API and AbsolutionOrientationSensor interface should provide all of the information necessary to construct a GeoPose through I agree that for XR purposes it is likely more useful to time this data with the rest of the XR positioning information rather than constructing it piecemeal from a number of unrelated APIs. @marcoscaceres @reillyeon, I'm not really sure what, if anything, we are supposed to add or change in the Geolocation spec.

Can you take this one? </comment_new>

Fixes #130

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

---

Preview | Diff