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

Re: How to find the members of an LDPC?

From: Eric Prud'hommeaux <eric@w3.org>
Date: Wed, 6 Nov 2013 17:53:28 -0500
To: "Wilde, Erik" <Erik.Wilde@emc.com>
Cc: Henry Story <henry.story@bblfish.net>, Steve K Speicher <sspeiche@gmail.com>, Alexandre Bertails <bertails@w3.org>, Linked Data Platform WG <public-ldp-wg@w3.org>
Message-ID: <20131106225327.GI25913@w3.org>
* Wilde, Erik <Erik.Wilde@emc.com> [2013-11-06 16:52-0500]
> On 2013-11-06, 12:20 , "Eric Prud'hommeaux" <eric@w3.org> wrote:
> >>> One would assume that the POST would return a 201-Created status
> >>>message and Location header of the URL for the new resource created.
> >>>The server may produce another triple to link the created resource
> >>>(LDPR), not sure what it might be:
> >> >     <> ex:describes <#>.
> >> 
> >> yes, the post returns a Location header. But that only allows the
> >>client that POSTed the
> >> resource to know the address of the LDPR created. It would be useful if
> >>other clients could
> >> also find that resource by asking the LDPC.
> >If an LDP client POSTs an appropriate RDF message to an LDP server, the
> >server creates a new resource and tells that client what the resource is.
> >What other clients would want to know about the newly created resource?
> >How would they even know it exists?
> 
> - by clients sharing URIs (bookmarks) of resources through whatever means?
> 
> - by clients listing collection contents and expecting a new resource
> being made availabel to them through a navigable link?

Yeah, the client shared it after getting it back from the server that
created the resource, or some other client interrogated the container
and found some member which matched some interesting properties.

The text I was replying to is included above: "But that only allows
the client that POSTed the resource to know the address of the LDPR
created. It would be useful if other clients could also find that
resource by asking the LDPC." This implies to me that some other
client is known to be interested in a resource as it is created.

What protocol does this imply? Is it that some client subscribes to
every new resource created by POST to a container? Is it that it has a
special pairing with the POSTing client but the POSTing client won't
share the newly created resource?


> cheers,
> 
> dret.
> 

-- 
-ericP

office: +1.617.599.3509
mobile: +33.6.80.80.35.59

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.

There are subtle nuances encoded in font variation and clever layout
which can only be seen by printing this message on high-clay paper.
Received on Wednesday, 6 November 2013 22:53:59 UTC

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