- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Sat, 21 Jun 2014 14:41:18 +0200
- To: Martynas Jusevicius <martynas@graphity.org>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, public-hydra@w3.org, public-declarative-apps@w3.org
Hi Martynas, I'm afraid I don't fully understand yet. > You are right, our work is mostly about server side. ”server side": does it mean internal things that are not visible from the outside, or (an) external interfaces() offered by a server? > We want to empower developers, so that they would be able to build > full-featured Linked Data (and Web in general) applications by writing > much less code, ideally none, and managing them as data instead. > > are not so much > concerned about the so far hypothetical Web where every client can > interact with every server. But those goals are somehow related right? Not having to write much code to interact with any server X, seems close to having every client interact with every sever. > It boils down to replacing obsolete Web architecture components such as RDBMSs In what sense are RDBMS Web architecture components? It what sense are they obsolete? > What we have is a generic read-write processor implementation [1], on > which declarative application descriptions can be run in RDF form. So if I understand this right, it is about server-side components that have similar observable behavior on the other side of the HTTP connection, but different inner workings? But why does this need standardization then? Who needs to talk to the inner system of the server? Best, Ruben
Received on Saturday, 21 June 2014 12:41:54 UTC