Skip to content

How should the spec handle metadata about a schema? #4

@nsheff

Description

@nsheff

We've had some discussion today (and in the past) about what information someone would want to know about a schema. For example, what is its "latest version", who is the author, who is the maintainer, what is it used for, what standards does it use, etc.

Do we want to have a "tags" system? This way you would add a tag to a schema, making it pretty flexible; but then that could cause fragmentation?

Are some terms "higher tier" which are required, or stuck onto the object as attributes rather than tags? How do we decide which are these?

This is a large question and could require some detailed thought. For an initial look, we put metadata about schemas as "maintainer" and "latest_version" only. This could be revisted.

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