Paul Walsh, the Irish Opportunist

My new Head of Communications has advised (eh, no, he has told me) to create a new blog under my name and move my non-Segala related posts with me. I must admit, this is something I’ve been pondering for ages as the Segala blog has attracted a great audience, but one that is perhaps, a little diverse for it to gain real benefit.

I think Dennis Howlett will agree that this has been a good move as I’ve asked him for advice on this matter in the past. I should have plenty of real estate to include my buddy’s gapingvoid widget too.

By splitting my posts between the Segala blog and here (oh, and BIMA), I hope to make my writing a little more relevant for you. Mind you, my writing skills aren’t likely to improve, I’ll continue to use poor grammar and spell things as if I’m looking in a mirror. I’m likely to cross-post where I feel my thoughts where relevant also.

I’ll continue to post on the Segala blog about the Semantic Web, Accessibility, Mobile Web, Standards, W3C, Content Labels, Trust, Search and anything else that’s relevant to Segala. This should make what we’re launching in 2008 much more prominent.

On this blog, I intend to cover everything else that I used to cover on Segala’s blog, such as Social Media, Web 2.0, Web and Mobile Trends, Twitter, Facebook, Networking, Events, Connecting People and anything else that I have an opinion on. I might even write about some personal stuff.

Kamrul, our Wordpress and PHP guru, is currently working on an Semantic Web application for Aido, but I’m hoping to squeeze a couple of hours out of him today to get some minimum functionality added to this blog, not to mention a little branding.

I don’t expect many comments left on this post because my mother doesn’t even know about it yet. However, if for some reason you stumble across this post before it falls off the edge of the blog with the introduction of new posts, please provide some feedback on what functionality you’d like to see?

Would you like to see any of the following on the sidebar

1. Most recent comments and who made them?
2. A summary of posts with the highest number of comments?
3. Digg?
4. Photographs of the people who left comments?
5. Recent Readers (MyBlogLog)?
6. Tag cloud or Recent Posts?
7. My last Twitter message?
8. My followers twitter messages?

Please ignore any design or layout changes (breakages) as Kamrul and I make changes on the fly to get this blog off the ground. We’ll transfer all my social media and entrepreneurial type posts from Segala to here, along with the comments next week. That should be fun.

I look forward to building a wee community here and hope you can be part of it

To subscribe to this blog, click here

Welcome to my personal Web site. I’m a CEO, Chair, Executive, Advisor and Mentor who loves to influence and connect likeminded people. When bored, I like to host networking events and parties.

Company stuff

• Segala, Founder / CEO
• Wubud, Founder
• BIMA (British Interactive Media Association), Chair
• Jaipur Restaurants, Partner
• Newspepper.com, Non-executive Director
• 3 Dynamics, Mentor to the CEO

Blogs I scrible on

• Personal * Segala * Wubud * BIMA

A little more detail

• Founder and CEO of Segala, industry authority in content classification and Web standards compliance certification.
• Founder of Wubud, a social network application for mobile people. In September 2008, we raised £160k in Angel funding from Paul Birch, Co-founder, Bebo - sold to AOL for $850M.
• Former executive at Eqos, a pioneer in the development of Web technologies for the B2B retail industry.
• One of the first to join AOL as a small startup in the mid-’90s. Key member of the team developing AOL’s UK presence and assisted with the launch of other AOL European territories.
• 10 years International experience within the telecommunications industry and have consulted companies such as Vodafone, O2, Orange, CMG and ADC Metrica.
• Chair of the British Interactive Media Association (BIMA) since 2006.
• Advisor to the British Council, helping to build and improve a digital pioneer program with Hong Kong and a 3 year entrepreneurial related project with India.
• Non-Executive Director at Newspepper.
• Mentor to the CEO of 3 Dynamics, a Hong Kong based games company.
• Partner in Jaipur, a group of award winning, Michelin-rated restaurants in Dublin.

Contribution to Industry standards

