This page lists information about subject http://www.w3.org/2004/02/skos/core by displaying relations and properties
Direct links from the subject.
| Property | Value |
|---|---|
|
The subject is an instance of a class. |
|
|
SKOS Vocabulary @en |
|
|
Alistair Miles |
|
|
Sean Bechhofer |
|
|
An RDF vocabulary for describing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies. @en |
|
|
Dave Beckett |
|
|
Nikki Rogers |
|
|
Participants in W3C's Semantic Web Deployment Working Group. |
Inverse links to the subject.
| Property | Subject |
|---|---|
|
skos:closeMatch is used to link two concepts that are sufficiently similar that they can be used interchangeably in some information retrieval applications. In order to avoid the possibility of "compound errors" when combining mappings across more than two concept schemes, skos:closeMatch is not declared to be a transitive property. |
|
|
Relates two concepts coming, by convention, from different schemes, and that have comparable meanings |
|
|
A statement or formal explanation of the meaning of a concept. |
|
|
skos:exactMatch is used to link two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications. skos:exactMatch is a transitive property, and is a sub-property of skos:closeMatch. |
|
|
skos:relatedMatch is used to state an associative mapping link between two conceptual resources in different concept schemes. |
|
|
Relates a concept to a concept with which there is an associative semantic relationship. |
|
|
skos:narrowMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes. |
|
|
skos:broadMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes. |
|
|
Relates a concept to a concept that is more specific in meaning. |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
Links a concept to a concept related by meaning. |
|
|
Relates an ordered collection to the RDF list containing its members. |
|
|
An ordered collection of concepts, where both the grouping and the ordering are meaningful. |
|
|
Relates a collection to one of its members. |
|
|
An idea or notion; a unit of thought. |
|
|
A meaningful collection of concepts. |
|
|
A note that helps to clarify the meaning and/or the use of a concept. |
|
|
A general note, for any purpose. |
|
|
A note about the past state/use/meaning of a concept. |
|
|
An example of the use of a concept. |
|
|
A note for an editor, translator or maintainer of the vocabulary. |
|
|
A note about a modification to a concept. |
|
|
A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme. |
|
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
|
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
|
|
A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag. |
|
|
Relates a concept to the concept scheme that it is a top level concept of. |
|
|
A set of concepts, optionally including statements about semantic relationships between those concepts. |
|
|
Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |