OntologySummit2013 Hackathon & Clinics Activities    (3O1H)

Co-Champions: MikeDean, KenBaclawski & PeterYim    (3O9L)

This is the workspace for the OntologySummit2013 Hackathon & Clinics Activities    (3O1I)

See: Reports from the Hackathon during the OntologySummit2013_Symposium    (457S)

Congratulations! ... The First IAOA Prize for the Best Hackathon-Clinic Project was awarded to "HC-03: Evaluation of OOPS!, OQuaRE and OntoQA for FIBO Ontologies"    (3S83)

This was awarded at the OntologySummit2013_Symposium (ref.) by a panel of judges that comprised of Dr. LeoObrst, Dr. MatthewWest & Dr. MichaelGruninger.    (3S84)

Again, congratulations, MikeBennett, MariaPovedaVillalon, AstridDuqueRamos, SamirTartir and the rest of the HC-03 team!    (3S85)

The Hackathon-Clinics Program    (3S87)

Hackathon-Clinics Event Schedule (Master Calendar)    (3PG4)

... the assumption is that each project will (essentially) take up one whole day; the Saturday will be the main event day (the Sunday will be an optional extension day, if the team wants to spend more time finishing up.)    (3PG7)

Events on (Day-1): Sat 2013.03.30    (3PGB)

Events on (Day-2): Sat 2013.04.06    (3PGG)

Events on (Day-3): Sat 2013.04.13    (3PGL)

Description, Objective & Goals    (3O9M)

Background ... the OntologySummit organizing committee had overwhelming consensus that we should not spend the symposium wordsmithing (the Communique) this year. Instead, do something that extends from the insights we have gained through the summit sessions, discourse, and the development of the Communique.    (3O9N)

Objective & Goals ... the OntologySummit2013 Hackathon & Clinics Activities are intended to have summit participants collaborate intensively to create something 'real' and 'useful' (relevant to this OntologySummit and/or the "Ontology Evaluation" theme), to produce something that can be demonstrated during the face-to-face Symposium (May 2 & 3, 2013), and possibly something that will spin-off into meaningful projects that can be continued after this Ontology Summit is over.    (3O9O)

Description ... Three (3) forms of collaborative activities will be featured in the OntologySummit2013 Hackathon & Clinics Activities ...    (3O9P)

... consistent with the OntologySummit practice, all process and work products involved in these activities will be "open." Please refer to details in our prevailing Open IPR Policy.    (3OHK)

Call for Proposals    (3O9V)

Please come up with meaningful project(s), find your collaborating partner(s), and form a team, design your project(s) and craft your proposal(s), and get that to us before the submission deadline.    (3O9W)

