Skip to content

type entry in JSON can cause major issues #1

@iamt4nk

Description

@iamt4nk

When thinking about the schema in general, "type" is a little redundant as the whole schema is based around that "type" (being FlowMD). I would suggest "type" being removed completely from the schema for two reasons:

  1. When specifying type in an object, it doesn't work well because "type" is a built-in for pretty much every programming language I know of. This can cause issues when attempting to build parsers.
  2. The proper "JSON" way of establishing a type is by specifying the schema at the beginning of the file. Something like:
{
  "schema": "https://raw.githubusercontent.com/bjb2/FlowMD/refs/heads/main/schema/flowmd-v0.json",
  ... <rest of file>
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions