| rdfs:comment
| - Authoring of Adaptive Hypermedia comprises the design and creation process of adaptive hypermedia. It has been long considered as secondary to adaptive hypermedia delivery. This is not surprising in the early stages of adaptive hypermedia, when the focus was on research and expansion. Now that adaptive hypermedia itself has reached a certain maturity, the issue is to bring it out to the community and let the various stakeholders reap the benefits. However, authoring and creation of hypermedia is not trivial at all. Unlike in traditional authoring for hypermedia and the web, a linear storyline is not enough. Instead, various alternatives have to be created for the given material. For example, if a course should be delivered both to visual and verbal learners, there should be created at leas
|
| abstract
| - Authoring of Adaptive Hypermedia comprises the design and creation process of adaptive hypermedia. It has been long considered as secondary to adaptive hypermedia delivery. This is not surprising in the early stages of adaptive hypermedia, when the focus was on research and expansion. Now that adaptive hypermedia itself has reached a certain maturity, the issue is to bring it out to the community and let the various stakeholders reap the benefits. However, authoring and creation of hypermedia is not trivial at all. Unlike in traditional authoring for hypermedia and the web, a linear storyline is not enough. Instead, various alternatives have to be created for the given material. For example, if a course should be delivered both to visual and verbal learners, there should be created at least two perfectly equivalent versions of the material in visual and in verbal form, respectively. Moreover, an adaptation strategy should be created that states that the visual content should be delivered to visual learners, whereas the verbal content should be delivered to the verbal learners. Thus, authors should not only be able to create different versions of their content, but be able to specify (and in some cases, design from scratch) adaptation strategies of delivery of contents. There already exist some approaches to help authors to build adaptive-hypermedia-based systems. However, there is a strong need for high-level approaches, formalisms and tools that support and facilitate the description of reusable adaptive hypermedia and websites. Such models started appearing (see, e.g., the AHAM model of adaptive hypermedia, or the LAOS framework for authoring of adaptive hypermedia). Moreover, recently have we noticed a shift in interest, as it became clearer that the implementation-oriented approach would forever keep adaptive hypermedia away from the ‘layman’ author. The creator of adaptive hypermedia cannot be expected to know all facets of the process as described above. Still, he/she can be reasonably trusted to be an expert in one of these facets. For instance, it is reasonable to expect that there are content experts (such as, e.g., experts in chemistry, for instance). It is reasonable to expect, for adaptive educational hypermedia, that there are experts in pedagogy, who are able to add pedagogical metadata to the content created by content experts. Finally, it is reasonable to expect that adaptation experts will be the one creating the implementation of adaptation strategies, and descriptions (metadata) of such nature that they can be understood and applied by laymen authors. This type of division of work determines the different authoring personas that should be expected to collaborate in the creation process of adaptive hypermedia. Moreover, the contributions of these various personas correspond to the different modules that are to be expected in adaptive hypermedia systems. Authoring of adaptive hypermedia can also be considered web engineering for adaptive web-based systems. Usually this term appears in connection with automatization of the authoring process, e.g., in automatic generation of links and contents based on meta-data. Moreover, this terms appears in connection with application of web standards in the authoring process.
|
![[RDF Data]](/fct/images/sw-rdf-blue.png)