On 2 Aug 07, at 1:22 AM 2 Aug 07, Shane Isbell wrote:
Okay. I see where you are coming from. If we are using multiple
datasources
- traditional pom object hierachy, RDF, Lucene index, XML stores -
then we
need a 1) common API (for application developers); 2) SPI (from
Maven);
In much
On 1 Aug 07, at 12:25 AM 1 Aug 07, Shane Isbell wrote:
I would like to see if there is any general interest from the Maven
community in using RDF for storing and retrieving of repository
information.
As the only means, and not accessed via some API shielding the
underlying store then my
A couple more points I thought of:
There is another implementation that uses JSR 170 so it would be very
hard to have any level of interoperability without an API. I
certainly don't want that being RDF.
There are plenty of good tools that can be leveraged, for example I
use Lucene
To clarify: NMaven uses RDF for its local repository store (and has
abstractions of an AssemblyResolver/ProjectDao for the API). It does not
require that the remote repository contain RDF, but rather parses and stores
the information from the remote pom artifact into the RDF store. There is
also
On 1 Aug 07, at 4:39 PM 1 Aug 07, Shane Isbell wrote:
To clarify: NMaven uses RDF for its local repository store (and has
abstractions of an AssemblyResolver/ProjectDao for the API). It
does not
require that the remote repository contain RDF, but rather parses
and stores
the information
Okay. I see where you are coming from. If we are using multiple datasources
- traditional pom object hierachy, RDF, Lucene index, XML stores - then we
need a 1) common API (for application developers); 2) SPI (from Maven); 3)
adapters (from framework developers). The SPI would need (at a minimum)
I would like to see if there is any general interest from the Maven
community in using RDF for storing and retrieving of repository information.
I switched NMaven's resolver implementation to one using RDF and am happy
with the results. This implementation allows: 1) easily extending meta-data,
in
