OpenOntologyRepository

Priorities & Most Critical Tasks At Hand:    (17YH)

   updated: 2012.07.10    (3D55)
  • 1. Systematically engage other communities to advance the state-of-the-art as well as to solicit content contributions    (1VMD)
    • collaborate and solicit content contributions from the communities engaging in ontology research, development, engineering and applications    (2KTL)
    • collaborate and solicit content contributions from the communities engaging in digital content and knowledge organization structures    (2KTM)
  • 2. Identify compelling and relevant reference implementations and use cases of OOR, with a focus on demonstrating the application and value of OOR    (3D51)
    • consider possibilities in: bigdata, standards, … bridging db-schema, xml, uml, …    (3D52)
  • 3. Prepare and adopt an OOR system architecture    (2I9U)
    • define and adopt a set of API’s    (2I9V)
    • define and adopt the set of ontology metadata (as an extension of OMV) that authors of the ontology are required to provide when they upload ontologies to the OOR    (2I9W)
    • define and adopt a core development platform    (2L0P)
  • 4. Initiate implementation of key development priorities    (2R92)
    • build out “gatekeeping” and move from just having an OOR-sandbox to having available instances of an OOR-sandbox and an OOR-production    (23YW)
    • add CL support to OOR    (2GLZ)
    • federation    (2R93)
  • 5. get the work of this team funded; and help/support/coordinate members’ teaming up and getting funded    (1TID)
    • start a regular “Funding” workshop series (just like Architecture+API, Metadata, Code-development, etc.)    (3D53)
  • 6. continue with efforts in publicity and outreach    (28Q5)
    • systematically get OOR-related presentations and papers into pertinent conferences and workshops    (3D54)
  • 7. set up policies and process for contributing to OOR work    (1PZR)
    • setup clear and easy policies and process to engage developers and have them contribute code    (28Q3)
    • getting ourselves into a position where team members can contribute code    (2R91)
  • 8. regularly review requirements and existing standards to make sure we are on track    (1P5V)