How to attach "what is being modelled (ion channel, brain region,..." to a model (emodel, ...)" about nexus-bbp-domains

[apdavison]

I think modelOf should point to ontology terms, e.g.

{
    "path": "nsg:brainRegion",
    "name": "Brain region",
    "description": "Brain region",
    "node": "{{base}}/schemas/bbp/core/typedlabeledontologyterm/v0.1.0/shapes/BrainRegionOntologyTermShape",
    "minCount": 1
},

{
    "path": "nsg:cellType",
    "name": "Cell type",
    "description": "The cell type.",
    "node": "{{base}}/schemas/bbp/core/typedlabeledontologyterm/v0.1.0/shapes/CellTypeOntologyTermShape",
    "maxCount": 1
}

The idea of distinguishing model and modelinstance is to have an easy way to conceptually and practically group together different versions and parameterizations of the same model, something like how a Github repository groups together different versions of some piece of software.

"Model Project" would be a possible alternative for what I have been calling "Model" (i.e. it would meet the functional need, although the concepts are not quite the same and I prefer "Model")

[MFSY]

Thank you @apdavison .
I agree for taking values of nsg:modelOf from controlled vocabularies. If we can know the current known list of 'modelOf' values that would be great.

It would be great if we could have examples of a model (with the attributes examples) and a model instance.