-
Notifications
You must be signed in to change notification settings - Fork 52
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
NTR: Australian Soil Classification #825
Comments
Since soils are being discussed again #895 #894 perhaps this one could get a kick along.
|
I wonder if someone could help me tease these apart for axiomatization? @kaiiam |
Hey @dr-shorthair thanks for bringing this up again. I think this is in ideal place for us to begin implementing ROBOT templates, by creating a The proposed
@pbuttigieg @cmungall let me know what you think of this idea testing the ENVO ROBOT waters with a soil template. |
I may be misunderstanding, but the textual definitions look pretty hard to turn into logical axioms. Is there really a use case for these. (see the section "beware of over-axiomatization" in this doc -- https://docs.google.com/document/d/1nxMDJkU_eyCdBhy7-RMSLSMEHRsk3udrOKNIJPHZTQ4/edit#heading=h.pariap1j3foa -- this will become a post) What about a more incremental approach. Get your table in with the only logical axiom being subClassOf some soil. Then we can iterate on logical axioms
I'm not sure this is the best place to put this into practice? I think a lot (most?) of your proposed logical axiom slots would be blank for most of these types? Sorry to be boring but I would just fire up Protege, add in these terms as subclasses of soil, add the codes as xrefs, and add the definitions, with provenance. Logical axioms and templates will be fantastically useful for the Zobler definitions as requested in #995 https://github.com/microbiomedata/nmdc-metadata/blob/master/identify/Zobler_Definitions.txt#L20-L127 These are compositional, consisting of a qualifer (e.g. humic) and a core coil type (e.g. acrisol). I would use dosdp for compositional classes. |
@cmungall sounds reasonable, I was (and probably still am) overly enthusiastic about ROBOT and DOSDP. Thanks for the link to the post, reading the next one I see that you are discouraging the use of @dr-shorthair are we wrong here, are you confident about making such logical statements and would there be a need for them? Would incorporating these terms as subclasses of soil suffice for now? For future projects I am very interested in employing DOSDPs with equivalence classes to create compositional classes for which we can achieve rector normalization and maybe "learn more" when reasoning. From my understanding of @cmungall's posts, there can be some danger in overdoing equivalence classes, but as I understand it, equivalence axioms are required to infer novel subsumption hierarchies when reasoning (is this correct?). Is it possible there is some middle ground where we could axiomatize more of our classes in a consistent way as to enable the reasoner to discover hierarchies instead of asserting them? Perhaps for classes like |
Sub-classes of Soil is what they are. So I see no harm, and some benefit, in doing the simple thing now. It would achieve my original goal which is to remind the ENVO community of the fact that there are multiple alternatives around, some of which are well described and systematized, though not axiomatized ;-) So more axiomatization can be something we work on when we are ready (and I'm more experienced). |
Here are the definitions of the orders in the Australian Soil Classification - as revised in 2021: https://www.soilscienceaustralia.org.au/asc/soilkey.htm Note the introduction of a new Order - RE (Arenosols) - which replaces parts of the CA (Calcarosols), TE (Tenosols) and RU (Rudosols). I mentioned this over in #333 |
Also available as SKOS+ for download at https://vocabs.ardc.edu.au/viewById/629 |
If I get the opportunity to work for USDA next year and they allow me to work on this I'd try to take this on then. Otherwise others including @dr-shorthair if you want to make a pull request following the ENVO-Robot-template-and-merge-workflow it's available for people to work through and prepare terms with. |
IDrange request at #1365 |
Thanks @dr-shorthair for preparing this very quickly! I hope the template format was helpful. This is quite a large request so I think it might take some time to review. I think there are some small changes to get things to fit with ENVO's label (lowercase) and definition conventions. I don't have a ton of free time at the moment, but I'll try to get back to this when I have time. Anyone else please feel free to have a look at Simon's Robot template |
The textual definitions are copied directly from the sources cited. I think they are essentially cast in the class/differentia form, though in some cases there are multiple differentia with an OR connector. Apologies I overlooked the label-case convention. |
It looks like a large request indeed - >100 classes.
I added a couple of pointers over to the equivalent, or more or less equivalent US orders, but that's all. I agree that the definitions are a bit sprawling, but structurally they do follow the sub-class/differentia pattern. |
Ping @kaiiam - just a tickle to see if there is an ETA on this? |
Thanks @dr-shorthair I'm between jobs at the moment, so on vacation not working. As for the terms, ENVO is pretty strict about definitions and would ask for term contributions to be formatted following our standards, see https://github.com/EnvironmentOntology/envo/wiki/Creating-good-definitions. If you can or you have anyone who can help format them in the robot template please do so. If not I can try to get to it later. Hope that helps. |
Most of the definitions do satisfy the rules, but are a bit wordy. I think I can extract and tweak the first sentence to get there. I moved all the original defs to the |
The original definitions are very thorough it's more a formatting thing we prefer things be very strictly in the form "A is a B which C's". Moving the original definitions to comments is great and we can extract a more concise genus differentia form. I think like you say most are close to that. We can pretty easily get it there. We can easily swap out "that" for "which" for many. Also the label conventions in ENVO are to be lowercase e.g., |
I've fixed the labels to be lower case. |
On another issue (#1375) @dr-shorthair asked about definitions by exclusion. I think these are problematic but if this is what the authoritative source says then we try and fit them to genus-differentia form, e.g. "A G which is not a X1, X2, X3, and which Y1, ...". I don't think this should be a blocker. |
I know this issue has been open a long time but I feel we should have asked some more questions from the outset
E.g there is a very large USDA soil taxonomy guide This also includes a lot of concepts for things like soil materials, horizons, that would inform the soil definitions themselves. |
Some of the 'orders' are the same, but most are somewhat different. This is partly a result of culture and history, but is also because a different geological and environmental setting actually means that the soils are different, or at least that we need to have a more refined classification for some parts of the spectrum than what is needed in other geographic contexts. Note that the Australian Soil Classification was revised and reissued in 2021, so this is not a stale classification.
My original goal was to supplement the the presentation of the The USDA definitions can certainly be used to formalize the differentia, but I don't think we are there yet. |
On further investigation, it looks like the ENVO soil classification largely follows the 2015 IUSS WRB system which was primarily European. So my claim about Scientific imperialism was inaccurate. The US and ANZ systems both have a different set of top-level 'orders', and there are a number of others - https://www.fao.org/soils-portal/data-hub/soil-classification/national-systems/en/ . |
There is a lot of info in this thread. I'm trying to get a handle of whether this a difference in labeling (i.e., lexicon) or something deeper. For example, in the dental domain (for humans), 'wisdom tooth' and 'third molar' refer to the same type of tooth; 'Tooth 1' in the ADA tooth numbering system and 'Tooth 18' in the FDI numbering system refer to the same type of tooth. Which label you use for a tooth depends on the context in which you are operating. Is something like this going on with soil classification? |
@wdduncan you are right there is a lot going on. I'm trying to tease things out into more actionable issues: |
There is a mapping ('approximate correlation') between the ASC and some other classifications including the WRB here: https://www.soilscienceaustralia.org.au/asc/append5.htm In an email to me, the editor of ASC Noel Schoknecht notes the following:
Another colleague Gerard Grealish advises
So it may be that the approach suggested by @cmungall in #1377 must be used with extreme caution. |
New issue to follow up topic raised in #333 (comment)
The Australian Soil Classification [1] has the following top-level orders:
AN Anthroposols
CA Calcarosols
CH Chromosols
DE Dermosols
FE Ferrosols
HY Hydrosols
KA Kandosols
KU Kurosols
OR Organosols
PO Podosols
RU Rudosols
SO Sodosols
TE Tenosols
VE Vertosols
A turtle file containing the definitions from [1] expressed as skos:Concepts is provided [2], which includes a license from CSIRO Publishing.
[1] http://www.publish.csiro.au/book/7428
[2] ASC-orders.ttl.txt
The text was updated successfully, but these errors were encountered: