Apache Cocoon: a web applications framework for the JISC IE
| Pages | 70-77 |
| Published date | 01 March 2005 |
| DOI | https://doi.org/10.1108/03055720510588515 |
| Date | 01 March 2005 |
| Author | David Casal |
| Subject Matter | Information & knowledge management |
Apache Cocoon: a web
applications framework for the
JISC IE
David Casal
Luminas Internet Applications and University of East Anglia, Norwich, UK
Abstract
Purpose – Proposes to describe and evaluate Cocoon, an Apache Software Foundation project.
Design/methodology/approach – Reports from a digitisation and repository building experience
based on a number of Joint Information Systems Committee (JISC) projects, through which a need for
an open standards, open source framework for building XML-based applications emerged between
1998 to 2003. Describes and evaluates Cocoon, an Apache Software Foundation project. Uses a general
project outline to exemplify the potential impact that open source technologies have on JISC projects,
and presents two case studies based on the Artworld and Virtual Norfolk projects (both funded under
JISC 5/99).
Findings – Finds that Apache Cocoon as an ideal solution to emerging projects within or outside the
JISC environment. Argues that open source technologies offer a robust, sustainable architecture for the
future of academic information environments. Concludes with an outline of recent activity focused
around and driven by Apache Cocoon and its meaningful relationship with academic projects.
Originality/value – Contains useful information on Apache Cocoon.
Keywords Extensible MarkupLanguage, Information systems,Internet, Electronic media
Paper type Research paper
1. Background
1.1. Problem
1.1.1. Standards requirements from funding bodies. In recent years, it has become
common for public funding bodies to require that, as a condition for funding, bidding
projects adhere to certain standards. As an example, during the Joint Information
Systems Committee’s (JISC’s) initiative to bring into realisation their concept of an
Information Environment, guidelines were published describing which standards and
what levels of compliance to them were to be achieved in the lifetime of a project, to fit
better in the environment. Some of these were metadata standards, and some best
practice, general guidelines for web and overall i nformation publishing and
digitisation. For most bidding parties, the guidelines were daunting. The technical
level of expertise required was fairly high, and the tools available to achieve
compliance not very numerous. Further, there was a conceptual shift from JISC which
came with these guidelines; one where information was to be gathered, formalised
following standards to describe it, and then delivered as a product which could live in
harmony with other archives, repositories, applications and services. A vision quite
near to that of the Semantic Web, and one which required project builders to face a
string of acronyms: XHTML, CSS, DC, OAI, XML, XSLT, were all part of a picture
which contained fairly strict guidelines as to what was to be achieved, but few
guidelines on how to achieve it.
The Emerald Research Register for this journal is available at The current issue and full text archive of this journal is available at
www.emeraldinsight.com/researchregister www.emeraldinsight.com/0305-5728.htm
VINE
35,1/2
70
VINE: The journal of information and
knowledge management systems
Vol. 35 No. 1/2, 2005
pp. 70-77
qEmerald Group Publishing Limited
0305-5728
DOI 10.1108/03055720510588515
To continue reading
Request your trial