A Document-Oriented Paradigm for the Construction of Content-Intensive Applications

Abstract

In this paper we describe our work on the formulation of a document-oriented paradigm for improving the construction and maintenance of content-intensive applications (i.e. applications that make intensive use of the information provided by the experts in a given domain: the contents). According to this paradigm, the development of a content-intensive application must be the result of close collaboration between two kinds of actors: domain experts and developers. The goal of this collaboration is the authoring of (i) a set of documents describing the most relevant aspects of the application (i.e. the contents and other relevant customizable features); (ii) a grammar describing a domain-specific markup language that will be used to make the structure and the data in these documents explicit; and (iii) a suitable processor for this language. The final running application will be automatically produced by processing the marked documents with this processor. The use of this paradigm in the development of content-intensive applications can increase the initial cost of application production, but in the long run it can substantially improve maintenance and portability, and promote information and software reuse as well. We have successfully applied this paradigm to the development of educational and hypermedia applications, and knowledge-based systems. From these experiences, we have found that the feasibility of the paradigm depends to a great extent on having mechanisms that enable the incremental definition of the markup languages and the incremental construction of their processors. This has led us to the formulation of a documentoriented approach for the development of content-intensive applications tightly coupled with these principles of incremental formulation and operationalization of domain-specific markup languages.

Form Follows Function: Model-Driven Engineering for Clinical Trials

“…Sierra et al [30] describe a document-centric approach to application development, similar to ours in the sense of involving a domain metamodel, models as structured documents, and model-driven generation of software artifacts; but they expect domain experts to author models in markup languages like XML rather than by simpler form completion. McLaren and Wicks [22] discuss a generative framework using XML; they present an 'indirect' approach using XSLT to turn an XML model into an XML-or other format of-software artifact, and a 'direct' approach using traditional (for example, Java) code to parse and interpret XML on the fly.…”

Model-checking for adventure videogames

“…Among these roles, he-Adventurei considers that producing and maintaining the storyboard are the primal activities in the development process of this kind of games, and thus it adopts a document-driven approach [48,49]. In this approach, the writers use a descriptive markup language (the he-Adventurei language) to make the structure of the story explicit.…”

A Game-Based Adaptive Unit of Learning with IMS Learning Design and <e-Adventure>

“…To achieve this purpose, <e-Adventure> extends our previous work in a documentoriented approach to the production and maintenance of content-intensive applications [25]. For this purpose, <e-Adventure> draws from the existing expertise in the field of Domain-Specific Languages [29] and Descriptive Markup Languages [6], and it provides an XML syntax [3] for the definition of the games.…”