Modelling the schema and supporting interoperability Flashcards
(159 cards)
OWL Week 8 Summary
Knowledge Graphs are a particular case of Ontology Based Information System, (OBIS) i.e. a system providing components for collection, storage and processing of data. In OBIS, the data is modelled according to one or more ontologies, and is used to provide information, contribute to knowledge as well as facilitate decision making. An OBIS is characterised by:
Incomplete and semi-structured data often obtained by integrating heterogeneous sources;
View of data that is independent of logical/physical schema;
Queries that are formulated with terms familiar to users;
Queries can be refined, query navigation;
Answers that reflect knowledge & data, e.g.: “Engine suffering from a block in the Fuel Filter”.’
Ontologies are abstractions that provide an agreement on the semantics of the terms used to define the data in OBIS and the constraints on the use of these terms.
Ontology Engineering refers to the set of activities that compose the ontology development process and the ontology life cycle, including also methodologies, tools and languages for building ontologies. Ontology engineering provides the standard components for building knowledge models, and allows the correct modelling and reuse of knowledge in a knowledge base by defining conceptualisations, the modelling assumptions and requirements made in the problem solving process that will use the knowledge base. In these videos we will describe the main principles that ontologies should satisfy, and will discuss some of the most used ontology engineering methodologies, with a more in-depth discussion on Methontology, one of the most comprehensive ontology engineering methodology. We will also focus our attention on Ontology 101Links to an external site., a process that describes the set of principles for designing an ontology which are often captured more formally in the various ontology engineering methodologies.
Key week 7 points to remember:
Ontology based Information Systems:
Data, Information, Knowledge;
Ontologies: definition and ontological commitment;
Importance of ontologies for interoperability.
There are different methodologies for building ontologies that model a domain / task;
These methodologies have common phases:
Eliciting requirements:
Understand the user needs through competency questions, tables of concept names, card sorting, UML diagrams…
Reuse ontologies to ensure interoperability;
Identify classes and properties, and organise them in hierarchies;
Model class expressions and constraints
Populate the ontology, check consistency and restart.
Not a sequential method, but it can be repeated several times.
Why do we need ontologies?
Ontologies provide a common vocabulary and definition of rules defining the use of the terms by independently developed resources, processes, services
- Unless we represent an object using ontologies we’re missing it’s context
What does DIKW stand for and what is it?
Data - information - knowledge - wisdom
- this is a model
Data: is unorganised, unprocessed discrete, objective facts or observations
* has no meaning or value because of lack of context and interpretation
Information: is organised or structured data, processed in a way that the info now has relevance for a specific purpose or context, it’s meaningful, valuable, useful and relevant
Knowledge: Different perspectives:
* a mix of contextual info, values, experience and rules;
* information combined with understanding and capability;
* a belief structuring” and “internalisation with reference to cognitive frameworks
Wisdom: the knowledge and insights into a learning experience that guides our actions
* evaluated understanding
What are the steps involved to move through the DIKW model?
Data → convention → Information → cognition → Knowledge → contemplation → Wisdom
What is knowledge?
The intersection between truth and belief. The truth is objective and is observable. Belief is a form of model of what the agent thinks is the truth in the scope of the domain. It’s not objective, the truth could change in a different domain.
What factors does Sharing knowledge (between components or systems) depend on?
- common symbols and concepts (Syntax)
- agreement about their meaning (Semantics)
- classification of concepts (Taxonomy)
- associations and relations of concepts (Thesauri)
- rules and knowledge about which relations are allowed and make sense (in the domain of interest) (Ontologies)
How do we conceptualise ontologies?
Ontologies function like the brain (of your app). They work and reason with concepts and relationships in ways that are similar to the way humans perceive interlinked concepts. They try to mimic the way human reasoning works.
How do ontologies enhance the graph data model in a knowledge graph (KGs)?
By providing:
* a formal specification of a shared conceptualisation
* an abstract symbolic representation of a domain expressed in a formal language
* precise meaning to the data represented in KGs.
-They’re essential for clarifying the usage and context of the data.
How are ontologies expressed as domain models useful?
They:
* help people to communicate (as the abstraction can be used for clarification on a concept)
* explain (certain domains) and make predictions
* mediate among different viewpoints (they provide an interlingo for different viewpoints)
They:
* specify the meaning (semantics) of terms in the vocabulary (e.g. with RDFS)
* are formalised using a suitable logic-based language (e.g.OWL)
Describe ontological commitment:
Agreements to use the vocabulary in a coherent and consistent manner
* An agent commits (conforms) to an ontology if it “acts” consistently with the definitions
* The assignment of the meaning to the terms in the ontology vocabulary
How are different types of Ontologies classified? This is in terms of domain and task
- Ontologies are classified depending on how generic or specific they are.
We classify them in levels: - Top Level, Generic Domain, Domain, Application Domain
- Top Level, Generic Task, Task, Application Domain Task
What features change depending on the level of Ontology language used?
- Whilst Usability increases, reusability decreases.
- Whilst reusability increases, usability decreases
What is the definition of a top level ontology?
Generic enough to be used across different domain ontologies. They represent very general concepts as e.g., Time, Space, Event (FOAF). These are independent of a specific domain or problem. Also known as Upper Ontology or Foundational Ontology
What is the definition of a Domain ontology?
These are fundamental concepts according to a generic domain. Typically they specialise terms introduced in top-level ontology (constraining their meaning to a specific domain).
What is the definition of a Task ontology?
Fundamental concepts according to a general activity or task; specialises terms introduced in top-level ontology
What is the definition of a Application ontology?
Specialised ontology focussed on a specific task and domain. Often a specialisation of both task and domain ontology; often specify roles played by domain entities for specific activity
Give an example of how the the level of granularity dictates the expressivity of the language:
The concepts in the Top level category aren’t very usable because they’re so generic, they’re valid across several domains, so they will be very reusable by several domains. However the more we constrain them, the more usable they become to a specific application.
Describe the ontology development process:
We start with something vague, ambiguous and undefined and get to something well defined, organised and expressed through our logical axiom.
- We can often forget which assumptions we’ve already made, before performing a task and assume that someone else already knows these things.
What is ontology engineering?
The set of activities that concern the ontology development process, the ontology life cycle, and the methodologies, tools and languages for building ontologies
When building an ontology what terms do we need to define in the domain and relations among them:
- define concepts in the domain (classes)
- Arranging the concepts in a hierarchy (subclass-superclass hierarchy)
- define which attributes and properties classes can have, and constraints on their values
- Define individuals and fill in property values
Give examples of Methodological questions:
- What part of the domain do we need to model?
- What are the constraints on the use of this knowledge?
- How can tools and techniques best be applied?
- Which languages and tools should be used in which circumstances, and in which order?
- What about issues of quality control and resource management?
What are the Principles for the design of an ontology:
- Clarity
- Coherence
- Extendibility
- Minimal Ontological Commitments
- Minimal Encoding Bias
(Principles for the design of an ontology) Explain why clarity is important:
Clarity: necessary to communicate intended meaning of defined terms
* Definitions should be objective and should be stated with formal axioms.
* A complete definition (defined by necessary and sufficient conditions) is preferred over a partial definition (defined by only necessary or sufficient conditions)