[ANN] Linked Data Templates: Call for feedback and CG charter

Hey group,

just because it has been quiet on the mailing list, it does not mean we
haven't been busy :)

I am pleased to present the first public draft of Linked Data Templates:
https://atomgraph.github.io/Linked-Data-Templates/

The purpose of Linked Data Templates 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, and we would like to contribute this draft to the CG as a
basis for further work. That said, we would like to receive some feedback
as an indication if this is something that the group finds interesting and
is willing to work on. If you know someone this might be relevant to,
please invite them to join the CG [6]. We should also have a charter that
establishes the guidelines for further work [7]. Given positive feedback,
we could draft the charter and make the contribution next week.

We propose the following charter -- please feel free to ask questions and
suggest changes or additions. Most of the items are already covered in the
LDT draft, we could start with reviewing the document and resolving
existing issues.


Goals
=====

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 [8] and foster reuse of
Linked Data API descriptions and development of generic software. The
evaluation of interactions shall be unambiguous and defined using precise
semantics.

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

Scope of Work
=============

- abstract syntax and domain model of LDT applications
- formal interaction evaluation semantics
- HTTP bindings
- LDT vocabulary

Out of scope
============

Support for non-SPARQL based applications.

Compatiblity with Linked Data Platform (at this stage).

Deliverables
============

- LDT specification
- LDT core vocabulary
- possibly protocol-specific vocabularies, e.g. for HTTP
- default LDT ontologies
- test suite
- open source implementation(s)


Martynas
http://atomgraph.com

[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
[4]
https://github.com/AtomGraph/Linked-Data-Templates/blob/master/XML%20London%202016%20paper/Linked%20Data%20Templates.pdf
[5]
https://github.com/AtomGraph/Processor/blob/master/src/main/resources/com/atomgraph/processor/dht.ttl
[6] https://www.w3.org/community/declarative-apps/
[7] https://w3c.github.io/cg-charter/CGCharter.html
[8] https://en.wikipedia.org/wiki/HATEOAS
[9] https://www.w3.org/2005/Incubator/webid/spec/
[10] http://spinrdf.org
[11] https://ipfs.io