conformsToKnowledgeRepresentationParadigm contributesToOntology createsOntology definedBy defines designedForOntologyTask developedBy develops Indicates the parties (i.e. organisations, people) that have expressed support or approval to the this ontology. endorsedBy endorses hasAffiliatedParty hasContactPerson hasContributor hasCreator hasDomain hasFormalityLevel hasLicense hasOntologyLanguage hasOntologySyntax hasPriorVersion hasSyntax isBackwardCompatibleWith isContactPerson isIncompatibleWith isLocatedAt isOfType isSubDomainOf specifiedBy specifies supportsRepresentationParadigm useImports usedOntologyEngineeringMethodology usedOntologyEngineeringTool The URI of the ontology which is described by this metadata URI A short name by which a kR paradigm is known acronym Name of the city (and zip code). city The name of the country country Date when the ontology was initially created creationDate Free text description of the formality level description URL for further documentation documentation The email address of a person eMail The fax number of a person faxNumber The first name of a person firstName Indicates what the central/best represented classes of the ontology are. keyClasses List of keywords related to an ontology. Typically this set includes words that describe the content of the ontology keywords knownUsage The surname of a person lastName Date of the last modification made to the ontology modificationDate The name by which this element is formally known. name The language of the content of the ontology, i.e. English, German, etc. naturalLanguage Additional information can be expressed here. Kind of like the stuff you don't want to put inside documentation notes Number of axioms in the ontology numAxioms Number of classes in the ontology numClasses Number of individuals in the ontology numIndividuals Number of properties in the ontology numProperties The phone number of a person phoneNumber List of bibliographic references describing the ontology and its applications reference The location where the ontology can be found. It should be accessible via a URL resourceLocator The state of a country. state It specifies the tracking information for the contents of the ontology. Pre-defined values status Name of the street and number (address). street Specifies the version information of the ontology. Version information could be useful for tracking, comparing and merging ontologies. The number could be incremented by 1, or a smaller or larger value, depending on the personal preference of the author. version 1 1 FormalityLevel The level of formality of an ontology FormalityLevel 1 1 1 1 KnowledgeRepresentationParadigm Information about a knowledge representation paradigm a particular language adheres to KnowledgeRepresentationParadigm 1 1 1 1 LicenseModel A license model describing the usage conditions for an ontology LicenseModel 1 1 1 1 Location The geographical location of a party. To keep things simple we use only DatatypeProperties instead of introducing classes for country, street, etc. Location 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Ontology Aspects of specific realizations are covered modular (and extendable) by the class Ontology. Ontology 1 1 OntologyDomain While the domain can refer to any topic ontology it is advised to use one of the established general purpose topic hierarchy like DMOZ or domain specific topic hierarchy like ACM for the computer science domain. OntologyDomain 1 1 1 1 OntologyEngineeringMethodology Information about the ontology engineering methodology OntologyEngineeringMethodology 1 1 1 1 OntologyEngineeringTool A tool used to create the ontology OntologyEngineeringTool 1 1 1 1 OntologyLanguage Information about the language in which the ontology is implemented OntologyLanguage 1 1 1 1 OntologySyntax Information about the syntax used in an Ontology OntologySyntax 1 1 1 1 OntologyTask Information about the task the ontology was intended to be used for OntologyTask 1 1 1 1 OntologyType This class subsumes types of ontologies according to well-known classifications in the Ontology Engineering literature. OntologyType 1 1 Organisation An organisation of some kind. Represents social institutions such as universities, companies, societies etc. Organisation Party A party is a person or an organisation Party 1 1 1 Person A named individual. Represents an individual responsible for the creation, or contribution to an ontology Person owl:Thing Academic Free License (AFL) Altova SemanticWorks the ontology is used as a controlled vocabulary to annotate Semantic Web resources. This task includes the usage of a semantically rich ontology for representing arbitrarily complex annotation statements on these resources. The task can be performed manually or (semi-)automatically. AnnotationTask Apple Public Source License (APSL) describes some domain in an application-dependent manner Application Ontology Common Public License (CPL) the ontology is designed to provide a controlled and unambiguous means to represent valid configuration profiles in application systems. As the aim of the ontology is to support the operationalization of particular system-related processes; this task is performed automatically in that the ontology is processed in an automatic manner by means of reasoners or APIs. ConfigurationTask describes the most important concepts in a specific domain Core Ontology DAML-OIL Description Logics describes some domain of the world Domain Ontology the task describes at a very general level how ontologies are applied to refine the solution space of a certain problem, such as information retrieval or personalization. The task is targeted at being performed semi-automatically or automatically. FilteringTask Frames General Public License (GPL) IBM Public License (IBM PL) INTEL Open Source License (INTEL OSL) in this scenario, the goal of the ontology is to provide a clearly defined classification and browsing structure for the information items in a repository. Again, the task can be performed manually by domain experts or as part of an application in an automatic or semi-automatic way. IndexingTask the task characterizes how ontologies provide an integrating environment, an inter-lingua, for information repositories or software tools. In this scenario the ontology is applied (semi-)automatically to merge between heterogeneous data pools in the same or in adjacent domains. IntegrationTask IsaViz Lesser General Public License (LGPL) the goal of matching is to establish links between semantically similar data items in information repositories. In contrast to the previous task, matching does not include the production of a shared final schema/ontology as a result of aggregating the matched source elements to common elements. W.r.t. the automatization level the range varies from manual to fully-automatical execution. MatchingTask the ontology is built to reduce the ambiguities between communicating human or machine agents. It can act as a normative model which formally and clearly defines the meaning of the terms employed in agent interactions. In the context of programmed agents, the task is envisioned to be performed automatically. MediationTask Modified BSD License (mBSD) NeOn-Toolkit OWL OWL-DL OWL-Full OWL-Lite OWL-XML OilEd OntoBuilder OntoStudio Open Software License (OSL) the ontology is used mainly for providing personalized access to information resources. Individual user preferences w.r.t. particular application settings are formally specified by means of an ontology, which, in conjunction with appropriate reasoning services, can be directly integrated to a personalization component for filtering purposes. The usage of ontologies in personalization tasks might be carried out in various forms, from a direct involvement of the user who manually specifies ontological concepts which optimally describe his preferences, to the ontological modelling of user profiles. PersonalizationTask Protégé the ontology is used in information retrieval settings as a controlled vocabulary for representing user queries. Usually the task is performed automatically in that the concepts of the ontology is are listed in a query formulation front-end in order to allow users to specifies their queries. QueryFormulationTask complementary to the query formulation dimension, this task applies ontologies to semantically optimize query expressions by means of the domain knowledge (constraints, subsumption relations etc.) The task can be interpreted as a particular art of filtering information. The task is performed automatically; however, it assumes the availability of patterns describing the transformations at query level. QueryRewritingTask RDF(S) RDF/XML SWOOP Schema the task characterizes how ontologies are used to refine common keywordbased search algorithms using domain knowledge in form of subsumption relations. Ontology-driven search is usually performed automatically by means of reasoning services handling particular aspects of an ontology representation language. SearchTask describes generic types of tasks or activities e.g. selling, selecting. Task Ontology Taxonomy Terminology Thesaurus describes general, domain-independent concepts e.g. space, time Upper Level Ontology Vocabulary WSMO Studio WebODE