Erdal Karaca

> > Additional observations from trying to test functionality in other modules: > > Missing functionality: > > * `BIDSLayoutFile.get_df` > > * `get_dict` > * `get_entities` > * `path`...

> @erdalkaraca yes it is a higher-level API that requires reading in the `_events.tsv` files. > > It is independent than the querying/indexing functionality. I will admit in hindsight its...

An example of how a coherent schema might look like using Yamale: ```yaml Dataset: .extends: Folder subjects: list(include('Subject'), required=False) dataset_description: include('DatasetDescriptionFile') README: include('File', required=False) CHANGES: include('File', required=False) LICENSE: include('File', required=False)...

Example definitions of entities: ```yaml - key: subject name: Subject entity: sub description: | A person or animal participating in the study. type: label - key: run name: Run entity:...

Example metadata fields definitiones: ```yaml - name: AcquisitionDuration description: | Duration (in seconds) of [...] type: min: 0 unit: s - name: AnatomicalLandmarkCoordinates description: | Key:value pairs of any [...]...

@Tokazama At https://github.com/ANCPLabOldenburg/ancp-bids with have experimented with several "systems for schemas": - XSD, JSON Schema, YAMALE/Yaml XSD is very verbose and "noisy" meaning it is not very convenient for humans...

Well, as also mentioned, Yaml is more compact and has some more features that JSON does not provide such as mixing documents from different namespaces which is called TAGs in...

In BIDS we have the RECOMMENDED type fields which are neither covered by YAMALE nor XSD and I guess also not by JSON Schema. Unfortunately, the author of YAMALE refused...

> > Furthermore, that schema definition is used to generate Python code which allows type safe programming against the BIDS schema. For example, all entities (directly read from the new...

BTW, you can find the generated code here: https://github.com/ANCPLabOldenburg/ancp-bids/blob/main/ancpbids/model_v1_7_0.py I am not yet sure, but I think this approach will also allow to have future schemas co-exist next to each...