Standard for VEX document discovery

[openvex]

Standard for VEX document discovery

[puerco]

I love it @micahhausler.

Regarding the format, one of the goals we want with OpenVEX is that once you discover one document, the format itself can provide links to the rest of the relevant statements using its linked data capabilities.

One of the features we're thinking of adding to OpenVEX is support for references to link to other documents. One of the use cases this will unlock is to have "empty" OpenVEX documents - that is docs without any VEX statements - that only reference other documents. For example (this is just an idea no proposal exists yet for this):

{
  "@context": "https://openvex.dev/ns/v0.2.0",
  "@id": "https://openvex.dev/docs/example/vex-9fb3463de1b57",
  "links": [
      {"ref": "https://myurl.com/index.openvex.json"},
   ]
}

Using that schema, you can reference another document with relevant statements, but also you could point to an OpenVEX API endpoint or a continuously appended document (like an index) with links to known documents. For example:

{
  "@context": "https://openvex.dev/ns/v0.2.0",
  "@id": "https://myurl.com/index.openvex.json",
  "links": [
      {"ref": "https://myurl.com/document1.openvex.json"},
      {"ref": "https://myurl.com/document2.openvex.json"},
      {"ref": "https://myurl.com/document3.openvex.json"},
   ]
}

It would be awesome to fast forward this, the .well-known URL could respond with these documents.