It turned out that no projects are missing a DOAP file; I have had
problems parsing
a couple of files; they seem not to be valid RDFs according to
http://www.w3.org/RDF/Validator/
http://forrest.apache.org/doap.xml
http://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/doap/uima.rdf
Forrest does not contain any RDF statement
UIMA has a detailed asfext:PMC section which generates these errors:
Error: {E201} rdf:about not allowed as attribute here.[Line = 61, Column
= 34]
Error: {E202} Expecting XML start or end element(s). String data "Apache
UIMA" not allowed. Maybe there should be an rdf:parseType='Literal' for
embedding mixed XML content in RDF. Maybe a striping error.[Line = 62,
Column = 31]
Error: {E201} Multiple children of property element[Line = 63, Column = 21]
Error: {E202} Expecting XML start or end element(s). String data
"Marshall Schor" not allowed. Maybe there should be an
rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a
striping error.[Line = 65, Column = 36]
Error: {E201} Multiple children of property element[Line = 68, Column = 23]
Error: {E202} Expecting XML start or end element(s). String data "The
mission of the Apache UIMA project is" not allowed. Maybe there should
be an rdf:parseType='Literal' for embedding mixed XML content in RDF.
Maybe a striping error.[Line = 68, Column = 64]
------------------------------------------------------------------------
61:<asfext:PMC rdf:about="UIMA">
62:<asfext:name>Apache UIMA</asfext:name>
63:<asfext:chair>
64:<foaf:Person>
65:<foaf:name>Marshall Schor</foaf:name>
66:</foaf:Person>
67:</asfext:chair>
68:<asfext:charter>The mission of the Apache UIMA project is
69: the creation and maintenance of
70: open-source software related to the analysis of unstructured
71: data, guided by the UIMA Oasis Standard.</asfext:charter>
72:</asfext:PMC>
I thought it might be useful to share this info,
Cheers,
Davide
Il 15/01/2013 22:18, Ross Gardler ha scritto:
It would be excellent if you could encourage projects without a DOAP file
to create one. In fact all top level Apache projects should have one as per
our branding requirements [1] which state:
"All projects must provide a DOAP - Description Of A Project - file or
entry for both the project itself and all product releases that they make.
Follow the guidelines at<http://projects.apache.org/create.html> to make a
DOAP file and register it. This will allow the ASF to best showcase all of
its projects and products in a variety of ways."
Compiling a list of those projects that do not yet have a DOAP file and
posting it here will be an excellent contribution to help us help them.
Note we provide a web form for Apache projects to create their DOAP at [2]
Ross
[1]http://www.apache.org/foundation/marks/pmcs.html
[2]http://projects.apache.org/create.html
On 15 January 2013 09:30, Davide Galletti<davide.galle...@gmail.com> wrote:
> Hi,
>
> I am new to the list; my name is Davide Galletti and I am working on a EEC
> funded research project named MARKOS;
>
> "MARKOS intends to realize the prototype of an automatic service providing
> an integrated view
> on the Open Source projects available on the web, focusing on functional,
> structural and licenses
> aspects of the software code released by the projects."
> More detail and updates onhttp://www.markosproject.eu/
>
> Within MARKOS I will realize a component called "Crawler" which will be
> responsilble for
> gathering as much informationon OSS Projects as possible from forges,
> metaforges and any
> source we might find interesting. The first release is expected in 2013,
> and development will
> continue till the end of 2014, of course with an OSS license.
> I believe I will access information on Apache projects from the list of
> DOAP files available here:
>
https://svn.apache.org/repos/**asf/infrastructure/site-tools/trunk/projects/files.xml
> I have read from Rich Bowen that not all projects have a DOAP file.
