OntologySummit2014: (Track-E) Hackathon (43EO)
Track Co-champions: DanBrickley, AnatolyLevenchuk. Advisor: KenBaclawski (43EP)
Mission Statement: (43EI)
The mission of the Hackathon (http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2014_Hackathon) is to have fun during a 1-day long international hacking event exploring hacking solutions that span both paradigm and technology gaps between the Big Data, Semantic Web, Application Ontology domains. (456Q)
In particular, the structured data gap (tables vs triples vs exotic specialized data structures vs text), schema reusability gap (ad hoc schemas vs ontology), and the hybrid reasoning gap ("statistical reasoning" vs "axiomatic reasoning"). We particularly encourage projects that cross a minimum of two (ideally three) of these themes, but hackathon teams from all areas of applied or theoretical ontologies are welcomed! (456R)
The Hackathon includes both software coding and data preparation that provide example of cross-domain experience for hackathon teams members. (4B7C)
Hackathon Community Input (suggestions, feedback, ideas, corrections, etc.) page available to any participant: OntologySummit2014_Hackathon_CommunityInput (43EK)
What happened (4BMJ)
- 6 individual Hackathon projects had happened! (4BMK)
- 47 participants had fun of collective hacking. (4BML)
- Most of the projects have taken 2 days, and some of them 3 days to get results. (4BMM)
- Most of produced during Hackathon Event artifacts (e.g. ontology files, code snippets, etc.) are available at a individual projects public repositories. (4BMN)
- Preliminary reports have published and discussion of results have started. (4BMO)
- Final reports are under development now and will be presented to Ontology Summit community at the 2014 Symposium (4BMP)
If you have any questions, please get in touch. You can use the Ontolog Summit List (ontology-summit[at]ontolog.cim3.net) to post your suggestions and call of participants to your team. Also you can use wiki (OntologySummit2014_Hackathon_CommunityInput) or contact the Hackathon organizers to help refine your ideas or look for advise and collaborators. (457C)
Current projects: (47O8)
1. Reference data for Anime and Manga: Semantic Linking and Publishing of Diverse Data-Sets (47O9)
Project roster page: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2014_Hackathon_ReferenceDataForAnimeAndManga (4B7D)
Team: 9 participants from Russia, Belorussia, Switzerland, Germany. (4BMQ)
Team lead: VictorAgroskin (MSK, UTC+4), vic5784 at gmail.com (4B7E)
Results: http://github.com/ailev/anird (reference data from 2 anime online databases in ISO 15926 format, ontology patterns for semantization, data fetching and conversion code) (4BMR)
2. Ontology Design Patterns and Semantic Abstractions in Ontology Integration (47S3)
Project roster page: OntologySummit2014_Hackathon_DesignPatternsAndAbstractions (48CM)
Team of 9 participants from Australia, Russia, Italy, France, England and the US (East and West coast). (4BMS)
Team Leads: MikeBennett (mbennett at hypercube.co.uk) and GaryBergCross (4B7H)
Results: «sufficient information to specify the ontology and design for a simple travel risk mobile application in which the user may enter a desired time and destination and either enter different travel modes or have these calculated by existing applications which already do this; the application would return comparative risk figures for the different travel options». (4BMT)
3. Optimized SPARQL performance management via native API (47OU)
Project roster page: OntologySummit2014_Hackathon_OptimizedSPARQLviaNativeAPI (48CN)
Team 5 participants from Russia. (4BMU)
Team Lead VictorChernov (MSK, UTC+4), vchernov at nitrobase.com (47OE)
Results: «Before we started these experiments, we had the belief that RDF databases are slow. The experiments revealed that RDF databases are developing and performance is growing. For example, query 20 and further results show that RDF storages perform fast and can compete with SQL databases. In future we plan joint testing of SQL and RDF databases. (4BMV)
Comparison of the results showed that NitrosBase is performance leader on practically all queries. Virtuoso sure takes 2nd place. Stardog takes 3rd, but it does not mean that the last is poor. All 3 triplestores are indisputable performance leaders». (4BMW)
4. Ontohub consolidation (47OP)
Project roster page: OntologySummit2014_Hackathon_OntohubConsolidation (48CO)
Team Lead TillMossakowski (mossakow at iws.cs.uni-magdeburg.de), OliverKutz (okutz at mac.com). (4B7P)
Team: 10 participants locally and 1 remote. (4BMX)
Results: from 22 open issues for milestone FOIS Competition to only 4 (https://github.com/ontohub/ontohub/issues?milestone=12&state=open). «One particular nasty bug (https://github.com/ontohub/ontohub/issues/576), in the analysis of which we already had invested a lot of time, could be solved with a one-liner; this probably only was possible through so many people working together for a whole day». (4BMY)
5. Semantic Annotation of the Ontolog Community Environment (SAOCE) (47P8)
Project roster page: OntologySummit2014_Hackathon_OntologSemanticAnnotations (48CP)
Team: 9 participants. (4BMZ)
Team lead: KenBaclawski (EST, UTC-5), Ken at Baclawski.com (47P9)
Results: https://github.com/baclawski/saoce (test website: http://ontolog-test.cim3.net/wiki/WikiHomePage). (4BN0)
6. An ontological catalogue of ontology and metadata vocabulary characteristics relevant to suitability for semantic web and big data applications. (47SV)
Project roster page: OntologySummit2014_Hackathon_OntologicalCatalogue (48CQ)
Team: 5 participants from USA and Malaysia. (4BN1)
Team lead: AmandaVizedom (EST, UTC-5) (47SW)
Results: https://github.com/vocref/vocref (both ontology files and issues). «Many representations and concepts related to ontologies and evaluation, from a variety of sources, were considered and weeded out (as, for example, out-of-scope or specific to the assumptions and focus or their original context, or of dubious quality in one way or another). As a result, we arrived at a satisfyingly solid vocref-top, where work will continue». (4BN2)
-- maintained by the Track co-champions ... please do not edit (43EN)