Coder Social home page Coder Social logo

Backend choice about hydrus HOT 4 CLOSED

http-apis avatar http-apis commented on June 17, 2024 2
Backend choice

from hydrus.

Comments (4)

Mec-iS avatar Mec-iS commented on June 17, 2024

@pchampin I would prefer MongoDB as a solution because it is something I have been using a lot, but it has always been told to me (at least until two years ago) that reasoning on that it is pretty impossible and there is no SPARQL endpoint that can do it (using SPARQL is not my priority for sure, but everybody I have talked to was pretty much convinced that that is no real alternative). Can you extend your proposal to include other libraries involved in a MongoDB-based stack to have the full picture?

from hydrus.

pchampin avatar pchampin commented on June 17, 2024

I would not be so radical about providing a SPARQL endpoint, especially if we supplement it with a Triple Pattern Fragment service...

Regarding reasoning, the problem with document-based DBs is that they work with JSON structure, so from the point of view of RDF/Linked Data, they are not convenient for any kind of processing at the semantics level. I wouldn't go as far as stating that reasoning is impossible, but it has to be handled by an additional layer (see for example https://arxiv.org/abs/1307.2603)

That being said, it all depends on the level of intelligence that we need/want to implement on the server side, if any. I would be happy with a very simple server, merely providing CRUD operations on a set of semantically-described resources, and leave it to the client to do smart stuff with those. To quote Ruben Verborgh, we can aim at "a Web on which clients possess more intelligence than the servers they use".

from hydrus.

Mec-iS avatar Mec-iS commented on June 17, 2024

@pchampin

I would be happy with a very simple server, merely providing CRUD operations on a set of semantically-described resources, and leave it to the client to do smart stuff with those.

Yeah definitely, same idea in my starting annotations. the "client" (that in many cases will be just another layer of service for the "end-user") will actually handle the "intelligent" part. Let's discuss this matter when we will have a well-based prototype for an HYDRA server, so we can decide how to improve it and make it work with the client.

from hydrus.

Mec-iS avatar Mec-iS commented on June 17, 2024

temporary closing. To be reopened in a later phase.

from hydrus.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.