[esip-semantictech] [ESIPFed/sweet] Earth Science Idol (#33)

[HUHNS, MICHAEL]

Thanks, Beth, this all seems reasonable to me now.

[Slightly off-topic] I heard the following about limitations of crowdsourcing and Big Data: “50 billion flies eating manure does not imply it is healthy for you to eat it.” LOL.

Cheers,
Mike

From: bethhuffer [mailto:notifications at github.com]
Sent: Friday, August 04, 2017 8:16 AM
To: ESIPFed/sweet <sweet at noreply.github.com>
Cc: HUHNS, MICHAEL <HUHNS at mailbox.sc.edu>; Comment <comment at noreply.github.com>
Subject: Re: [ESIPFed/sweet] Earth Science Idol (#33)


Well, if the two concepts really are different, then we shouldn't try to reconcile them. We should instead consider renaming the SWEET concept "sedimentary soil" or something, to make it clear that it is not intended to refer to all soil, but only that which is also sediment. Alternatively this exercise will help us recognize that soil is misclassified in SWEET, and should be somewhere else in the ontology. The ontologists among us will then go to work figuring out where.

I apologize for using the term "crowd-sourcing". The intent is to have subject matter experts help us in defining terms correctly, or in helping us realize that we need a different term. We'll probably never actually have a whole crowd of them, and if we do, we will give much less weight to the opinions of people who think dolphins are fish than we do the opinions of marine biologists when it comes to defining "dolphin". :-) The YAMZ tool is a convenient platform for presenting terms to people who may not want to deal with a full-fledged ontology. Definitions can include phrases like "that has settled to the bottom of a liquid" to indicate that the concept in question is a subclass of sediment. Ontologists are, in fact, involved in this effort, and they can help ensure that, once we've agreed on what a term means, it is properly situated in the ontology. This is a pilot to try to sort out the way forward in making SWEET a valuable COMMUNITY resource, and in ensuring that it is aligned with ENVO. If it turns out that the approach we outlined while drinking beers at a pub in Bloomington is inadequate, we can always refine it. :-)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/ESIPFed/sweet/issues/33#issuecomment-320234056>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AcXVnPkHF0809h_WFoSWbXFA7HrEI-GLks5sUwuQgaJpZM4OtGxQ>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-semanticweb/attachments/20170804/0972e71b/attachment.html>