fix abstract. "universal approach" was weird. "Linked Data" does not refer to handling data. "which has the idea" is odd phrasing. "Linked Data" does not give a data layer on top of application, rather applications can use the data layer... bblfish
authorHenry Story <henry.story@bblfish.net>
Thu, 29 May 2014 13:39:06 +0200
branchbblfish
changeset 609 3f9d1ea6f82e
parent 608 7ec8fe696def
child 610 d9ad42f29847
fix abstract. "universal approach" was weird. "Linked Data" does not refer to handling data. "which has the idea" is odd phrasing. "Linked Data" does not give a data layer on top of application, rather applications can use the data layer...
ldp-primer/ldp-primer.html
--- a/ldp-primer/ldp-primer.html	Thu May 29 13:30:26 2014 +0200
+++ b/ldp-primer/ldp-primer.html	Thu May 29 13:39:06 2014 +0200
@@ -248,7 +248,9 @@
     <h1 id="intro">Introduction</h1>
 
     <p>
-      Linked Data[[LINKED-DATA]] is a universal approach for handling data which has the idea of data entities and links between them, where the mechanisms and principles of the Web is used to give a data layer on top of applications are delivered, through the modification, processing, visualization and sharing of information. 
+      The term "Linked Data" [[LINKED-DATA]] refers to an approach to publishing data that puts linking at the heart of the notion of data, and uses the linking technologies provided by the Web to enable the weaving of a global distributed database. 
+     By naming real world entities - be they web resources, physical objects such as the Eiffel Tower, or even more abstract things such as relations or concepts - with http(s) URLs, whose meaning can be determined by dereferencing the document at that URL, and by using the relational framework provided by RDF, data can be published and linked in the same way web pages can. 
+    The Linked Data Protocol specifies how web applications can, using the HTTP protocol, find resources and follow links, publish new resources, edit and delete existing ones. 
     </p>
     <p>
       To construct clients and servers that read and write Linked Data resources, LDP specifies standard HTTP and RDF techniques and best practices that you should use, and anti-patterns you should avoid,  The Primer aims to provide introductory examples and guidance in the use of the LDP protocol. For a systematic account the reader should consult the normative LDP reference [[LDP]]. For an overview of the use cases for LDP and the elicited requirements that guided its design, the reader should consult the LDP Use Cases and Requirements [[LDP-UCR]] and for best practises and guidelines, the reader should consult the LDP LDP Best Practices and Guidelines document [[LDP-BP]].