Concept
An abstract idea or notion; a unit of thought.
Concept Scheme
A set of concepts, optionally including statements about semantic relationships between those concepts.
A concept scheme may be defined to include concepts from different sources.
Thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', and other types of controlled vocabulary are all examples of concept schemes. Concept schemes are also embedded in glossaries and terminologies.
Collection
A meaningful collection of concepts.
Labelled collections can be used with collectable semantic relation properties e.g. skos:narrower, where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.
A property which can be used with a skos:Collection.
Collectable Property
The following rule applies for this property: [(?x ?p ?c) (?c skos:member ?y) (?p rdf:type skos:CollectableProperty) implies (?x ?p ?y)]
Ordered collections can be used with collectable semantic relation properties, where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.
Ordered Collection
An ordered collection of concepts, where both the grouping and the ordering are meaningful.
hidden label
A lexical label for a resource that should be hidden when generating visual displays of the resource, but should still be accessible to free text search operations.
The following rule applies for this property: [(?c skos:memberList ?l) elementOfList(?e,?l) implies (?c skos:member ?e)]
member list
An RDF list containing the members of an ordered collection.
A concept that is more general in meaning.
Broader concepts are typically rendered as parents in a concept hierarchy (tree).
has broader
Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.
A reference to a related resource.
Relation
An image that is a symbolic label for the resource.
symbolic label
This property is roughly analagous to rdfs:label, but for labelling resources with images that have retrievable representations, rather than RDF literals.
example
An example of the use of a concept.
Type includes terms describing general categories, functions, genres, or aggregation levels for content. Recommended best practice is to select a value from a controlled vocabulary (for example, the DCMI Type Vocabulary [DCMITYPE]). To describe the physical or digital manifestation of the resource, use the Format element.
Resource Type
The nature or genre of the content of the resource.
definition
A statement or formal explanation of the meaning of a concept.
A resource may have only one primary subject per concept scheme.
has primary subject
A concept that is the primary subject of the resource.
A general note, for any purpose.
This property may be used directly, or as a super-property for more specific note types.
note
This property replaces the two deprecated properties skos:privateNote and skos:publicNote. To describe a note for a particular audience (e.g. 'editor', 'indexer', 'general user') use a note property with a related resource description and the dc:audience property.
Narrower concepts are typically rendered as children in a concept hierarchy (tree).
A concept that is more specific in meaning.
has narrower
An alternative lexical label for a resource.
alternative label
Acronyms, abbreviations, spelling variants, and irregular plural/singular forms may be included among the alternative labels for a concept. Mis-spelled terms are normally included as hidden labels (see skos:hiddenLabel).
Title
A name given to the resource.
Typically, a Title will be a name by which the resource is formally known.
An entity primarily responsible for making the content of the resource.
Creator
Examples of a Creator include a person, an organisation, or a service. Typically, the name of a Creator should be used to indicate the entity.
A note for an editor, translator or maintainer of the vocabulary.
editorial note
Description may include but is not limited to: an abstract, table of contents, reference to a graphical representation of content or a free-text account of the content.
Description
An account of the content of the resource.
An entity responsible for making the resource available
Examples of a Publisher include a person, an organisation, or a service. Typically, the name of a Publisher should be used to indicate the entity.
Publisher
A note about a modification to a concept.
change note
A concept with which there is an associative semantic relationship.
related to
A subject indicator for a concept. [The notion of 'subject indicator' is defined here with reference to the latest definition endorsed by the OASIS Published Subjects Technical Committee.]
This property allows subject indicators to be used for concept identification in place of or in addition to directly assigned URIs.
subject indicator
is primary subject of
A resource for which the concept is the primary subject.
A note about the past state/use/meaning of a concept.
history note
alternative symbolic label
An alternative symbolic label for a resource.
A member of a collection.
member
semantic relation
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.
A concept related by meaning.
The preferred lexical label for a resource, in a given language.
No two concepts in the same concept scheme may have the same value for skos:prefLabel in a given language.
preferred label
Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 [W3CDTF] and follows the YYYY-MM-DD format.
Date
A date associated with an event in the life cycle of the resource.
A note that helps to clarify the meaning of a concept.
scope note
Examples of a Contributor include a person, an organisation, or a service. Typically, the name of a Contributor should be used to indicate the entity.
An entity responsible for making contributions to the content of the resource.
Contributor
The present resource may be derived from the Source resource in whole or in part. Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.
A reference to a resource from which the present resource is derived.
Source
A resource for which the concept is a subject.
is subject of
This property replaces the deprecated skos:TopConcept class.
has top concept
A top level concept in the concept scheme.
Coverage
Coverage will typically include spatial location (a place name or geographic coordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity). Recommended best practice is to select a value from a controlled vocabulary (for example, the Thesaurus of Geographic Names [TGN]) and that, where appropriate, named places or time periods be used in preference to numeric identifiers such as sets of coordinates or date ranges.
The extent or scope of the content of the resource.
A concept may be a member of more than one concept scheme.
in scheme
A concept scheme in which the concept is included.
has subject
A concept that is a subject of the resource.
The following rule may be applied for this property: [(?d skos:subject ?x)(?x skos:broader ?y) implies (?d skos:subject ?y)]
Subject and Keywords
The topic of the content of the resource.
Typically, a Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme.
Recommended best practice is to use RFC 3066 [RFC3066], which, in conjunction with ISO 639 [ISO639], defines two- and three-letter primary language tags with optional subtags. Examples include "en" or "eng" for English, "akk" for Akkadian, and "en-GB" for English used in the United Kingdom.
Language
A language of the intellectual content of the resource.
An unambiguous reference to the resource within a given context.
Resource Identifier
Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Example formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN).
Typically, a Rights element will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. If the Rights element is absent, no assumptions can be made about the status of these and other rights with respect to the resource.
Rights Management
Information about rights held in and over the resource.
Format
The physical or digital manifestation of the resource.
Typically, Format may include the media-type or dimensions of the resource. Format may be used to determine the software, hardware or other equipment needed to display or operate the resource. Examples of dimensions include size and duration. Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types [MIME] defining computer media formats).
No two concepts in the same concept scheme may have the same value for skos:prefSymbol.
The preferred symbolic label for a resource.
preferred symbolic label
Combining Search & Consistency Algorithms
Finding the Maximum in a One-Variable Function
Problem Representation - The STRIPS Model
Characteristics, Architecture & Functionality of Knowledge-based Systems
Characteristics of Knowledge-based Systems
Bayesian Probability Networks & Inference Networks
Knowledge-based Systems & Conventional Programs
Advanced Interaction with the Environment
Knowledge-based Systems Development Tools
Evaluation of Knowledge Representation Methods
Fuzzy Variables, Numbers, Propositions & Rules
Solution-driven Hierarchical Classification
RDF - The Web Resources Description Model
The Frame Problem & the STRIPS Representation
Characteristics of Configuration Problems
Convergence & Replacement of the Population
Interaction Between Creating & Executing Plans
Agents with Beliefs, Desires, Intentions