PUBLIC MARKS with tag validation

A light-weight RelaxNG validator written in javascript.

The interesting thing to do is to use Validation as a tool and not as a goal. Why my code is invalid? What is the source of errors? Which script, libraries, etc create invalid code?

So basically for me it helps me to create a better framework or script at the source. I don't want to validate every pages, but I want to be sure that the page which are produced are valid. That means I have to create "checking steps" in my code, or to use the appropriate tools. For example using an xml library to replace an element by another more than doing a regex, checking and sanitize the input of forms, etc. etc.

karl on March 7, 2009 07:08 AM

Incidentally, I used validator.nu to check my work. It seemed the most up to date, but there’s no guarantee it’s perfectly accurate.

Etant donné que c'est le seul qui soit sérieusement fait, on espère qu'il est à peu près à jour. Maintenant, difficile de valider un machin mouvant comme HTML 5 (et à quoi ça sert d'abord, étant donné qu'aucun navigateur n'implémente le gros de la spéc, à savoir les 232 pages d'algorithme de parsing).

Whether Henri ever writes a validator that handles HTML5 and RDFa, I am confident that somebody at the W3C will. Even if I have to do it myself.

The Initiative

This site is dedicated to helping those creating their own iCalendars or iCalendar feeds to ensure their calendars will work with other systems. It also serves as a meeting place for those developing validation tools to collaborate and ensure the validation is as accurate and useful as possible.

Why Validate?

Validating your iCalendar feeds before they are deployed ensures that they will be compatible with other iCalendar systems.

I’m delighted to report that two developers of libraries that support iCalendar are collaborating to do just that. Ben Fortuna is the author of iCal4j, which powers the best currently-available online iCalendar validator. And Doug Day is the author of DDay.iCal, a C# iCalendar library. Both iCal4j and DDay.iCal are open source projects.

They’re collaborating, at icalvalid.wikidot.com, on a platform-neutral suite of tests that can serve as foundation for a more robust iCalendar validation service.

JsValidator est un plugin pour l'éditeur de texte Gedit qui permet de valider la syntaxe d'un fichier javascript grâce à JSLint.

Error detection: Noticing that there is an error. Error handling: Deciding what to do with the error Error recovery: Skipping over the error and continuing with parsing. Error correction: Doing what the author "really meant".

But in the real world, often there are data values or structures which have fixed choices, but not completely fixed: a twilight zone.

For CSS compression I just used cleancss manually. I also looked at cssoptimizer but it was a bit too extreme to my taste. cleancss is based on csstidy so I could possibly integrate that into my build. For validation I have used W3C validators, but it would be nice to be able to integrate validators in the build step as well. For Javascript it seems JSLint would be a good option. I haven’t spent any time thinking about HTML and CSS validation during the build step, but obviously this would be a nice thing to have as well.