Author: jakob
Date: Wed Nov 12 12:54:37 2014
New Revision: 1638777
URL: http://svn.apache.org/r1638777
Log:
Updated LDP documentation in the Marmotta Webpage
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=1638777&r1=1638776&r2=1638777&view=diff
==============================================================================
--- marmotta/site/trunk/content/markdown/platform/ldp-module.md (original)
+++ marmotta/site/trunk/content/markdown/platform/ldp-module.md Wed Nov 12
12:54:37 2014
@@ -6,16 +6,32 @@ Since 3.2.0 Marmotta [provides experimen
for the [current working draft](http://www.w3.org/TR/2014/WD-ldp-20140311/) of
the
[Linked Data Platform 1.0](http://www.w3.org/TR/ldp/) specification.
-The ASF activelly participares in the [W3C Working
Group](http://www.w3.org/2012/ldp) helping to define the
+For the (upcoming) 3.3.0 version, the LDP implementation has been updated to
the [last call working draft](http://www.w3.org/TR/2014/WD-ldp-20140916/)
+and a [official compliance
report](https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/reports/ldp.html#subj_8)
is available at the W3C.
+
+The ASF actively participates in the [W3C Working
Group](http://www.w3.org/2012/ldp) helping to define the
standard, and also providing an early implementation.
## Implementation Restrictions
The current LDP support should be *compliant* with the [current working
draft](http://www.w3.org/TR/2014/WD-ldp-20140311/),
-but *not complete* yet. For now there few [implementation
restrictions](http://wiki.apache.org/marmotta/LDPImplementationReport#Implementation_Restrictions),
-which will be addressed in upcoming releases.
+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.
-In addition, as soon as the test suite evolves, we'll provide formal
implementation reports.
+**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.
## Usage
@@ -24,11 +40,24 @@ would live together with LDP, here some
### Add a source resource to a container
+The LDP root container (located at `/ldp`) is created automatically. You can
add new resources using the following command:
+
curl -i -X POST -d @test.ttl -H "Content-Type: text/turtle" -H "Slug:
test" http://localhost:8080/ldp/container1
curl -i -H "Accept: text/turtle" http://localhost:8080/ldp/container1/test
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
+say so in the `POST` request:
+
+ curl -i -X POST -d @test.ttl -H "Content-Type: text/turtle" -H "Slug:
resource" \
+ -H 'Link: <http://www.w3.org/ns/ldp#Resource>; rel="type"' \
+ http://localhost:8080/ldp/container1
+ curl -i -H "Accept: text/turtle"
http://localhost:8080/ldp/container1/resource
+
+Resources created with the *LDPR interaction model* cannot be used as
container and therefore do not accept `POST` requests.
+
### Add a binary resource to a container
curl -i -X POST --data-binary @test.png -H "Content-Type: image/png" -H
"Slug: test" http://localhost:8080/ldp/container2
@@ -38,3 +67,5 @@ where `test.ttl` contains the <abbr titl
where `test.png` is the <abbr title="LDP Non-RDF Source">LDP-NR</abbr> you
want to add to the `/container2` container.
+<abbr title="LDP Non-RDF Source">LDP-NR</abbr>s are always created using the
[*LDPR interaction
model*](http://www.w3.org/TR/2014/WD-ldp-20140916/#h5_ldpc-post-createrdf).
+
