A file analysis results produced by a secondary analysis pipeline.
$ jsonschema install https://schemas.sourcemeta.com/humancellatlas/metadata/v5.0.0/type/file/5.0.0/analysis_file schemas/analysis_file.json$ref: "https://schemas.sourcemeta.com/humancellatlas/metadata/v5.0.0/type/file/5.0.0/analysis_file"import schema from "https://schemas.sourcemeta.com/humancellatlas/metadata/v5.0.0/type/file/5.0.0/analysis_file" with { type: "json" };| Identifier | https://schemas.sourcemeta.com/humancellatlas/metadata/v5.0.0/type/file/5.0.0/analysis_file |
|---|---|
| Base Dialect | Draft4 |
| Dialect | http://json-schema.org/draft-04/schema# |
| Health | |
| Size | 0.001088 MB |
This schema declares 0 examples.
This schema has 8 quality errors.
/descriptiondescription_trailing_periodDescriptions should not end with a period to give user interfaces flexibility in presenting the text
/properties/describedBy/descriptiondescription_trailing_periodDescriptions should not end with a period to give user interfaces flexibility in presenting the text
/properties/file_core/typedraft_ref_siblingsIn Draft 7 and older dialects, keywords sibling to $ref are never evaluated
/properties/file_core/descriptiondescription_trailing_periodDescriptions should not end with a period to give user interfaces flexibility in presenting the text
/properties/schema_type/enumenum_with_typeSetting type alongside enum is considered an anti-pattern, as the enumeration choices already imply their respective types
/properties/schema_type/descriptiondescription_trailing_periodDescriptions should not end with a period to give user interfaces flexibility in presenting the text
/properties/schema_version/exampleunknown_keywords_prefixFuture versions of JSON Schema will refuse to evaluate unknown keywords or custom keywords from optional vocabularies that don't have an x- prefix
/properties/schema_version/descriptiondescription_trailing_periodDescriptions should not end with a period to give user interfaces flexibility in presenting the text