index.html
25.3 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>W3C Personalization Roadmap: Ubiquitous Web Integration of AccessForAll 1.0</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
.optional {text-decoration: line-through; display: none;}
dt.fm {font-weight: normal; margin-top: 5px;}
.ecma-block { border: 1px solid black; color: black; background-color: #dfdfdf; }
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base">
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE">
</head><body><div class="head">
<a href="http://www.w3.org/"><img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home"/></a>
<h1><a name="title" id="title"></a>W3C Personalization Roadmap: Ubiquitous Web Integration of AccessForAll 1.0</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a></h2>
<h2>W3C Working Group Note 09 April 2009</h2>
<dl><dt>This version:</dt><dd>
<a href="http://www.w3.org/TR/2009/NOTE-UWA-personalization-roadmap-20090409/">http://www.w3.org/TR/2009/NOTE-UWA-personalization-roadmap-20090409/</a>
</dd><dt>Latest version:</dt><dd>
<a href="http://www.w3.org/TR/UWA-personalization-roadmap/">http://www.w3.org/TR/UWA-personalization-roadmap/</a>
</dd>
<dt>Editors:</dt><dd>Andy Heath, The Open University, UK</dd><dd>Rich Schwerdtfeger, IBM</dd></dl>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
</div><hr><div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>This document describes an activity of integrating personalization with device context for the delivery of content materials and interface components that are customized to meet both individual personal needs and preferences and delivery context. It brings together the work of separate standards and specifications organizations and working groups, notably W3C Ubiquitous Web Applications working group, IMS Global Learning Consortium Accessibility Special Interest group, ISO/IEC JTC1 SC36 Information Technology for Learning, Education and Training: Human Diversity and Access For All working group and associated working groups in SC36. The document should be viewed as a roadmap for the work to be undertaken and includes description of the basis for the work, the organizational context, the likely technologies and a partially complete description of how the technologies fit together.
</p></div><div>
<h2><a name="status" id="status"></a>Status of this Document</h2>
<p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
<p>Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p>
<p>This document is a Working Draft by the <a href="http://www.w3.org/2007/uwa/">Ubiquitous Web Applications Working Group</a>.</p>
<p>As Web content becomes more complex a one-size-fits-all strategy for delivering accessible web solutions is inadequate. This document defines a roadmap for bringing personalization to the Web. It does so by molding the Access For All adaptive learning standards found in the IMS Global Learning Consortium and ISO SC36 to fit mainstream delivery context arbitration mechanisms. User personalization should be considered part of the delivery context of the device. This document is intended to serve as a guide for how the Working Group may integrate personalization information from other sources into the Working Group's ongoing work. It is likely to be updated as the work progresses.</p>
<p>It revises the timeline expected to accomplish the objectives set out in the Roadmap, following what is set out in the Ubiquitous Web Application Charter.</p>
<p>The Ubiquitous Web Application working group seeks feedback on the requirements, gap analysis, and plan set out in this document. In particular, the Working Group would like input about whether:</p>
<ul>
<li>The direction outlined in this plan captures addresses the needs for ubiquitous delivery across a broad range of devices;</li>
<li>There are better alternatives for delivering ubiquitous personalization over the Web.</li>
</ul>
<p>Please provide feedback on the Working Group's <a href="mailto:public-uwa@w3.org">public mailing list</a>, an archive of which is available at <a href="http://lists.w3.org/Archives/Public/public-uwa/">http://lists.w3.org/Archives/Public/public-uwa/</a>.</p>
<p> This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/40755/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>. </p>
</div><div class="front"><div class="div1">
<h2><a name="intro" id="intro"></a>Introduction</h2><p>This section is <a title="" href="#">informative</a>. </p><div class="div2">
<h3><a name="intro-layers-guidance" id="intro-layers-guidance"></a>Rational</h3><p>Delivery of content that is useful to and accessible to all in whatever delivery context or environment they are in at the time is a complex business potentially involving many technologies conforming to a variety of standards. This picture is big enough that to date different specifications and standards bodies have worked on the separate parts of the problem separately and not always in a way that interoperates. Completely different and separate business and technology scenarios have evolved completely separately and non-interoperably - for example mobile device technologies and desktop software technologies or learning technologies and banking. To date integration across these different technology and business worlds has been only on a small scale with isolated use cases, sometimes confined to a single vendor's products.
</p><p>
At the same time accessibility of content and interface to all users has become a more visible and necessary requirement as governments around the world mandate that all content and systems should be accessible to all and as the business cases for that, including for example delivery to consumers having an ever-increasing age profile, come into focus. Furthermore, with the advent of more visually complex, browser-delivered, content it is becoming increasingly important to deliver content alternatives to meet user's needs. This mandates a more flexible, personalized web infrastructure that will respond to the needs of each user. This provides a defines a plan and strategy, with standards collaboration, to define a personalized accessible infrastructure for the Web.
</p></div><div class="div2">
<h3><a name="requirements" id="requirements"></a>Requirements</h3><p>In order that content and interface components can be personalized for a given user in a given context we need set of key components to allow content to be transformed either through transcoding or replacement by equivalent alternatives. The major required informational components are:
</p><ul><li>
A functional personal needs and preferences description - what the user requires in machine readable form
</li><li>
A functional description of the immediate delivery context
</li><li>
Metadata describing properties of a resource in a form that can match (or not match) the personal needs and preferences of the user for that context.
</li></ul><p>
In order to ease progress on implementation and provide a consistent interoperable scheme it is desirable that resource instances, devices, and aggregation systems support a common vocabulary for these descriptive pieces to deliver a solution that matches the user's needs. For example, overlap or contradiction in requirements between the three sets makes implementation of matching more difficult. It is also desirable that the form of the information match both in model concept and detail terms. That is, it will ease the path if the information across the three sets is modeled using a common conceptual representation.
</p><p>
The major delivery level components being considered are:
</p><ul><li>
Open delivery transport layers: browser client-side storage to access the preferences in the browser and the use of Ajax to share preferences with the server component of the application.
</li><li>
Closed system personalization services for user preferences such as those provided by a profile repository stored on WebSphere Application Server.
</li><li>
Mashup offerings such as <a href="http://www-01.ibm.com/software/lotus/products/mashups/">Lotus Mashups</a></li></ul></div></div></div><div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#history">History</a><br>
2 <a href="#gaps">Gap Analysis</a><br>
3 <a href="#work">Existing work, organizations and work underway</a><br>
4 <a href="#usecases">Sample Use Cases</a><br>
4.1 <a href="#usecase_blind">Blind user prefers text equivalent</a><br>
4.2 <a href="#usecase_largefonts">Vision impaired user prefers large fonts</a><br>
4.3 <a href="#trascript">Hearing impaired user requiring closed captioning with video</a><br>
5 <a href="#timeline">Roadmap Timeline</a><br>
</p>
<h3><a name="appendices" id="appendices"></a>Appendix</h3><p class="toc">A <a href="#acknowledgments">Acknowledgments</a> (Non-Normative)<br>
</p></div><hr><div class="body"><div class="div1">
<h2><a name="history" id="history"></a>1 History</h2><p>This section is <a title="" href="#">informative</a>. </p><p>
The IMS Global Learning Consortium produced the <a href="http://www.imsglobal.org/accessibility">AccessForAll</a> specifications with the intent of improving the accessibility of e-learning for users. AccessForAll provides two matching specifications: Accessibility Metadata (ACCMD) for description of the accessibility properties of a resource, such as a Learning Object, Education package or web page, and Accessibility Preference Descriptions described by the specification called the Accessibility Learner Information Package (ACCLIP). Using the vocabulary of these two specifications together allows a system to choose the correct resource or modified resource to best match the access needs of a learner.
</p><p>
The AccessForAll specifications were then further developed into an ISO standard <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=41521">ISO/IEC 24751-1:2008, 24751-2:2008, 24751-3:2008 - Individualized adaptability and accessibility in e-learning</a>, education and training. Instead of ACCMD and ACCLIP instances this standard provides for a Digital Resource Description (DRD) and Personal Needs and Preferences statement (PNP) respectively.
</p><p>
The IMS Global Learning Accessibility working group is now developing version 2.0 of the AccessForAll specifications with the intent of harmonizing the changes made by ISO standardization, synchronizing terminology defined by the W3C Delivery Context Ontology, and delivering a new version of AccessForAll better aligned to meet the needs for mainstream adoption.
To facilitate mainstream adoption of personalization the W3C Ubiquitous Web Applications Working Group intends to incorportate AccessForAll v2.0 user preferences into the W3C Delivery Context Ontology to add personalization to delivery context specifications for a device. Once here, all devices will have a standard vocabulary for specifiying how the user experience may be personalized
as part of the overall device delivery context.
</p></div><div class="div1">
<h2><a name="gaps" id="gaps"></a>2 Gap Analysis</h2><p>This section is informative. </p><table border="1"><tr><th>Requirement</th><th>Fulfillment</th></tr><tr><td>User Preference Vocabulary</td><td>IMS GLC AccessForAll v2.0, ISO PNP aligned with device preferences from the W3C Delivery Context Ontology (DCO)</td></tr><tr><td>User Agent access to user preferences</td><td>Access through local browser storage and shared with server-side application components via Ajax.
Examples of Client Side Storage are:
<ul><li><a href="http://www.w3.org/TR/2008/WD-html5-20080610/structured.html#structured">HTML 5 Client-side storage</a></li><li><a href="http://gears.google.com/">Google Gears</a></li></ul>
</td></tr><tr><td>Standard Ontology for Device Personalization</td><td>Integrate AccessForAll Preferences into the <a href="http://www.w3.org/TR/dcontology/">W3C Delivery Context Ontology</a></td></tr><tr><td>Proprietary user Preference Stores</td><td>
<ul><li><a href="http://tdstage.teachersdomain.org:8001">Teacher's Domain Preference Store</a></li><li><a href="http://www.ibm.com/developerworks/websphere/techjournal/0701_ilechko/0701_ilechko.html">WebSphere Application Server federated repository</a> with <a href="http://www.w3.org/TR/dcontology/">DCO</a> extensions for Personalization</li></ul>
</td></tr><tr><td>Meta data implementation data data feeds</td><td><a href="http://www.ietf.org/rfc/rfc5023.txt">Atom</a></td></tr></table></div><div class="div1">
<h2><a name="work" id="work"></a>3 Existing work, organizations and work underway</h2><p>
Here we identify a number of pieces of work that we plan to integrate identify some of the work that needs to take place and its possible form.
</p><table border="1"><tr><th>Organization</th><th>Component</th><th>Source</th><th>Status</th><th>Kind of content</th><th>Overlaps with or needs to match with or supplements</th><th>Formats or Bindings available</th><th>Planned work</th></tr><tr><td>W3C UWAWG</td><td>Delivery Context Ontology</td><td><a href="http://www.w3.org/TR/dcontology/">DCO</a></td><td>W3C working draft 15th April 08</td><td></td><td>ISO/IEC JTC1 SC36</td><td>ontology</td><td></td></tr><tr><td>ISO/IEC JTC1 SC36</td><td>Individualized Adaptability for eLearning, Education and Training (24751): Personal Needs and Preference Statement (PNP)</td><td>ISO</td><td>expected published ISO standard September 08</td><td>functional accessibility and personalisation preferences to match with ISO/IEC JTC1 SC36</td><td>W3C UWAWG</td><td>Information model and Core and full ontology in draft</td><td></td></tr><tr><td>ISO/IEC JTC1 SC36</td><td>Individualized Adaptability for eLearning, Education and Training (24751) : Digital Resource Description (DRD)</td><td>ISO</td><td>expected published ISO standard September 08</td><td>Metadata describing accessibility and personalisation properties of a resource to match with W3C Delivery Context Ontology.</td><td>Metadata for relating resources and adaptations</td><td>Match with W3C Delivery Context Ontology and ISO SC36 PNP</td><td>Information model
<p>Core and full ontology in draft
</p>
</td></tr><tr><td>ISO/IEC JTC1 SC36</td><td>Metadata for Learning Resources work on Multimedia Element</td><td>internal public document TBC</td><td>work in progress</td><td>Metadata describing delivery resource properties</td><td>Supplement SC36 DRD, Match with W3C Delivery Context Ontology</td><td>editors draft information model</td><td></td></tr><tr><td>IMS</td><td>AccessForAll 2.0</td><td><a href="http://www.imsglobal.org/accessibility">Access for All Specifications</a></td><td>work in progress</td><td>
<ul><li>Revisions and Merger of SC36 DRD and PNP</li><li>Merge with W3C Delivery Context Ontology</li></ul>
</td><td></td><td>draft information model. Core and full profiles (ontologies) in consruction</td><td></td></tr><tr><td><a href="http://www.eu4all-project.eu/">European Unified Approach for Accessible Lifelong Learning project (EU4ALL)</a></td><td colspan="7">Implementation experience in an educational context with:
<ul><li>ISO SC36 PNP</li><li>ISO SC36 DRD</li><li>ISO SC36 Metadata for Learning Resources work on Multimedia Element</li></ul>
</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><ul><li><a href="http://www.w3.org/TR/dcontology/">W3C UWAWG Delivery Context Ontology (DCO)</a><ul><li>A formal model of the characteristics of the environment in which devices interact with the Web or other services.</li></ul></li><li>ISO/IEC JTC1 SC36 Individualized Adaptability for eLearning, Education and Training (24751)
<ul><li>This is a published ISO Standard available (September 2008) [here]
<ul><li>Part 1: Framework
<p>
This part describes how the parts relate together.
</p></li><li>Part 2: Personal Needs and Preference Statement (PNP)
<p>
Metadata describing, in a functional form, personal accesssibility requirements for an individual for a context.
</p></li><li>Part 3: Digital Resource Description (DRD) <p>
Metadata describing in a functional form in a way that can be matched to a PNP the accessibility properties of a resource and of adaptations for a resource and a mechanism for association of adaptations and resources.
</p></li></ul></li><li>ISO/IEC JTC1 SC36 Metadata for Learning Resources: Proposed work on Multimedia Element
<p>This is work in progress that is specifying Metadata to be associated with content describing some precise delivery requirements, such as audio and video codecs, screeen size etc. It is envisaged that the editors of that work will want to keep it harmonized with this.
</p></li><li> IMS Access For All 2.0
<p>This is work underway to update the ISO PNP and DRD.</p></li><li>The EU4ALL Project
<p> This is a major European project that is implementing personalization for accessibility based on the ISO PNP and DRD.
</p></li></ul></li></ul></div></div><div class="div1">
<h2><a name="usecases" id="usecases"></a>4 Sample Use Cases</h2>
This section provides some sample uses cases illustrating the need for personalization.
<p>
In each case it should become clear that user preferences must be part of the device
delivery context.
</p><div class="div2">
<h3><a name="usecase_blind" id="usecase_blind"></a>4.1 Blind user prefers text equivalent</h3><p>
It is commonly accepted that it is very difficult to make a complex visualization, such
as directions drawn on a map accessible to the blind. However, for people who are not blind
these visualizations have been useful for many sighted users. Rather than try to make them
accessible to a blind user it would be much easier to swap the map with a text alternative.
</p><p>
Here are two complex renderings of driving directions and the text equivalent:
</p><ul><li><a href="map.jpg">Map of Driving Directions</a></li><li><a href="earth.jpg">Satellite and superimposed street map of driving directions</a></li><li><a href="textequiv.jpg">Driving Directions</a></li></ul></div><div class="div2">
<h3><a name="usecase_largefonts" id="usecase_largefonts"></a>4.2 Vision impaired user prefers large fonts</h3><p>
User's with low vision will often require large fonts. What an acceptable large font is
is dependent on the device on which you are rendering it. For example, a 25 point font
may be way to large for a cellular phone having a very small screen.
</p></div><div class="div2">
<h3><a name="trascript" id="trascript"></a>4.3 Hearing impaired user requiring closed captioning with video</h3><p>
Users who are deaf or hard of hearing may require that video be delivered with
closed captioning turned on. This may be a simple function of turning that feature on
on your local device but it may also require the user to request videos which are closed
captioned in a specific language. In these cases a user would request the host system
to match the user's request with a set of available alternatives. Again, how the video is delivered
has dependencies on the network bandwidth and screen resolution.
</p></div></div><div class="div1">
<h2><a name="timeline" id="timeline"></a>5 Roadmap Timeline</h2><table border="1" cellpadding="2" cellspacing="0" summary="Merge AForAll with UWAWG Activities"><thead><tr><th colspan="10">Personalization Integration Timeline</th></tr></thead><tbody><tr><th scope="col">Deliverable</th><th scope="col">1st draft</th><th scope="col">2nd draft</th><th scope="col">Last Call</th><th scope="col">ends</th><th scope="col">CR</th><th scope="col">PR</th><th scope="col">REC</th><th scope="col">2nd Ed.</th><th scope="col">3rd Ed.</th></tr><tr><th scope="row">
IMS Access For All ACCMD/ACCLIP V2.0 (Core/Full Profiles)
</th><td>
March 31, 2009
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td></tr><tr><th scope="row">
ISO PNP and DRD with IMS V2 changes
</th><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td></tr><tr><th scope="row">
W3C Delivery Context Ontology with Personalization
</th><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td><td>
TBD
</td></tr></tbody></table></div></div><div class="back"><div class="div1">
<h2><a name="acknowledgments" id="acknowledgments"></a>A Acknowledgments (Non-Normative)</h2><p>This section is <a title="" href="#">informative</a>. </p><p>The editors wish to acknowledge the contributions of members of the UWA WG.
</p><p>
The editors wish to acknowledge the specific written contributions of:
</p><ul><li><p>Andy Heath (IBM)</p></li><li><p>Rich Schwerdtfeger (IBM)</p></li></ul></div></div></body></html>