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

Re: DOAP and software description

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Fri, 17 Mar 2006 23:01:29 +0100
Message-ID: <441B31B9.4000803@w3.org>
To: Edd Dumbill <edd@usefulinc.com>
Cc: Karl Dubost <karl@w3.org>, public-wai-ert@w3.org, www-qa@w3.org

Hi Edd,

Thanks for providing this. Just a question, why have you decided to introduce doap:created instead of reusing dc:date?

Also, I think an optional description for the project or software may be useful too. However, I don't know how that fits in (it doesn't seem to be part of the <version> information).

Regards,
  Shadi


Edd Dumbill wrote:
> Sorry for the delay in responding.  You are right that the current
> vocabulary for describing releases is a little primitive.  It basically
> comes down to having multiple doap:release properties, e.g.
> 
> 	<release> 
> 		<Version>
> 			<name>unstable</name>
> 			<created>2003-06-07</created>
> 			<revision>0.4.1</revision>
> 		</Version>
> 	</release>
> 
> That covers release dates, versions, names, you could hang extra
> properties off that.  CodeZoo added file-release to point to a
> tarball/zip, and I included that.
> 
> I am open to considering new properties for inclusion based on a
> demonstration of the need for them.  I have been considering a vocab to
> represent dependencies for some time, for instance.
> 
> You may also be interested in what Apache have done with DOAP, 
> http://times.usefulinc.com/2006/03/17-doap-apache
> 
> -- Edd
> 
> On Wed, 2006-03-01 at 16:00 +0100, Karl Dubost wrote:
>> Hi Edd,
>>
>> DOAP is very useful in terms of the description of a project.
>> DOAP doesn't seem to cover the description of an individual software  
>> like name, version, release dates, bug list, etc.
>>
>> I'm asking this because I was in ERT/QA joint meeting [2] yesterday.  
>> The ERT WG in the design of EARL needs an "earl:software" [1] for  
>> describing a specific software.  But using the earl namespace for  
>> this seems to be a bit awkward.
>>
>> Have you already worked a bit on this?
>> Or do you have an example which would cover this case?
>> Or do you have pointers which might interest the ERT WG?
>>
>>
>> [1] http://www.w3.org/TR/EARL10/#terms-classes-software
>> [2] http://www.w3.org/2006/02/28-er-minutes#item01
>>
>>
> 
> 

-- 
Shadi Abou-Zahra     Web Accessibility Specialist for Europe | 
Chair & Staff Contact for the Evaluation and Repair Tools WG | 
World Wide Web Consortium (W3C)           http://www.w3.org/ | 
Web Accessibility Initiative (WAI),   http://www.w3.org/WAI/ | 
WAI-TIES Project,                http://www.w3.org/WAI/TIES/ | 
Evaluation and Repair Tools WG,    http://www.w3.org/WAI/ER/ | 
2004, Route des Lucioles - 06560,  Sophia-Antipolis - France | 
Voice: +33(0)4 92 38 50 64          Fax: +33(0)4 92 38 78 22 | 
Received on Friday, 17 March 2006 22:01:55 GMT

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