Draft
Conversation
Major changes: - Rename fields to snake_case: lp_version, location_type, event_timestamp, media_data, media_type, recipe_type, recipe_payload - Update srs field to require OGC HTTP URI format (http://www.opengis.net/def/crs/...) - Add attributes and attributes_schema fields for structured metadata - Change versioning to full semver (1.0.0) - Update terminology: "attestation" -> "record" for generalization - Add comprehensive README with clear WHY and differentiation from GeoJSON/STAC/KML/Overture Updated files: - README.md: New "Why Location Protocol?" section with comparison table - data-model.md: All base field definitions updated with new names and constraints - schemas.md: Complete JSON Schema with v0.2 field names - composable-fields.md: Snake_case fields + new attributes extension - core-concepts.md: Updated terminology and examples - location-types.md: Updated field references 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
…ement Major messaging fix: - Emphasize LP wraps existing formats (GeoJSON, H3, WKT, etc.) - NOT a 15th competing standard - it's a meta-standard/envelope - Clear 'What Location Protocol Is NOT' section - Focus on adding missing metadata layer (versioning, SRS, verifiability) - Existing formats go INSIDE the location field 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Corrected format from underscore/dot-separated to hyphen-separated: - coordinate_decimal → coordinate-decimal - geojson → geojson-point - h3 → h3-index All identifiers now follow <format>-<type>[+<additional-details>] pattern Updated: data-model.md, schemas.md, location-types.md, core-concepts.md, composable-fields.md, README.md 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
This content was outdated and inconsistent with the main v0.2 spec: - Used different field naming conventions (camelCase vs hyphen-separated) - Had typos (recepient, prooverAddress, folder name itself) - Duplicated EAS integration content now in docs/spec-page/appendices/ - Was tightly coupled to EAS vs the platform-agnostic main spec 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Links to specification/ files needed ../ prefix since workflow.md is in implementation/ directory. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
✅ Deploy Preview for protocol-spec-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…x references
This commit introduces a comprehensive new appendix on Spatial Reference Systems (SRS), URI/URN CRS identifiers, and coordinate order guidance in 'docs/spec-page/appendices/srs.md'. It updates the appendices index ('docs/spec-page/appendices/index.md'), the main documentation index ('docs/spec-page/index.md'), and the MkDocs navigation ('mkdocs.yaml') to add links to the new SRS documentation. This provides authoritative guidance for implementers and ensures the new appendix is properly integrated and discoverable within the documentation.
Member
Author
|
@johnx25bd, After doing a little bit of a deep dive today on the change for the srs field, and 💯 agree with using URI in lieu of short-hand codes. I ended up creating a new appendix resource page discussing spatial reference systems, since I know it's a bit of a gray area for many users. When you get a chance, please review and let me know if there are any modifications and/or additions. |
Member
Author
|
What's the reasoning for renaming the fields from |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.