---- On Wed, 24 Aug 2016 00:16:56 +0200 Martynas Jusevičius
<[email protected]> wrote ----
> Simon,
>
> with LDT, every application is a service, backed by SPARQL dataset,
> and driven by an ontology.
What is a LDT service to you? Can it be a Java application that uses Linked
Data as its API or is it a completely declarative approach that doesn't allow
side effects for example.
>
> The service description is made discoverable by making the ontology
> dereferencable. Every LDT response contains header information linking
> the resource back to the application, to its ontology, and the
> matching template.
>
> LDT generates SPARQL commands from templates. They are part of the
> service description, therefore also part of the ontology. SPIN RDF
> vocabulary makes it easy to embed SPARQL in RDF form.
>
> There is currently no registry of LDT apps/services, although it
> wouldn't be hard to implement (as an LDT app :))
> We are currently working on a cloud platform that will offer hosted
> apps with a user-friendly UI. In principle it could interact with
> hosted as well as registered 3rd party LDT apps. So far we haven't had
> this use case though.
I still don't get it. I guess, since LDT is such a new thing, there is not much
documentation around. Luckily the important part of the source code, the
Processor is available. I'm going to read it maybe that answers my questions.
