Make App config a partially fulfilled requirement.

index.html

@@ -511,8 +511,9 @@
 
     The following requirements are only partially addressed by existing specifications: <a href="#req-interoperability" class="reqRef"></a>,
     <a href="#req-mobile-specific" class="reqRef"></a>,
-    <a href="#req-offline" class="reqRef"></a>,
-    <a href="#req-responsive" class="reqRef"></a>, and
+    <a href="#req-responsive" class="reqRef"></a>,
+    <a href="#req-meta-data" class="reqRef"></a>,
+    <a href="#req-offline" class="reqRef"></a>, and
     <a href="#req-orientation-lock" class=reqRef></a>.
 
     There is ongoing work to address each of those requirements within W3C as detailed below. The CG encourages these efforts.
@@ -522,18 +523,23 @@
 
     While <a href="#req-interoperability" class="reqRef"></a> and <a href="#req-mobile-specific" class="reqRef"></a> are generally addressed by a number of existing specifications, there is one area which is still problematic - user input. Touch-enabled devices delay click inputs (presumably to handle long and double taps). While there are some [different](https://developers.google.com/mobile/articles/fast_buttons) [solutions](https://github.com/ftlabs/fastclick) that remove the delay, developers tend to rely instead on touch events [[TOUCH-EVENTS]]. In turn, this creates content which doesn't work properly when used with a different kind of input mechanism. In order to address this situation, the [Pointer Event WG](http://www.w3.org/2012/pointerevents/) was formed and has published a first Working Draft [[POINTER-EVENTS]].
 
+    Responsive Images
+    -----------------
+
+    While a lot has been done to address <a href="#req-responsive" class="reqRef"></a>, notably through media queries, there is no set solution for responsive images to date. The [Responsive Images CG](http://www.w3.org/community/respimg/) has made a proposal ([The picture element](http://picture.responsiveimages.org/)), and so has the HTML WG ([The srcset attribute](http://www.w3.org/html/wg/drafts/srcset/w3c-srcset/Overview.html)). The HTML WG is set to determine the merit of both solutions and examine whether they should be combined.
+
+    Application meta-data
+    ---------------------
+
+    The multitude of existing formats to describe application meta-data (<a href="#req-meta-data" class="reqRef"></a>) have been [listed](http://www.brucelawson.co.uk/2011/installable-web-apps-and-interoperability/) [elsewhere](http://blog.tobie.me/post/14262541286/app-manifests-an-anthology) already. The WebApps WG is [chartered](http://www.w3.org/2012/webapps/charter/Overview.html#deliverables) to work on this and has two related specs: Widget Packaging and Configuration [[WIDGETS]] (which has had little traction among the main vendors), and Web Application Manifest Format and Management APIs [[WEBAPPS-MANIFEST-API]] (which is still an early Editor's draft). Additionally, the combination of a number of [[HTML5]] features, such as the `title` element, `meta` application-name element and `link` icons element provides similar capabilities, yet this solution lacks sufficient comprehensiveness and cohesiveness to meet the requirements.
+
     Offline
     -------
 
     Currently, Application Cache is the only Web technology designed to address <a href="#req-offline" class="reqRef"></a>. Its issues have already been [exhaustively](http://www.w3.org/2011/web-apps-ws/Report) [documented](https://etherpad.mozilla.org/appcache-london) [elsewhere](https://etherpad.mozilla.org/appcache). This technology is very complex, poorly understood, and hard to use. It is also [marked at risk](http://www.w3.org/TR/html5/#status-of-this-document) in the HTML5 specification.
 
     Recently, the [WebApps WG has decided to take over this work](http://www.w3.org/2012/10/30-webapps-minutes.html#item06) with the blessing of the HTML WG. In parallel, the [Fixing Application Cache CG](http://www.w3.org/community/fixing-appcache/) is collecting case studies, use cases and requirements.
 
-    Responsive Images
-    -----------------
-
-    While a lot has been done to address <a href="#req-responsive" class="reqRef"></a>, notably through media queries, there is no set solution for responsive images to date. The [Responsive Images CG](http://www.w3.org/community/respimg/) has made a proposal ([The picture element](http://picture.responsiveimages.org/)), and so has the HTML WG ([The srcset attribute](http://www.w3.org/html/wg/drafts/srcset/w3c-srcset/Overview.html)). The HTML WG is set to determine the merit of both solutions and examine whether they should be combined.
-
     Screen Orientation
     ------------------
 
@@ -543,17 +549,10 @@
     Unaddressed requirements
     ========================
 
-    The following requirements aren't addressed by existing specifications: <a href="#req-meta-data" class="reqRef"></a>,
-    <a href="#req-fast-scroll" class=reqRef></a>, and
-    <a href="#req-fullscreen" class=reqRef></a>.
+    The following requirements aren't addressed by existing specifications: <a href="#req-fast-scroll" class=reqRef></a>, and <a href="#req-fullscreen" class=reqRef></a>.
 
     However, there is early work going on to address some of these.
 
-    Application meta-data
-    ---------------------
-
-    The multitude of existing formats to describe application meta-data (<a href="#req-meta-data" class="reqRef"></a>) have been [listed](http://www.brucelawson.co.uk/2011/installable-web-apps-and-interoperability/) [elsewhere](http://blog.tobie.me/post/14262541286/app-manifests-an-anthology) already. The WebApps WG is [chartered](http://www.w3.org/2012/webapps/charter/Overview.html#deliverables) to work on this and has two related specs: Widget Packaging and Configuration [[WIDGETS]] (which has had little traction among the main vendors), and Web Application Manifest Format and Management APIs [[WEBAPPS-MANIFEST-API]] (which is still an early Editor's draft).
-
     Momentum and infinite scrolling
     -------------------------------