"Brains! Brains! Give us your brains!""
- Friendly neighbourhood machine minds
The collective knowledge in the ESIP community is immense and invaluable. During this session, we'd like to make sure that this knowledge drives the semantic technology (ontologies) being developed to move data with machine-readable knowledge in Earth and planetary science.
What we'll do:
In the first half hour of this session, we'll a) sketch out how and why we build ontologies and b) show you how to request that your knowledge gets added to ontologies (with nanocrediting).
We'll then have a 30-minute crowdsourcing jam session, during which participants can share their geoscience knowledge on the SWEET issue tracker. With a simple post, you can shape how the semantic layer will behave, making sure it does your field justice! Request content and share knowledge here: https://github.com/ESIPFed/sweet/issues
In the last, 30 minutes we'll take one request and demonstrate how we go about ""ontologising"" it in ENVO and how we link that to SWEET to create interoperable ontologies across the Earth and life sciences.
Come join us and help us shape the future of Geo-semantics!
Stuff you'll need:
A GitHub account available at https://github.com/
An ORCID (for nanocrediting your contributions) available at https://orcid.org How to Prepare for this Session:
Presentations:
View Recording: https://youtu.be/tr0coi5ZQvMTakeaways- Working toward a future (5-10 year goal) of making an open Earth & Space Science Foundry (from SWEET) similar to the OBO (Open Biological and Biomedical Ontology) Foundry. “Humans write queries”. Class definitions need to be machine-readable for interoperability, but must remain human-readable for authoring queries, ontology reuse, etc.
- Please feel free to add phenomena of interest to the SWEET https://github.com/ESIPFed/sweet/issues/ or ENVO https://github.com/EnvironmentOntology/envo/issues/ issue trackers.
- At AGU they added a convention for changes to ontologies. Class level annotation convention. Can get now get textual defs from DBpedia for SWEET terms. See https://github.com/ESIPFed/sweet/wiki/SWEET-Class-Annotation-Convention
