You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@marmotta.apache.org by ja...@apache.org on 2014/11/12 14:54:43 UTC

svn commit: r1638791 - /marmotta/site/trunk/content/markdown/platform/ldp-module.md

Author: jakob
Date: Wed Nov 12 13:54:43 2014
New Revision: 1638791

URL: http://svn.apache.org/r1638791
Log:
some more ldp documentation

Modified:
    marmotta/site/trunk/content/markdown/platform/ldp-module.md

Modified: marmotta/site/trunk/content/markdown/platform/ldp-module.md
URL: http://svn.apache.org/viewvc/marmotta/site/trunk/content/markdown/platform/ldp-module.md?rev=1638791&r1=1638790&r2=1638791&view=diff
==============================================================================
--- marmotta/site/trunk/content/markdown/platform/ldp-module.md (original)
+++ marmotta/site/trunk/content/markdown/platform/ldp-module.md Wed Nov 12 13:54:43 2014
@@ -18,20 +18,19 @@ The current LDP support should be *compl
 but not yet *complete*. For now there are a few [implementation restrictions](http://wiki.apache.org/marmotta/LDPImplementationReport#Implementation_Restrictions),
 which will be addressed in future releases:
 
-Currently, Marmotta only supports <abbr title="LDP Basic Containers">LDP-BC</abbr> as containers, <abbr title="LDP Direct Containers">LDP-DC</abbr>
-and <abbr title="LDP Indirect Containers">LDP-IC</abbr> will be discussed for further development.
-<abbr title="LDP Non-RDF Source">LDP-NR</abbr>s are fully supported.
-
-LDP allows a server to ignore *server-managed* properties of a <abbr title="LDP RDF Source">LDP-RS</abbr>. Currently (3.3.0), the following
-properties are considered as *server-managed*:
-
- * <abbr title="http://www.w3.org/ns/ldp#contains">ldp:contains</abbr>
-
-This list may be extended for future versions.
+* Currently, Marmotta only supports <abbr title="LDP Basic Containers">LDP-BC</abbr> as containers, <abbr title="LDP Direct Containers">LDP-DC</abbr>
+    and <abbr title="LDP Indirect Containers">LDP-IC</abbr> will be discussed for further development.
+    <abbr title="LDP Non-RDF Source">LDP-NR</abbr>s are fully supported.
+* LDP allows a server to ignore *server-managed* properties of a <abbr title="LDP RDF Source">LDP-RS</abbr>. Currently (3.3.0), the following
+    properties are considered as *server-managed*. This list may be extended in future versions:
+    * <abbr title="http://www.w3.org/ns/ldp#contains">ldp:contains</abbr>
+* All resources created using a `Content-Type` that is not recognized as *RDF Format* are treated as <abbr title="LDP Non-RDF Source">LDP-NR</abbr>.
+    The list of supported *RDF Formats* is provided in the `Accept-Post` header.
 
 **WARNING:** Changing <abbr title="LDP Resource">LDPR</abbr>s through other channels than the LDP Server (e.g. *SPARQL UPDATE*)
 may cause an inconsistent and corrupt resource state.
-In its current implementation, LDP is designed as **exclusive** (write-)access method for <abbr title="LDP Resource">LDPR</abbr>s.
+In its current implementation, LDP is designed as **exclusive** (write-)access method for <abbr title="LDP Resource">LDPR</abbr>s and 
+<abbr title="LDP Container">LDPC</abbr>s.
 
 ## Usage
 
@@ -48,7 +47,7 @@ The LDP root container (located at `/ldp
 where `test.ttl` contains the <abbr title="LDP RDF Source">LDP-RS</abbr> you want to add to the `/container1` container.
 
 By default, all created <abbr title="LDP RDF Source">LDP-RS</abbr>s are created using the [*LDPC interaction model*](http://www.w3.org/TR/2014/WD-ldp-20140916/#h5_ldpc-post-createrdf), 
-which means that they also act as Container. If you want to create a resource using the *LDPR interaction model* you need to explicitly
+which means that they also act as <abbr title="LDP Container">LDPC</abbr>. If you want to create a resource using the *LDPR interaction model* you need to explicitly
 say so in the `POST` request:
 
     curl -i -X POST -d @test.ttl -H "Content-Type: text/turtle" -H "Slug: resource" \