The W3C already some some amount of certification, at least you can run their validators and put an emblem on your site advertising your compliance. They and many others provide spec compliance training materials.

DHTML doesn't automatically run correctly on every platform from desktop to mobile phone even if it's perfectly compliant. In most cases, the content needs to be adapted to each interface. While you might use a big image-heavy graphic design for desktop browsers, mobiles require a more stripped-down design and many sites that aim to support multiple platforms and provide good content on all will detect the browser type on the server and send content tailored for that platform. You can do some of that detection and selection in DHTML, but in most cases it's more straightforward in the server-side code.

So what exactly is your idea? To form a group like the W3C to advocate and train for DHTML compliance? How does the crowd help other than doing what they're already doing, building websites.

1) A complaincy certificate for devices that can run DHTML other than computers: cellphones, etc.

2) A company a) giving certificates on courses of DHTML
b) providing courses itself (seminars and e-seminars)
c) assessment based certifying knowledge/capacities
[this would be the main aspect]

i dont understand so you get 3 stars

LOL
I second Brenden
Tommy

If I understand correctly, you're aiming to certify devices rather than sites as DHTML-compliant? That's going to be much more difficult as it requires cooperation from the major device manufacturers rather than just individual webmasters and site owners.

How do you propose to get around the problem micco mentions, that DHTML won't magically show a correct page even across compliant devices? If I bought something labelled as DHTML-compliant I'd expect any (well-written) DHTML page to display on it.

Part 2 of your idea has merit - by all means, train people in how to write correct DHTML that does adapt to other devices where possible and certify them in this - but I can't see you getting anywhere with part 1.

It would depend on the web browser the cell phone is using.

You can in fact detect what browser the user is viewing your site with. Then use that info to display the proper version of your site.

I actually am working on a cellphone browser compliant online web design program. If your interested you could join the team, send me a pm.

I don't understand why being DHTML compliant is meaningful - it still means you have been through a huge amount of pain to get your page rendering exactly the same on various browsers, devices and platforms just like any other poor bugger using any other means for rendering a page. DHTML does NOT mean pages magically render perfectly everywhere.

DHTML doesn't make it any easier or difficult to support multiple platforms and viewers wouldn't care how you made a site look good, so long as it does - so why make a song and dance about compliance?

Who is your audience for this?

1° I have to precise DHTML apparently.

I mean standard HTML 4.1 and Javascript 1.1

(last level of HTML implimented by all standard internet browser; for Javascript 2.1 it might eventually be as well )

2° The certification can be done just by developping an online test kit for end users sake

3° This way it becomes also a sales argument...

ok

"3° This way it becomes also a sales argument..."

That sounds to me like an admission that you know this certification isn't going to be worth the paper it's written on but you're going to try and sell it anyway. Good luck with that...

I wouldn't even use paper. A website with all the proven DHTML compliant stuff would do quite fine.

The importance of DHTML is that it allows cross-browser, cross-platform, cross-media programming.

Just take the example of my French exercises at http://jansegers.classy.be

They can be put on a disk, a CD-ROM, an hard drive, a memorystick, under any LMS and they will run providing the availability of a standard web browser.

Even on an old 368 computer, they perform as aspected. (I presume even on a 268, but I did never test this.)

The certification of the ability to write decent DHTML is my main concern: cross-browser (Opera, Firefox, Safari, Explorer,... ) HTML scripting isn't really the norm on the net at this moment.

I just want one code that doesn't have to check to browser in running in for anything at all. Period.

not sure I see the business model (make money)

Neither do I - but you get extra points for looking like Mr T's white half-brother. ;)