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

Re: LDP service discovery.

From: Andrei SAMBRA <andrei.sambra@gmail.com>
Date: Wed, 14 Nov 2012 10:59:08 -0500
Message-ID: <CAFG79eiZW01a=pDARaKJhjRDS6X1j19ciFcJhtv7NO0U8NnrWw@mail.gmail.com>
Cc: public-ldp-wg@w3.org
Yes, I believe ldp:endPoint is what I'm interested in. I can give you the
following use case:

I run my own personal data space, which in the end is basically an
LDP-enabled server. When I got application X, I want it to be able to
read/write data directly to/from my data space. To do this, the application
X can simply lookup my FOAF profile (WebID) to find out where it needs to
connect to. You can further generalize this concept and apply it each time
there are two applications trying to connect to one another.


On Wed, Nov 14, 2012 at 10:20 AM, Steve K Speicher <sspeiche@us.ibm.com>wrote:

> > From: Andrei SAMBRA <andrei.sambra@gmail.com>
> > To: public-ldp-wg@w3.org,
> > Date: 11/12/2012 05:09 PM
> > Subject: LDP service discovery.
> >
> > Hello all,
> >
> > I've been thinking a lot recently about bootstrapping LDP, so I went
> looking
> > at the LDP ontology and I couldn't find any mention of the concept of an
> > endpoint. Wouldn't it be useful to have some sort of ldp:Seed or
> > ldp:Endpoint class which can then be used in the process of discovery
> (by
> > adding it to a user's FOAF card)? In this case, when a user
> authenticates
> > (say using WebID) to a service, the service will immediately know where
> it
> > can potentially store user data.
> >
> > Is this something worth opening an action for, or would you consider it
> just
> > something that should be part of the "use cases and requirements" wiki
> page?
> >
> > Best,
> > Andrei
> I did a quick check to see if there was anything explicitly but not sure
> ISSUE-7 covers it completely and it is being proposed to be closed saying
> it is covered by new issues.
> The process to insert new use cases is to open an issue assigned the
> product to the UC&R.
> I think one way to position the question or use case, such as:
> Determining from a URI whether it is a LDPC.
> Does this cover your case or do you expect to have to have "more" data
> about the LDP server?  If more data is needed, then what use case is
> motivating this from the client?
> It almost feels like we could solve your case by simply introducing a
> predicate that other vocabularies could insert into their models, such as
> ldp:container or ldp:endPoint.
> Thanks,
> Steve Speicher
> IBM Rational Software
> OSLC - Lifecycle integration inspired by the web ->
> http://open-services.net
Received on Wednesday, 14 November 2012 16:02:20 UTC

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