Online Training Course: An Introduction to W3C’s Mobile Web Best Practices (Sep to Nov 2009)

Monday, August 31, 2009 - World Wide Web Consortium - Web Standards

2009-08-31: W3C announces today the next edition of its successful online course to introduce Web developers and designers to its Mobile Web Best Practices. The next session runs from 7 September to 9 November 2009. W3C received very positive reviews from participants who attended the previous session, including:

SSML 1.1 Candidate Recommendation Updated

Thursday, August 27, 2009 - World Wide Web Consortium - Web Standards

2009-08-27: The Voice Browser Working Group has updated the Candidate Recommendation of Speech Synthesis Markup Language (SSML) Version 1.1. SSML is designed to provide a rich, XML-based markup language for assisting the generation of synthetic speech in Web and other applications. Although the Working Group has not formally identified any features as being at-risk, as a result of the previous publication, the Working Group now understands that some features may not receive adequate implementation experience. This draft identifies them in the status section and asks for feedback. A few editorial errors in the previous draft and the Implementation Report Plan document were also fixed. A list of changes from the previous draft is available. Learn more about the Voice Browser Activity. (Permalink)

W3C Announces Two New Co-Chairs for the HTML Working Group

Wednesday, August 26, 2009 - World Wide Web Consortium - Web Standards

2009-08-26: Tim Berners-Lee announced today that two people will join Sam Ruby (IBM) in co-Chairing the HTML Working Group: Paul Cotton (Microsoft) and Maciej Stachowiak (Apple). Chris Wilson has stepped down as co-Chair and indicated that he will be changing his focus to programmability in the web platform. As Berners-Lee wrote about this transition, "The work of this group is tremendously important to the Web. I am pleased that all three co-Chairs have taken on the responsibility for working closely with the editor and group to make HTML 5 a success." More information about the new Chairs is available in Berners-Lee's announcement. Learn more about the HTML Working Group. (Permalink)

HTML 5 Drafts Published

Tuesday, August 25, 2009 - World Wide Web Consortium - Web Standards

2009-08-26: The HTML Working Group has published Working Drafts of HTML 5 and HTML 5 differences from HTML 4. In HTML 5, new features are introduced to help Web application authors, new elements are introduced based on research into prevailing authoring practices, and special attention has been given to defining clear conformance criteria for user agents in an effort to improve interoperability. "HTML 5 differences from HTML 4" describes the differences between HTML 4 and HTML 5 and provides some of the rationale for the changes. Learn more about HTML. (Permalink)

SVG Open 2009 Schedule Available; Early-Bird Registration Ends 31 August

Tuesday, August 25, 2009 - World Wide Web Consortium - Web Standards

2009-08-25: SVG Open 2009, the 7th International Conference on Scalable Vector Graphics, will be held 2-4 October, hosted by Google in Mountain View, California, with workshops hosted by IBM, on 5 October. The theme is "SVG Coming of Age", reflecting increased industry support and interest by Web designers and developers. The schedule and confirmed keynote speakers are now available. Over 70 presentations will be delivered by SVG experts from around the globe, on topics including script libraries, authoring tools, mobiles, Web mapping and geo-location services, and much more. Chris Lilley, Doug Schepers, and the W3C SVG Working Group will be participating. Learn more about W3C's SVG Activity. (Permalink)

Blog Mothership

Monday, August 24, 2009 - Matt

Your Blog is Your Mothership.

Voice Extensible Markup Language (VoiceXML) 3.0 Draft Published

Monday, August 24, 2009 - World Wide Web Consortium - Web Standards

2009-08-25: The Voice Browser Working Group has published a Working Draft of Voice Extensible Markup Language (VoiceXML) 3.0. This document specifies VoiceXML 3.0, a modular XML language for creating interactive media dialogs that feature synthesized speech, recognition of spoken and DTMF key input, telephony, mixed initiative conversations, and recording and presentation of a variety of media formats including digitized audio, and digitized video. A list of changes from the previous draft is available. Learn more about the Voice Browser Activity. (Permalink)

Open City Data

Thursday, August 20, 2009 - Matt

Yesterday I was part of a press conference by Mayor Gavin Newsom promoting DataSF.org, which is one of San Francisco’s first steps at opening up. Tim O’Reilly also spoke and made the point to me afterward that as he dives deep into every part of the intersection of technology and government he’s most excited about the prospect for change at the city level. Here are some pictures from the event. I think we’ll see more along these lines, and more WordPress, for San Francisco in the future.

Starting a Bank

Thursday, August 20, 2009 - Matt

I often get asked something along the line of, “If you weren’t leading Automattic, what would you work on?” There’s not a single answer to this question; the answer changes day to day. But I think if you asked me today, I’d say I would like to start a bank.

There are very few people who really love their bank.Wwe’ve all dealt with overage fees that stack up, brain-dead fine print, and a general malaise. There’s also a unique opportunity in that mainstream contempt for financial institutions has never been higher, while at the same time there is an incredible amount of government backing that essentially makes it a no-risk environment. People are hungry just for anything different, something contrarian. A David to the Golaith banking industry.

The name of my bank would be something supremely boring, like SafeBank. The idea behind it is that bad behaviour in the banking world has been largely inevitable because their compensation structures incented people to do overly risky things. SafeBank would maintain a reserve level 2-3x higher than Fed requirements and any other bank. SafeBank would have no bonuses. Critics would say this would make it impossible to attract top-shelf talent. Every time the bank gets attacked we’d turn it into an advertising opportunity to emphasize why we’re different. “We can’t attract top-shelf talent? We take your money and put it in a vault. We don’t need the million-dollar bonus geniuses on Wall Street to do that. SafeBank. Bank, safe.”

In fact, the first few years of SafeBank would be largely focused on acquisition through every trick in the book. At the very beginning pull a Gmail/WordPress.com and make it invite-only, which will create a buzz and also allow you to give amazing white-glove service to the initial customers, who will in turn tell their friends and make a ton more buzz. (You can also target certain profitable segments and ultra-safe depositors at first, like Gmail users in San Francisco (using Firefox with an ad-blocker) who make six figures a year.) There would be only one style of checks and debit cards and they’d need a distinctive design so if you saw one you’d say, “What’s that?” which would then start the whole conversation again about how SafeBank is different.

For the first two years you could also do things like not allow accounts larger than the FDIC-insured limit. No one has ever heard of a bank turning away money! But you’d say that although everything SafeBank does is risk-free, it’s still a startup and if people have more than the insured limit (250k for single, 500k for couples) in an account, they should put the extra somewhere else. Again, this will impact a very low percentage of customers, but everyone will think it’s remarkable. This can be phased out after a few years; in fact, it would be a PR opportunity. “We’ve been in business now long enough that we feel comfortable with larger accounts.” Boom, free coverage.

I’m a tech guy so of course a lot of focus would be on the website. Imagine an old-time vintage design aesthetic combined with a Google-like simplicity and attention to speed. All logins would be two-factor, with the default being it’d SMS you a one-time code to log in when you gave your email address. A big part of the website would be the blog, of course. It would have a strong Ben Franklin-like common sense voice, and in addition to giving a few cool saving or home tips each week, it would cover at least one financial industry story a day.

  • “Bank of America spent $40,000,000 dollars on airplanes last year. We spent $40,000 to develop an iPhone application so you can check your balance from anywhere.”  (Hmm, the iPhone app should cost like $2.99.)
  • “Here’s how to block advertising when you browse the web with Firefox; it makes the web faster and less annoying.”
  • “Goldman Sachs just paid out 16 billion dollars in bonuses to their employees. If we had an extra 16 billion dollars lying around, we’d put it in the bank for a rainy day. (If Goldman had never paid out bonuses they never would have needed government intervention.)”
  • “So-and-so Bank’s website requires you to use Internet Explorer. We beg that you don’t, because there are way cooler and faster browsers. Here are 3 open source browsers you can switch to today.”
  • “68 Million Reasons Your Bank Sucks. That’s the amount BoA collected last quarter in needless ATM fees.”

(That’s all made up.) The headlines would almost write themselves, and every time a financial institution is in the news it’d be an opportunity to contrast why SafeBank is different and what the underlying philosophy is behind why it’s different.

All of the marketing would be on the web and viral, because it’d be an online-only bank like ING Direct. No storefronts where people have to wait in line or risk a bad interaction with a teller, or that get robbed and need insurance; basically a lot of the historical risk of running a bank could be eliminated. When you sign up it would have a “tell your friends about SafeBank” address book feature that would connect you to them if they signed up for an account, give you both money (Bank of America has something like this), and also make it easy to send them money, Paypal-style, if they have an account.

How would the bank make money? I think it wouldn’t touch anything risky on the financial side — it would be a data company. The first 3 years the focus would be entirely on customer acquisition, marketing, PR, and building a world-class tech team building a rock solid infrastructure. SafeBank would make way, way less money than banks currently do, but it would be more than enough to build an amazing product in a sustainable way, like Craigslist did with newspaper classifieds. After a certain milestone, say 100 billion in deposits, I would buy or clone Mint. SafeBank would have more (and more accurate) data about its customers than almost any other company in the world other than credit card companies, so the online interface would have Mint-like lead generation offers based on that information. For example, you spend $140 a month on electricity, but if you switch to this new solar provider you’d save $200 a year. Think of it like Gmail contextual advertising but based on where you spend your money rather than the words in an email. There also might be aggregate data opportunities for economic research or targeting, but I’m not sure if I like the privacy implications there.

SafeBank couldn’t raise VC or anything like that because having any sort of exit expectations would completely kill the safety story, but I think it could be bootstrapped and after a few years would be hugely profitable. Its existence would also put huge pressure on existing banks because despositors would be leaving in drones, putting pressure on their reserve requirements. Existing banks couldn’t compete in a traditional way because they have such a sordid history of customer apathy and bad PR. SafeBank wouldn’t be trying to capture their profits, it would largely be destroying them and making much smaller amounts of money in non-traditional bank ways. It would be somewhat like a credit union, but for the masses.

Anyway, this is just how my mind wandered this morning while brushing my teeth. Tomorrow I’ll think the last industry I’d every want to be in is banking. ;)

Would you trust your money to SafeBank?

XMLHttpRequest Drafts Published

Thursday, August 20, 2009 - World Wide Web Consortium - Web Standards

2009-08-20: The Web Applications Working Group has published updates to Working Drafts of XMLHttpRequest and XMLHttpRequest Level 2. The XMLHttpRequest specification is part of the Web application technology stack, enabling Ajax-style development. XMLHttpRequest defines an API that provides scripted client functionality for transferring data between a client and a server. XMLHttpRequest Level 2 offers additional features, such as cross-origin requests, progress events, and the handling of byte streams for both sending and receiving. Learn more about the Rich Web Client Activity. (Permalink)

Gravatar

Thursday, August 20, 2009 - Matt

Gravatar gets a light visual refresh, portent of things to come.

W3C Relaunches Multimodal Interaction Working Group

Wednesday, August 19, 2009 - World Wide Web Consortium - Web Standards

2009-08-19: W3C is pleased to announce the relaunch of the Multimodal Interaction Working Group to develop technology that enables users to use their preferred modes of interaction with the Web. Deborah Dahl (Invited Expert) chairs the group which is chartered to develop open standards to adapt to device, user and environmental conditions, and to allow multiple modes of Web interaction including GUI, speech, vision, pen, gestures, haptic interfaces, sensor data, etc. W3C Members may use this form to join the Working Group. Read about the Multimodal Interaction Activity. (Permalink)

Call for Review: XForms 1.1 Proposed Recommendation Published

Tuesday, August 18, 2009 - World Wide Web Consortium - Web Standards

2009-08-18: The Forms Working Group has published a Proposed Recommendation of XForms 1.1. XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML, ODF or SVG. XForms 1.1 refines the XML processing platform introduced by XForms 1.0 by adding several new submission capabilities, action handlers, utility functions, user interface improvements, and helpful datatypes as well as a more powerful action processing facility, including conditional, iterated and background execution, the ability to manipulate data arbitrarily and to access event context information. Comments are welcome through 22 September. Learn more about the XForms Activity. (Permalink)

Last Call: Widgets 1.0: APIs and Events

Tuesday, August 18, 2009 - World Wide Web Consortium - Web Standards

2009-08-18: The Web Applications Working Group has published a Last Call Working Draft of Widgets 1.0: APIs and Events. Widgets are full-fledged client-side applications that are authored using Web standards. Examples range from simple clocks, stock tickers, news streamers, games and weather forecasters, to complex applications that pull data from multiple sources to be "mashed-up" and presented to a user in some interesting and useful way. The APIs and Events specification defines a set of APIs and events for the Widgets 1.0 family of specifications. Comments are welcome through 15 September. Learn more about the Rich Web Client Activity. (Permalink)

From Chaos, Order: SKOS Recommendation Helps Organize Knowledge

Tuesday, August 18, 2009 - World Wide Web Consortium - Web Standards

2009-08-18: Today W3C announces a new standard that builds a bridge between the world of knowledge organization systems - including thesauri, classifications, subject headings, taxonomies, and folksonomies - and the linked data community, bringing benefits to both. Libraries, museums, newspapers, government portals, enterprises, social networking applications, and other communities that manage large collections of books, historical artifacts, news reports, business glossaries, blog entries, and other items can now use Simple Knowledge Organization System (SKOS) to leverage the power of linked data. The Semantic Web Deployment Working Group also published today two Group Notes with the Recommendation, updating the SKOS Primer and SKOS Use Cases and Requirements. Read the press release and testimonials and learn more about the Semantic Web Activity. (Permalink)

Last Call: Widgets 1.0: APIs and Events

Tuesday, August 18, 2009 - World Wide Web Consortium - Web Standards

2009-08-18: The Web Applications Working Group has published a Last Call Working Draft of Widgets 1.0: APIs and Events. Widgets are full-fledged client-side applications that are authored using Web standards. Examples range from simple clocks, stock tickers, news streamers, games and weather forecasters, to complex applications that pull data from multiple sources to be "mashed-up" and presented to a user in some interesting and useful way. The APIs and Events specification defines a set of APIs and events for the Widgets 1.0 family of specifications. Comments are welcome through 15 September. Learn more about the Rich Web Client Activity. (Permalink)

Incubator Group Report: Emergency Information Interoperability Framework (EIIF)

Tuesday, August 18, 2009 - World Wide Web Consortium - Web Standards

2009-08-18: The Emergency Information Interoperability Framework Incubator Group published their final report. The group also published Emergency Information Interoperability Frameworks, which describes some critical requirements for an interoperability information framework for emergency management, and provides candidate components of an ontology that can support interoperability for some common use cases. The approach discussed outlines how one can achieve information interoperability across the stakeholder functions within the area of emergency management. The group recommends that W3C initiate an Interest Group to continue the work of the Incubator Group and expand the outreach to standards development through partnerships with professional communities and interoperability workshops. This publication is part of the Incubator Activity, a forum where W3C Members can innovate and experiment. This work is not on the W3C standards track. (Permalink)

TEDMED

Tuesday, August 18, 2009 - Matt

I’m going to be attending TEDMED this year. I think we’re at a crucial juncture for health, where in my lifetime we’ll look back at our treatments today with the same wonder as we have when contemplating medicine before the understanding of germs. I have a feeling TEDMED will be the best spot to get a glimpse of this future.

OS X Optimizations

Sunday, August 16, 2009 - Matt

Monolingual is a Open Source utility for Mac OS X that removes all the not-needed languages from your computer, freeing up hundreds of megabytes. My Mac mini is going “laggy” with the mouse jumping around instead of being smooth when I move the cursor around — any more tips for optimizations?

Diminishing Data

Friday, August 14, 2009 - Matt

The diminishing returns on data, by Nick Carr riffing on an interesting interview with Hal Varian.

Evolution of Blogging

Friday, August 14, 2009 - Matt

The Evolution of Blogging by Om Malik.

Real-Time, Productive Communication

Thursday, August 13, 2009 - Matt

Real-Time, Productive Communication (using P2).

Augmented Reality Tube Finder

Tuesday, August 11, 2009 - Alex Schleifer

Very nice use of the iPhone 3GS' compass on this navigation app that finds (and points to) tube/metro stations in your vicinity. Seems like the BBC is really roling with the "augmented reality" moniker and you'll hear it way too many times in this three minute video but don't let it distract you from an otherwise great example of a portable HUD.

Augmented Reality Tube Finder

Tuesday, August 11, 2009 - Alex Schleifer

Very nice use of the iPhone 3GS' compass on this navigation app that finds (and points to) tube/metro stations in your vicinity. Seems like the BBC is really roling with the "augmented reality" moniker and you'll hear it way too many times in this three minute video but don't let it distract you from an otherwise great example of a portable HUD.

Clunker Broadband

Saturday, August 8, 2009 - Matt

Cash for Broadband instead of Clunkers.

6 Steps to Kill Your Community

Thursday, August 6, 2009 - Matt

There have been a number of new platforms popping up recently that claim to increase your user engagement, get you more comments, increase your traffic, and more, through means that I consider short-sighted and harmful. Since people seem not to mind, I thought I’d write a guide for how to increase the number of comments you get by 400-1,000% and ruin whatever shred of community you had on your site.

  1. Don’t Moderate. Allow anybody to post anything regardless of whether it contributes to the conversation or not. Stupidity, libel, hate, curse words are all okay because in the comments you have plausible deniability. Make sure people know that whatever they post will live forever, and anything goes. The few smart people you did have in your comments will enjoy responding to these folks. Advertisers love being next to a good fight, too.
  2. Allow Spam Through. I don’t mean the obvious viagra mortgage stuff, but the human-written and surface-thoughtful comment that “Florida Real Estate” or “Poll Widgets” decided to leave on your entry. Or the guy who comments on every post and has a 3-link signature. Or the lame startup that mentions itself at every possible opportunity, however tangentially related it is. Once spammers catch a sniff of this stuff getting through, they’ll descend on your site like locusts and instantly double or treble your “community.”
  3. Force Signup. You’re not a blog, you’re a social network cum media empire and even to leave the smallest comment you should make me fill out a profile, preferably with demographic information you can use in advertiser pitches later. (*cough* CNET) Please ignore useful services like Gravatar and try to get me to upload yet another profile picture because you think that makes your site more “sticky.” (In a sense of the word, it does.)
  4. Don’t Participate in Comments. Make it clear that your post itself is for annointed authors who don’t mix with the hoi polloi in the comments ghetto. Don’t link or highlight anything good from the comment section; those people silly enough to contribute content to your site for free should feel ignored. If an author does happen to drop in and make a comment, make sure it doesn’t stand out from the rest so it’s lost amid the sea of…
  5. Random Crap from Around the Web. Make sure any comments you have are buried by every random piece of “conversation” from around the web, especially retweets, Delicious links, Digg and Slashdot comments, pretty much anything will work here. Bonus points for unmoderated pingbacks, so every scraper spam blog copying the content of the post gets a free link in the comments.
  6. Design Like NASCAR. The more buttons, widgets, stickers, and visual clutter the better. I want to see every possible login system including but not limited to Facebook, Twitter, OpenID, Google Friend Connect, and that Myspace thing. Because of their respective crappy terms of service, use the giant buttons they insist on. Also include a megabyte of “share this” icons for every obscure service in every language. People love options! Complexity is for closers.

