W3C home > Mailing lists > Public > public-ldp-wg@w3.org > November 2012

Re: Creation of Containers

From: Jürgen Jakobitsch <j.jakobitsch@semantic-web.at>
Date: Thu, 08 Nov 2012 10:38:24 +0100
To: Niclas Hoyer <niclas@verbugt.de>
Cc: public-ldp-wg@w3.org
Message-ID: <1352367504.5275.24.camel@linux-1rgw.site>

for intro : my name is jürgen jakobitsch, i'm a software developer
mainly concerned with linked data applications. i'm the developer of
things like webIDRealm [1], tuqs [2] and one of the developers of skos
server poolparty [3]. a while ago i switched to linked data only
(besides some applications) with my own domain, an example resource can
be seen here [4]. a sample webpage based on that server can be seen here
[5], it is basically only javascript and sparql. back then i was
starting to implement the graph-store-protocol [6], but switched to
changesets only for manipulating data.

now just a short comment on LDPC :

this discussion looks a lot like => application development <= to me.
i'm pretty sure there's reason these containers came to be and i don't
want to confuse anybody or start discussions again, that long have been
dealt with, but wouldn't it be better when dealing with a spec to define
a way a ld-server can be extended? with my server i have the possibility
of what i call http-plugins that intercept http-requests and do
something. there are many ways this can be used, think of the following
http-plugins : 
- indexer-plugin (a http-plugin, that indexes data to a lucene index)
- monitoring-plugin (a http-plugin for, you guessed, does monitoring of
the most important resources)
- ping-back-plugin (sends ping-backs to interested parties about
resource-updates, you could for example subscribe to certain resources
and be notified if these change)

if there was a generic way of extending an ldp's behaviour in certain
situations, ldp-containers would just be one implementation of such an

just a thought...

wkr http://www.turnguard.com/turnguard

[1] http://webid.turnguard.com/WebIDTestServer/
[2] http://sourceforge.net/p/tuqs/wiki/Home/
[3] http://www.poolparty.biz/
[4] http://www.turnguard.com/turnguard
[5] http://business.turnguard.com/html/
[6] http://www.w3.org/TR/sparql11-http-rdf-update/

On Wed, 2012-11-07 at 22:38 +0100, Niclas Hoyer wrote:
> Hi,
> is there a simple way to create a ldp container? I thought of turning a 
> ldp resource into a container just by changing the rdf information, so 
> if http://example.org/resource1 is a ldp resource the following HTTP 
> request could turn the resource into a container:
> PUT /resource1 HTTP/1.1
> Host: example.org
> Content-Type: text/turtle
> Content-Length: 188
> @prefix dcterms: <http://purl.org/dc/terms/>.
> @prefix ldp: <http://www.w3.org/ns/ldp#>.
> <http://example.org/resource1>
>      a ldp:Container ;
>      dcterms:title "A new empty container" .
> Should we cover this in an extra use case?
> A possible implementation could just start with a ldp resource. The user 
> or client programs could create containers as they need them. I was 
> thinking of a sioc:Thread that could also be a ldp:Container, so that 
> other clients could reply on the thread easily.
> --
> Niclas

| Jürgen Jakobitsch, 
| Software Developer
| Semantic Web Company GmbH
| Mariahilfer Straße 70 / Neubaugasse 1, Top 8
| A - 1070 Wien, Austria
| Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22

| web       : http://www.semantic-web.at/
| foaf      : http://company.semantic-web.at/person/juergen_jakobitsch
| web       : http://www.turnguard.com
| foaf      : http://www.turnguard.com/turnguard
| g+        : https://plus.google.com/111233759991616358206/posts
| skype     : jakobitsch-punkt
| xmlns:tg  = "http://www.turnguard.com/turnguard#"

Received on Thursday, 8 November 2012 09:38:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:33 UTC