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
This entails also a general discussion of how we want to support ontology linking in NeXus, because we would want to say something like NeXus:NXmpes???:isInstanceOfPaNet:photoelectron emission (the ??? indicates that is not clear from where the URI location comes, maybe PaNet, maybe NeXus, maybe general OWL?). We could just introduce something like an rdf triple which contains a self, which means that this particular field connected the way described in the triple.
There is also the question: Do we want to spell this out in NXDL or rather write this externally in a separate ontology?
It also goes beyond PaNet. We could also link our terms to other ontologies (or ontology-alike-concepts), e.g., the fairmat materials taxonomy.
One specific feature I would like to see is creating a list of valid enumeration items from an ontology in NeXus.
The text was updated successfully, but these errors were encountered:
We want to link our definitions to the PaNet ontology.
This entails also a general discussion of how we want to support ontology linking in NeXus, because we would want to say something like
NeXus:NXmpes
???:isInstanceOf
PaNet:photoelectron emission
(the???
indicates that is not clear from where the URI location comes, maybe PaNet, maybe NeXus, maybe general OWL?). We could just introduce something like an rdf triple which contains aself
, which means that this particular field connected the way described in the triple.There is also the question: Do we want to spell this out in NXDL or rather write this externally in a separate ontology?
It also goes beyond PaNet. We could also link our terms to other ontologies (or ontology-alike-concepts), e.g., the fairmat materials taxonomy.
One specific feature I would like to see is creating a list of valid enumeration items from an ontology in NeXus.
The text was updated successfully, but these errors were encountered: