Submissions:Topic
From Odp
If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 9138 |
Graphical representation
Diagram
General description
Name: | Topic |
---|---|
Submitted by: | SaraBernardini, AldoGangemi |
Also Known As: | |
Intent: | To represent topics and their relations. |
Domains: | |
Competency Questions: |
|
Solution description: | Topics are modelled as conceptual complexes with part of (containment), overlap, and vicinity relations, and can be related to any kind of entity. They are disjoint from "Concepts", which can be at the "core" of topics. |
Reusable OWL Building Block: | http://ontologydesignpatterns.org/cp/owl/topic.owl (904) |
Consequences: | We are able to represent topics, subjects, or themes of something, and to organize topics into partonomic and topological structures.
In order to represent more sophisticated relations between topics, concepts, terms, etc., refer to the full ontopic.owl ontology. |
Scenarios: | "The topic of Moby Dick is the hatred of humanity", "What is the main subjects in neswpapers today? And more specifically?" |
Known Uses: | |
Web References: | |
Other References: | |
Examples (OWL files): | |
Extracted From: | |
Reengineered From: | |
Has Components: | |
Specialization Of: | |
Related CPs: |
Elements
The Topic Content OP locally defines the following ontology elements:
Distance is typically established with reference to a threshold on the number of concepts or entities that are common between the two topics. Alternatively, it can be established with reference to the a geometrical semantics applied to the spaces (super-topics) of which topics are part (cf. ontopic.owl ontology).
For example, Saxophone (as a Concept) isCoreConceptFor Saxophones (as a Topic).
It can be used widely to talk about document annotations, subject directories, etc.
hasTopic is very general. For example, consider the following cases:
(1) A biography of Brigitte Bardot hasTopic 'star system'
(2) The concept of 'starlet' hasTopic 'cinema'
(3) A biography of Claude Chabrol hasTopic 'Nouvelle Vague'.
For example, Saxophone (as a Concept) isCoreConceptFor Saxophones (as a Topic).
It can be used widely to talk about document annotations, subject directories, etc.
hasTopic is very general. For example, consider the following cases:
(1) A biography of Brigitte Bardot hasTopic 'star system'
(2) The concept of 'starlet' hasTopic 'cinema'
(3) A biography of Claude Chabrol hasTopic 'Nouvelle Vague'.
Vicinity is typically established with reference to a threshold on the number of concepts or entities that are common to the two Topic(s), or based on a geometrical semantics applied to the spaces common between two topics (cf. ontopic.owl ontology).
Overlap is typically established with reference to a threshold on the number of concepts or entities that are common between the two topics. Alternatively, it can be established with reference to the a geometrical semantics applied to the spaces (super-topics) of which topics are part (cf. ontopic.owl ontology).
Both concepts and topics are used to classify entities, but concepts typically have an "is a" relation to the entities; e.g.
(1) A biography of Brigitte Bardot hasTopic 'star system' (Topic)
(2) A biography of Brigitte Bardot is a Biography (Concept)
(3) A biography of Claude Chabrol hasTopic 'Nouvelle Vague' (Topic)
(4) The Nouvelle Vague is a CulturalMovement (Concept)
Topics have a controversial intuition across common sense, document management systems, knowledge organization systems, etc.
There is an interesting duality of topics: they are commonly interpreted as areas of shared knowledge within a Community (therefore as collections of social objects). On the other hand, existing directories and thesauri use 'topic' (or 'subject') more restrictively, as a relation between a document and a concept.
For example, thesauri do not usually distinguish when their 'concepts' (cf. skos:Concept) are actually intended as concepts (in the sense of Concept in this pattern) and when they are intended as topics. The distinction is clear when you compare these two sample sentences: 'the football topic is part of the sport topic' vs. 'the concept of football is part of the concept of sport'.
While the first is perfectly acceptable, the second is counterintuitive and even possibly wrong. This effect is due to the fact that concepts are 'intensional' notions and are not intended as areas of knowledge, document spaces, etc., which are 'extensional' notions.
Accordingly to these basic observations, in this pattern Concept and Topic result to be disjoint, and an appropriate representation should be in place in order to model thesauri. E.g. skos:Concept should be mapped to the union of Concept and Topic.
Additional information
It is a simplified version of the ontology http://ontologydesignpatterns.org/ont/dul/ontopic.owl
Scenarios
No scenario is added to this Content OP.
Reviews
There is no review about this proposal. This revision (revision ID 9138) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
There is no Modeling issue related to this proposal.
References