1. LAOS: Layered WWW AHS Authoring Model and their corresponding Algebraic Operators Dr. Alexandra Cristea a.i.cristea@warwick.ac.uk http://www.dcs.warwick.ac.uk/~acristea/

2. Invited Tutorial, Madrid, Spain April 2008 LAOS 1.What is LAOS? 2.Concept based adaptation 3.LAOS components 4.Why LAOS? 5.LAOS authoring steps 6.Future directions

3. Invited Tutorial, Madrid, Spain April 2008 What is LAOS?

4. Invited Tutorial, Madrid, Spain April 2008 What is LAOS ? a generalized model for generic adaptive hypermedia authoring based on the AHAM model based on concept maps http://wwwis.win.tue.nl/~alex/HTML/Minerva/papers/ WWW03-cristea- mooij.dochttp://wwwis.win.tue.nl/~alex/HTML/Minerva/papers/ WWW03-cristea- mooij.doc http://www.ifets.info/journals/7_4/7.pdfhttp://www.ifets.info/journals/7_4/7.pdf

5. Invited Tutorial, Madrid, Spain April 2008 Why LAOS?

6. Invited Tutorial, Madrid, Spain April 2008 General motivation for layer distributed information Flexibility Expressivity (semantics: also meta-data) Reusability Non-redundancy Cooperation Inter-operability Standardization

7. Invited Tutorial, Madrid, Spain April 2008 LAOS components

8. Invited Tutorial, Madrid, Spain April 2008 LAOS components domain model (DM), goal and constraints model (GM), user model (UM), adaptation model (AM) and presentation model (PM)

9. Invited Tutorial, Madrid, Spain April 2008

10. LAOS motivation in detail Why domain model (DM) ? Why goal and constraints model (GM)? Why user model (UM)? Why adaptation model (AM)? and Why presentation model (PM)?

11. Invited Tutorial, Madrid, Spain April 2008 LAOS motivation in detail Why domain model (DM) ? Because of historical AHS, ITS, AHAM Why goal and constraints model (GM)? Why user model (UM)? Why adaptation model (AM)? and Why presentation model (PM)?

12. Invited Tutorial, Madrid, Spain April 2008 LAOS motivation in detail Why domain model (DM) ? Why goal and constraints model (GM)? Why user model (UM)? Because of historical ITS, AHS, AHAM Why adaptation model (AM)? and Why presentation model (PM)?

13. Invited Tutorial, Madrid, Spain April 2008 LAOS motivation in detail Why domain model (DM) ? Why goal and constraints model (GM)? Why user model (UM)? Why adaptation model (AM)? and Because of AHAM – see also LAG !! Why presentation model (PM)?

14. Invited Tutorial, Madrid, Spain April 2008 LAOS motivation in detail Why domain model (DM) ? Why goal and constraints model (GM)? Why user model (UM)? Why adaptation model (AM)? and Why presentation model (PM)? Because of Kuypers, AHAM

15. Invited Tutorial, Madrid, Spain April 2008 LAOS motivation in detail Why domain model (DM) ? Why goal and constraints model (GM)? Because of book metaphor Also because of goal adaptation!! (see adapt to what?) Why user model (UM)? Why adaptation model (AM)? and Why presentation model (PM)?

16. Invited Tutorial, Madrid, Spain April 2008 GM book metaphor – why? Domain model: –equivalent to skip the presentation and just tell the user to read the book. search space too big Not only one purposeful orientation

17. Invited Tutorial, Madrid, Spain April 2008 GM motivation intermediate authoring step, goal & constraints related: goals: focused presentation –specific end-state constraints: limit search space –DM filter

18. Invited Tutorial, Madrid, Spain April 2008 DM

19. Invited Tutorial, Madrid, Spain April 2008 GM

20. Invited Tutorial, Madrid, Spain April 2008 Authoring steps in LAOS domainSTEP 1: write domain concepts + concept hierarchy + attributes (contents) + other domain relations GMSTEP 2: add content related adaptive features regarding GM (design alternatives – AND, OR, weights, etc.) UMSTEP 3: add UM related features (simplest way, tables, with attribute-value pairs for user-related entities (AHAM); UM can be represented as a concept map) adaptationSTEP 4: decide among adaptation strategies, write in adaptation language medium-level adaptation rules or give the complete set of low level rules (such as condition-action (CA) or IF-THEN rules). presentationSTEP 5: define format (presentation means-related; define chapters)

21. Invited Tutorial, Madrid, Spain April 2008 LAOS components – definitions

22. Invited Tutorial, Madrid, Spain April 2008 Domain concept model Definition 1. An AHS domain map DM is determined by the tuple, –where C: set of concepts, – L: set of links, –Att a set of DM attributes Definition 2. A domain concept c DMi. C is defined by –where A : set of attrs and C : set of sub-concepts. Constraint 1. A min is the minimal set of (standard) attributes required for each concept to have (A A min ). –for sufficient meta-data –if A min = required standard attributes.

23. Invited Tutorial, Madrid, Spain April 2008 Domain concept model – cont. composite domain conceptDefinition range 2.1. A domain concept c C is a composite domain concept if c.C. atomic domain conceptDefinition range 2.2. A concept c C is an atomic domain concept if c.C=. domain linkDefinition 3. A domain link l L is a tuple with S,E {DM i.c k } i,k (S, E ) start and end sets of DM concept instances, respectively; N set of labels of the links; W set of weights of the links.

