You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since abbreviations seem to be the most used terms between scientists we need to have a complete list encoded in the ontology. They need to exist in the more specific techniques that we will assign to beamlines. We need to decide:
if we need abbreviations to be unique or not.
the annotation property we will use to host them
Probably we cannot be sure that abbreviations are unique and sometimes more than one can be assigned to a specific technique.
Also regarding the property that we can use it is a good idea to have a new DataType property :hasAbbreviation (string)
as well as use a skos:altLabel to keep abbreviations. In that way the ontology is compatible with SKOS-enabled tools and reasoners (for concept matching, synonym discovery etc) and can also be used with custom reasoners that take into account our DataType property. We should not be afraid to repeat the information in several fields in an ontology if this improves interoperability and improves semantics.
For now in ESRF we use a unreliable script to collect all abbreviations for all classes and produce a dictionary for the scientists to select and provide information to ICAT and the NeXus file:
Since abbreviations seem to be the most used terms between scientists we need to have a complete list encoded in the ontology. They need to exist in the more specific techniques that we will assign to beamlines. We need to decide:
Probably we cannot be sure that abbreviations are unique and sometimes more than one can be assigned to a specific technique.
Also regarding the property that we can use it is a good idea to have a new DataType property :hasAbbreviation (string)
as well as use a skos:altLabel to keep abbreviations. In that way the ontology is compatible with SKOS-enabled tools and reasoners (for concept matching, synonym discovery etc) and can also be used with custom reasoners that take into account our DataType property. We should not be afraid to repeat the information in several fields in an ontology if this improves interoperability and improves semantics.
For now in ESRF we use a unreliable script to collect all abbreviations for all classes and produce a dictionary for the scientists to select and provide information to ICAT and the NeXus file:
The text was updated successfully, but these errors were encountered: