W3C home > Mailing lists > Public > public-html-commits@w3.org > July 2009

html5/spec Overview.html,1.2689,1.2690

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 29 Jul 2009 01:17:41 +0000
To: public-html-commits@w3.org
Message-Id: <E1MVxnZ-0006NM-Fv@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv24494

Modified Files:
Log Message:
Tweak microdata vcard example. Add appcache v2 idea for multiuser appcaches. (whatwg r3491)

Index: Overview.html
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2689
retrieving revision 1.2690
diff -u -d -r1.2689 -r1.2690
--- Overview.html	29 Jul 2009 00:32:06 -0000	1.2689
+++ Overview.html	29 Jul 2009 01:17:38 -0000	1.2690
@@ -38455,7 +38455,8 @@
  &lt;h2&gt;Assorted Contact Methods&lt;/h2&gt;
   &lt;li itemprop="tel" item&gt;&lt;span itemprop="value"&gt;+1 (310) 597
-  3781&lt;/span&gt; &lt;span itemprop="type"&gt;work&lt;/span&gt;&lt;/li&gt;
+  3781&lt;/span&gt; &lt;span itemprop="type"&gt;work&lt;/span&gt;
+  &lt;meta itemprop="type" content="pref"&gt;&lt;/li&gt;
   &lt;li&gt;&lt;a itemprop="url"
   href="http://en.wikipedia.org/wiki/Jack_Bauer"&gt;I'm on
   Wikipedia&lt;/a&gt; so you can leave a message on my user talk
@@ -38466,7 +38467,7 @@
   &lt;li itemprop="tel" item&gt;&lt;span itemprop="value"&gt;+1 (310) 555
   3781&lt;/span&gt; &lt;span&gt;&lt;meta itemprop="type" content="cell"&gt;mobile
-  phone&lt;/span&gt;&gt;&lt;/li&gt;
+  phone&lt;/span&gt;&lt;/li&gt;
  &lt;p itemprop="note"&gt;If I'm out in the field, you may be better
  off contacting &lt;span itemprop="agent" item="vcard"&gt;&lt;a
@@ -44175,6 +44176,37 @@
+     * Multiuser appcaches.
+       If the application code (HTML, JS, CSS) is all the same for two
+       users, then appcache works for multiple users by just having
+       the data for the users separate from the logic.
+       This is the expected model for most apps. For example, your
+       typical blog has just one set of CSS for all users.
+       For systems where the user affects what HTML, JS, and CSS is
+       served back, the spec as written pretty much requires that
+       there be one app per user, and one generic "login" app that
+       then redirects to one of those other apps - and where each app
+       has a different base URL, separate manifest, etc.
+       An alternative that we could explore in a future version is to
+       have the manifest include a manifest name, and then have script
+       that allows you to "activate" a particular manifest name for a
+       given appcache.
+       So each appcache group would be futher subdivided into named
+       subgroups, and for a given manifest URL with such a group of
+       subgroups, one subgroup would be the default one at a time. The
+       inactive ones would just lie dormant, but and the active ones
+       would act like now, but there'd be a scripted way to change the
+       default (and maybe query what available variants exist for the
+       current appcache), so that you could log back in as someone
+       else by just making the script pick the other user's variant,
+       and then reloading.
   --><h4 id="introduction-4"><span class="secno">6.9.1 </span>Introduction</h4><p><i>This section is non-normative.</i><p>In order to enable users to continue interacting with Web
   applications and documents even when their network connection is
   unavailable &mdash; for instance, because they are traveling outside
Received on Wednesday, 29 July 2009 01:17:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:09:24 UTC