New abstract and revised status for User Context FPWD June_2014_FPWD
authorMichael Cooper <cooper@w3.org>
Tue, 17 Jun 2014 12:00:50 -0400
branchJune_2014_FPWD
changeset 221 4c3f1dd10f1b
parent 219 98e9e4954292
child 223 a18652a3ad51
New abstract and revised status for User Context FPWD
src/indie-ui-context.html
--- a/src/indie-ui-context.html	Mon Jun 16 14:20:11 2014 -0400
+++ b/src/indie-ui-context.html	Tue Jun 17 12:00:50 2014 -0400
@@ -88,17 +88,20 @@
 	<body>
 		
 		<section id="abstract">
-			<p>This specification, in conjunction with the <a href="./indie-ui-events.html">Events Module</a>, is intended address the problem of device-, <abbr title="operating system">OS</abbr>-, and localization-independent control of web content. See the <a href="#intro">introduction</a> for background and usage examples.</p>
+			<p>IndieUI: User Context defines a set of preferences that users can choose to expose to web applications. User can set preferences for features such as screen and font size, color, and typographical preferences. Users with disabilities can provide information about assistive technologies in use, indicate that the display is in an accessibility mode, and indicate whether and what kind of subtitles and audio descriptions they need. Web applications can choose to use this information to optimize the presentation without a requirement to target a specific device, operating system, or locale. While customizations based on these properties benefit users, the information could also be used to make assumptions about users or compromise anonymity. Therefore, the specification allows users to opt out and choose not to expose information on a category basis.</p>
+			<p>See the <a href="#intro">introduction</a> for background and usage examples. Also see the <a href="http://www.w3.org/WAI/intro/indieui">IndieUI Overview</a>.</p>
 		</section>
 
 		<section id="sotd">
-			<p>This is a First Public <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#RecsWD">Working Draft</a> by the <a href="http://www.w3.org/WAI/IndieUI/">IndieUI Working Group</a> (IndieUI WG) of the <a href="http://www.w3.org/WAI/">Web Accessibility Initiative</a>. The Working Group has produced this document based on initial proposals and review of features critical to include for this first review opportunity. The <a href="http://www.w3.org/WAI/IndieUI/track/products/3">IndieUI: User Context tracker</a> lists open issues and actions, and links to closed issues and actions, which are the basis for most of the previous and upcoming updates; newer issues are tracked in <a href="https://www.w3.org/Bugs/Public/buglist.cgi?component=IndieUI%3A%20User%20Context&amp;product=IndieUI&amp;version=1.0"><abbr title="World Wide Web Consortium">W3C</abbr> Bugzilla for IndieUI: User Context</a>. The Working Group has published <a href="http://www.w3.org/TR/indie-ui-requirements/">use cases
-				and requirements</a> that are expected to be met by this specification; feedback on these is encouraged as well. Also see the <a href="http://www.w3.org/WAI/intro/indieui">IndieUI Overview</a>.  <!--A <a href="#changelog">history of changes to UndieUI: User Context</a> is available in the appendix.--> </p>
+			<p>This is a First Public <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#RecsWD">Working Draft</a> by the <a href="http://www.w3.org/WAI/IndieUI/">IndieUI Working Group</a> (IndieUI WG) of the <a href="http://www.w3.org/WAI/">Web Accessibility Initiative</a>. The Working Group has produced this document based on initial proposals and review of features critical to include for this first review opportunity. The <a href="http://www.w3.org/WAI/IndieUI/track/products/3">IndieUI: User Context tracker</a> lists open issues and actions, and links to closed issues and actions, which are the basis for most of the previous and upcoming updates; newer issues are tracked in <a href="https://www.w3.org/Bugs/Public/buglist.cgi?component=IndieUI%3A%20User%20Context&amp;product=IndieUI&amp;version=1.0"><abbr title="World Wide Web Consortium">W3C</abbr> Bugzilla for IndieUI: User Context</a>. The Working Group has published <a href="http://www.w3.org/TR/indie-ui-requirements/">use cases and requirements</a> that are expected to be met by this specification; feedback on these is encouraged as well. Note the requirements posted at the time of this publication does not include User Context requirements; see the <a href="http://www.w3.org/WAI/IndieUI/wiki/User_Context/Requirements">User Context requirements wiki page</a> for a list of candidate requirements. <!--A <a href="#changelog">history of changes to UndieUI: User Context</a> is available in the appendix.-->
+			</p>
+			<p>For the First Public Working Draft, the Working Group has included a basic set of user context properties that the group believes provide high benefit and wide applicability. A larger set of properties has been identified as useful, but including them all might complicate initial adoption of the model. For this reason, many of those properties are currently expected to be introduced in later versions of the specification, but some may appear in future Working Drafts of this 1.0 version. Potential properties are explored on the <a href="http://www.w3.org/WAI/IndieUI/wiki/User_Context/Requirements">User Context requirements wiki page</a>.</p>
+			<p>Privacy is an important consideration for IndieUI: User Context. It is important that the specification provide an appropriate balance between the usefulness of the features defined and the ability of users to keep information confidential. The Working Group is coordinating with the <a href="http://www.w3.org/Privacy/">Privacy Interest Group</a>, and public input on this issue is also encouraged.</p>
 			<p>Feedback on this specification is essential to success of the technology. The IndieUI WG asks in particular:</p>
 			<ul>
-				<li>Does the spec meet its requirements, and are the requirements complete?</li>
-				<li>Does the spec meet both accessibility and mainstream use cases successfully without compromising one for the other?</li>
-				<li>Is this approach useful and necessary compared to existing techniques? </li>
+				<li>Does the specification meet its requirements, and are the requirements complete?</li>
+				<li>Is the set of properties appropriate for the 1.0 version? Should any properties be added or removed?</li>
+				<li>Is the privacy model satisfactory?</li>
 				<li>Is this approach easy to implement? If not, why not?</li>
 			</ul>
 			<p>To comment on this document, send email to <a href="mailto:[email protected]?subject=Comment%20on%20IndieUI:%20User%20Context%2026%20June%202014">[email protected]</a> (<a href="http://lists.w3.org/Archives/Public/public-indie-ui-comments/">comment archive</a>) or <a href="https://www.w3.org/Bugs/Public/enter_bug.cgi?product=IndieUI&amp;component=IndieUI:%20Events&amp;version=1.0">file an issue in <abbr title="World Wide Web Consortium">W3C</abbr> Bugzilla</a>. Comments should be made by <strong>1 August 2014</strong>. In-progress updates to the document may be viewed in the <a href="https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html">publicly visible editors' draft</a>.</p>