From OntologPSMW

Revision as of 03:25, 9 January 2016 by KennethBaclawski (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
[ ]

Ontology Summit 2013: (Track-D) "Software Environments for Evaluating Ontologies" - Synthesis     (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)

Work-products from this Track     (1C)

The following is an initial input from track D for the Summit Communique. Not all of these points will necessarily be addressed and included. These are provided for comment. --MikeDenny /2013.03.28     (1C6)

Track D, as "Software Environments for Evaluating Ontologies", falls within the current Communique outline in:     (1C7)

C. The State of the Art of Ontology Evaluation (4) What tool-support is currently available to support the evaluation of the characteristics (identified in C-2) and the best practices (identified in C-3)?     (1C8)

Within this vein, some preliminary Track D concepts that may be developed for inclusion in the Summit communique are, in no special order:     (1C9)

  • The notion of tool support of quality is broader than the track��s title and should include "guidance" as well as "evaluation" of those ontology characteristics determining an ontology��s quality and fitness. Ontology tools and software environments may intentionally constrain or recommend to the user proper ontology structure and content.     (1C10)
  • Tools may contribute this "evaluation" or "guidance" function at different points along the ontology life cycle, and for a given characteristic, some tools may perform better in one life cycle phase than in another phase where a different tool is better suited. Generally, appreciation of the full cycle of life of an ontology is not well established within the ontology community.     (1C11)
  • There are central aspects of ontology that may not be amenable to software control or assessment. For example, the need for clear, complete, and consistent lexical definitions of ontology terms is not presently subject to software consideration beyond identifying where lexical definitions may be missing entirely. Another area of quality difficult for software determination is the semantic fitness of an ontology to its world domain (reality) or to its application domain. Software guidance may be available for the fitness of candidate ontologies for import and reuse, but not so for the novel content of a new ontology.     (1C12)
  • The design, implementation, and use requirements of an ontology may affect how quality and fitness on a particular ontology characteristic are determined, as well as interpreted and valued. Perhaps all quality and fitness assessments by software should be traceable to stated ontology requirements.     (1C13)
  • Significant new ontology evaluation tools are currently becoming available to users. Carving a link between such tools and existing IT architecture and design tools (e.g., EA and SA) remains a future possibility in order to integrate ontology into mainstream application software development within enterprise or more focused IT environments. This capability could offer a definitive means of connecting ontology quality/fitness characteristics and measures to use case and application software requirements.     (1C14)
  • Approximate lexical and structural matching of a new ontology or ontology component to the content of a repository of known ontologies may offer an effective means of identifying comparable ontology content for:     (1C15)
  • Given sufficient results from the Ontology Quality Software Survey, the degree to which current tool capabilities align with ontology quality priorities expressed by Tracks A-C.     (1C16)
  • Discoveries about the state of ontology evaluation stemming from the Hackathon and Clinic experiences.     (1C17)

maintained by the Track-D co-champions: Mike Denny, Ken Baclawski & Peter P. Yim ... please do not edit     (1C19)

This page has been migrated from the OntologWiki - Click here for original page     (1C20)