ONTOLOG Community & Project Planning Worskhop 2005

Resources

review / update Community Charter (--PeterYim / 2005.02.28)
- Ref: proposed updated charter - see: http://ontolog.cim3.net/forum/ontolog-forum/2005-02/msg00020.html

adopt a definition for Formal & Informal Ontologies
- Ref: thread initiated by Duane Nickull, and responses from Peter P. Yim & Leo Obrst - see: http://ontolog.cim3.net/forum//ontolog-forum/2005-03/msg00005.html

Work Session 2005.04.14 - Kurt Conrad, Bob Smith & Peter P. Yim
- Kurt: our problem is that community members engage at levels they choose, planning has nothing to do with traction
- Peter: we've got CoP activities (casual) and Project Activities (disciplined); if the latter is funded, then we can better reinforce the discipline
- Kurt-Bob-Peter: 6 buckets
  - CoP activities
  - experimental/evangelistic projects
  - discplined projects
  - project infrastructure
  - CoP infrastructure
  - Other
- Kurt's table: Issue or Activities - Source - Buckets(6) - Priority - Dependencies - Resources - Level of Interest
  - Priority & Level of Interest: 1 ~ 5, 5 being high
  - Resources: in terms of getting enough resources to pull the activity off
- Action Items
  - Have an ontology of project planning. Who we are, opportunities, constraints
  - Sustainability of CoP, as a whole
  - Continue technology transfer, help people "sell" ontology approach
  - extend SUMO (from Adam's: Do real work that gets used by somebody, especially UBL focus, concrete results )
    - continue from here - more 'real work' going on yet
  - develop a robust semantic policy decision making framework
  - validating planning team's ranking through a survey
- Next work Session 2005.05.05 right after the regular call - Kurt Conrad, Bob Smith, Peter P. Yim & Leo Obrst

Work Session 2005.06.09 - Kurt Conrad, Bob Smith & Peter P. Yim
- Current Priorities
  - Meeting time
    - NIST: Monday, Wednesday, Friday
    - Conflicts w/ W3C Semantic Web Best Practices meeting
    - What are the competing organizations and their meeting times?
    - Drives importance of an updated membership survey. Who would join us if we changed our time? Who would drop out if we change the time? Iterate 3-4x.
    - Not an actionable issue, at this time.
  - Metrics (how many show depending on agenda)
  - Governance
    - Annual budget target for sustained operations (financial and non-financial resources)
    - Assigned roles and responsibilities
    - Structures to support "commercial" activities and committments
  - Team Roster
    - Current XML-based roster is too labor intensive to continue
    - Need alternative approach
- Resourcing considerations
  - Colab engages individuals as part of job duties (Federal or contractor)
  - Ontolog primarily resourced by non-funded labor (tend to see participation drop off as commercial activities increase)
- Meeting schedule
  - Alternative weeks vs non-event days: Try every two weeks until a better option presents itself