Skip to content

Protocol registry: specification availability #257

@martinthomson

Description

@martinthomson

The inclusion criteria lists "MUST be defined in a specification which is freely and publicly available" as a requirement. This is good, but it is not sufficient as stated.

I request that this be extended to transitively include all normative dependencies of the referenced specification. Having chased other specifications into a maze of paywalls, this is a genuine problem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    registryregistry related

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions