1. Welcome
Welcome to the GeoVoCamp 2015
Santa Barbara, CA, March 23-25, 2015
Krzysztof Janowicz
STKO Lab, University of California, Santa Barbara, USA
1/9
2. Welcome
Some Facts About The GeoVoCamp
Vocamps are unconferences; their informal character is an
essential part of the experience
Document your discussions using the dropbox, etherpad, and yED
Implement Geo-ontology design patterns in OWL, RDFS
The best ontology is the one that is out there; Do-ocracy style
The schedule and why we (do not) need it
Follow up of the camps SB 2014 and DC 2014 (and many other
GeoVocamp at the East and West Coast since 2009)
Yes, we have Wifi, you can read your emails...
2/9
4. Welcome
Are GeoVoCamps the Right Way to Go?
We believe that it is very important to keep the GeoVoCamps
informal
This makes them chaotic and difficult to control at times but it does
not make them unproductive
Typically, 2-4 patterns papers are published per year at high-quality
workshops, conferences, and journals as a direct results of
GeoVoCamps
Some of the patterns are already reused by others and also used to
annotate real (and big) datasets
Even more importantly, GeoVoCamps help us to set the agenda.
There is a very clear and visible shift away from older paradigms
towards ontology design patterns, ontology alignment,
micro-ontologies and vocabularies, etc. (of course, this is not just because of us)
Informal vocabulary workshops and patterns seem to be the glue
between ontology engineers, the Linked Data community, and
subject matter experts
There are also disadvantages of running GeoVoCamps...
4/9
5. Welcome
Ontology Design Pattern in a Nutshell
Modular but self-contained
building blocks
Reusable and extendible
Even huge ontologies can be
modularized using ODP (for
example DOLCE)
No need to import full ontology and
all ontological commitments
Different types of patterns, e.g.
content vs. logical
How many patterns are there?
What are the major ontology design patterns for our domain?
5/9
6. Welcome
The 4 GeoVoCamp Steps
Steps
1 Discuss (and disagree!)
2 Create concept maps, e.g., using yED
3 Develop DL/OWL axiomatization
4 Publish and document your patterns
* Focus on steps 1 and 2 during the VoCamp, we know how to do the rest by email, tele-conferences, and so forth.
Best use of our joint time
Establishing contacts
Develop understanding of the tasks at hand
Identify real, purpose-driven use cases and cross-community needs
Best left for work done after the VoCamp
Getting hung up on details
Axiomatization details, especially those about engineering styles
Alignment to existing work (very important but unproductive during a VoCamp)
6/9
7. Welcome
A Combination of Ontology Design Patterns
Keep in mind, ontologies are formal theories, not pictures (concept maps).
7/9
8. Welcome
Creating Patterns Brief Guiding Principles (by Mark Gahegan)
Keep it simple, stupid
Where you end up depends on where you start, and what you think is
important
Choose and agree on (and document) a ‘Subject’
Check existing patterns to see what other subjects might form useful
connection points
What is important about your subject depends on what it means to
you – what you want to do with it, what problem it solves for you
Choose and agree on (and document) a ‘Purpose’
Ensure there are data that fit this purpose
Later, also consider other purposes, as this will help you to avoid
over-specifiying
Provide three examples of where this pattern works
8/9
9. Welcome
Potential topics
Work on ontology design patterns for Life-cycle assessment (LCA)
and industrial ecology in general
Continue work from the Washington DC Geovocamp Dec/2014.
Finish the map legend ontology design pattern
Report and future work (e.g., alignment) wrt. the material
transformation pattern
More on tasks/events/activities?
EarthCube GeoLink patterns
(add your topic here)
9/9