Identify Subject Matter Experts for Review and Governance

[lewismc]

As a community, we've acknowledged that we need SMEs to ensure the accuracy and integrity of SWEET.
From previous documentation on SWEET, I've identified the following areas which we 'may' need SMEs for

Integrative Topics

• Natural Phenomena (Macroscale)
• Human Activity
• Data

Faceted Topics

• Living Substances
• Non-Living Substances
• Physical Processes (microscale)
• Earth Realm
• Pysical Properties (observation)
• Space
• Time
• Units
• Numerics

Are there any others?

[lewismc]

The Global Change Master Directory (GCMD) Keyword Governance and Community Guide Document provides Subsection 3.3 Change Process Overview which we could use as guidance...

[rduerr]

So the problem that I have with this is insufficient specificity. For example, I'd be happy to sign up for cryospheric terms.... but that isn't on the list.

[lewismc]

OK @rduerr, well let's add that area to the roster of interested members. I'm going to overhaul the document here, so we can begin capturing this stuff @rduerr. It is not intentional that that area was left out, it's just that I didn't know enough about it to state it explicitly right now. Thanks for writing here to register interest.

[fils]

@lewismc I'd be happy to help in the area of Geologic time. I'd love to try and help with connections between Simon's OWL time based Geologic Timescale Ontology https://github.com/dr-shorthair/GeologicTimeScale and SWEET. I know several others who would love to be involved too. I will point them at the repo and this issue. Is there any formal mechanism you would like us to self identify? If I can get some interested parties together I suspect we can assess the functional needs of our community re: the ontologies. I'll try and start some discussions with them. Perhaps under a separate issue.

[lewismc]

Hi @fils thanks, I think over time, we will most likely need a separate group (subgroup of the semantic tech committee) which works on SWEET. I would suggest, we start overhauling the document here which I've obviously borrowed from the W3C SSN effort. For the time being I think people should just tag themselves here and we can take it fro there. I'm going to start work on the document linked above.

[alisonboyer]

Hi, I am willing to review natural phenomena and living substances. I'm with the NASA DAAC at Oak Ridge National Lab, specializing in data archival for ecological and biogeochemical data.

[tbs1979]

I am interested in being involved and see how the GCMD Keyword can fit into this.

[lewismc]

Thank you both @alisonboyer and @tbs1979 theses are very important areas so thank you for coming forward. Your interest is noted and you will both be included in any talks going forward thank you.

[CommonClimate]

Hi! I'm a PI on the NSF-funded EarthCube project LinkedEarth. I'd like to sign up as a subject matter expert for climate and paleoclimate data. For the latter we have a fairly robust ontology that could help extend SWEET in this direction. Please let me know the best way to participate.

[lewismc]

Excellent @CommonClimate this is brilliant, thank you for registering your interest. I think we will be discussing this at our next ESIP SemTech committee meeting. I'll ping you in good time so you are aware and involved in the organization moving forward. Thanks.

[CommonClimate]

My pleasure @lewismc . Ping away.

[narock]

@fils @lewismc W3C is looking for implementations of OWL Time. The connection between Simon's work, SWEET, and OWL Time could be a good fit for this: https://www.w3.org/blog/news/archives/6346

[lewismc]

ack I agree @narock. I'm not really in a position to lead that work... I don't know enough about OWL Time tbh. Can you tag Simon here?

[narock]

@lewismc I think @fils already reached out to Simon. I will check, and if not, I'll tag him.

[xgmachina]

@lewismc Nice to see many familiar colleagues here. I will be glad to contribute to topics of Space, Time and Data provenance, but will not limit only to them - SWEET is a big ontology with so many topics of interest.

[lewismc]

Excellent @xgmachina, thank you for registering interest. We will be in touch shortly.

[pbuttigieg]

@lewismc - we're happy to add insight from or sync ENVO's branches here. Our community contributors (often subject matter experts) have helped build some good branches over the years.

[lewismc]

Excellent @pbuttigieg thank you for noting your interest.

[linepouchard]

Hi Lewis and all:
I am happy to contribute to Data and related processes.

[lewismc]

