Re: Understanding linked data fragments

Thanks Ruben,

What I don't understand though is that, from the LDF spec itself, it says:

"A Linked Data Fragment of a Linked Data dataset is a set of RDF triples
that consists of three parts:
data: all triples of this dataset that match a specific selector;
metadata: triples that describe the dataset and/or the Linked Data Fragment;
controls: hypermedia links and/or forms that lead to other Linked Data
Fragments."

I guess I'm confused about the relationship of TPF to LDF because the above
description is what I thought I was describing in the last part of my
previous message: "And the standardized response format (LDF) facilitates
the universal applicability of any smart client built around it."

Is a TPF therefore just a specific LDF response format? I'm not sure that
is correct as you've been quite adament in pointing out that I'm confusing
TPF with LDF, though the following sentence in the LDF spec - "The goal of
Linked Data Fragments is to provide a uniform view on all possible
interfaces to Linked Data" - suggests that LDF simply defines the
composition of any response that qualifies as LDF, of which TPF would be
just one.

Perhaps the confusion was in my use of the word "format"?

thanks,
Nathan

On 6 February 2015 at 18:32, Ruben Verborgh <ruben.verborgh@ugent.be> wrote:

> Hi Nathan,
>
> > Thanks Ruben, Tomasz and Markus, your responses were very helpful; I
> believe I understand now.
>
> Great to hear!
>
> > In particular, Ruben's video, linked by Tomasz, provided the clarity I
> was seeking.
>
> Your feedback made me realize I had to put this on the website:
> - http://linkeddatafragments.org/
> - http://linkeddatafragments.org/in-depth/#video
>
> > As I now understand it, what we're essentially talking about is a
> concept for doing *some* of the work on the server and *some* of the work
> on the client, with the idea that the smarter you can make the client, the
> more it can take the burden off of the server, which not only reduces the
> chances of bottlenecking by the server, but gives you a better client that
> has greater, more universal querying capabilities, thus aligning with the
> decentralised nature of the semantic web.
>
> I couldn't summarize it better!
>
> > And the standardized response format (LDF) facilitates the universal
> applicability of any smart client built around it.
>
> Make that "TPF", and I fully agree.
>
> Best,
>
> Ruben




-- 
*Google*: axefrog@gmail.com
*Skype*: axefrog
*Twitter*: @NathanRidley
*Website*: http://axefrog.com / http://nathanridley.com
*Phone: *+61 (0) 475 072789