Hi Sergio,
2013/1/3 Sergio Fernández <[email protected]> > Hi, > > Now that INFRA-5610 [1] has been solved, before work over MARMOTTA-2 [2], > in the following days I'd like to discuss with all people what code we'll > import into Marmotta. > > The idea is to have a milestone releasing LMF 2.4 this month, and then > move to Marmotta. But, as we asserted in the proposal [3], the whole LMF > will not be contributed to Marmotta; to focus the project, actually only > those parts that make up the "Linked Data Platform", that includes the > following modules: > > * lmf-core > * lmf-sparql > * lmf-cache > * lmf-reasoner > * lmf-scheduler > * lmf-security > * lmf-ldpath > * lmf-versioning > * lmf-webapp > > There are some generic libraries we may also include: > > * ldpath > * sesame-tools > I have one small addition here. I am currently working on separating the KiWi triple store from the LMF so 1) it can be used outside the LMF as Sesame SAIL, and 2) the LMF can be used with any other Sesame backend. I would also consider this as a generic library. It is in the module * kiwi in the triplestore branch of Mercurial. Before importing the code into GIT, we should merge back all branches to make sure everything is available there. > > Plus some installation infrastructure: > > * lmf-installer > * lmf-splash > > Around that there are some Maven plugins: > > * lmf-maven-plugin > * buildinfo-maven-plugin > * refpack-maven-plugin > > And archetypes: > > * lmf-archetype-module > * lmf-archetype-webapp > > On top of that, the lmf client library is currently implemented in > different languages: > > * lmf-client-java > * lmf-client-php > * lmf-client-js > > Besides some refactorizations and reorganization, I consider all those > artifacts relevant for Marmotta. > > For instance, all the media stuff would be out of the importation, > including: > > * lmf-search > * lmf-social > * lmf-classifier > * lmf-stanbol > My idea here was to keep them on the Google Code repository under the name LMF, but let them depend on Apache Marmotta in future versions. But we could also consider having "contrib" or "extra" modules in Marmotta itself. > > But I have doubts regarding some third-party tools: > > * SKOSjs > Should be a separate project, but Marmotta should depend on it. Maybe we can use the Maven JavaScript dependency management for it? > * Module for Drupal > "contrib" or "extra" ;-) > * Extension for Google/Open Refine > > "contrib" or "extra" ;-) Greetings, Sebastian
