A Friendship is not an entity but a relation. "On the other hand" there was no "on the first hand". Links can lead to new entity descriptions. "make discoverable forward paths in the application" is opaque. "Affordances" is never explained clearly. bblfish
authorHenry Story <henry.story@bblfish.net>
Sun, 01 Jun 2014 13:02:30 +0200
branchbblfish
changeset 614 540b57854f9a
parent 613 504e45843e1d
child 615 a95dc79e1ef3
A Friendship is not an entity but a relation. "On the other hand" there was no "on the first hand". Links can lead to new entity descriptions. "make discoverable forward paths in the application" is opaque. "Affordances" is never explained clearly.
ldp-primer/ldp-primer.html
--- a/ldp-primer/ldp-primer.html	Sun Jun 01 11:12:50 2014 +0200
+++ b/ldp-primer/ldp-primer.html	Sun Jun 01 13:02:30 2014 +0200
@@ -312,11 +312,10 @@
     <p>
       A server hosting Linked Data Platform Resources (LDPRs) may manage two kinds of LDPRs, those resources whose state is represented using RDF called LDP RDF Sources (LDP-RS) and those using other formats called LDP Non-RDF Source (LDP-NR) such as html files, images, other binary files, etc. 
 Resources respond to retrieval operations using HTTP GET. 
-Often a description conveyed in the response document will describe a specific domain entity: Status, Friendship, Product, Order, Bug, etc.
-On the other hand, it might contain a description of a number of different concepts.
- The links contained in the descriptions lead to the subsequent discovery and processing of other resources.
- Affordances offered by the server make discoverable the forward paths in the application.
- Together the resources, links and associated affordances together specify what might be termed the API. 
+A description conveyed in the response document will describe one or more entities: a Person, a Status, a Product, an Order, a Bug, a Concept, a Relation, etc. by linking it to other entities or literals.
+ These descriptions can lead an agent to  discover and process other information resources, describing yet further entities.
+ Those entities served by an LDP Server - a.k.a LDPRs - can themselves be described in this way, so as to enable a client to understand what consequences interacting with them entails.
+ The description of LDPRs and their relations to entities specify what might be termed the API. 
     </p>
     <p>
       <img src="images/resources.png" />