tag:blogger.com,1999:blog-13722520.post1049060986696756013..comments2024-01-23T17:05:43.163-08:00Comments on Calendar Swamp: Will HTML 5 make calendar sharing even swampier?Scott Macehttp://www.blogger.com/profile/01831862884367555570noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-13722520.post-42297411162572186022011-09-29T13:34:08.660-07:002011-09-29T13:34:08.660-07:00HTML5 by itself is not the issue. The question is ...HTML5 by itself is not the issue. The question is what <b>related</b> technologies that the browser will be able to use through api:s.<br /><br />But journalists and marketing people tend to call every new web technology "HTML5".<br /><br />So far Mozilla has not started to work on calendar access. No sign of that among the listed bugs in https://bugzilla.mozilla.org/show_bug.cgi?id=673923<br /><br />One thing we do not want is for a web page to access ones calendar or contacts without a very clear and informed user consent. Implications for security and personal integrity are enormous. And the current "click ok" model is woefully inadequate since users are programmed to say yes without really thinking.<br /><br />The one technology that HTML5 (in the wide marketing speak sense) will provide is an offline mode, meaning you can access and change "online" calendar and contacts data while disconnected from the net.<br /><br />Using this model one can envision a phone or slate where locally stored calendar and contacts data is unnecessary, since the web app is always available.<br /><br />Another issue is that web technologies can now be used to build local apps. Most apps built with Java for Android or Objective C + Cocoa for iOS could quite easily be duplicated using modern web technologies. Thus "HTML5" must not always run inside a traditional browser.Lars Gunther (itpastorn)https://www.blogger.com/profile/11544012919049072827noreply@blogger.com