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

Alasdair,

I'll take this to the public-lod list, I don't want to cross-post again.

I think what you're asking depends somewhat on whether you mean both read
and write, and also whether we consider CSV and JSON, and the SPARQL result
formats, a part of Linked Data.

One option would be expand the supported query types from CONSTRUCT and
DESCRIBE to also include SELECT and ASK. Effectively SPARQL result sets
would become part of Linked Data, along with RDF graphs, but read-only. You
would request SPARQL results CSV or JSON format using conneg on resources
that map to those queries.

If you mean CSV/JSON as graphs, a generic way would be to use something
like CSV on the web minimal mode [1] and translate it from/to RDF on the
fly during request. But normally you'd also want to map the columns to
vocabulary properties, which would require a mapping CONSTRUCT and that
becomes a 2-step request flow (first upload file, then create import). You
can read how that is done on AtomGraph platform:
http://linkeddatahub.com/docs/usage/import-data

Does that help?

Martynas

[1] https://www.w3.org/TR/2015/REC-csv2rdf-20151217/#dfn-minimal-mode



On Thu, Jun 29, 2017 at 1:03 PM, Gray, Alasdair J G <A.J.G.Gray@hw.ac.uk>
wrote:

> Hi Martynas
>
> The Linked Data Templates look like a really interesting way of getting a
> read/write data web. However, I’m unclear whether you support data returned
> in non-RDF serialisations, e.g. CSV, or JSON.
>
> In the Open PHACTS Discovery Platform [1] we used the Linked Data API to
> provide an abstraction for our web (HTML/CSS/JSON) app developers so that
> they did not need to be proficient in Semantic Web technologies (RDF, OWL).
> This greatly improved the efficiency of the development of our project as
> it meant our app developers could focus on what they were good at and the
> semantic web technology was exploited but hidden [2].
>
> I have more recently be using the Linked Data API approach in different
> projects where we are starting to see a need for being able to write data,
> not just read it.
>
> It would be a huge limitation of the Linked Data Templates if they did not
> support serialising to CSV, JSON, etc.
>
> Best regards,
>
> Alasdair
>
> [1] https://dev.openphacts.org/
> [2] http://content.iospress.com/articles/semantic-web/sw088
>
> On 29 Jun 2017, at 10:47, Martynas Jusevičius <martynas@atomgraph.com>
> wrote:
>
> Fellow Linked Data and Semantic Web developers,
>
> apologies for cross-posting.
>
> I am pleased to present the first public draft of Linked Data Templates
> specification:
> https://atomgraph.github.io/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
> following:
>
>   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
> semantics.
>
>   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
> protocol.
>
> Looking forward to your feedback and participation.
>
>
> Best regards,
>
>
> Martynas
> http://atomgraph.com
> https://twitter.com/atomgraphhq
>
> [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://en.wikipedia.org/wiki/HATEOAS
> [7] https://www.w3.org/2005/Incubator/webid/spec/
> [8] http://spinrdf.org
> [9] https://ipfs.io
>
>
> Alasdair J G Gray
> Fellow of the Higher Education Academy
> Assistant Professor in Computer Science,
> School of Mathematical and Computer Sciences
> (Athena SWAN Bronze Award)
> Heriot-Watt University, Edinburgh UK.
>
> Email: A.J.G.Gray@hw.ac.uk
> Web: http://www.macs.hw.ac.uk/~ajg33
> ORCID: http://orcid.org/0000-0002-5711-4872
> Office: Earl Mountbatten Building 1.39
> Twitter: @gray_alasdair
>
>
>
>
>
>
>
>
>
>
> ------------------------------
>
> Founded in 1821, Heriot-Watt is a leader in ideas and solutions. With
> campuses and students across the entire globe we span the world, delivering
> innovation and educational excellence in business, engineering, design and
> the physical, social and life sciences.
>
> This email is generated from the Heriot-Watt University Group, which
> includes:
>
>    1. Heriot-Watt University, a Scottish charity registered under number
>    SC000278
>    2. Edinburgh Business School a Charity Registered in Scotland,
>    SC026900. Edinburgh Business School is a company limited by guarantee,
>    registered in Scotland with registered number SC173556 and registered
>    office at Heriot-Watt University Finance Office, Riccarton, Currie,
>    Midlothian, EH14 4AS
>    3. Heriot- Watt Services Limited (Oriam), Scotland's national
>    performance centre for sport. Heriot-Watt Services Limited is a private
>    limited company registered is Scotland with registered number SC271030 and
>    registered office at Research & Enterprise Services Heriot-Watt University,
>    Riccarton, Edinburgh, EH14 4AS.
>
> The contents (including any attachments) are confidential. If you are not
> the intended recipient of this e-mail, any disclosure, copying,
> distribution or use of its contents is strictly prohibited, and you should
> please notify the sender immediately and then delete it (including any
> attachments) from your system.
>