Comments (12)
Roy is around but now only looking at e-mail about once a week.
from p01.
Here are some other examples I’m unsure how to model. These parameters involve calculations (sums, ratios, indices/other calculation) with more than one chemical entity
The parameter is 'concentration of ammonium-N and nitrite-N (NH4 + NO2)-N'
- What would the property (S06) be?
- What would go in the chemical entity (S27)?
Parameter ‘anion storage capacity’
3. What would the property (S06) be?
4. What would go in the chemical entity (S27)?
and there are more examples ......
P buffer index (PBI)
phosphorus buffering capacity (PBC)
P saturation ratio
Colwell-P/PBI (ColP) ratio (ratio of two soil P results)
Cation exchange capacity (CEC) and Exchangeable Cation Exchange Capacity (ECEC) – (depending on the method, these re different calculations using elements Ca2+/Mg2+, Na+, K+ - calculations specified as part of method)
Base saturation percentage (BSP)
Ratio of calcium to magnesium (Ca2+/Mg2+) (a ‘basic cation saturation ratio’)
from p01.
Over in nvs-vocabs/S06#74 (comment) we have a parameter that we are unsure how to model using the semantic model.
The parameter is 'ratio of X/Y in the sample'.
- what is the S06 'property'
- how do we link chemicals X and Y into the parameter definition?
@roy-lowry surely you have seen this before?
Hi @dr-shorthair Sorry for slow response I was on leave and Roy must be away too. We have 3 types of vocabularies to define the "object of interest" of a measurement variable: one for when the object of interest is a biological entity (S25), one when it is a chemical entity (S27) and one when it is a physical entity or anything that is neither a chemical nor a biological entity. The latter is the S29 vocab. This is where we decided to define ratios of chemical substances. See examples such as: http://vocab.nerc.ac.uk/collection/S29/current/PE001382/
As you will see we used the SKOS core#related property to link the S29 entity to its S27 components.
from p01.
@dr-shorthair There are existing examples of chemical ratios such as CNWCXX10 that are either 'Atomic ratio' or 'Mass ratio'. Couldn't find any examples of 'Concentration ratio' though. You could have a look at the modelling for these for a precedent.
@meganrwong There are many examples for summed concentrations of multiple chemical species such as NTRZMOD1, which (ignoring the 'N' issue) is similar to your example.
from p01.
@meganrwong I was going to answer and I see that Roy has just done so.
from p01.
Thx @gwemon and @roy-lowry - that clarifies a lot. Anything that isn't a chemical or biota is a physical entity (including ratios).
I now see that some, though not all, of the S29 chemical ratios have explicit related
links to their component concepts from S27 - compare http://vocab.nerc.ac.uk/collection/S29/current/PE001378/ with http://vocab.nerc.ac.uk/collection/S29/current/PE001391/.
However, it is not clear how this relates to the Semantic Model.
As you know, I have implemented the Semantic Model as an OWL/RDFS ontology - see https://github.com/CSIRO-enviro-informatics/PUV-ont/blob/main/README.md.
In particularly, see the summary https://raw.githubusercontent.com/CSIRO-enviro-informatics/PUV-ont/main/image/puv-Parameter.png
This provides semantic labels to the relationships between the elements of the parameter definition.
Looking at the way you are composing a Physical Entity
for a ratio of Chemical Entities
, and a sum of entities, it appears that a couple of relationships are missing from the Semantic Model, at least as it is shown in the summary diagram.
- Is the summary diagram complete, or are there some additional relationships that should be incorporated in the RDF implementation?
- In particular
- if
Chemical Substance (S27)
was also a sub-class ofPhysical Entity Component
, then aPhysical Entity
could refer refer to the entities to build ratios, etc - if there was an
is composed of
link fromChemical Entity
back to itself, this would allow for entities that are composed of multiple chemical species for summed concentrations etc.
Finally,
3. in our application, there are a variety of 'qualifiers' of chemicals used, including soluble
, exchangable
, pseudo
, oxidisable
, extractable
, reducible
, titratable
. Do you think these should be included in separate S27 entities, in the same way that you have Organic
carbon and easily-reducible
total iron
from p01.
Thanks everyone. I appreciate your very helpful responses @roy-lowry and @gwemon
Simon has covered all of the follow up questions we have
I am following with interest :) Thanks again
from p01.
Thanks @meganrwong @dr-shorthair Indeed it would be good to add this to the semantic model. We also need to consider this in the framework of the latest developments with the I-ADOPT model. Maybe we could have a short meeting so that we can put your work in context with what we are currently working on?
from p01.
Thanks for all the thought folk, this has been giving the model and its application a good workout. I've had to make a decision re our soil chem so logged it here -
#ANZSoilData/def-au-parameters/issues/6
Also, discussion prompted this issue #ANZSoilData/def-au-parameters/issues/5
from p01.
also added the chem qualifiers question over at repo for soil chem parameters for use in Aust National Soil Info System (ANSIS)
from p01.
Thanks @meganrwong @dr-shorthair Indeed it would be good to add this to the semantic model. We also need to consider this in the framework of the latest developments with the I-ADOPT model. Maybe we could have a short meeting so that we can put your work in context with what we are currently working on?
Hi Gwen - noted :) - Simon was reflecting on pts 1 and 2 above
from p01.
How about this:
![image](https://private-user-images.githubusercontent.com/608303/239823678-2b03c54d-af62-4128-9452-08df2fd0647e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk3OTgyMDYsIm5iZiI6MTcxOTc5NzkwNiwicGF0aCI6Ii82MDgzMDMvMjM5ODIzNjc4LTJiMDNjNTRkLWFmNjItNDEyOC05NDUyLTA4ZGYyZmQwNjQ3ZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzAxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcwMVQwMTM4MjZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hYThlZmU3ZWU4MjgwYjlmYzFiZGE5ZmUyYjg4MGZmZWM0NDUxNzY1NmU2MDM2ZjJmN2NhNTJhNzYyOTU0ZGM1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.lq_Xw-_XfzPCaKdSuF5gMFEPl6_fh2e3vYAI0v_zdfc)
Note: puv:ChemicalEntity
== "Chemical Substance (S27)"
In which case we could see
<http://vocab.nerc.ac.uk/collection/S29/current/PE001378/> a puv:PhysicalEntity ;
skos:prefLabel "neodymium-143/neodymium-144" ;
[...]
puv:isComposedOf <http://vocab.nerc.ac.uk/collection/S27/current/CS002797/> ,
<http://vocab.nerc.ac.uk/collection/S27/current/CS003788/> ;
.
and
<http://vocab.nerc.ac.uk/collection/S27/current/CS026905/> a puv:ChemicalEntity ;
skos:prefLabel "nitrate+nitrite" ;
[...]
puv:isComposedOf <http://vocab.nerc.ac.uk/collection/S27/current/CS002879/> ,
<http://vocab.nerc.ac.uk/collection/S27/current/CS002877/> ;
.
Using the same predicate all round still doesn't reflect the maths, but does provide explicit links to the component chemicals, which would help with some functions (e.g. discovery).
from p01.
Related Issues (20)
- NTR Depth of shell (BODCNVS-1232) HOT 3
- NTR Width of shell (BODCNVS-1232) HOT 1
- Remodeling Specimen weight terms into new semantic model HOT 1
- NTR: Request for batch of P01 terms - chemical substances in bulk sediment [BODCNVS-1912] HOT 2
- NTR Relative cover to be used for macrophytes, corals, macroalgae (BODCNVS-1232) HOT 1
- Deprecated: pH P01 codes related to spectrophotometry and internal/external sensors
- NTR: New P01 Beta backscattering terms required - volume scattering coefficient [BODCNVS-2066] HOT 4
- New parameter codes for parameters collected by AUV navigation sensor [BODCNVS-2101] HOT 5
- NTR: abundance of sequence reads [BODCNVS-2107] HOT 10
- NTR: Batch of new P01s required for ICES contaminants [BODCNVS-2058] HOT 4
- Question on P01 code for count OCOUNT01 [BODCNVS-2121] HOT 3
- New terms contaminants in biota P01 terms loaded [BODCNVS-2045] HOT 1
- New P01s: pH(T) ISFET internal & external electrodes with corrections [BODCNVS-2149] HOT 1
- New P01 codes for NRT Autosub [BODCNVS-2087]
- Remodelling and migration of outstanding P01 codes from P02 grouping [HEAD](https://vocab.nerc.ac.uk/collection/P02/current/HEAD/) HOT 5
- NTR: new P01 Concentration of O2 (umol/kg) from secondary sensor [BODCNVS-2183]
- Remodelling and migration of remaining P01 codes from P02=[LITH](https://vocab.nerc.ac.uk/collection/P02/current/LITH/) HOT 1
- Change P02 mapping of P01 code P200M00Z (abundance of dinoflagellates) from PATX (taxonomically identified) to PNTX (non-taxonomically identified) (BODCNVS-1192) HOT 2
- Remodelling and migration of relative humidity codes HOT 1
- NTR: two new terms for internal temperatures of Precision Infrared Thermometer [BODCNVS-2254] HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from p01.