Open pbuttigieg opened 4 years ago
Also, we note that "periglaciation" does not map to any phenomena we encountered. By definition, it cannot be a subclass of a glaciation.
Further, "periglacial" is a subclass of "glacial process" in SWEET, which cannot be (by definition). This is also a strange use of an adjective.
Also, "accumulation" is a subclass of "glacial process", which seems backwards.
The links http://purl.obolibrary.org/obo/ENVO_01001659 http://purl.obolibrary.org/obo/ENVO_01001641 gave me a "term not found."
I don't see them in the ontology. Maybe in an earlier version? (The copy I have is 2019.03.18 into BioPortal. Doesn't appear they were in the previous version either, 2018.05.18, based on a quick diff check.)
No they are in an unreleased Editor’s version so haven’t been released
The semantic harmonization cluster meeting on 04/08/2020 worked on this topic. We note that the following concerns need to be discussed and addressed with the broader community. 1) How to deprecate terms that are not in agreement with scientific community use. 2) Provenance to account for harmonization cluster activity and procedure. This should be documented in the wiki. Issue #179.
Also linked to #126.
We're wrestling with which Annotation Property is appropriate for our harmonisation and mapping.
A bug report assumes that you are not trying to introduced a new feature, but instead change an existing one... hopefully correcting some latent error in the process.
Description
SWEET's phenCryo TTL file includes :
Our work in the Semantic Harmonization Cluster and with the GCW / Polar Semantics team notes that periglacial processes or phenomena - by definition - cannot be subclasses of glacial counterparts.
What would you like to see changed?
Periglacial phenomena should be siblings of their glacial counterparts; however, note that periglacial processes need not be accumulation processes. This suggests that periglacial should be a subclass of "physical process". This change makes the class more general, which may cause some issues for users who have used it in a precise manner.
Note that this is part of the ENVO/SWEET alignment. Relevant ENVO classes include: http://purl.obolibrary.org/obo/ENVO_01001659 http://purl.obolibrary.org/obo/ENVO_01001641
Attribution
If you would like a nano-attribution, please use the following guidance.
The guidance doesn't seem to be up. The ESIP Semantics Harmonization Cluster can be credited.