On Mon, 28 Oct 2019 at 10:56, Christofer Dutz <[email protected]> wrote:
>
> Hi,
>
> Well as far as I understood it, this data is provided by the RDF files 
> projects maintain themselves.

Yes, projects maintain their own DOAP files.

If the project data file is wrong, then the output is likely to be wrong also.

I suppose it might be possible to do some more validation on the DOAP
files, but I'm not sure the effort would be worth it.

> I too noticed some time ago the "iot" category was only used by Apache Camel, 
> so I fixed this at least for Apache PLC4X.
> We integrated this into our code-repo and the site-generation:
> https://github.com/apache/plc4x/blob/develop/src/site/resources-filtered/plc4x-doap.rdf
>
> And I just noticed it is slightly out of date with respect to our latest 
> releases.
>
> Chris
>
>
> Am 25.10.19, 01:26 schrieb "sebb" <[email protected]>:
>
>     On Thu, 24 Oct 2019 at 23:30, Nick Burch <[email protected]> wrote:
>     >
>     > Hi All
>     >
>     > I've spotted what looks like a data bug, but might be a code bug, on
>     > projects.apache.org. For some projects, they are being shown not against
>     > their proper category (eg library), but against a category that's 
> prefixed
>     > with the https://projects.a.o link for their category
>     >
>     > For example, Apache Tika is showing as a category of
>     > https://projects.apache.org/projects.html?category#library instead of 
> just
>     > library. You can see that at
>     > 
> https://projects.apache.org/projects.html?category#https://projects.apache.org/projects.html?category#library
>
>     That is a data bug.
>
>     See https://projects.apache.org/guidelines.html for category syntax.
>
>     > Thanks
>     > Nick
>     >
>     > ---------------------------------------------------------------------
>     > To unsubscribe, e-mail: [email protected]
>     > For additional commands, e-mail: [email protected]
>     >
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: [email protected]
>     For additional commands, e-mail: [email protected]
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to