topic.owl
type: Ontology
scenarios: "The topic of Moby Dick is the hatred of humanity","What is the main subjects in neswpapers today? And more specifically?"
version info: 1.1 - Updated by Aldo Gangemi with proper references, annotations, etc. (Feb 2010) 1.0 - Created by Sara Bernardini (2009)
version info: 1.1 added rdfs:isDefinedBy for all named entities
comment: It is a simplified version of the ontology http://ontologydesignpatterns.org/ont/dul/ontopic.owl
has author: Sara Bernardini
has intent: To represent topics and their relations.
has 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.
covers requirements: What is the topic of something?, What topics are included in this one?, What are the topics near to that one?
extracted from: http://www.ontologydesignpatterns.org/ont/dul/ontopic.owl
imports: partof.owl
imports: cpannotationschema.owl

far topic from
type: ObjectProperty
type: SymmetricProperty
label: è un argomento lontano da @it
comment: The opposite to vicinity relation between two topics, e.g. 'star system' (as a Topic) is farTopicFrom 'geology' (as a Topic). 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).
range: Topic
domain: Topic

has core concept
type: ObjectProperty
comment: A Concept is a core concept for a Topic when it can classify many entities that have that Topic. For example, Saxophone (as a Concept) isCoreConceptFor Saxophones (as a Topic).
range: Concept
domain: Topic
inverse of: è concetto centrale di {it}

ha argomento più specifico {it}
type: ObjectProperty
type: TransitiveProperty
label: has subtopic
comment: The relation between two instances of a Topic, in terms of their cultural coverage. For example, Sport hasSubTopic Football. It can be used widely to talk about document annotations, subject directories, etc.
sub property of: hasPart
range: Topic
domain: Topic
inverse of: è argomento più specifico di {it}

ha argomento {it}
type: ObjectProperty
label: has topic
label: ha argomento @it
comment: The relation between something and its Topic (subject, argument, domain, theme, subject area, etc.). 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'.
range: Topic
inverse of: is topic of
domain: Thing

è concetto centrale di {it}
type: ObjectProperty
label: is core concept for
comment: A Concept is a core concept for a Topic when it can classify many entities that have that Topic. For example, Saxophone (as a Concept) isCoreConceptFor Saxophones (as a Topic).
domain: Concept
range: Topic

è argomento più specifico di {it}
type: ObjectProperty
type: TransitiveProperty
label: is sub topic of
comment: The relation between two Topic(s), in terms of their cultural coverage. For example, Football isSubTopicOf Sport. It can be used widely to talk about document annotations, subject directories, etc.
sub property of: isPartOf
range: Topic
domain: Topic

is topic of
type: ObjectProperty
label: è argomento di @it
comment: The relation between something and its Topic (subject, argument, domain, theme, subject area, etc.). 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'.
domain: Topic
range: Thing

near topic to
type: ObjectProperty
type: SymmetricProperty
label: è un argomento vicino a @it
comment: The vicinity relation between two topics, e.g. 'star system' (as a Topic) is nearTopicTo 'cinema' (as a Topic). 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).
range: Topic
domain: Topic

overlapping topic
type: ObjectProperty
type: SymmetricProperty
comment: The relation between two topics, e.g. 'star system' (as a Topic) is overlappingTopic with 'Bollywood movies' (as a Topic). 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).
domain: Topic
range: Topic

Concept
type: Class
label: Concetto @it
disjoint with: Topic
comment: A Concept is a social object, which is used to classify entities. Differently from a Topic 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)

Topic
type: Class
label: Argomento @it
equivalent class: Restriction
  on property: is topic of
  min cardinality: 1
subclass of: Restriction
  on property: è argomento più specifico di {it}
  all values from: Topic
subclass of: Restriction
  on property: ha argomento più specifico {it}
  all values from: Topic
comment: A topic, or subject, argument, domain, theme, subject area, etc. 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.