json-ld/json-ld.org

Hi all,

Mostly from curiosity, I'm trying to find a JSON-LD pattern that let's me use nested node identifier indexing so that URI paths match their corresponding JSON Pointer.
For example, suppose I have the following JSON-LD document, representing Oregon cities, and hosted at the root of https://oregon.gov

    {
        "@context": {
            "@version": 1.1,
            "@vocab": "https://rels.org/",
            "@base": "http://oregon.gov/cities/",
            "path":"@id",
            "cities": {
                "@id": "city",
                "@container": "@id"
            },
            "neighborhoods": {
                "@id": "neighborhood",
                "@container": "@id"
            },
            "buildings": {
                "@id": "building",
                "@container": "@id"
            }

        },
        "@id":"#",
        "cities": {
            "portland": {
                "@context": {
                    "@base": "portland/neighborhoods/"
                },
                "neighborhoods": {
                    "laurelhurt": {
                        "@context": {
                            "@base": "laurelhurt/buildings/"
                        },
                        "buildings": {
                            "ice-cream-shop": {
                                "path": "/cities/portland/neighborhoods/laurelhurt/buildings/ice-cream-shop"
                            }
                        }
                    }
                }
            }
        }
    }

This document captures what I intended: the URI of "ice-cream-shop" is http://oregon.gov/cities/portland/neighborhoods/laurelhurt/buildings/ice-cream-shop. Its URI path is /cities/portland/neighborhoods/laurelhurt/buildings/ice-cream-shop, which also happens to be its JSON pointer within the document. This is fun, because it lets clients with no JSON-LD processing capability infer the path structure directly from the document.

The only trouble are those nested @contexts. Currently they get lost if I attempt to do any kind of framing, and I can't see how to "hoist" them up to the parent document's @context because they depend on the identifier index of the node they belong to. The current approach effectively uses nested @contexts to build up a stack of @base path fragments.

Is there any way to address this use case without relying on nested @contexts?

Thanks!