After all proposals have been collected, we will collaboratively align and tweak the projects and the teams, so we have some very interesting projects to work on, during the (community picked) Hackathon-Clinics weekends (we'll try to pick two, since some people may be involved in more than one project, and some may have conflicts with a particular date.)    (3O9X)

What needs to go into a "Project Proposal"    (3O9Y)

The proposal needs to be succinct (1 page, at most 2) and should include ...    (3O9Z)

... You don't have to have the proposal fully completed. Gaps in the proposals are acceptable - just state what you need to fill those gaps (e.g. the kind of collaborators (specifying skills needed) you are looking for, etc.)    (3OA7)

Post your proposal to the [ontology-summit] list before the Fri 2013.03.08 submission deadline. If need be, email any question you may have to the Hackathon-Clinics Activities co-champions: MikeDean <mdean-at-bbn.com>, KenBaclawski <kenb-at-ccs.neu.edu> and PeterYim <peter.yim-at-cim3.com>    (3OA8)

Important Dates    (3OA9)

Hackathon Proposals Received:    (3O1L)

from KenBaclawski, MikeDean & PeterYim / 2013.03.12 ... rather than doing another proposal towards developing the API that will allow services like OOPS! (and other ontology evaluation tools) to be integrated with OOR and OntoHub (since they supposedly share the same architecture), we suggest that we incorporate the above goal into the two above proposals - namely, OOR-KEEPER & Ontohub-OOPS!    (3OIC)

from SteveRay / 2013.03.08 ... As you might expect, Joel, I'm definitely interested in this work, since I expect to be integrating an OWL version of ASHRAE SPC201P (i.e. FSGIM) with "neighboring" standards, including BACnet. It would be so great if BACnet migrated to OWL.    (3OBF)

Ontology Clinic Proposals Received    (3O1N)

Abstract: ... This ontology clinic is aimed at the evaluation of publicly available ISO 15926 reference data, viewing it as an ontology for the engineering domain. We will look for compliance to upper ontology constraints, diagnose problems in reference data, evaluate ease of understanding and use of existing data, and make suggestions for ontology improvement. Another goal is to apply formal ontology quality metrics for data in question.    (3O6R)

The effort will develop rules and algorithms to support generic verification tests, and also attempt to invent and implement specialized checks and quality metrics for ISO 15926 reference data.    (3O6S)

Collaborators: ... Project initiators are TechInvestLab.ru, a Moscow (Russia) based company, developer of the .15926 software environment. Another team of tool developers from Moscow (http://agentlab.blogspot.ru) has also expressed interest in participating.    (3O6U)

We are looking for collaborators – ontology evaluation experts commanding any generic or specialized software tools to work on proposed ISO 15926 datasets. We will welcome software tool developers willing to show use of their instruments for project tasks.    (3O6V)

from JoelBender / 2013.03.08 ... I'm interested in participating. I'm not an ontology evaluation expert by any stretch of the imagination, nor do I have access to any but the most basic tools, but I would bring enthusiasm, a thirst for knowledge, and my own well developed flare for self deprecating humor.    (3OB7)

from MariCarmenSuarezFigueroa / 2013.03.11 ... I'm very interested on collaborating in your proposal playing the role of an ontology evaluation expert. We can use OOPS! as first step for identifying problems in the ontologies and then we can also use the method in which OOPS! is based (probably in combination with other quality frameworks such as the one presented by SamirTartir and the one presented by AstridDuqueRamos).    (3OHJ)

Our own tool .15926 Editor is freely available (http://techinvestlab.ru/dot15926Editor), well documented, is designed for exploratory programming and includes examples of use for data verification. Basic knowledge of the Python programming language will be enough to join us in the project with this tool.    (3O6W)

We will be happy to provide office space for real world collaboration in Moscow, well connected to the virtual environment of the Hackathon.    (3O6X)

Application Clinic Proposals Received    (3O1P)

The development of the ontology will follow the same logic and framing on the SemantEco Water Quality Ontology from the Tetherless World Constellation.    (3O8Z)

The 2013 Ontology Summit is bringing together a rich range of perspectives on ontology evaluation. Some of these perspectives are fairly abstract, some are encoded in methods and practices, and some are encoded in tools. Critical interaction via summit sessions and discussion has resulted in greater sharing of knowledge and in richer understandings of ontology evaluation at multiple elements. This enrichment is likely to be apparent in the activities and future products of summit participants. Another manifestation of this enrichment will be the summit Communique. The goal of this “hackathons & clinics” activity is to add another manifestation: a formal ontology representing ontology evaluation elements, factors, relationships, processes, etc., as they have emerged from summit discussion.    (3OBO)

The scope of this project is staged to increase with available resources or as time permits, beginning with representation of the most important general concepts and their relationships to one another, through representation of specific metrics, tools, ontology characteristics, evaluation processes, and multi-faceted organizations thereof. Scope and prioritization will be requirements-driven, based on two or more rough use cases developed ahead of time. These use cases will include, at minimum, one direct human-use scenario and one system-incorporation scenario, such as (for example): (a) a human user, using the ontology in the process of determining how well-suited a particular ontology is for a particular application; and (b) a repository environment incorporating the ontology into a feature set meant to enable matching of use cases and well-suited ontologies, through stated or inferred requirements and performed or recorded evaluations.    (3O92)

Collaborators: ... soliciting support and contribution from:    (3OBM)

o Ontologists: The feasibility of this project as a 1-2 day ontology sprint depends on having at least a handful of folks to do the representation. The plan, pending consultation with collaborators, is to make major design decisions in collaboration, and to modularize and distribute chunks of KR throughout the team, working in parallel with open communication channels during the sprint.    (3OBN)

o Potential Users While we can work with imagined use cases, real potential ones are better. If you can see how you might use the resulting ontology, and have some real (albeit potential and result-dependent) interest in doing so, your use case would be most welcome. Real use cases, and real potential deployment, will help focus and energize this ontology development sprint.    (3O93)

from AliHashemi: I'd be interested in collaborating with you and others on this project.    (3OR1)

Independent Contributors (sign-up)    (3O1R)

Anyone who is not directly associated in one of the proposed projects, but would want to participate, should sign up below, and identify what projects you would like to participate in, and the skills you can bring to the table.    (3O1S)