Knowledge, economy, technology and society: The politics of discourse

The WSIS is centrally interested in knowledge and has defined for itself a mission that is broadly humanitarian. Its development ‘talk’ is, rightly, replete with notions of equity, preserving culture, justice, human rights and so on. In incorporating such issues into knowledge society and economy discussions, WSIS has adopted a different posture towards knowledge than is seen in dominant discourses. This study analyses the dominant knowledge discourse using a large corpus of knowledge-related policy documents, discourse theory and an interrelational understanding of knowledge. I show that it is important to understand this dominant knowledge discourse because of its capacity to limit thought and action in relation to its central topic, knowledge. The results of this study demonstrate that the dominant knowledge discourse is technocratic, frequently insensitive to the humane mission at the core of the WSIS, and is based on a partial understanding of what knowledge is and how knowledge systems work. Moreover, I show that knowledge is inherently political, that the dominant knowledge discourse is politically oriented towards the concerns of business and technology, but that an emancipatory politics of knowledge is possible.

A reference architecture for instructional educational software

Our extensive research has indicated that high-school teachers are reluctant to make use of existing instructional educational software (Pollard, 2005). Even software developed in a partnership between a teacher and a software engineer is unlikely to be adopted by teachers outside the partnership (Pollard, 2005). In this paper we address these issues directly by adopting a reusable architectural design for instructional educational software which allows easy customisation of software to meet the specific needs of individual teachers. By doing this we will facilitate more teachers regularly using instructional technology within their classrooms. Our domain-specific software architecture, Interface-Activities-Model, was designed specifically to facilitate individual customisation by redefining and restructuring what constitutes an object so that they can be readily reused or extended as required. The key to this architecture is the way in which the software is broken into small generic encapsulated components with minimal domain specific behaviour. The domain specific behaviour is decoupled from the interface and encapsulated in objects which relate to the instructional material through tasks and activities. The domain model is also broken into two distinct models - Application State Model and Domainspecific Data Model. This decoupling and distribution of control gives the software designer enormous flexibility in modifying components without affecting other sections of the design. This paper sets the context of this architecture, describes it in detail, and applies it to an actual application developed to teach high-school mathematical concepts.