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

Re: ldp-ISSUE-38 (filtering, inlining): filtered representations and inlining [Linked Data Platform core]

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Tue, 20 Nov 2012 13:15:46 -0500
Message-ID: <50ABC8D2.8050908@openlinksw.com>
To: public-ldp-wg@w3.org
On 11/20/12 12:57 PM, Wilde, Erik wrote:
>> >The ldp: vocabulary already provides a way to expose the relation
>> >between the two LDPRs, using ldp:membershipSubject and
>> >ldp:membershipPredicate. What else is needed?
> sorry, i don't quite follow you here. there has to be some way how a
> client knows that composing the URI /bugs?inline=bugs:has_bug is a
> sensible thing to do, right? how would it know that, without
> knowing/finding rules how to do that?

Once the first step is made re. accepting that this is achieved via RDF. 
We can then look into relations that make URI templates visible.

Until we accept what we are doing, we won't be able to talk about 
discovery patterns in a coherent way. An RDF graph can also describe 
discovery patterns such that a client or a server can figure out URL 
patterns for specific interactions. This is beyond mime, its language 
understood by machines, since the entity relationship semantics are 
machine comprehensible, due to their first-order logic underpinnings.

Simple URL pattern discovery example, using XRD (just another notation 
for representing and entity relationship graph):



Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen

Received on Tuesday, 20 November 2012 18:16:15 UTC

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