Help:Knowledge unit

Concept

In the TALQ project a structure for competence description (the sectoral layer) is developed where Skills, Knowledge and Autonomy / attitude are underlaying to the competences. While the Skills are mostly unique, and described as part of the competence description, the Knowledge and Autonomy / attitude descriptions are often reusable.

Therefore they are described in separate blocks that can be linked to the competence.

This has several advantages, the knowledge blocks can be:

• reused in the competences
• used to write a syllabus, where the inverse relation with competences gives context to the “theory”
• related to each other based on “prerequisite knowledge” , in order to include fundamental knowledge that is not directly related to a competence
• structured in “knowledge fields” clustering knowledge in logical groups.
• enriched with teaching tips, learning materials, evaluation methods, sources, …
• used to develop concrete learning materials and exercises.

Definition

A knowledge block is a coherent and documented collection of the knowledge components of a learning topic that always occur together in learning or competence description.

Size or volume of a knowledge block

The size or volume, in other words how much knowledge is contained in a unit, needs to be considered carefully to ensure the reusability of the blocks and to fulfill the requirements described above. This is not an abstract science, but needs an approximation method. To support the development, some questions can guide you to critically look at the results.

• Do the knowledge components always occur together in relation to a single competence?
• Do the knowledge components fit in a syllabus structure?
• Are they belonging to the same knowledge field, the same topic?
• Can the knowledge unit be described in a single concept that is concrete and understandable, in other words, can it have a clear title?
• Does the block / unit has a “teachable size”, does it limits to one topic?
• Do blocks fit together, are there no overlaps or gaps?

Properties used

Below, all the properties used to describe a knowledge unit are described, including remarks on syntax, links to value lists and required values. (Properties with an * are essential for the functioning of the system)

Header

Label or Title*

The label or title represents the knowledge unit. It should be clear to the readers

* Type: Monolingual 
* Syntax: Nouns 

Description

The description is a short sentence that defines the title, it helps the readers to understand the exact meaning.

* Type: Monolingual
* Syntax:

Alternative label

Can be used to give alternative names or ways of writing for searching purposes.

* Type: Monolingual, multiple values possible
* Syntax:

Technical properties

Instance of*

Technical field to represent the type of information in the Item

* Type: Item
* Value: “Knowledge” (Q4)

Part of value list*

Technical field to make the Item part of a value list.

* Type: Item
* Value: “Knowledge value list” (Q40)

General information

Scope note

Can be used to clarify boundaries of a unit.

* Syntax: starts with “includes” or “excludes”
* Type: Monolingual

Knowledge detail

Knowledge components of the unit Multiple values possible

* Type: Monolingual
* Syntax: Nouns with specifications

Structuring information

Knowledge field*

* Type: Item
* Value list: Knowledge field value list (Q16)

Unique identifier

Orders the knowledge units in a field Good practice is to use multiples of 10, to be able to insert units later.

* Type: String
* Syntax: numeric value 	

Prerequisite knowledge

Refers to other knowledge units that are needed to understand / teach this unit.

* Type: Item
* Value list:

Underlaying to competences (inverse property label of knowledge ( ))

Shows what competences use this knowledge

* Type: Item
* Value list:

Training

Teaching tips

Monolingual-long