• Instrumental in the formation of the W3C’s first ever incubator activity, to review Content Labels as a formal method of classifying and labelling content
• Segala’s W3C Advisory Committee Representative
• Original Founding Sponsor of the W3C Mobile Web Initiative and member of the Steering Council

I heard the Google mobile being touted around the time we were providing mobile test consultants to Disney, to help it setup a Mobile Virtual Network Operator (MVNO) last year. Unfortunately for Disney (and Segala for loosing the contract), it decided to can the project. I say unfortunately because it has the content to deliver a compelling family mobile, but it just didn’t get it technically or commercially in my opinion.

Read more…

I responded to a thread on the Mobile Monday list tonight in defense of the W3C Mobile Web Initiative (MWI) and those who want to make the Web more accessible to more people around the world.

Please refer to a recent post on this subject if you’re looking for hyperlinks to other resources.

I must declare an interest before commentating though. I’m a member of the W3C MWI Steering Council. Segala is not only one of the seven original Founding Sponsors, it’s also co-author of the conformance specification called mobleOK.

I must also declare that I’m particularly interested in mobileOK for two reasons. First, because it will help make the Web more accessible to more people, including those in developing countries where mobile is their primary access point to the Web. Secondly because making conformance claims about mobileOK will come in the form of a Content Label. As most of my readers will know, Content Labels underpin Segala’s business model of enabling trust on the Web based on compliance with standards and codes of conduct.

Now that I’ve got the disclaimer out of the way, whilst taking the opportunity to talk about Segala’s business proposition…

The Mobile Web vs WAP debate seems to crop up regularly as some people continue to protect their revenue stream from WAP, by claiming that the open Web on mobile devices is spawned by the devil.

The W3C MWI Best Practice Guidelines are of benefit to what some may call, traditional Web developers who know little if anything, about WAP or anything mobile. They simply want to build Web sites as they do today, but with the added benefit of them also working better on mobile devices.

Ok, so building mobile friendly Web sites isn’t easy and it’s not exactly perfect by a long shot. However, creating new standards is about future proofing. It’s not about creating a quick fix. They will continue to improve as will mobile technology, tariffs, bandwidth etc and has human behavior changes.

I met a guy tonight in Adam Street who very quickly (and wrongfully) *assumed* that I wanted to see the end of WAP as soon as I mentioned W3C MWI. I found him very defensive as if he were trying to protect his revenue stream, which comes from WAP and only WAP. I found his attitude to be very dismissive and typical of a WAP-centric extremist with no interest in anything outside of WAP. He is right to protect his revenue stream. I wouldn’t expect him to care about the future of the Web - that’s for us idealists to think about. Some of us get the commercials and some don’t. I’d like to think I’m in the former camp.

I reminded him that I never mentioned WAP, to which he replied, ‘yeah well the W3C is confusing developers’. First may I point out that there is room for both. Secondly, the W3C MWI in my opinion, is targeted at Web developers, not mobile developers. Accept the fact that mobile and Web developers are different. Some get both but most don’t.

The ‘one Web’ for me, is about bringing access to the current Web (hyperlinked documents as invented by Tim Berners-Lee) to mobile devices. It’s not about changing or impacting WAP sites which are developed specifically for mobile phones by mobile developers. There will always be a need to develop specifically for mobile devices. Likewise, there is a use case to develop one site that renders according to the device capability, whether that’s a desktop computer or a mobile device.

The W3C is being referred to as if it was wasting time/energy. May I point out that the W3C is made up of companies, government agencies, associations, universities, freelancers etc. from around the world. It’s not made up of a bunch of white coats at MIT. The W3C MWI includes every stake holder which has an interest in both traditional Web and mobile specifics.

The W3C is in my opinion the best and only consortium that should be responsible for creating and harmonizing *Web* standards - based on the assumption that it works with everyone who is qualified to contribute.

