- From: Sandor Herramhof <Sandor.Herramhof@jku.at>
- Date: Fri, 20 May 2005 10:03:00 +0200
- To: <public-wai-ert@w3.org>
Hi, The idea of DOAP is building internationalizable descriptions of software projects and its associated resources, including participants and Web resources By now (first iteration) the description of software releases is not included. There are some incongruities between [1] and [2], so I couldn't find every property stated in the textual description [2] also in the schema [1]. Currently DOAP implements 3 classes: - Project: obviously the main class, - Version: an instance of released software - Repository: a source code repository DOAP includes the property revision which might fit into our concept [1]. property: revision Revision identifier of a software release. isDefinedBy: http://usefulinc.com/ns/doap# domain: http://usefulinc.com/ns/doap#Version range: http://www.w3.org/2000/01/rdf-schema#Literal I'm not sure if this project is in an operable state. [2] states 4 properties of class Version: branch A string indicating the branch of this version, such as stable, unstable, gnome24, or gnome26 name A release name, such as Panther created Date of release in YYYY-MM-DD form revision Revision number of the release, such as 1.0 Does it make sense to declare a subclass of class Version in EARL, and use property revision (or isVersion)? details on: [1] http://xml.mfd-consult.dk/ws/2003/01/rdfs/?rdfs=http://svn.usefulinc.com/svn/repos/trunk/doap/schema/doap.rdf [2] http://www-106.ibm.com/developerworks/xml/library/x-osproj3/ cus.
Received on Friday, 20 May 2005 08:03:36 UTC