W3C home > Mailing lists > Public > public-wai-ert@w3.org > May 2005

Re: Conformance to EARL

From: Nils Ulltveit-Moe <nils@u-moe.no>
Date: Wed, 25 May 2005 16:51:11 +0200
To: shadi@w3.org
Cc: Charles McCathieNevile <chaals@opera.com>, "public-wai-ert@w3.org" <public-wai-ert@w3.org>
Message-Id: <1117032671.12864.360.camel@moe-ulltveit-moe.com>

Hi Shadi,

This sounds like a very good strategy for extending EARL over time!


ons, 25,.05.2005 kl. 16.41 +0200, skrev Shadi Abou-Zahra:
> Hi,
> Charles McCathieNevile wrote:
> > I don't think so. I think we should specify that things like producing  
> > "valid EARL plus other made-up EARL" as non-conformant behaviour, since  
> > this can harm interoperability (less so because EARL is RDF and not 
> > XML,  but is still a bad idea).
> In several areas, it makes sense to extend a core EARL with domain specific vocabulary. For example, I want to use mycompany:toaster as an earl:subject (I am testing toasters for their ergonomy and want to record my findings in machine readable format).
> Similarly, specify earl:WebContent as a built-in subject subclass because our main motivation in this group is Web accessibility and it is also something we have expertise in. However, we agreed that we need to open up to generic QA where there are endless domains we can not control.
> Is it essential for a generic EARL processing tool (for example a QA statistics generator) to know about the domain of toasters or just that the subject is a toaster? All we need to do is require that an earl:assertion contains exactly one (or whatever we define) earl:subject (or a subclass thereof). This way we ensure interoperability yet at the same time openness for domain specific extensions.
> Another advantage to this approach is to monitor what extensions tool developers come up with over time and slowly integrate them into core EARL in future versions if appropriate.
> Regards,
>   Shadi
Nils Ulltveit-Moe <nils@u-moe.no>
Received on Wednesday, 25 May 2005 14:44:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:52:49 UTC