IEC\/PAS 62883:2014(E) specifies a framework for adaptive handling of explicit interaction among humans and AAL spaces. This is based on a differentiation between explicit and implicit interaction as a consequence of the paradigm shift from Human-Computer Interaction to Human-Environment Interaction, further explained in the definition of the latter term. As a framework, a main subject matter of the specification is the identification of relevant areas for further standardization, thereby also looking at the interrelationships among the identified areas. The PAS also provides a first extensible specification in some of those areas.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | INTRODUCTION Figures Figure 1 \u2013 Paradigm shift from HCI to HEI <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | Figure 2 \u2013 logical separation of application and presentation layers <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 1 Scope Figure 3 \u2013 The scope of the specified UI framework marked by the green colour <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 2 Normative references 3 Terms, definitions and abbreviations 3.1 Terms and definitions Figure 4 \u2013 The notion of AAL spaces <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | Figure 5 \u2013 The need of smart environments to utilize channelsfor bridging between the physical world and the virtual realm <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | Figure 7 \u2013 The notion of a smart environment <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 3.2 Abbreviation 4 The Specification of the universAAL UI Framework 4.1 Overview <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 4.2 Analysis of the relationships between UI Handlers and I\/O Channels Figure 8 \u2013 An open system for plugging in applicationsand UI handlers independently from each other Figure 9 \u2013 Channel binding by I\/O devices <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | Figure 10 \u2013 The notion of a driver with the case of a UPNP-aware driver Figure 11 \u2013 The case of a universAAL aware driver <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 4.3 Dialog descriptions Figure 12 \u2013 Possible relationship between UI handlers and drivers <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | Figure 13 \u2013 The dialog package based on the notion of a form <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | Figure 14 \u2013 A possible graphical visualization of the mapping between dialog types and the predefined standard groups <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 4.4 The Adaptation Concept 4.4.1 Overview 4.4.2 Responsibilities of Applications Figure 15 \u2013 The universAAL framework for supporting adaptivity, which builds on top of the universAAL context and service buses (see footnote 4) <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 4.4.3 Responsibilities of UI handlers <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 4.4.4 Responsibilities on the brokerage layer Figure 16 \u2013 A model for describing access impairments <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | Figure 17 \u2013 Summary of the adaptation parameters <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 4.5 Provisions of the UI Framework 4.5.1 Introduction 4.5.2 The UI Bus and its brokerage protocols Figure 18 \u2013 The components comprising the universAAL UI framework <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | Figure 19 \u2013 The main messages exchanged on the UI Bus Figure 20 \u2013 The notion of a UI request as constructed by applications <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | Figure 21 \u2013 Overview of the sequence of actions when the priority check is positive <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | Figure 22 \u2013 The case of switching to a new UI handlerwhen handling changes in the context <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 4.5.3 The dialog manager and its role in assisting the UI Bus Figure 24 \u2013 The abstract class to be extended by applicationsthat want to send UI requests to the UI bus Figure 25 \u2013 The abstract class to be extended by UI handlersthat accept UI requests forwarded by the UI bus for rendering Figure 26 \u2013 The interface of the UI Bus <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 4.5.4 The Resource Manager Figure 27 \u2013 Access to the resources managed by the RM <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | Annex A (informative) Use cases A.1 Use Case: Supporting rich human computer interaction <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | A.2 Use Case: Healthy Lifestyle Service Package Use Case (universAAL) <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | Annex B (informative) An Overview of the universAAL Project Figure B.1 \u2013 Project ID Card <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | Figure B.2 \u2013 The three pillars of the universAAL platform <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" The universAAL framework for user interaction in multimedia AAL spaces<\/b><\/p>\n |