Skip to content

The published SDL schema $id returns 404 #1516

Open

Description

@doublewhy

Problem

Every published schema under contracts/schemas/ (135 files on dev a4357f9a) declares an $id under https://openrae.github.io/rae/schemas/, for example https://openrae.github.io/rae/schemas/sdl-authoring-input-v1.json. Nothing serves those URLs. The Pages deployment uploads only the Sphinx output, docs/_build/html (.github/workflows/docs.yml:50-52), which has no schemas/ directory. On 2026-10-12, curl -L returned HTTP 404 for the SDL authoring schema and for experiment-task-v1.json, while https://openrae.github.io/rae/ returned 200. The #1412 feasibility study in #1452 observed the same 404 on 2026-10-09 (evidence row S4).

An editor or YAML language server that resolves the schema by its $id, as the study's prototype extension does for *.sdl.yaml, cannot fetch it.

The $id also names no release. The schema at tag v6.0.1 has 45 top-level properties and no execution_policy; on dev it has 46, including execution_policy (evidence row S5). A document that is valid against the dev schema, such as name: demo with execution_policy: {}, is rejected by raes 6.0.1. Serving one file at the unversioned $id would therefore describe only one of the two.

Scope

  • Serve the published schemas at their $id URLs from the docs deployment, or change the $id values to URLs that are served.
  • Decide which release line the unversioned URL describes (the released main line or dev), and record it where the schemas are documented.

Done when

  • curl -L on the $id of sdl-authoring-input-v1.json and of a sample of other published schemas returns 200 with the schema's content.
  • The documentation states which release the served schemas describe, and the served sdl-authoring-input-v1.json matches it.
  • A docs-lane or release check fails when a published schema's $id would not be served.

Related

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions