Skip to content

Failure to identify violation of Inheritance Principle #2224

@Lestropie

Description

@Lestropie

Related to bids-standard/bids-specification#2155.

Aware that this issue, or the others linked below, may not be rectified in the legacy validator due to deprecation; posting here nevertheless for completeness.

Singular failure unique to legacy validator

For a given data file, it is not permissible for there to be multiple applicable JSON metadata files at a single filesystem hierarchy level.
The legacy validator fails to identify this issue in datasets: ip112e1bad, ip170e2, ipmultielfce1v2, as provided in: bids-standard/bids-examples#504.
This applies to BIDS versions 1.1.2 (first online), 1.7.0 (change to Inheritance Principle), 1.10.0 (latest).
The schema-based validator correctly flags these datasets as being in violation.

Failures common to both validators

To avoid replication, and given that there are no issues present in the schema-based validator that are not also present in the legacy validator, I am going to post the list of issues that I have observed that are common to both validators over on the schema validation repository and link here.

Edit: bids-standard/bids-validator#217

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