- From: Edd Dumbill <edd@usefulinc.com>
- Date: Fri, 17 Mar 2006 21:34:34 +0000
- To: Karl Dubost <karl@w3.org>
- Cc: Shadi Abou-Zahra <shadi@w3.org>, public-wai-ert@w3.org, www-qa@w3.org
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 > >
Received on Friday, 17 March 2006 21:33:36 UTC