A debate has started on Vodafone’s BetaVine. If you’ve been reading my blog for a while, you’ll know that Vodafone provided me with exclusive rights to seed interest in the wider industry to help launch the Portal, after providing advice prior to its launch. Unfortunately I haven’t been able to find the time to continue commentating about it. Anyway, it’s doing exactly what I had hoped. It’s stimulating and supporting conversation within the industry. In this instance, it’s a heated debate which is likely to raise more awareness for the Portal if nothing else.

Luca Passani is the culprit (I mean that in the nicest possible way) responsible for starting the debate. If there’s one thing he’s good at, it’s starting a debate. Unfortunately he doesn’t know how to agree to disagree, or even respect the fact that he can sometimes be wrong.

My intention here is not to discuss the debate itself but instead, get people to use the right terminology. Ok, so my post about the correct spelling of Web site was a bit of a joke, but knowing the difference between WAP and the mobile Web is not, as it impacts end users for the worse.

It was a TechCrunch post that inspired me to write this note. I was about to post a comment but quickly realised that my message is important (and long) enough to warrant it’s own post. I’ve written about this previously where Luca has commented along with Google, Microsoft, .mobi, Opera and others. See here and here.

In my opinion, Luca has absolutely no interest in seeing the Web as we know it on the desktop, come to mobile phones. He is in favour of WAP and is an expert on the subject. WAP is not the mobile Web though, they are two entirely different technologies and he doesn’t have an appreciation for Web trends.

• WAP = sites built only for mobile phones
• Web = sites which should work on any device

WAP browsers and Web browsers look the same but what they display is completely different. One generates revenue for Operators and Content Providers and the other provides end users the ability to search and browse the Web. That’s why most end users don’t know the difference between a WAP site and a Web site. However, it’s not good enough to assume that they don’t care. It’s also wrong to assume they don’t want a choice.

In more detail
WAP sites are sites which have been built specifically to work on mobile phones. They do not work on desktop computers. This means if you come across a WAP site on your phone and wish to email the URL to a friend so they can see it at home, they can’t unless they’re using a mobile.

I used to own an LG Chocolate phone to demonstrate this point when giving presentations at conferences. I’d ask someone for the URL of their company Web site and then explain that it was impossible for me to view it on my new cool phone because it didn’t have a Web browser capable of displaying it.

Not all mobiles have browsers capable of displaying Web sites. Some phones come with a Web browser but it’s sometimes removed or hidden down the menu system by the Operator (not the manufacturer). Operators have always been extremely keen to keep it this way as they make money from WAP through revenue share deals with content providers.

It’s also worth mentioning that the Content Providers to which Luca and TechCrunch refer, are not likely to want users to access the Web (as invented by Tim Berners-Lee and harmonized by the W3C), as you do on a desktop computer. Otherwise they’ll stop making money through their commercial agreements with Operators. This means end users get whatever WAP sites Operators believe will generate the most revenue. This is not in the best interest of end users today.

It made sense to only offer WAP sites when mobiles were unable to display Web sites. It also makes sense to continue building WAP sites while mobile devices continue to improve, standards are adopted, prices come down, speeds improve and developers build Web sites so they work better on mobile devices.

In my opinion, we’re almost there. You only have to look at the recent launch of the iPhone to see what’s possible. It won’t be long before this capability is more widespread across more devices and the above points are addressed. As I keep saying, I’ve heard all the same arguments whilst at AOL in the mid 90’s. People use to say that online marketing would never take off because the Web was too slow, yada yada yada. The same type of people used to say that TV would never take off because it was so much smaller than the cinema screen.

End users do care about the difference between the two, or at least they would if told they were restricted to what the Operator wants them to see. Mobile stake holders make too many assumptions about what users want. That’s why the industry is so crap at getting it right.

So, can you see the difference between the two? If you had a mobile which stopped you from accessing the Web, would you care? Would you be happy to only view the WAP sites that your Operator forces upon you?

Please stop referring to WAP as mobile Web, it’s not. Just call it WAP.

From a customer point of view, you buy a mobile so you can surf the Web as you do from your desktop computer. Would you be happy to learn that you’re only able to use iMode, Live or other WAP sites?