Thanks for the info... we may be looking to use Marmotta for a project but was concerned about some the bugs I've encountered out of the box. For example, mysql doesn't seem to have a 'triples' table when I select that for the KiWi back-end... I had to create this manually. And even the Postgres setup gives some error I tried to track down. All in all, the feature set here is very close to what my needs are, but the above, and some performance issues with SPARQL when I tested it made me shy away. I'm willing to work on it to get things going, but I do have to consider other alternatives, at least other graph db's, if not full blown LDP platforms.
I'd love to hear more updates and chatter here (and on the dev channel). I think going to RDF4J is a great start too - and maybe I can try to fix the mysql and Postgres issues once I track down where those DDL files are. Thanks again! Alan On Wed, Feb 27, 2019 at 3:49 PM Xavier Sumba <xavier.sumb...@ucuenca.edu.ec> wrote: > Hello all, > > We can propose something for GSoC 2019 with the aims of reviving the > project and attract contributors. What do you think Jakob? > > I can try to finish the migration to RDF4J if I find some free time. :D > > In the meantime Alan, if you'd like to contribute with something the > migration is a good start [1], and IMHO, it was a matter of moving to the > version 3.4.0 and solving some naming conventions. I think for now we can > avoid the experimental backends. > > > Best, > Xavier > > [1] https://github.com/apache/marmotta/pull/31 > > > > On Feb 27, 2019, at 15:22, Jakob Frank <jakob.fr...@redlink.co> wrote: > > > > Hi Alan, > > > > I'd say dormant, not dead. > > > > To be frank: Development activities have been rather low in the past > months. > > Any help is appreciated, so if you'd like to contribute something you > > are more than welcome! > > > > Best, > > Jakob > > > > > > On Wed, 27 Feb 2019 at 15:27, Alan Snyder <alan8...@gmail.com> wrote: > >> > >> Thanks Aaron.. just to be clear.. Is Marmotta a dead project now? There > was just a release in June for 3.4.0 so I hoped there'd be some momentum.. > any plans for future work here? > >> > >> > >> > >> On Wed, Feb 27, 2019, 9:03 AM Aaron Coburn <acob...@amherst.edu> wrote: > >>> > >>> Hi, > >>> if you are looking for an LDP server, the Apache Annotator project > (Web Annotation Protocol sits atop LDP) has a list of implementations on > this page: > >>> > >>> > https://github.com/apache/incubator-annotator/wiki/LDP-and-Web-Annotation-Protocol-Implementations > >>> > >>> Other than Virtuoso, which is a commercial product, all of the > projects listed are Apache 2 licensed. > >>> > >>> -Aaron > >>> > >>> On Tue, Feb 26, 2019 at 3:20 PM Alan Snyder <alan8...@gmail.com> > wrote: > >>>> > >>>> Hi, just wondering if this project is still active? I don't see any > activity in the mailing list archives. Is there another venue for > communication with the team? And if the project isn't worked on routinely, > is there another platform recommended to use with similar features / > license? > >>>> > >>>> Thanks! > >>>> Alan > >>>> > > > > > > -- > > Jakob Frank > > | http://redlink.at > > | m: +43 699 10588742 | e: jakob.fr...@redlink.at > > | http://at.linkedin.com/in/jakobfrank > > > -- > Advertencia legal: > Este mensaje y, en su caso, los archivos anexos son > confidenciales, especialmente en lo que respecta a los datos personales, y > se dirigen exclusivamente al destinatario referenciado. Si usted no lo es > y > lo ha recibido por error o tiene conocimiento del mismo por cualquier > motivo, le rogamos que nos lo comunique por este medio y proceda a > destruirlo o borrarlo, y que en todo caso se abstenga de utilizar, > reproducir, alterar, archivar o comunicar a terceros el presente mensaje y > ficheros anexos, todo ello bajo pena de incurrir en responsabilidades > legales. Las opiniones contenidas en este mensaje y en los archivos > adjuntos, pertenecen exclusivamente a su remitente y no representan la > opinión de la Universidad de Cuenca salvo que se diga expresamente y el > remitente esté autorizado para ello. El emisor no garantiza la integridad, > rapidez o seguridad del presente correo, ni se responsabiliza de posibles > perjuicios derivados de la captura, incorporaciones de virus o > cualesquiera > otras manipulaciones efectuadas por terceros. >
