W3C HTML Validation Service: To Do List

This page has the to-do list for the W3C HTML Validation Service, including bugs that need fixing and general wishlist items.

See also: www-validator mailing list archives for recent discussion that may not be reflected on this page.

These items are roughly in prioritized order; i.e. the items near the top are those which I consider most important.

1. make the output valid (!)
2. do more i18n bug fixes
3. put the explanations in a database (flat files are probably okay), offer an option to display them inline with the errors
4. add a "fix my HTML for me" option using tidy.
5. add support for form-based file upload (RFC 1867)
6. add a textarea for testing short HTML fragments
7. add a doctype-overriding option
8. write documentation, describing each feature and option of the validator and answering questions like "What's the difference between an SGML parser and Weblint?", "Which DOCTYPE should I use?", ...
9. upgrade weblint to the most recent version
10. add XML validation
11. add CSS validation
12. make e.g. http://validator.w3.org/check/referer;imgonly return only an image showing the validation status of the referring page
13. bug fix: fix the heading-based "outline" feature to include ALT text if it appears in the headings.
14. if the validator gets a redirection from the given URI, instead of displaying a page about the redirection, just put something at the top of the report saying "by the way, I was redirected to: ..."
15. add link validation using Renaud's checklink code
16. make an "elements found" section a la Webtechs, with links from each element to the appropriate place in either the DTD tree listing produced with dtd2html (after running dtd2html with all DTDs in the catalog), or the HTML 3.2/4.0 specs, or htmlhelp.com stuff, ... Similarly, put links on each element in the parse tree.
17. add a "document meta-information" section to the report, to encourage people to use META tags appropriately?
18. add a "recommend a DTD for me" feature (check a document against all available DTDs, report which one has the fewest errors)
19. start caching validation results locally and doing an If-Modified-Since HTTP request to only download and re-validate URLs if they actually changed since their last validation
20. site walker/validator: need to add a "registered user" feature first, because this feature could be abused (many requests on a server in a short period of time)?
21. URL-minder service: "remind me if this page or set of pages ever ceases to validate"
    • "registered user" feature is also necessary for this (to prevent unwanted e-mail)
    • "registered users" could have a list of URLs they're interested in, and whenever they return to the service they can modify this list, and e-mail can be sent whenever any of them cease to validate
    • right now someone could probably use the existing URL-minder service instead of writing a new one (tell it to "mind" the URL that points to the validation result for a page?) But I'm not sure how regularly URL-minder checks for changes; it seemed to be weekly or something, which isn't frequent enough, IMO. Doing an If-Modified-Since GET every day doesn't cost much if pages don't change. Some of these features should only be enabled if the page consistently returns a Last-Modified header, maybe.
22. add an HTML pretty-printer feature, using tidy?
23. provide messages in different languages?
24. add a graphical representation of the document's structure, using GIFs-mixed-with-text, or an entire GIF?
25. add a section with PICS info?
26. issue PICS labels for documents that do/don't conform? or for editing tools that don't conform?

Gerald Oskoboiny
$Date: 1999-04-09 00:38:39 $