-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rework NMR instrument manufacturer #12
Comments
We decided that for the time being, we will consider both manufacturers of whole spectrometers and parts as "device manufactures". |
@NRayya should I interpret your last comment that part of resolving this issue is not just reusing OBI:manufacturer and subsume the above listed NMR related ones under there, but also to do the same for the instruments and instrument parts under OBI:device and OBI:NMR instrument repsectively? If yes, we should add this to the description of the issue. |
Done |
While working on the implementation in https://github.com/nmrML/nmrCV/tree/12-rework-NMR-instrument-manufacturer I noticed that we have a class 'NMR instrument vendor' which is defined as an 'instrument attribute' (basically a piece of information) that seems redundant to me, since we already have 'NMR device manufacturer'. Can we deprecate this as part of this issue? |
Working on subsuming existing NMR devices under the respective OBI:device branch entails having to deprecate nmrCV classes that were already defined in OBI (coming originally from the nmrCV crew i.e. Daniel Schober). Now, in the current nmrCV some of these NMR devices are grouped under NMRCV:cardinal part of NMR instrument, but as this class is being dropped when the OBI equivalents are used instead, its semantics gets lost. The solution would be to assert on its children in OBI that they are part of an OBI:NMR instrument which is done in OBI only for OBI:NMR sample tube, OBI:NMR probe and OBI:magic angle spinning rotor. I wil lmake these asserions for now in nmrCV, but since this is considered axiom injection, we will need to get this into OBI in a separate issue. So this is an interim fix, to get this issue resolved. When these axioms are requested by us in OBI we should also use this opporunity to revise the definitions of these classes, as they are not in line with the OBO Foundry best practices. |
We have now a separate issue for vendors: #31 |
It was decided to do the fixes as needed in nmrCV and contact OBI team so that they import our terms and not the other way around as nmrCV is the NMR specific ontology. This will also solve the axiom injection |
To properly document the overlap with OBI, we need to provide a mapping between NMR devices defined in nmrCV and their equivalents in OBI as part of fixing this issue. We will provide this mapping in SSSOM format. |
We decided that for the time being, we will consider both manufacturers of whole spectrometers and parts as "device manufactures".
The text was updated successfully, but these errors were encountered: