Schema Drift: Incompatible Location Attestation Representations

[johnx25bd]

Priority: Critical

Description

There are at least three incompatible representations of the "location attestation schema" within the documentation:

1. /api/v0/config response shows schema_fields as:

uint256 eventTimestamp, string srs, string locationType, string location,
string[] recipeType, bytes[] recipePayload, string[] mediaType,
string[] mediaData, string memo

2. Location Protocol v0.2 documentation lists fields like:

• lp_version
• location_type
• location as bytes
• srs as OGC URI

3. Records API examples show:

• event_timestamp
• location_type (e.g., geojson-point)
• location as stringified GeoJSON
• extracted longitude/latitude fields

This inconsistency undercuts trust and makes it impossible for developers (or LLMs) to know which representation is authoritative.

Fix Direction

• Pick a single "canonical schema shape" for v0.2 in the documentation
• Create an explicit mapping table showing: spec version → deployed schema → API response format
• Cross-link to the authoritative spec at https://github.com/DecentralizedGeo/location-protocol-spec/tree/v0.2-draft
• Deploy version 0.2 conformant schemas for internal consistency across the architecture

Related

• References Location Protocol v0.2 spec