From OntologPSMW

Jump to: navigation, search
[ ]

Contents

OntologySummit2013: (Track-D) "Software Environments for Evaluating Ontologies" Community Input     (1)

Track Co-champions: Michael Denny, Ken Baclawski & PeterYim     (1A)

Mission Statement:     (1B)

Through this track, we aim to coordinate the following:     (1B1)

  • provide a venue to bring together individuals and communities who can help define and advance the state-of-the-art in software and systems for evaluating ontologies     (1B2)
  • the collection and enumeration of software environments and tools for evaluating ontologies (with emphasis on those that are open efforts and those that are publicly available)     (1B3)
  • investigations and development work (software prototyping and implementation) focused on the ontology evaluation theme, leading to interim presentations at the symposium, and possibly continued after this Ontology Summit ... (this bullet, which was on our original mission statement is now handled by the Hackathon-Clinics Activities champions - see: OntologySummit2013_Hackathon_Clinics)     (1B4)


Enter your input below ... (please identify yourself and date your entry)     (1B7)


Ontology Summit 2013 Hackathon-Clinic Contributor confcall (n.05) - Fri 2013.03.19     (1C)

  • Expecting: all leads of submitted hackathon-clinics projects; all independent contributors who have signed up     (1C5)
    • (optional) all Ontology Summit 2013 organizing committee members, invitees, and all who are interested or considering to participate ... this meeting is open to all (as observers).     (1C5A)

Agenda Idea:     (1C7)

  • collaboratively align and tweak the projects and the teams, so we pare the number down to a few very interesting projects to work on, during the (community picked) Hackathon-Clinics weekends.     (1C7A)
  • picking the dates of the Hackathon-Clinics weekend(s) and scheduling projects to those dates     (1C7B)
  • prepare for the Thu 2013.03.28 - session-11 - Getting the "hackathon," "clinics" and related activities going virtual session     (1C7C)
  • discussing next steps on rolling out the Ontology Summit 2013 Hackathon-Clinics;     (1C7D)

Agenda & Proceedings:     (1D)

1. Roll call, review and adopt agenda.     (1D3)

2. Collaboratively align and tweak the projects and the teams, so we pare the number down to a few very interesting projects to work on, during the (community picked) Hackathon-Clinics weekends.     (1D4)

3. Picking the dates of the Hackathon-Clinics weekend(s) and scheduling projects to those dates     (1D6)

we will assume that each project will take up one 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.)     (1D10)

4. Prepare for the Thu 2013.03.28 - session-11 - Getting the "hackathon," "clinics" and related activities going virtual session     (1D11)

5. Discussing next steps on rolling out the Ontology Summit 2013 Hackathon-Clinics;     (1D13)

  • Peter P. Yim will harmonize the schedule input received and post a proposed hackathon-clinics calendar for everyone on the [ontology-summit] list to review and adopt     (1D14)

6. Any other business     (1D15)

7. Follow-up, next meeting, adjournment.     (1D16)

  • let's discuss over the [ontology-summit] (for general and proposal-related issues) and [ontolog-dev] (for low level hackathon details) mailing lists     (1D17)


-- session ended: 10:32 am PDT -- 



Ontology Summit 2013 Hackathon-Clinic Proposal confcall (n.04) - Fri 2013.03.05     (1E)

Ref. Call for Proposals to the the "hackathon" and "clinics" activities - http://ontolog.cim3.net/forum/ontology-summit/2013-02/msg00056.html     (1E7)

Agenda Idea:     (1E8)

  • Make explicit that proposals may include slots for which they want/need additional help (what expertise). Also, there should be a call for, and way for, willing contributors who are not affiliated with one of these projects to register themselves and their skills, for proposers to see (and to generate additional energy/excitement). Having these separate, explicitly, may help with proposal speed / number (suggested by AmandaVizedom)     (1E8A)
  • encouraging collaboration and partnering in putting together a proposal     (1E8B)
  • any remaining issues, Q&A ref. the making of a "hackathon" or "clinic" proposal     (1E8C)
  • re-assess planned timeline and milestones     (1E8D)

Agenda & Proceedings:     (1F)

1. Roll call, review and adopt agenda.     (1F3)

2. Taking inventory on candidate projects, and Q&A ...     (1F4)

  • Any question on what are projects under: "Hackathon," "Ontology Clinic-A," "Ontology-Clinic-B" & "Application Clinic" ... questions on the proposal writing?     (1F5)

3. Possible coordination to make as many of these projects into reality as we can     (1F7)

4. Reviewing the Calendar again - slides#13:     (1F11)

  • Announcement of the call for proposals: Thu 2013.02.21     (1F12)
  • Deadline for proposal submission: Thu 2013.03.08 (2 weeks to prepare proposal)     (1F13)
  • Alignment of projects and teams: 2013.03.09~03.19 (10 days to tweak proposals/projects)     (1F14)
  • Announcement of selected projects: Thu 2013.03.21     (1F15)
  • Hackathon-Clinics project plan debut: session-11 - Thu 2013.03.28     (1F16)
  • Staging of projects: Fri 2013.03.22 to hackathon-clinics weekend (see below; 1 week+)     (1F17)
  • Hackathon-Clinics Weekends:     (1F18)
  • preparation of writeup/presentation/demo - 2013.04.15~29 (2 weeks+)     (1F19)
  • writeup/presentation/demo material due - 2013.04.30 (2 days before event)     (1F20)
  • Presentation / Demo: Thu 2013.05.02 (Symposium Day-1)     (1F21)
  • (?)Award Ceremony: Fri 2013.05.03 (Symposium Day-2)     (1F22)
  • do we want/need to extend the 2013.03.08 (this Thursday) proposal submission deadline?     (1F23)
    • Peter P. Yim: looks like we don't need to ... however, Again, proposal deadline is 2013.03.08 (this Thursday) ... anyone who needs an extra day or two for this, should write <peter.yim@cim3.com> offline about it.     (1F23A)

