- From: Timothy Cole <t-cole3@illinois.edu>
- Date: Tue, 2 Jun 2015 17:25:35 -0500
- To: "'Web Annotation'" <public-annotation@w3.org>
- Message-ID: <06a401d09d83$0ce2a140$26a7e3c0$@illinois.edu>
The LDP 1.0 Primer (http://www.w3.org/TR/ldp-primer/, Editor’s draft dated today) gives an example of how to create a new basic container inside an existing basic container (modified from example 6 in section 2.3):
In Turtle and assuming the parent container is http://example.org/containerA/
POST containerA/ HTTP/1.1
Host: example.org
Content-Type: text/turtle
Link: <http://www.w3.org/ns/ldp/BasicContainer>; rel="type"
Slug: timsAnnos
@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
<> a ldp:Container, ldp:BasicContainer;
dcterms:title "Tim’s Annotations" ;
dcterms:description "This container will contain Annotations created by Tim." .
This should result in a new child basic container, http://example.org/containerA/timsAnnos/
The key, according to the text accompanying the original example in the Primer is the inclusion of the Link: <http://www.w3.org/ns/ldp/BasicContainer>; rel="type" header. Following this logic, if I want to make sure that the new container is understood by the LDP Server to be a container for annotations, should I also include an additional link in the Post request Link header? i.e.:
POST containerA/ HTTP/1.1
Host: example.org
Content-Type: text/turtle
Link: <http://www.w3.org/ns/ldp/BasicContainer>; rel="type",
<http://www.w3.org/TR/annotation-protocol/constraints>; rel="http://www.w3.org/ns/ldp#constrainedBy"
Slug: timsAnnos
@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
<> a ldp:Container, ldp:BasicContainer;
dcterms:title "Tim’s Annotations" ;
dcterms:description "This container will contain Annotations created by Tim." .
Apologies if this is dealt with somewhere in the Protocol draft and I missed it.
Thanks,
Tim Cole
Received on Tuesday, 2 June 2015 22:26:07 UTC