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:
- 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.
- 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>
}
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:
{ "schema": "https://raw.githubusercontent.com/bjb2/FlowMD/refs/heads/main/schema/flowmd-v0.json", ... <rest of file> }