5. Any other business     (1F24)

  • Yuriy Milov: why limit the hackathon to 1 or 2 days ... why not 4 weeks?     (1F25)
    • Answer: [ppy] the constraint is in our ability to sustain an open distributed collaboration workspace for intensive work for a long time ... we should recognize the project partner can (and would) be working independent of those 1 or 2 days; just treat those 1 or 2 days as the "community collaboration" days.     (1F25A)

6. Action items     (1F26)

7. Follow-up, next meeting, adjournment     (1F28)

  • let's discuss over the [ontology-summit] (for general and proposal-related issues) and [ontolog-dev] (for low level hackathon details) mailing lists     (1F29)


-- session ended: 8:30 am PST -- 



Ontology Summit 2013 Survey and Website sub-team confcall (n.03) - Fri 2013.02.22     (1G)

  • Date / Start time: Friday 2013.02.22 - 6:00am PST / 9:00 am EST / 11:00am ART / 3:00pm CET / 14:00 GMT/UTC     (1G1)
  • Duration: ~1.0 Hours (for survey); maybe another 30 minutes on website planning     (1G2)

Agenda & Proceedings:     (1H)

1. Roll call, review and adopt agenda.     (1H3)

2. 2013-Survey design, implementation and deployment discussion - we want to come away with a plan for: (ref.)     (1H6)

3. Website design, implementation and deployment discussion     (1H11)

4. Any other business     (1H17)

  • exposing/publishing 2012-survey work ... [discussion deferred]     (1H18)

5. Action items     (1H19)

6. Follow-up, next meeting, adjournment     (1H21)


-- session ended: 7:57am PST -- 



OOR Ontology Summit 2013 Hackathon-Clinic Team Meeting (n.02) - Tue 2013.02.05     (1I)

  • Date / Start time: Tuesday 2013.02.05 - 7:30am PST / 10:30am EST / 4:30pm CET / 15:30 GMT/UTC     (1I1)
  • Duration: 1.5 Hours     (1I2)


Software for Ontology Evaluation: Exploratory Meeting - Fri 2013.01.25     (1J)

Conference call details:     (1J1)

Agenda & Proceedings:     (1J8)

{{ 


[ chat transcript ] 


  • aligning what we mean by the "hackathon"     (1J8C)
    • what: need to define the "challenge" between now and March     (1J8C1)
    • how: distributed network of power hack-teams (who would probably be co-located)     (1J8C2)
    • when: weekends between 2013.03.28 and 2013.04.25 ... maybe earlier (to avoid conflict with students' final exams)     (1J8C3)
  • Getting organized     (1J8D)
    • (i) (A) Research, Survey, Enumerate "what's out there," and (B) showcase exemplary software environments and tools for evaluating ontologies     (1J8D1)
      • who's on board: Michael Denny (will lead 'Research, Survey, Enumerate "what's out there"' effort), Mike Bennett, ...     (1J8D1A)
      • candidate deliverables: ... (deferring to discussion on mailing list) ... suggest starting with each member (or team-pair) propose their own deliverable(s) and then discuss     (1J8D1B)
    • (ii) User communities that have real needs to evaluate ontologies, to provide us the use cases, upon which we can ground our work     (1J8D2)
      • who's on board: (Manufacturing / Process Industry) David Leal, (Finance) Mike Bennett, (Earth Science) PeterFox (added: JL/2013.01.28) ... RDA?? Biomedical Informatics??     (1J8D2A)
      • candidate deliverables: ... (deferring to discussion on mailing list) ... suggest starting with each member (or team-pair) propose their own deliverable(s) and then discuss     (1J8D2B)
    • (iii) Communities/teams of Ontology Software developers and tool-makers, who will join us in this track's activities, especially in terms of prototyping and implementations that could help advance the state-of-the-art in software and systems for ontology evaluation     (1J8D3)
  • Any other business     (1J8E)
    • Yuriy Milov suggested, and there was consensus among those at the meeting, that, for the hackathon work, all hack-teams will put their work on the Eclipse development environment.     (1J8E1)
  • Next meeting, wrap-up     (1J8G)
    • [consensus] (for now) we will not make further attempts to confer synchronously (it's too difficult) and will defer to asynchronous transactions     (1J8G1)
    • we will communicate all other outstanding issues via this wiki page, and via discussions on the mailing list(s) -     (1J8G2)
      • "[ontology-summit] " for teams (i) & (ii) work     (1J8G2A)
      • "[ontolog-dev] " for team (iii) work ... PPY: I will subscribe everyone on this team to this list     (1J8G2B)


session adjourned: 9:10 am PST
--
notes taken by: Peter P. Yim / 2013.01.25-9.14am PST
All participants, please review and edit to enhance accuracy and granularity of the documented proceedings.