Matches in LOV for { <http://www.ontologydesignpatterns.org/ont/dul/ontopic.owl#Topic> ?p ?o. }
Showing items 1 to 12 of
12
with 100 items per page.
- Topic type Class.
- Topic comment "A topic, or subject, argument, domain, theme, subject area, etc.\nTopics have a controversial intuition across common sense, document management systems, knowledge organization systems, etc.\nHere we conceptualise a semiotic notion of iol:Topic as 'a (usually potential) dul:Collection of dul:SocialObject(s). \nFor example, 'music' is a topic constituted by the set of social objects that are associated with music-related entities. Such social objects can be information objects (texts, documents, words, images) about music-related entities, concepts classifying music-related entities, descriptions of musical theories and systems, etc.\nThe relation between social objects and topics is called here 'hasTopic', and is a rdfs:subPropertyOf dul:isMemberOf\nSpecific topics for e.g. a conversation or an article (therefore, closer to the notion of 'title' or 'entry') are called Subject(s).\n\nThere 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. \nThere is a sense of 'meaning' that can be reduced to the one given here to Topic (cf. the comment at the property dul:expresses), but in general there seems to be enough room to distinguish carefully between concepts and topics. \nFor example, thesauri do not usually distinguish when their 'concepts' (cf. skos:Concept) are actually intended as concepts (in the sense of dul:Concept) 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'. \nWhile 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.\nAccordingly to these basic observations, in this ontology dul: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 dul:Concept and Topic.".
- Topic label "Argomento".
- Topic label "Topic".
- Topic subClassOf B4ede144529449ba78efce7562e4d2be0.
- Topic subClassOf B70be31ff0037423d015c92a5c814e3c1.
- Topic subClassOf Bb4c82fc9abf7ac271b5036c19fda943a.
- Topic subClassOf Bc1ca466edb0c331d28e633ee7be58b8b.
- Topic subClassOf Bce4f509002405fd3eb5064fca9021540.
- Topic subClassOf Be67a8566639fa6fba660db81c371d1de.
- Topic subClassOf Collection.
- Topic equivalentClass B7cfae9e59f613474490016e4b485c597.