A document model is a model of the
document.
A document is model-enhanced if the
document model is embedded in the document itself.
We can design a
model-enhanced document by introducing extra MAWC tags
into the document.
We have 4 kinds of MWAC tags:
All of them have levels. The following is an example of ts tags:
<ts>
<ts1>
<ts11> </ts11>
<ts12>
<ts121> </ts121>
</ts12>
</ts1>
<ts2>
<ts21>
</ts21>
</ts2>
</ts>
A simple example as to how to annotate the text.
Annotation is important and is to be done before you use any of the MAWC commands. These commands look for the <ts>, <is>, <as> and <vs> tags in the pages to execute.
Here is an example, which demonstrates this.
_______________________________________________________________________________________________________________________________
Text:
_______________________________________________________________________________________________________________________________
<html>
<body>
This is a sample.
<a href="#start">CLICK HERE</a> to go to the start of the page.
Here is an Image Tag <img src="xyz.jpg" align="right">
<a name="start"></a>
This is the start of the document.
</body>
</html>
_______________________________________________________________________________________________________________________________
After Annotation:
_______________________________________________________________________________________________________________________________
<html>
<body>
<ts>
This is a sample.
<ts1>
<a href="#start">CLICK HERE</a> < /FONT>
</ts1>
to go to the start of the page.
Here is an Image Tag
<is>
<img src="xyz.jpg" align= "right">< /FONT>
</is>
<ts1>
<a name="start"></a>< /FONT>
This is the start of the document.
</ts1>
</ts>
</body>
</html>
_______________________________________________________________________________________________________________________________
The TAGS that the user is supposed to insert are highlighted in color. The rules for adding tags are like:
Some bugs associated with the current version:
<ts><a href> RIGHT
<ts> <a href> WRONG
_______________________________________________________________________________________________________________________________
So the Above Annotated Text should look like
_______________________________________________________________________________________________________________________________
<html>
<body>
<ts>
This is a sample.
<ts1><a href="#start">CLICK HERE</a></ts1>
to go to the start of the page.
Here is an Image Tag
<is><img src="xyz.jpg" align="right"></is>
<ts1>
<a name="start"></a>< /FONT>
This is the start of the document.
</ts1>
</ts>
</body>
</html>
_______________________________________________________________________________________________________________________________
Adaptive hypermedia systems are the hypertext and hypermedia systems that reflect some features of the user in the user model and apply this model to adapt various visible aspects of the system to the user. [Peter1] From this definition, I want to point out 2 crucial aspects about adaptive media: the user model, the adapting ability of hypermedia documents. In the prototype Growing Book, we simplified the user model. But we model-enhanced the hypermedia documents by adding MAWC tags and thus make the adapting ability as the underlying nature of Growing Book hypermedia documents. Although we simplified the user model in current Growing Book prototype, I still want to give a brief explanation about user model because it's a preliminary base of the adapting. User model tells what aspects of the user working with the system can be taken into account when providing adaptation and to which features, that can be different for different users (and may be different for the same user at different time), the system can adapt. So far, five features are identified: users' goals, knowledge, background, hyperspace experience, and preferences. Users' knowledge is the most important user feature for adaptive media systems. User's knowledge is a variable for a particular user. An adaptive hypermedia system has to recognize the changes in the user's knowledge state and update the user model accordingly. The goals of the user is a feature related with the context of a user's work, for work in application systems, for searching in information retrieval systems or for problem solving and learning in educational systems. The User's background is the information related to user's previous experience outside the subject of the hypermedia system. The user's experience is how familiar the user with the structure of the hyperspace and how easy can the user navigate in it. The preferences of users have to be informed into the system directly or indirectly about such preferences or the system infers user's preferences from users' histories. There're 5 adapting techniques from a "what can be adapted" point of view: direct guidance, sorting, hiding, annotation, map adaptation. Direct guidance is the simplest technique, the system can outline visually the link to the "best" node. Adaptive ordering is to sort all the links of a particular page according to the user model and to some user-valuable criteria: the more close to the top, the more relevant the link is. Hiding restricts the navigation space by hiding links to "not relevant" pages. Adaptive annotation augments the links with some form of comments that can tell the user more about the current state of the nodes behind the annotated links. Map adaptation is to comprise various ways of adapting the form(structure) of global and local hypermedia maps presented to the user. The adapting technologies from the content adaptation point of view are additional explanations, prerequisite explanations and comparative explanations, and explanation variants. Additional explanations means hiding from the user some parts of information about a particular concept which are not relevant to the user's level of knowledge about this concept. The prerequisite explanations and comparative explanations are to change the information presented about a concept depending on the user knowledge level of related concepts. The explanation variants mean storing variants for some parts of the page content and the user gets the variant corresponds to his or her user model. Adaptive navigation support techniques are used to achieve several adaptation goals: to provide global guidance, to provide local guidance, to support local orientation, to support global orientation, and to help with managing personalized views in information spaces. Global guidance can be provided in hypermedia systems where users have some "global" information goal and browsing is the way to find the required information. Local guidance is to help the user to make one navigation step by suggesting(according to the preferences, knowledge, and background of the user) the most relevant links to follow from the current node. Local orientation support is to help the user in local orientation (i.e., to help them in understanding what is around and what is his/her relative position in the hyperspace). By providing additional information(i.e. annotation) about the nodes available from the current node and limiting(hiding) the number of navigation opportunities to decrease the cognitive overload. Global orientation support is to help the user to understand the structure of the overall hyperspace and his or her absolute position in it. Managing personalized views is to organize an electronic workplace for the users who need a access to a reasonably small part of a hyperspace. Each view is just a list of links to all hypermedia documents which are relevant to a particular working goal.