RE: web standards project article

Karl Dubost wrote:
it might be worthwhile do demonstrate that an element is useful for the 
user implementation-wise.
People uses "something" because they have a reason to do so. Among 
them, it can be:
	- Ethics (weak)
	- Fun    (weak)
	- Practical personal benefits (strong)
	- Benefits for other persons  (strong)

I think this is exactly the sort of explanation I was looking for.
I think there are two points which any documentation must consider:
	there is a need to educate web designers as to best practice and its
benefits;
	there is also a need to provide web designers with a business case
for using "best practice".

I'm sure the second point is debateable and possibly out with the scope of
the W3C, but I think it is important in supporting advocacy.
As a web designer who wants to move a product from old style to semantic
markup, I am going to need a solid business case. Backing from the W3C in
the form of a readable "best practice" document might cement that business
case.