| vizualization |
Add "visualisation", "visualization" to SoftwareFeature presentationVisualisation.jsonld |
Instance name is scoped to "presentation" visualisation; the Wikidata cross-reference supports the broader concept, but that widens the instance's intended scope. |
| Multi-platform software |
Add "multi-platform"/"cross-platform"/"multiplatform"/"crossplatform" to OperatingSystem platformIndependent.jsonld |
"Platform independent" is a stronger claim than "multi-platform": a platform-independent software is multi-platform but not vice versa. So this isn't a strict synonym. But the Wikidata entry itself discusses both terms together, which is the main argument for treating them as interchangeable in practice. |
| head fixation / head-fixed |
Add "head-fixed", "head fixed" to SubjectAttribute headRestrained.jsonld |
"head-fixed" is probably narrower than "head-restrained". So this may fit better as its own SubjectAttribute instance than as a synonym here. Or add "head-fixation" as a new Technique instance? |
| Supercomputer |
Add "supercomputer" to OperatingDevice highPerformanceComputer.jsonld |
The instance's Wikidata entry points to "supercomputer," but "supercomputer" (one machine) and "HPC" (a cluster) aren't strictly interchangeable. |
| neural-mass / Neural mass |
Add "neural mass"/"neural-mass" to ModelAbstractionLevel populationModelling-neuralMass.jsonld |
Short form, but dropping the "population modelling:" prefix may make the synonym too generic outside this specific abstraction level. |
| Cornu Ammonis |
Add "Cornu Ammonis" to NervousSystemStructure AmmonsHorn.jsonld |
Latin term but only appear as a related synonym in http://purl.obolibrary.org/obo/UBERON_0001954 |
| spiking networks / Spiking neural network |
Add "spiking network", "spiking neural network", "SNN" to ModelAbstractionLevel spikingNeurons.jsonld |
Standard ML/computational neuro terms, but "network" (an architecture) vs. "neurons" are not strictly interchangeable. The instance's own definition already says "modelling neural networks..." |
| Median raphe |
Add "median raphe" to NervousSystemStructure medianRapheNucleus.jsonld |
Not strictly synonymous but dorsalRapheNucleus.jsonld already has "dorsal raphe" as a bare short-form synonym, and midbrainRapheNuclei.jsonld has "midbrain raphe", so the short-form pattern is established elsewhere. |
| time series data |
Add "time series data" to DataType timeSeries.jsonld |
DataType.table already has "tabular data" as a synonym (bare noun → "data"-suffixed form). So this pattern is established in the same schema |
| corticopontine projections |
Add "corticopontine projections" to NervousSystemStructure corticopontineFibers.jsonld |
openMINDS uses "projection" and "fiber(s)" interchangeably elsewhere (e.g. neuronProjectionBundle), but that's inferred precedent, not a documented equivalence rule. |
| Intracardial perfusion |
Add "intracardial perfusion" to Technique transcardialPerfusionTechnique.jsonld |
To be treated as synonymous? Or add a new instance? |
| Population models |
Add "population model" to ModelAbstractionLevel populationModelling.jsonld |
Noun-form variant, but shifts from a process/approach ("modelling") to a product/instance ("model"). NB: "statistical model" sits alongside "population modelling" in the same terminology. So the schema itself already mixes both forms as legitimate instance names |
| JSONLD |
Add "JSONLD" to ContentType application_ld+json.jsonld |
The instance's own name follows the formal IANA syntax ("application/ld+json"), but it's not clear how strictly that format is meant to extend to the synonym field |
| NWB |
Add "NWB" to ContentType application_vnd.nwb.nwbn+hdf.jsonld |
Same question as JSONLD above |
| V1 |
Add "V1" to NervousSystemStructure primaryVisualCortex.jsonld |
Is it a strict synonym or too ambiguous? |
| two-photon imaging |
Add "two-photon imaging" to Technique twoPhotonFluorescenceMicroscopy.jsonld |
Is "imaging" specific enough to this Technique, or too generic to add safely? |
Context
We reviewed candidate synonyms for existing openMINDS controlled terms, drawn from
TermSuggestionand frequently-used NWB keywords not yet covered by the vocabulary. This issue collects the cases judged not trivial (where the target instance, scope, or synonym validity is debatable) for discussion before any are added.Trivial cases are addressed in PR #525
Candidates for discussion
Feedback welcome on any of the above.