Earlier today when looking for new shorts I bump into this 2D code on an Adidas short...
They are everywhere :-)

Just when we were talking about it... thanks Marco:

Mobile Link Discovery Specs

These days a lot of web sites have mobile optimized webpages and usually publishers use different URLs for them. For example, Google has its mobile version of homepage at http://www.google.com/xhtml (instead of http://www.google.com/).
Usually publishers (Google in this case) uses techniques to dispatch mobile devices to its mobile version by looking up User-Agent string. This works fine when you make mobile webpage that only links to web pages under your control.
However, this might cause a problem linking to external sites from mobile optimized web pages. We can't make sure the target URL has mobile optimized page or not. Mobile Link Discovery tag solves this problem.

<link
rel="alternate"
media="handheld"
type="application/xhtml+xml"
href="http://yoursite.example.com/mobile" />

What?
W3C Webinar: "Mobile Web Design"
When?
Wednesday, July 26 2006
12am Paris - 11am London - 6am Boston
Duration: 1h

Designing Web sites that are usable, accessible and elegant has its challenges - but add digital products to the mix and it's a whole, new ball game. The variety of screen sizes, devices, and operating platforms alone can be overwhelming.

This presentation takes a look at where we're at, where we're headed, and how to best extend an existing or planned Web site to handheld devices with minimal repurposing of code, content, and images. Discover the elements of forward thinking design needed to maintain consistency, regardless of where and how users access your content.

Invited Speaker: Cameron Moll from cameronmoll.com: Free W3C webinar: "Mobile Web Design"

Say hi to Johnny on Pasta and Vinegar



Spime on WIkipedia

Also to know more about QR Code and if you read french, you can go on Le blog Gadget which has a pretty good introduction on QR Code

Job description in german is there... (english version is comingis there)
Located in Zürich.... (Lausanne office is getting small :-)

To apply you can also send me your resume...

and here is the QR Code to bookmark the job description on your mobile:

Mobinomy.com:

Mobinomy.com is the first .com directory for .mobi sites online. While .mobi sites will be used primarily through the mobile, there will exist a need for users to check out relevant .mobi sites on the web. Mobinomy.com attempts to cater to this need.

I understand the needs of having access to mobile formated content and directories is one way to achieve that... not quite sure it is the best way to do it.

More and more website will have this mobile version somewhere (most likely not with content negotiation), the problem is given one page on the web how to tell the browser where to find the mobile device friendly version.

We have been talking about that with Marco and one solution that comes up was to use the link element in html to indicate where to find a mobile version:

<link


   rel="alternate"


    type="application/vnd.wap.xhtml+xml"


    title="XHTML-MP version"


    href="http://www.smoothplanet.com/mobile" 


/>

To be continued...

Read it on MWBPWG blog

But what if there were a simple way for any Web developer to gain access to basic information about the devices hitting their site. What if they could use this information in a straight forward way in their templates (JSPs, ASPs, PHP, etc...) or other server-side logic for the purpose of more easily providing a mobile-friendly user experience in accordance. And what if this information were available as a utility - as transparent and ubiquitous as DNS or HTTP headers and integrated seamlessly into all the most used Web development frameworks and Web servers.

Sounds like the mobapi.com initiative I am working on my spare time (not much left :-)

W3C mobileOK Scheme 1.0

mobileOK is directly built upon the Mobile Web Best Practices: to be mobileOK, a page needs to pass a well-defined subset of the Best Practices, as assessed through a refinement of the tests developed as part of the Best Practices.

Via W3C MWBPWG blog