Excellent @linepouchard thank you

[lewismc]

@rduerr @alisonboyer @tbs1979 @CommonClimate @pbuttigieg can you all please make a request to join the following group https://github.com/orgs/ESIPFed/teams/semtech/members this way you will be included in notifications. Thank you

[tbs1979]

@lewismc at one point in an earlier version of SWEET, GCMD keywords were incorporated. Is there any plan from the SWEET end to incorporate or link the GCMD keywords in again?

[graybeal]

I wonder if these relations might be better published in a separate file(s)? That would allow independent maintenance/workflows, and possibly easier reuse of the mappings. Depends on how integral that info is to SWEET, I guess.

…

________________________________ From: Tyler Stevens <notifications@github.com> Sent: Wednesday, June 28, 2017 5:19:28 AM To: ESIPFed/sweet Cc: Subscribed Subject: [SPAM:###] Re: [ESIPFed/sweet] Identify Subject Matter Experts for Review and Governance (#3) @lewismc<https://github.com/lewismc> at one point in an earlier version of SWEET, GCMD keywords were incorporated. Is there any plan from the SWEET end to incorporate or link the GCMD keywords in again? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#3 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABNU0FxBpJ1wJw4LRUHk_mV_A7-QF7yVks5sIkTQgaJpZM4MsNYs>.

[lewismc]

We are getting into the terrain of ontology alignment here folks... which I think should be addressed on a separate thread. I'm going to put some work into the current SWEET Working document which I will style after out SRI Use Cases and Requirements documentation

[edshred2000]

I'm interested in contributing expertise to formats, provenance and data processing, as well as ocean phenomena expertise.

[lewismc]

Thank you @edshred2000, noted

[dr-shorthair]

@fils International Chronostratigraphic Chart - 2016-12 version - formalized in SKOS and OWL-Time, is now available through Research Vocabularies Australia:
https://vocabs.ands.org.au/international-chronostratigraphic-chart-2016
see
http://vocabs.ands.org.au/repository/api/lda/csiro/international-chronostratigraphic-chart-2016/2016-12-v3/resource?uri=http://resource.geosciml.org/vocabulary/timescale/isc2016-12

This data makes a lot of use of the OWL-Time interval relations - see figure 2 in https://www.w3.org/TR/owl-time/#topology

The individual http://resource.geosciml.org/classifier/ics/ischart/ URIs, such as http://resource.geosciml.org/classifier/ics/ischart/Phanerozoic , are now set up to resolve to this service, so it is a proper Linked Data resource.
Note that GeochronologicEra and GeochronologicBoundary resources are formalized as OWL individuals, rather than OWL classes, which I think is inconsistent with SWEET's classist approach.

[lewismc]

Thank you for input @dr-shorthair are you interested in being involved in the SWEET Ontology Interest Group? We can make sure your comment makes it onto the agenda.

[lewismc]

Note that GeochronologicEra and GeochronologicBoundary resources are formalized as OWL individuals, rather than OWL classes, which I think is inconsistent with SWEET's classist approach.

... and yes @dr-shorthair you are correct with the above statement.

[dr-shorthair]

There was a time when I would have entered an argument about this, but I think we are all more relaxed now. By defining all concepts as OWL classes you can take advantage of OWL axiomatization of the class definition, which is good. OTOH by defining classes (like GeochronologicEra) with individual members (like Cenozoic, Wenlockian, etc) you can say more about how they are used in datasets, using rdfs:range/domain and owl:Restriction constraints which apply to all the individual members of a class, not subclasses. OWL2 punning allows us to mix and match a bit, though also at some reasoning costs. But overall if we can be a bit accepting I think it can all work.

[dr-shorthair]

@fils Note additional axiomatization of timescale nesting logic here, using OWL-Time predicates
http://resource.geosciml.org/ontology/timescale/gts/w3c.ttl

Not really tested yet, but you can see the principle.

[lewismc]

I've added a note to our release announcement
https://github.com/ESIPFed/sweet/wiki/Community-Announcements
It calls for Subject Matter Experts... that is probably the best way we can get the message out there.