On 11/8/06, Steve Loughran <[EMAIL PROTECTED]> wrote:<snip/>

I have a work colleague who is converting all the maven2 metadata into
RDF, including class information, with which we can mine some
interesting things.


I've seen that on the repository mailing list, but I must admit that I'm not
familiar with the RDF format, so I was waiting to see what can be done with
it. If you (or your colleague) could give a  little example of what kind of
data he want to obtain, this could be very useful for people in the dark
like me.

My own goal is to use the data to audit the repo, look for anomalies
(loops, duplicate classes in different project's jars, missing links).
It makes a very good place to see if some of the semantic web vision
-individually published information- really can be merged together to
produce a unified whole, or whether consistency fails down as things
scale.

Stefano M is also interested in some RDF-based Gump successor, which is
itself dependency driven.


Dependency driven build server is a topic which interests me particularly.
I've developed  a plugin for cruisecontrol a long time ago to get dependency
driven builds in cruisecontrol, but the result is not perfect and does not
work with latest cruisecontrol version. Right now I haven't found a tool
satisfying my expectation, and was even wondering if I could find the time
to develop/patch something on my own.

While I personally dont think that much of RDF, I can see value in
having some metadata info that is entirely tool-neutral, which  RDF is,
and in the N3 notation, almost human readable once you've had enough
training in it. Plus swiprolog has good rdf integration, so I can work
with a proper logic language while processing it.


I'll believe you, my prolog courses are far away now, and as I said I do not
clearly see what an RDF representation of the maven repository could look
like.

It may make sense to have an RDF form as an interchange representation
of data, between m2, ivy and gump, and any other tools.


Why not, if it makes sense.

Where to discuss this? Here? [EMAIL PROTECTED] the maven mailing
list is too busy for a big discussion.


This is clearly related to dependency management, so here can be a good
place. I'm not confortable enough with the intent and the expectation of the
repository mailing list to say if it's appropriate or not, for me both are
ok.

Xavier

-Steve




Reply via email to