Skip to content

Document server.json #90

@tadasant

Description

@tadasant

We have a starting point for this, but we should:

  • Formally define what is and is not valid in this JSON
  • Make sure we have some mechanism for versioning the schema, because it's very likely to evolve over time (especially as non-registry initiatives start to prioritize defining the notion of static server data)

Metadata

Metadata

Assignees

No one assigned

    Labels

    go-live blockerThis issue is one we need to address prior to initial go-liveproduct requirements workUpstream of development work

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions