Contents

Photo by Elaine Vallet

1. Open and/or/is/vs. Closed
2. Towards Openness (The Client is Always Right)
3. Side Notes on Standards
4. W3C Mobile Web Initiative
5. Web Apps, Widgets + Policy + Device APIs + Social = More $$$

Distribution of control (1/2)

Openness is a measure of the distribution of control.

Distribution of control (2/2)

	Closed	Open
Access to content	Walled Gardens: Operators	Open Web: Users
Deployment of services and applications	Locked Devices: Operators / Manufacturers	Open Platform: Service / Application providers
Technologies	Proprietary: Technology owners	Open Standards: Developers

Photos by dandy_fsi, pixelfrenzy, ldandersen, jasonb42882, Darwin Bell.

Closed is not evil...

Photo by Elaine Vallet

• Simple trust model
  The one in control is the one to blame
• Shorter time to market
  The one in control simply needs to agree with himself
• Simple business model
  The one in control is the one who makes money (possibly indirectly)

... but can't be global

Photo by Elaine Vallet

• Mass market
  Because big is not enough...
• The long tail
  How to benefit from the long tail in a closed market?
• Innovation is boxed
  How can I reach the moon?
• Frustration
  I need freedom!

Open is chic

Open/Closed limits are fuzzy

Photo by Elaine Vallet

• De facto standards may emerge from proprietary formats (PDF, MP3)
• Is RAND open/closed?

Money comes from clients

Photo by Elaine Vallet

Clients are end users

Photo by Elaine Vallet

End users yell: Make it work!

Photo by Elaine Vallet

Fragmentation is the Mobile plague

Photo by gin able

Interoperability is the key

Understanding each other

The mobile Web is opening up

Photo by mag3737

Open standards needed

• To reduce fragmentation
• To improve interoperability
• To improve user experience
• To benefit from the long tail

For a global effect

Standards are not uniformity

Photo by Elaine Vallet

Differentiation is good!

Why W3C is such a good Standards body

• Industrial consortium
• Process ensures stability and reviews
• Royalty-Free patent policy
• Vendor neutrality ensures all points of view are considered
• Technical team ensures homogeneity

Focus on the user

Measure mobile Web browsers fragmentation

Web Compatibility Test for Mobile Browsers

From mobile experts to regular Web authors (1/2)

Mobile Web Best Practices 1.0

From mobile experts to regular Web authors (2/2)

http://validator.w3.org/mobile

Tackle the whole delivery chain

Widgets

Mobile Widgets

• Widgets 1.0: Packaging and Configuration
• Widgets 1.0: APIs and Events

Mobile Web Application Best Practices

• Mobile Web Application Best Practices

Geolocation API

Geolocation API Specification

Policy / Device APIs

• Policy description
• Device APIs

Social Web

• W3C Workshop on the Future of Social Networking in February 2009
• Workshop report

The end

Contact

François Daoust <fd@w3.org>

W3C Mobile Web Initiative

Questions?

• ?
• ??
• ?!?

Supported by MobiWeb2.0,
funded by European Union's FP7.