OntologySummit2010: Future "Quality" - Synthesis of the Discussion    (25EC)

This is the workspace for the co-champions to synthesize the discussion on this track.    (25ED)

Track Label: Quality - Subtrack Label: Future    (25EE)

Track Co-champions: BarrySmith, NicolaGuarino and FabianNeuhaus    (25EF)

Introduction    (2920)

The other tracks are concerned with requirements for ontologists and the content of ontology. The goal of this track is to turn the results of the other tracks into a list of skills and knowledge that a student should be taught in an ontology program. Since ontology is a highly interdisciplinary field it is unrealistic to expect a student to learn everything that might be relevant. For this reason, one could characterize the job of this track to identify and select the most important knowledge and skills that an ontologist needs to do his job. How this content it taught is beyond the scope of this document, this needs to be decided by each individual educational institution based on the available resources. At least some of the content is likely to be covered by existing courses in other programs (e.g., in computer science or philosophy). For illustrative purposes we will include a draft sketch of a masters program below.    (2921)

One challenge in the creation of recommendations for the education of ontologists is that ontology is a young discipline, in many areas important research questions have not been settled and best practices are still evolving.    (2ASY)

Another challenge is that the careers of ontologists are diverse. IT-oriented ontologists are actively involved in the deployment of IT systems that consists of many other components than the ontology itself. For these ontologists it is essential to know how ontologies fit into the software development process and how to integrate the ontolgy with the applications. For this purpose the ontologist needs some background in software engineering, and in particular object-oriented programming and data analysis. Community-oriented ontologists are specialized on developing ontologies within a given domain in collaboration with experts often from large and very diverse communities. One of their main job is to facilitate the resolution of ambiguities and the building of consensus within their communities. To fulfill this role the ontologist needs not only to know the scientific area covered by the ontologies very well (e.g., protein biology or infectious diseases) but also he needs all the 'soft-skills' that enable him to lead a team of domain experts or to build a community that supports an ontology.    (2ASZ)

The knowledge and skills that we list below are covering the basics any ontologist need. However, they are not sufficient to have a career as an ontologist; this will require either an additional background in software engineering or domain specific knowledge.    (2AT0)

There is a strong consensus within the community that although there is a lot of academic knowledge that is relevant for ontologists, many important skills cannot be learned from lectures alone. Any education of ontologists has to be build around hands-on training experiences.    (28ZW)

In the following, we distinguish between skills (the ability of a student to do something) and knowledge (true believes). Since the former usually involves the latter, they have to be taught together. Because the careers of ontologists are diverse, it is not realistic to develop a single curriculum that fits all students. In the following we distinguish between core skills (knowledge) and elective skills (knowledge). The idea is that any student should be required to gain all of the core and some of the elective skills and knowledge.    (2922)

Core Skills    (290D)

Abilities required for developing and improving ontologies:    (290E)

  1. Clarifying the purpose of the ontology, understand potential deployment, perform requirements analysis,    (2900)
  2. Data analysis using a scripting language    (2AT2)
  3. Managing the ontology across the life cycle (versioning, documentation, help desk ...)    (2901)
  4. Knowing what sort of ontology is useful for what sort of problem (including: know where ontologies are not useful)    (2902)
  5. Identifying, evaluating and using software for ontology development    (2903)
  6. Choosing the appropriate representation language    (2904)
  7. Choosing the appropriate level of detail    (2905)
  8. Identify existing content resources (existing ontologies, terminologies and related resources; relevant data; domain expertise, ontology expertise)    (2906)
  9. Designing an ontology as an assembly of reusable modules    (2907)
  10. Using (reading, writing) different representation languages    (2909)
  11. Ontological analysis: identifying entities and relationships; formulating definitions and axioms    (290A)
  12. Improving ontologies (finding errors via manual term-by-term inspection, solving interoperability problems)    (290B)
  13. Documenting the ontology, including: providing natural language definitions    (2908)
  14. Working in a team, including teams for distributed development    (290C)

