w3c / w3c/json-ld-syntax

how to "retype" rdf:JSON to geo:geoJSONLiteral?

Open
#425 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

spec:enhancement
Dominant language
HTML
Stars
139
Forks
23
PR merge metrics
No merged PRs in 30d

Description

https://w3c.github.io/json-ld-syntax/#json-literals shows how a piece of the JSON can be captured as datatyped literal "..."^^rdf:JSON

@situx @nicholascar @mathib @dr-shorthair
https://github.com/opengeospatial/ogc-geosparql/issues/1 discusses the new GeoSPARQL 1.1 geo:geoJSONLiteral. According to the standard, such geometry serialization must both be connected by a specific property, and carry a specific datatype:

<geometry> geo:asGeoJSONLiteral "..."^^geo:geoJSONLiteral

@gkellogg Is it possible to somehow "retype" a rdf:JSON literal to a specific datatype geo:geoJSONLiteral?
It's easy enough to do this post-factum (eg with a SPARQL update), but seems unsatisfactory...

Perhaps something like this can be added:

"@context": {
    "@version": 1.1,
    "geo": "http://www.opengis.net/ont/geosparql#",
    "myGeom": {"@id": "geo:asGeoJSONLiteral", "@type": "@json", "@json": "geo:geoJSONLiteral"}
}

Notice the last key: this is similar to "@nest": "labels" in https://w3c.github.io/json-ld-syntax/#example-defining-property-nesting

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the JSON-LD 1.1 JSON literals section and the GeoSPARQL 1.1 geo:geoJSONLiteral definition linked in the issue, then compare them with the proposed @context syntax. Determine whether retyping rdf:JSON is supported or requires a specification change. Done means a documented resolution with any needed syntax or examples agreed by the working group.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.