remarks about diagrams. bblfish
authorHenry Story <>
Sun, 01 Jun 2014 21:33:31 +0200
changeset 618 6ff8939ea487
parent 617 4d613e39746b
child 619 ba2abbd4424a
remarks about diagrams.
"allows to use some domain specific vocabulary to relate the resources of the hierarchy" ?
"membership property" -> "membership triple"
clarified how membership properties can constrain what type of thing can be posted.
--- a/ldp-primer/ldp-primer.html	Sun Jun 01 20:04:39 2014 +0200
+++ b/ldp-primer/ldp-primer.html	Sun Jun 01 21:33:31 2014 +0200
@@ -345,12 +345,19 @@
  Our first scenario illustrates the use Basic Containers with a document storage system.
-      A Direct Container allows to use some domain specific vocabulary to relate the resources of the hierarchy. The additional assertion is called the membership property.
+  Creating a resource in a Direct Container has as additional consequence the creation of an extra domain specific relation betwen the created resource and some entity described in a document controlled by the server.
+  The additional assertion is called the membership triple.
+  The relation constituing a membership triple, known as the membership predicate, can set a constraint on the types of documents posted to a container.
+  For example the range of the <a href="">foaf:depiction</a> relation being an Image,  a Direct Container with such a membership property would be expected to only allow images to be posted to such a container.
     <figure id="fig-dc1">
       <img src="images/dc1.png" alt=".." />
       <figcaption>Using domain vocabularly with a Direct container.</figcaption>
+    <p class="issue">
+     The o:hasDoc relation is not defined and it is not clear what it adds in addition to ldp:contains. 
+     A distinction without a distinction is more confusing than not.
+    </p>
       Direct Containers can also use domain specific vocabulary and link from a resource other than the Container resource to the new resource.
@@ -358,6 +365,13 @@
       <img src="images/dc_photos.png" alt=".." />
       <figcaption>Membership triples with a non-Container subject.</figcaption>
+   <p class="issue">
+    Suggest replacing o:hasphoto with foaf:depiction since that relation is well known, and whose ontology can be looked up.
+    Also make the graph inside the document more meaningful: 
+    When an object that is not a document is being described show a document with a node ( a small circle ) inside the document to which external resources can point. 
+   So in the case of a person a node inside a document representing a person, perhaps with a relative 
+   URI &lt;#me&gt; would make this clearer.
+   </p>
       Different facets of a Resource can be managed using multiple Containers.
@@ -365,6 +379,11 @@
       <img src="images/dc_bugs.png" alt=".." />
       <figcaption>Managing multiple facets of a Bug with two Direct Containers.</figcaption>
+    <p class="issue">
+     A bug is different from a bug report: a Bug can be the same as another bug reported by someone else, even if the 
+bug reports are different, being created by different people at different times, with different histories.
+    Distinguish in the diagram the bug from the bug report.
+    </p>
       Existing applications with their own data model and business logic can expose their data using the LDP specification.
  These systems impose restrictions on LDPRs since the LDP interaction should be compliant with the underlying business logic and data model.