HTML5/Mobile Validation Issues - Bad value HandheldFriendly Etc.

[morestar]

Interestingly enough I found 0 results that could potentially solve my HTML5 validation issues at the W3C, about 9 errors to be exact - I'll only complain about 3 here today...

The first: Bad value HandheldFriendly for attribute name on element meta: Keyword handheldfriendly is not registered.

The second: Bad value MobileOptimized for attribute name on element meta: Keyword mobileoptimized is not registered.

The third: Bad value cleartype for attribute http-equiv on element meta.

Now I'm trying outone of those mobile templates that's coded in HTML5 (although I ripped the 5 to bits and pieces (my developer is going to shoot me)) - I think a few of us have heard of this template/style - it's the one where the layout is changed based on the user-agent/device (mobile, ipad, desktop etc.). This is basically my first HTML5 project, I've delved into it slightly but the validation issues I'm having here today, are confusing to say the least.

I guess my first question would be how do I made those bad values good values? Namespaces? This is rather complicated...

[kgun]

Now you are very fast. HTML5 is far from mature enough.

1. Have you tested the same code in different browsers?
2. Have you tried css style sheets for mobile devices?
3. Have you studied the php code in plugins like http://wordpress.org/extend/plugins/wptouch/ ?

.... Namespaces? This is rather complicated...

No it is not. Name spaces are there to avoid name clashes. In other words to create a unique scope.

Now I'm trying outone of those mobile templates that's coded in HTML5 (although I ripped the 5 to bits and pieces (my developer is going to shoot me))

Advice:
Tell your developer that he is looking for problems that he / you may be prepared to solve yourself if you aim to be a frontrunner.

Side note:
Namespaces are a much wanted feature in php 6.0, but already implemented in the last stable version 5.3.6 of php.

[morestar]

Advice:
Tell your developer that he is looking for problems that he / you may be prepared to solve yourself if you aim to be a frontrunner.

Looks like you're right and I think he's probably already got this in mind.

At the W3C Validation service under some of the errors I find:

Syntax of metadata name:
A metadata name listed in the HTML specification or listed in the WHATWG wiki. You can register metadata names on the WHATWG wiki yourself

Looks like if we're going to this route that we might have to do this...

Thanks K.