Skip to content

Context URLs are redirects to GitHub and do not return context files. #62

@BigBlueHat

Description

@BigBlueHat

I was exploring some of the examples in the VEX spec and trying to use them on the JSON-LD Playground, but quickly found that the context URL used in the examples and the spec does not dereference properly as it redirects to this repo.

The Playground says:

Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context. URL: "https://openvex.dev/ns/v0.2.0".

Since the domain is owned by this group, it's hopefully an easy fix--especially if you put something like Cloudflare in front of your Squarespace hosting so you could further manage headers and redirects.

The end result should be that https://openvex.dev/ns/v0.2.0 responds with (or redirects to) the latest context.json file which in this case is https://raw.githubusercontent.com/openvex/spec/refs/heads/main/ns/v0.2.0/context.json

There are also options with using Link header retrieval, but that's trickier to setup than a raw redirect (which is where something like Cloudflare comes in handy).

At any rate, I wanted (as one of the JSON-LD WG Chairs) to offer support to help improve the DevEx.

Cheers!
🎩

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions