W3C home > Mailing lists > Public > semantic-web@w3.org > June 2017

[ANN] Linked Data Templates: First draft and Call for participation

From: Martynas Jusevičius <martynas@atomgraph.com>
Date: Thu, 29 Jun 2017 11:47:06 +0200
Message-ID: <CAE35VmwHpbtmqg6BTH0TrmGEG_remR2-5H0jSG2VHGgYkcaEMw@mail.gmail.com>
To: public-lod <public-lod@w3.org>, Semantic Web <semantic-web@w3.org>, Hydra <public-hydra@w3.org>, public-sparql-dev@w3.org, "public-rww@w3.org" <public-rww@w3.org>, "public-ldp@w3.org" <public-ldp@w3.org>
Cc: Tim Berners-Lee <timbl@w3.org>
Fellow Linked Data and Semantic Web developers,

apologies for cross-posting.

I am pleased to present the first public draft of Linked Data Templates

The purpose of Linked Data Templates (LDT) is to provide means to define
read-write Linked Data APIs declaratively using SPARQL and specify a
uniform interaction protocol for them. We see it and use it as a
declarative and better-defined alternative to Linked Data Platform [1].

LDT is a formalization of the Linked Data processing model found in our
AtomGraph Processor [2]. It has evolved from, and has been tested in,
real-world Linked Data applications [3]. A summary of the approach can be
found in the XML London 2016 paper [4].
For an example of LDT ontology, see [5].

We feel that LDT could become a cornerstone technology of a distributed
Semantic Web. That said, we would like to receive some feedback as an
indication if this is something that the community finds interesting and is
willing to work on.

If you find this approach interesting, please join the Declarative Apps
Community Group: https://www.w3.org/community/declarative-apps/

The goals of the CG are to be stated in a charter. We have proposed the

  The Declarative Apps CG shall develop a specification for 1) declarative
application descriptions that map Linked Data interactions to SPARQL
commands and can be expressed as RDF ontologies 2) a uniform read-write
Linked Data protocol for such ontology-driven applications.

  The protocol should allow for (but not be limited to) implementation of a
distributed web architecture, support HATEOAS [6] and foster reuse of
Linked Data API descriptions and development of generic software. The
evaluation of interactions shall be unambiguous and defined using precise

  The specification(s) must be compatible with RDF, SPARQL, RDFS, OWL,
WebID [7], SPIN [8] specifications; they should be orthogonal to any
concrete RDF syntax and/or concrete transport protocol (HTTP, IPFS [9]
etc). However, the specification shall provide bindings for the HTTP

Looking forward to your feedback and participation.

Best regards,


[1] https://www.w3.org/TR/ldp/
[2] https://github.com/AtomGraph/Processor
[3] https://www.w3.org/2011/09/LinkedData/ledp2011_submission_1.pdf
[6] https://en.wikipedia.org/wiki/HATEOAS
[7] https://www.w3.org/2005/Incubator/webid/spec/
[8] http://spinrdf.org
[9] https://ipfs.io
Received on Thursday, 29 June 2017 09:47:40 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:45:50 UTC