The point is valid that a page that wears the badge should have been tested to make sure that it still complies. However, this is an open source, community supported, project -- not a shrink wrapped commercial product with a large marketing and legal department insuring that enough disclaimers are put on everything that the company can't be held to a standard.

If someone is concerned about the generated XHTML enough to go in and create a patch to fix the issues, I'm sure the committers will review it and if it doesn't break something else, add it to the project. The OFBiz team is everyone in the community, we can all work to make it better. I, for example, found some extraneous attributes in some tags in the demo, and a committer looked into it right away. If we cannot figure out how to "fix" an issue we see, then we can bring it to the community, as you did, and maybe someone else will pick up the torch and run with it.

Demo pages are "proof of concept", production is what we make it.

On Jun 24, 2009, at 11:31 AM, Ján Valkovič wrote:

Thanks for explanation, but Amazon.com haven't this
https://demo904.ofbiz.org/images/valid-xhtml10.png on _every_ page. And
catalog is part of ofbiz, it isn't 3rd party application deployed to
OFBiz. I wondered why is logo "XHTML 1.0 valid" on XHTML 1.0 non-valid
page creted by ofbiz team.

ya

Dňa St, 2009-06-24 o 10:33 -0700, John Hays napísal:
Ján, its as valid as you make it. The XHTML is generated by the
widgets, servlets, and ftl templates that go into the page.   If the
programmer who put together the "demo" catalog did not create valid
XHTML, then it won't pass the validator. Clean HTML, XHTML, etc. is a
great goal, which can be achieved through diligence by the designers
and coders, but is rarely truly necessary from a pragmatic point of
view -- for example, try running Amazon's home page through the
validator, you will see over 1500 warnings and errors in their HTML,
or over 500 XHTML errors for Overstock.com.

OFBiz provides the framework to create valid XHTML, but it is up to
the developer/implementor to make it so, the framework cannot force
good coding.





John 

Reply via email to