W3C home > Mailing lists > Public > public-rww@w3.org > April 2017

Re: Linked Data Platform Wikipedia Entry Draft

From: Brent Shambaugh <brent.shambaugh@gmail.com>
Date: Fri, 21 Apr 2017 14:39:13 -0500
Message-ID: <CACvcBVpBeqEh0coqJ1LBWVMGZTD8k6hviQ8vvZB0GTiZps6rOw@mail.gmail.com>
To: Kingsley Idehen <kidehen@openlinksw.com>
Cc: public-rww <public-rww@w3.org>
Thanks for your comments! I now have:

“Linked Data Platform (LDP) is a Linked Data specification defining a
set of integration patterns for building RESTful HTTP services that
are capable of read-write of RDF data. ...
The Linked Data Platform allows use of RESTful HTTP to consume,
create, update and delete both RDF and non-RDF resources.[5] In
addition, it defines a set of "Container" constructs—buckets into
which documents can be added with a relationship between the bucket
and the object similar to the relationship between a blog and its
constituent blog posts.[6]”
(https://en.wikipedia.org/wiki/Linked_Data_Platform)

History:

LDP evolved from work at IBM's Rational Product Group for application
integration. Starting in 2010, IBM looked at linked data for
application lifecycle management and sought what was an alternative
means for read-write Linked Data.
Read-Write Linked data was previously described using WebDAV and
SPARQL/UPDATE[8] by Tim Berners-Lee
in his design issues [1],[2] that built upon his 4 rules for linked data [3].

IBM joined with the W3C in June 2012 to form a working group.
It consisted of “50 particpants from 30 organizations”[7], and was
chaired by Arnaud J Le Hors. On 26 February
2015, the W3C Linked Data Platform 1.0 was approved as a W3C Recommendation [4].

The linked data platform includes Tim Berners-Lee's 4 rules, and focuses on the
following concepts:

-LDP Resources (LDPR)
  - HTTP and RDF techniques to read and write linked data
  - Resources can be created, modified, deleted and read using
standard HTTP methods
    (i.e.,POST,PUT/PATCH,DELETE,GET)
  - Cover "RDF sources" as well as "binary resources"

- LDP Containers (LDPC)
  - An LDPR to which you POST to create new things, GET to find existing things
  - Similar to what AtomPub does for XML
  - Available in three flavors: BasicContainer, DirectContainer, and
IndirectContainer

- Paging & Ordering
  - A mechanism to get the content of a LDPC in chunks and specify the
order in which the
    content is sorted”[7]

LDP is not a file system, but it uses Linked Data to produce the kind of
information that can be used to create a modern file system abstraction
for interacting with HTTP-accessible resources (colloquially referred to
as "Web Resouces").

In contrast, WebDAV is a "set of extensions to the HTTP protocol which
allows users to collaboratively edit and manage files on remote web servers"[9].
However, LDP can be used with WebDAV. For example, to load load
Kingsley Idenhen's
WebDAV repository with one of Tim Berners-Lee's LDP containers:

curl -ikLH "Origin: (I will throw this in if ok)" -H "Accept:
text/turtle" https://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/RWW/

Note: this requires authentication an authorization with WebID, ACL,
and TLS  using an x.509 certificate. See the SOLiD spec[10].

(actually, example.com works just fine, strike out the line above)

See also

Apache Marmotta
Fedora Commons
SOLiD

References:

[1] https://www.w3.org/DesignIssues/CloudStorage.html
[2] https://www.w3.org/DesignIssues/ReadWriteLinkedData.html
[3] https://www.w3.org/DesignIssues/LinkedData.html
[4] "Linked Data Platform (LDP) is a W3C Recommendation". W3C.
[5] Mihindukulasooriya, Nandana (2014-11-05). "Learning W3C Linked
Data Platform with examples".
[6] Burleson, Cory (10 July 2014). "Introduction to: Linked Data
Platform". semanticweb.com.
[7] https://www.youtube.com/watch?v=YxkFS8r3OUE&t=2756s
[8] https://www.w3.org/TR/sparql11-update/
[9] http://webdav.org/
[10] https://github.com/solid/solid-spec


External Links:

Linked Data Platform 1.0, W3C
Linked Data Platform 1.0 Primer, W3C
Linked Data Platform Use Cases and Requirements, W3C
LDP Implementations, W3C Wiki
Getting Started with the Linked Data Platform (LDP) – background and
history during early development
Introduction to Fedora 4 - Includes Discussion of LDP
<https://www.youtube.com/watch?v=5p-MmNgnDCg>
-Brent Shambaugh

GitHub: https://github.com/bshambaugh
Website: http://bshambaugh.org/
LinkedIN: https://www.linkedin.com/in/brent-shambaugh-9b91259
Skype: brent.shambaugh
Twitter: https://twitter.com/Brent_Shambaugh
WebID: http://bshambaugh.org/foaf.rdf#me


On Tue, Apr 18, 2017 at 9:23 AM, Kingsley Idehen <kidehen@openlinksw.com> wrote:
> On 4/18/17 12:53 AM, Brent Shambaugh wrote:
>> would suggest replacing "but realized that Tim Berners-Lee's four
>> rules for linked data[6] did not go far enough for their purpose" with
>> something along the lines of "and realized that Tim Berners-Lee's four
>> rules for linked data[6] could be applied to this problem space too."
>>
>> Why? Because that claim (by whoever made or is making it) is factually
>> incorrect, and somewhat nonconstructive.
>>
>> I need to pull in:
>>
>> "
>>
>> The Linked Data article gave simple rules for putting data on the web
>> so that it is linked. Then, "Read-Write Linked Data" follows on from
>> that to discuss allowing applications to write as well as read data.
>> This note adds decentralized access control of reading and of writing
>> to linked data.
>>
>> This can be called "socially-aware" storage, because the access
>> control within the storage layer is just powerful enough to implement
>> the social requirements of the social network applications. (In the
>> current model proves insufficiently powerful to do this, then it could
>> be enhanced by adding more inference to the ACL system, and more
>> expressivity to the ACL -- or rather policy language -- used to
>> express the social constraints). The overall goal is one in which
>> storage with the necessary functionality is a ubiquitous commodity,
>> and application growth becomes dramatic as the provision of storage is
>> decoupled from the design and deployment of applications."
>>
>> https://www.w3.org/DesignIssues/CloudStorage.html (date 2011/09/27 22:31:21)
>>
>> "
>> and https://www.w3.org/DesignIssues/ReadWriteLinkedData.html
>>
>> In a larger scope it appears timbl was going for webdav for RWW before
>> the LDP WG started, then he later adopted LDP (bringing over Joe
>> Presbey and Andrei (the latter knowingly in the LDP WG with Arnaud))..
>>
>> LDP WG: first recommendation for RWW that I know of
>> TimBL: first thinking of RWW that I Know of
>> -Brent Shambaugh
>
> Brent,
>
> TimBL's first thinking about a Read-Write Web dates back to the time he
> created the Web. He never envisaged the Web as a Read-Only medium.
> That's a fallacy emerging from the illusion thrust upon Web users by Web
> Browsers (starting with Mosaic!).
>
> TimBL tried using WebDAV at a time when LDP didn't exist. Today, you can
> use WebDAV or LDP to achieve his Read-Write goals.
>
> --
> Regards,
>
> Kingsley Idehen
> Founder & CEO
> OpenLink Software   (Home Page: http://www.openlinksw.com)
>
> Weblogs (Blogs):
> Legacy Blog: http://www.openlinksw.com/blog/~kidehen/
> Blogspot Blog: http://kidehen.blogspot.com
> Medium Blog: https://medium.com/@kidehen
>
> Profile Pages:
> Pinterest: https://www.pinterest.com/kidehen/
> Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
> Twitter: https://twitter.com/kidehen
> Google+: https://plus.google.com/+KingsleyIdehen/about
> LinkedIn: http://www.linkedin.com/in/kidehen
>
> Web Identities (WebID):
> Personal: http://kingsley.idehen.net/dataspace/person/kidehen#this
>         : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
>
>
Received on Friday, 21 April 2017 19:39:52 UTC

This archive was generated by hypermail 2.3.1 : Friday, 21 April 2017 19:39:53 UTC