As a bonus, here are a few extra that don’t make any sense to me, but seem to be popular:

  1. Abandon Search Engines. Make sure your comment system is externally hosted on a separate domain and injects comments in via JavaScript, so everything is completely invisible to search engines. For bonus points, even if you have an existing database, say WordPress, with all of your comments, make sure the external service doesn’t synchronize any of the new stuff back into it, so you’re at the mercy of the external provider forever and ever.
  2. Be Famous! You’ll get thousands of comments on almost everything you post and make sure only to let through the most sycophantic and saccharine, don’t tolerate real conversation or debate. To spice it up every now and then opine on a known controversial subject like abortion and let your audience loose on each other like gladiators while you watch from the stands.
  3. Put the Comment Form at Top. This ensures everyone making a comment hasn’t read any of the discussion so they’ll leave a comment anyway even if the exact same thing has been said already or a question has already been answered.
  4. No Subscriptions. Don’t allow me to get email notifications of new stuff, make me visit your site and reload the page constantly to see if there’s anything new.
  5. Make People Click Click Click. Ideally do 1-comment-per-page CNET-style and your pageviews will go through the roof, but if you can’t stomach that just make comments-per-page setting low or have some sort of complicated nesting scheme.
  6. Treat Everyone the Same. If I’ve left hundreds of great comments over many years on your site, please make me wait in the moderation queue like some random stranger off Digg. Don’t let anyone know I’m a regular, or talk to me, or invite me to test out beta stuff, or pretty much anything that acknowledges my existence or shows any degree of trust.
  7. Don’t Ask Anything of Your Audience. No polls, surveys, or open-ended blog entries. What do those plebes know anyway?

Shameless: IntenseDebate does all of the software stuff right, or will shortly. Core WordPress threading, moderation, and whitelists are already built in but also check out Subscribe to Comments and of course Akismet.

What are your pet peeves and rules?

Namespaces in XML 1.0 (Third Edition) is a W3C Proposed Edited Recommendation

Thursday, August 6, 2009 - World Wide Web Consortium - Web Standards

2009-08-06: The XML Core Working Group has published the Third Edition of Namespaces in XML as W3C Proposed Edited Recommendation. XML Namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references. The Third Edition as proposed incorporates all outstanding errata. The review period is open until 14 September 2009. Learn more about the XML Activity. (Permalink)

CSSOM View Module: Updated Working Draft

Tuesday, August 4, 2009 - World Wide Web Consortium - Web Standards

2009-08-04: The Cascading Style Sheets (CSS) Working Group has published an updated Working Draft of CSSOM View Module. This specification describes APIs that should be useful for Web application authors. The APIs inspect and manipulate the view information of a document, such as the position of element layout boxes, the width of the viewport, and also an element's scroll position. Learn more about the Style Activity. (Permalink)

Last Call for Widgets 1.0: Access Requests Policy

Tuesday, August 4, 2009 - World Wide Web Consortium - Web Standards

2009-08-04: The Web Applications Working Group has published a Last Call Working Draft of Widgets 1.0: Access Requests Policy. This specification defines the security model controlling network access from within a widget, as well as a method for widget authors to request that the user agent grant access to certain network resources. Comments are welcome through 20 September 2009. Learn more about the Rich Web Client Activity. (Permalink)

App Store

Sunday, August 2, 2009 - Matt

Chris Messina on why Steve Jobs hates the App Store.