Abilities required for applying ontologies. (See use cases below.)    (290F)

Elective Skills    (290G)

  1. Coordinating ontology development efforts    (290I)
  2. Creating meaningful visualizations of ontology structure for human beings    (290J)
  3. Training people in the use of ontologies    (290K)

Core Knowledge    (290X)

  1. The basic terminology of ontology (relation of ontology to knowledge representation, conceptual modeling, data modeling, ...)    (290L)
  2. Theoretical foundations    (290M)
    1. Logic (first order, second order, Description Logic, ...; logic of definitions)    (290N)
    2. Set theory    (290O)
    3. Philosophical ontology (universals and particulars, time, mereology ...)    (2AT1)
    4. Philosophy of language (the use-mention confusion, sense and reference, speech act theory, ...)    (290Q)
    5. Knowledge representation, conceptual modeling, data modeling; metadata    (291K)
  3. Representation languages Part 1: RDF, OWL; Common Logic    (290R)
  4. Building and Editing ontologies    (290S)
    1. human aspects (application of classification principles, manual auditing, ...)    (290T)
    2. software tools (Protégé, ...)    (290U)
    3. resolving interoperability problems among ontologies    (290V)
  5. Ontology evaluation strategies and theories (Ontoclean, ...)    (290W)
  6. Examples of ontologies, illustrating different methodologies    (290Y)
    1. upper-level ontologies (BFO, DOLCE, SUMO, ...)    (290Z)
    2. domain ontologies (GO, PSL, Enterprise Ontology, ...)    (2910)
  7. Examples of ontology applications (successes and failures)    (2911)
    1. as controlled vocabularies / standards, to achieve coordination between humans    (2913)
    2. to solve interoperability problems among external data resources    (2914)
    3. reasoning with ontology content    (2915)
    4. improve search and retrieval    (2916)
    5. NLP    (2917)
  8. Ontology and the Web    (2918)
    1. General foundations (URIs, XML, etc.)    (2919)
    2. Semantic Web initiative    (291A)
    3. Semantically enhanced publishing, literature annotation, data curation    (291B)

Elective Knowledge    (291C)

Underlying and related disciplines    (291D)

  1. Advanced logic (modal logic, temporal logic, default logic, ...)    (291E)
  2. Advanced philosophical ontology (mereotopology, tropes, ...)    (291F)
  3. Computer science    (291G)
    1. formal languages, formal machines, computability    (291H)
    2. automated reasoning    (291I)
    3. database theory    (291J)
  1. Linguistics / cognitive sciences    (291L)
    1. distinction between syntax, semantics, pragmatics    (291M)
    2. natural language processing, natural language generation    (291N)
    3. cognitive theories of categorization    (291O)

Supporting tools, technologies and methodologies    (291P)

  1. Representation languages Part 2 (SWRL, RIF, SKOS; OBO; UML; E-R, ...)      (291Q)
  2. Ontology content acquisition (role of text mining, ...)    (291R)
  3. Achieving ontology interoperability    (291S)
  4. Principles for building ontology repositories      (291T)
  5. User interface issues (visualization / usability, principles of meaningful arrangement, ...)    (291U)

Application domains    (2ASX)

Any domain could be an application domain for ontologists. For example, ontologies are used in the following areas:    (291V)

  1. Natural sciences (biology and and biomedical informatics, physics, astronomy, geology)    (291W)
  2. Business (enterprise modeling, enterprise memory, manufacturing systems, supply chain integration) and E-Commerce (GoodRelations)     (291X)
  3. Government (military, intelligence community, security)    (291Y)
  4. Education    (291Z)

Example    (2925)

The following would be an example for a 36 credit master program. 3 courses (9 credit) would be for electives, the following 9 courses (27 credits) are covering the core skills/knowledge. (The numbers in parenthesis reference the numbers in the lists above.)    (2927)

 This page is maintained by BarrySmith, NicolaGuarino and FabianNeuhaus
 Please do not edit or modify it yourself; send any editing request to any one of the individuals named above.    (25EJ)