Concept

Topic Type. A thesaurus entry representing a concept. Concepts can be connected together using the Broader/Narrower association (to create hierarchical relationships) or the Concept Relationship association (to create cross-cutting relationships). Each concept can have any number of Warrant, Scope Note, Editor Note, General Note, History Note or Hierarchy Note occurrences.

Warrant

Occurrence Type that holds information about the source warrant for the concept. The warrant usually refers to the authoritative source document that the concept and its preferred term was taken from.

Scope Note

An Occurrence Type that holds information about the concept. Several subclasses are defined for specific types of scope note.

History Note

A note providing historical information about the entry - e.g. when it was first added or last updated.

Hierarchy Note

A note providing information about the hierarchical placement of the entry in the thesaurus hierarchy.

General Note

A note providing general information about the thesaurus entry.

Editor Note

A note providing editors with information about the entry. For example, a note indicating that the entry should be reviewed.

Non-Preferred Term

A Scoping Topic that can be used to scope base names on Concept topics that define the non-preferred terms for the concept.

Download Simple Thesaurus NPCL file

Organisational Entity

A high-level type for departments, teams and people in an organisation. This class has the following three subclasses:

Organisational Unit

Part of an organisation. Organisational units can be organised into a Parent Unit / Child Unit hierarchy.

Cross Functional Team

A team within an organisation that operates across the normal organisational hierarchy.

Person

An individual within an organisation. A Person can be leader of one Organisational Unit, a member of one Organisational Unit and a member of any number of Cross Functional Teams.

Content Item

This is an abstract base class for representing content such as documents, articles, memos and so on. Content Items can have any number of Project, Skill, Product or Concept topics associated as a Primary Subject or Secondary Subject. A Content Item can be an Input To or Output From a Task. A Content Item is the Responsibility Of a Person.

The Content Item class is marked as abstract, so users should choose one of the concrete base classes when creating their topics. The concrete subclasses defined in this ontology are:

Document

Used to represent an internal document such as an MS Word document or Excel spreadsheet.

Article

Used to represent short content items that are intended for wider consumption. Typically these will be items written for public dissemination (e.g. content published on a website).

Concept

Represents any concept that is relevant to the business. This topic type is taken from
the Techquila definition for thesaurus construction. If you wish to arrange concepts into a thesaurus structure, you may want to add our Simple Thesaurus Ontology to your topic map.

Product

A product used or created by the organisation. A Product is the Responsibility Of an Organisational Entity

Project

A project carried out by the organisation or some part of it. A Project is the Responsibility Of an Organisational Entity. A Project Works On a Product. A Project Has zero or more Tasks.

Task

Work carried out by an individual or group of individuals. A Task can be Assigned To zero or more People. A Task can have any number of Input Documents and any number of Output Documents. A Task can be Part Of a Project.

Skill

A Person Has any number of Skills. Skills can be arranged in a Parent Skill/Child Skill hierarchy.

Download the Simple Organisation Ontology NPCL file.