domains / families / data / ontology-mapper

ontology-mapper

combined

Map materials science terms, crystal structures, and sample descriptions to ontology classes and properties. Supports any ontology registered in ontology_registry.json. Use when translating natural-language material descriptions to ontology terms, annotating simulation inputs with ontology metadata, or mapping crystal parameters (space group, Bravais lattice, lattice constants) to standardized ontology representations. Map construction data to standard ontologies. Create semantic mappings between different data schemas

When to use

• translating natural-language material descriptions to ontology terms
• annotating simulation inputs with ontology metadata
• mapping crystal parameters to standardized ontology representations
• mapping concepts or terms to ontology classes
• mapping crystal structure parameters to ontology terms
• annotating full sample descriptions

When not to use

• Concept mapping uses string matching and a per-ontology synonym table; it does not understand arbitrary natural language
• Crystal system validation checks basic constraints only (not all crystallographic rules)
• The element resolver recognizes common element names and symbols but may miss unusual spellings
• Bravais lattice aliases cover common usage (FCC, BCC, HCP) but not all crystallographic notation variants

Skill page

Conflict

The two skills share the name 'ontology-mapper' but target completely different domains and procedures. The first maps construction data to building ontologies (IFC, COBie, Uniclass) using a Python class-based approach. The second maps materials science data (crystal structures, space groups) to scientific ontologies (CMSO, ASMO) using a script-based CLI approach. They do not overlap in content, inputs, or outputs, so crowning one would hide a distinct, valid alternative for a different domain.