[html5] r3491 - [e] (0) Tweak microdata vcard example. Add appcache v2 idea for multiuser appcaches.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-07-28 18:17:32 -0700 (Tue, 28 Jul 2009)
New Revision: 3491

Modified:
   index
   source
Log:
[e] (0) Tweak microdata vcard example. Add appcache v2 idea for multiuser appcaches.

Modified: index
===================================================================
--- index	2009-07-29 00:32:00 UTC (rev 3490)
+++ index	2009-07-29 01:17:32 UTC (rev 3491)
@@ -43064,7 +43064,8 @@
  <h2>Assorted Contact Methods</h2>
  <ul>
   <li itemprop="tel" item><span itemprop="value">+1 (310) 597
-  3781</span> <span itemprop="type">work</span></li>
+  3781</span> <span itemprop="type">work</span>
+  <meta itemprop="type" content="pref"></li>
   <li><a itemprop="url"
   href="http://en.wikipedia.org/wiki/Jack_Bauer">I'm on
   Wikipedia</a> so you can leave a message on my user talk
@@ -43075,7 +43076,7 @@
   href="mailto:j.bauer at la.ctu.gov.invalid">j.bauer at la.ctu.gov.invalid</a></li>
   <li itemprop="tel" item><span itemprop="value">+1 (310) 555
   3781</span> <span><meta itemprop="type" content="cell">mobile
-  phone</span>></li>
+  phone</span></li>
  </ul>
  <p itemprop="note">If I'm out in the field, you may be better
  off contacting <span itemprop="agent" item="vcard"><a
@@ -49145,6 +49146,37 @@
 
        http://groups.google.com/group/gears-users/browse_thread/thread/efbd808325df607a/c73adb34f9b63cf7?hl=en&q=whatwg#c73adb34f9b63cf7
 
+
+     * 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>

Modified: source
===================================================================
--- source	2009-07-29 00:32:00 UTC (rev 3490)
+++ source	2009-07-29 01:17:32 UTC (rev 3491)
@@ -48614,7 +48614,8 @@
  <h2>Assorted Contact Methods</h2>
  <ul>
   <li itemprop="tel" item><span itemprop="value">+1 (310) 597
-  3781</span> <span itemprop="type">work</span></li>
+  3781</span> <span itemprop="type">work</span>
+  <meta itemprop="type" content="pref"></li>
   <li><a itemprop="url"
   href="http://en.wikipedia.org/wiki/Jack_Bauer">I'm on
   Wikipedia</a> so you can leave a message on my user talk
@@ -48625,7 +48626,7 @@
   href="mailto:j.bauer at la.ctu.gov.invalid">j.bauer at la.ctu.gov.invalid</a></li>
   <li itemprop="tel" item><span itemprop="value">+1 (310) 555
   3781</span> <span><meta itemprop="type" content="cell">mobile
-  phone</span>></li>
+  phone</span></li>
  </ul>
  <p itemprop="note">If I'm out in the field, you may be better
  off contacting <span itemprop="agent" item="vcard"><a
@@ -55922,6 +55923,37 @@
 
        http://groups.google.com/group/gears-users/browse_thread/thread/efbd808325df607a/c73adb34f9b63cf7?hl=en&q=whatwg#c73adb34f9b63cf7
 
+
+     * 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>Introduction</h4>