W3C home > Mailing lists > Public > public-qa-dev@w3.org > August 2006

[ucn] more notes on installing the unicorn tool on qa-dev

From: olivier Thereaux <ot@w3.org>
Date: Thu, 3 Aug 2006 16:09:15 +0900
Message-Id: <756B5083-1C8B-4832-8163-DC1CE4EE7EE0@w3.org>
To: QA Dev <public-qa-dev@w3.org>


I've been working, little by little and time permitting, on  
installing the "unicorn" framework onto the qa-dev server in the past  
few days. The instructions provided, and the ant build script, have  
proven very useful, things work mostly out of the box.

I've already exchanged a couple of mails with Damien and Jean-Gui,  
but think it may be a good idea to include the list in the loop, as I  
suspect others will want to install/test the tool, too.

I've installed the tool at:
(temporarily... I'll give mod_jk a look to perhaps make the URI  

A couple of things I've noticed or wondered about:

* has the CSS validator been patched yet to have a ucn output? I  
don't recall seeing the cvs messages. Yves, are you reviewing the  
patches at the moment?

* I've noticed a couple of tiny mistakes in the mime type  
configurations. If I'm not mistaken, the list of mime types supported  
by the markup validator should be the following:


Note the image/svg+xml media type for SVG. I'm not an expert, but if  
I recall properly, this, and not application/svg+xml, was chosen as  
mime type for SVG. Worth double checking at least.

So for the CSS validator it should be:

I updated these files, which my installation of the tool refers to,  
and was expecting the following to be working:

but it still wasn't, and I remembered that the supported mime types  
are also configured in the tasklist.

I don't know if that's the most usable. Could the list of mime types  
accepted for a given task be computed from the observers:
- concatenate all mime types supported by the observers of the task
- if an observer does not support the mime type, skip it if the  
document passing the task has that unsupported mime type.

alternatively, another approach:
- compute the list of supported mime types for a given task as the  
least common denominator from all its observers.

I prefer the former solution, but it may have its issues. And perhaps  
there were issues that pushed us to define mime type support both in  
observers and tasks, if so, sorry, I have forgotten, could you remind  

Received on Thursday, 3 August 2006 07:08:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:26 UTC