24. Invited Tutorial, Madrid, Spain April 2008 Domain concept model – cont. Definition 4. A domain attribute a DMi.C.A is a tuple, where –type is the name of the DM attribute; –val is the value (contents) of the DM attribute. Constraint 2. concept c must be involved at least in one link l. This special relation is called hierarchical link (link to ancestor concept). Exception: root concept.

25. Invited Tutorial, Madrid, Spain April 2008 algebraic operators & respective operations over the model constructors –create, edit destructors –delete visualization or extractors –list, view, check compositors –repeat Effects –restructuring (constructors, destructors and any compositors using at least one operator belonging to the previous categories) or –structure neutral (visualization and any compositors applied to visualization alone)

26. Invited Tutorial, Madrid, Spain April 2008 [1][1] We assume here that val is defined analogously for CM, c, l. operation & operator Range of operation in DMDescription Create & C Input (atomic): optionally object name (text label) of objects such as for DM x,; father concept for c; ids (numerical) of ( S, E ) and labels, weights for l, a i [h] (with h>A min ) Input (set): as above for sets of objects {c j } +,{l j } +,{a i [h]} + (with 1 h A min ) · Output space: DM, C, L, A · Output: DM x, {c j } *,{l j } *,{a i [h].type}* creates one object such as a concept map, concept, link, a non- standard attribute creates sets of objects such as set of new hierarchical child nodes and/ or links connected to the same parent or a full standard attributes set

27. Invited Tutorial, Madrid, Spain April 2008 Edit & E Input: object ids or expression Output: { {DM x, c, l, a i [h]}.type}* edits the object value Delete & D Input: as the two above together, condition or expression Output space: DM, C, L, A deletes an object (set) from the corresponding structure or empties the contents

28. Invited Tutorial, Madrid, Spain April 2008 List & L Input: Any sets from above, optional condition or expression Output: interface object lists the objects of the set(s) View & V Input: (set of) object id-s and mode (e.g., Graph/ Text) Output: interface object gives alternative views of the results to the author Check & Ck Input: (set of) object id-s from DM, C, L, A, checking goal, (and implicitly their value domains) Output: interface object checks the checking goal for the selected object and informs about value domain trespasses Repeat & R Input: Any of above, number of times or other stopping condition Output space: same as operation performed Repeats any of the operations above

29. Invited Tutorial, Madrid, Spain April 2008 Goal and constraints model constraint conceptDefinition 5. A constraint concept g GMi.G in GM is defined by the tuple GA is a set of attributes; G a set of sub-concepts; DMj.c C is the ancestor DM concept and DMj.c.a A is an attribute of that concept; GMi is the name of the GM map instance to whom it belongs. constraint linkDefinition 6. A constraint link gl L is a tuple with S,E {DMi.ck}i,k (S, E ) start and end sets of GM concept instances, respectively; N set of labels of the links; W set of weights of the links.

30. Invited Tutorial, Madrid, Spain April 2008 Description Create & C Atomic operation & operators Range of operation in GM Input: original concept id in GM and attribute id; optionally object name (text label) of objects such as for GM x, father concept for c; ids (numeric) of (S, E); labels, weightsfor l Input: as above for sets of objects {c j } +,{l j } +,{a i [h].var} + (1 h 2 ) · Output space: GM, G, L, A · Output: GM x, {c j } *,{l j } *, {a i [h].type}* creates object e.g. GM map, concept, link, a non-standard attribute creates sets of objects e.g., set of new hierarchical child nodes +/- links to the same parent or a full standard attributes set Edit & E Input: object ids or expression Output: { {GM x, c, l, a i [h]}.val}* edits the object value Delete & D Input: as the two above together, condition or expression Output space: GM, G, L, A deletes an object (set) from the corresponding structure or empties the contents

31. Invited Tutorial, Madrid, Spain April 2008 List & L Input: Any sets from above, optional condition or expression Output: interface object lists the objects of the set(s) View & V Input: (set of) object id-s and mode (e.g., Graph/ Text) Output: interface object gives alternative views of the results to the author Check & Ck Input: (set of) object id-s from GM, G, L, A c, checking goal, (and implicitly their value domains) Output: interface object checks the checking goal for the selected object and informs about value domain trespasses Repeat & R Input: Any of above, number of times or other stopping condition Output space: same as operation performed Repeats any of the operations above

32. Invited Tutorial, Madrid, Spain April 2008 What can LAOS do for you?

33. Invited Tutorial, Madrid, Spain April 2008 Example 1: flexibility index between concept C1 and rest of concepts in DM for automatic semantic linking in the DM or GM where C = card(DM) and A min = card( A min )

34. Invited Tutorial, Madrid, Spain April 2008 Example 2: flexibility degree for selecting attributes from DM concept C1 for GM, considering the order

35. Invited Tutorial, Madrid, Spain April 2008 Future developments LAOS

36. Invited Tutorial, Madrid, Spain April 2008 Further developments LAOS Operators for each layer (partially done) Automatic transformations between layers for authoring simplification (done) Automatic concept linking (done) Verification work of the different layers (partially done)

37. Invited Tutorial, Madrid, Spain April 2008 LAOS summary a five level AHS authoring model with a clear cut separation of the processing levels: 1.the domain model (DM), 2.the goal and constraint model (GM), 3.the user model (UM), 4.the adaptation model (AM) - more LAG following 5.the presentation model (PM).

38. Invited Tutorial, Madrid, Spain April 2008 Any questions?