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

Re: Audience (was Brainstorm of EARL Requirements)

From: Karl Dubost <karl@w3.org>
Date: Mon, 7 Mar 2005 16:11:24 -0500
Message-Id: <397682c1a12d48fc413af9fc3b4470b6@w3.org>
To: <public-wai-ert@w3.org> <public-wai-ert@w3.org> <public-wai-ert@w3.org>

Le 23 févr. 2005, à 06:38, Shadi Abou-Zahra a écrit :
> * evaluation tool developer who only wants to output EARL
>  - does not need too much background in RDF, OWL, etc

Yes. If they use library, you have also to precise if you talk about 
one of the syntax of RDF or if you talk about the RDF model.
For syntaxes:
	RDF/XML
	RDF/n3 (turtle)
	RDF/ntriples

> * (any) tool developer who wants to make use of EARL results
>  - needs to know how to work with RDF in order to interpret results

I'm not sure there is much difference between the two users groups. :)


> Of each of these two user groups, there may be two further categories 
> of
> developers which we should consider:
>
> * developers who are new to EARL and need more explanation / background
> * developers who already implement EARL and want to reference the spec


A W3C specification is a technical specifcation for developers, then 
explaining the semantics of the language which has been created. Then 
it's not a question of being new to EARL. The new release of EARL has 
to be as easy to understand than the old one ;) I would say even more, 
because it's not that simple to understand the first one.

> Does this sufficiently cover the target audience for EARL?

In your analysis, do you intend to have two documents?

	- EARL Technical specification
	- EARL Primer



-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager
*** Be Strict To Be Cool ***

Received on Monday, 7 March 2005 22:35:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:25 GMT